StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15161968
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-03-01T16:09:40.870
FavoriteCount
0
LastActivityDate
2013-03-01T16:09:40.870
LastEditDate
LastEditorUserId
0
OwnerUserId
775715
ParentId
15160222
PostTypeId
2
Score
10
ViewCount
0
LastEditorDisplayName
text
Body
The support for Sesssion.setIdleTimeout(long ms) was added recently to support JSR-356 (javax.websocket) work we are currently doing. However, with 9.0.0.RC2 you can do the following to set idle timeout early, before the Session is created (this is being fixed, hopefully will make it into RC3) Server Side option A: WebSocketServlet init-param In your <code>WEB-INF/web.xml</code> for your websocket servlet, specify the following init-param <pre class="lang-xml prettyprint-override"><code><init-param> <param-name>maxIdleTime</param-name> <param-value>10000</param-value> </init-param> </code></pre> Server Side option B: As policy change on WebSocketFactory In your WebSocketServlet.configure(WebSocketServletFactory factory) call <pre class="lang-java prettyprint-override"><code>@Override public void configure(WebSocketServletFactory factory) { factory.getPolicy().setIdleTimeout(10000); } </code></pre> Client Side option A: As WebSocketClient setting <pre class="lang-java prettyprint-override"><code>WebSocketClient client = new WebSocketClient(); client.getPolicy().setIdleTimeout(10000); client.start(); </code></pre> Annotated @WebSocket option This will work for server or client websockets. Note: you cannot mix WebSocketListener and @WebSocket annotations together <pre class="lang-java prettyprint-override"><code>import org.eclipse.jetty.websocket.api.Session; import org.eclipse.jetty.websocket.api.annotations.OnWebSocketClose; import org.eclipse.jetty.websocket.api.annotations.OnWebSocketConnect; import org.eclipse.jetty.websocket.api.annotations.OnWebSocketError; import org.eclipse.jetty.websocket.api.annotations.OnWebSocketMessage; import org.eclipse.jetty.websocket.api.annotations.WebSocket; @WebSocket(maxIdleTime=10000) public class MySocket { @OnWebSocketClose public void onClose(int statusCode, String reason) { } @OnWebSocketConnect public void onConnect(Session sess) { } @OnWebSocketError public void onError(Throwable cause) { } @OnWebSocketMessage public void onText(String message) { } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POJetty 9 RC2 websocket timeout
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJoakim Erdfelt
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POJetty 9 RC2 websocket timeout
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COSession.setIdleTimeout(ms) issue filed as bug at https://bugs.eclipse.org/402154
 singulars
 PostPostId
 PO
 UserUserId
 USJoakim Erdfelt
2. CONice, thanks...
 singulars
 PostPostId
 PO
 UserUserId
 USfso

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.