Hi Mary Ann, Which version of ULC are you using?
Which license are you using? The evaluation license is limited to 5 concurrent connections per Web container context. See http://www.canoo.com/ulc/products/licmodel.html. Coming back to your question: The server side session timeout that is specified in the web.xml is in minutes. E.g. value of 30 means 30 minutes. The keep alive interval specification to the ULC Client is in seconds. E.g. value of 900 means 900 seconds = 15 minutes. The client will send a keep alive request to the ULC servlet after every keep-alive-interval seconds. To prevent session time out in case of no activity, keep-alive-interval should be less than the session time out. About your error messages: I can answer this after I know which license and which version of ULC are you using. Thanks and regards, Janak -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mary Ann Pigora ARA/CFD Sent: Thursday, August 09, 2007 10:54 PM To: [EMAIL PROTECTED] Subject: [ULC-developer] keep-alive and session timeout Hi, I am load testing my ULC applet . After the sixth client connects, I get: com.ulcjava.base.client.ConnectorException: could not send requests to server . Caused by: com.ulcjava.container.servlet.client.ConnectorCommandException: unsupported HTTP response code: 500 (Internal Server Error) . The server side log says: javax.servlet.ServletException: unable to get ulc session (session already terminated) The ULC deployment guide says "the session timeout of the web application must be configured to be compatible with the.client configuration (eg using keep-alive requests)", but there are no details about what the compatibility is. An archived post on this subject indicated that the client timeout needed to be less than the keep-alive, which seems counter-intuitive to me. I am using the default tomcat session timeout (30 minutes) and keep-alive-interval of 900 (which the manual says is in seconds). Can anyone tell me if these numbers are compatible? If so, what else might be causing this exception? Client error and server side log is below. Thanks, Mary Ann Client error: com.ulcjava.base.client.ConnectorException: could not send requests to server at com.ulcjava.container.servlet.client.ServletConnector.sendRequests(ServletCo nnector.java:34) at com.ulcjava.base.client.UISession$k_.run(UISession$k_.java:71) at java.lang.Thread.run(Unknown Source) Caused by: com.ulcjava.container.servlet.client.ConnectorCommandException: unsupported HTTP response code: 500 (Internal Server Error) at com.ulcjava.container.servlet.client.ConnectorCommand.handleResponse(Connect orCommand.java:24) at com.ulcjava.container.servlet.client.ConnectorCommand.execute(ConnectorComma nd.java:9) at com.ulcjava.container.servlet.client.ServletConnector.executeCommand(Servlet Connector.java:84) at com.ulcjava.container.servlet.client.ServletConnector.sendRequests(ServletCo nnector.java:33) at com.ulcjava.base.client.UISession$k_.run(UISession$k_.java:71) at java.lang.Thread.run(Unknown Source) Server log error (repeated many times): ERROR: [09.08.07 12:14:45 PM] org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/emst].[EMSTA pplet] - Servlet.service() for servlet EMSTApplet threw exception javax.servlet.ServletException: unable to get ulc session (session already terminated) at com.ulcjava.container.servlet.server.ContainerCommand.getUlcSession(Containe rCommand.java:13) at com.ulcjava.container.servlet.server.RemoveSessionCommand.handleRequestConte nt(RemoveSessionCommand.java:6) at com.ulcjava.container.servlet.server.ContainerCommand.execute(ContainerComma nd.java:32) at com.ulcjava.container.servlet.server.ServletContainerAdapterHelper.b(Servlet ContainerAdapterHelper.java:147) at com.ulcjava.container.servlet.server.ServletContainerAdapterHelper.service(S ervletContainerAdapterHelper.java:121) at com.ulcjava.container.servlet.server.ServletContainerAdapter.service(Servlet ContainerAdapter.java:5) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126 ) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105 ) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:425) at org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler.process(AjpAprProt ocol.java:452) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1285) at java.lang.Thread.run(Unknown Source) _______________________________________________ ULC-developer mailing list [email protected] http://lists.canoo.com/mailman/listinfo/ulc-developer
