Hi Mary Ann, >I am using a developer license, and ULC version 6.1.
Just to make sure: 1. The deployment license on the path of the ULC servlet running in your app server (tomcat?) is not an evaluation license. 2. You are using ULC 6.1 and not later versions like ULC 6.1.3. >usage on the machine was low. The ceiling on the number of clients >seems to go up when I have the clients spread across several machines. So now you are able to connects more than 6 clients to the same ULC Application servlet but all these clients are running on different desktops. Is this correct. >Is there more of a network bottleneck on the client side? Can't say because I don't know your configuration. I can open number of (over 10) ULC clients in the same browser with the ULC application running in Tomcat on the same machine. Thanks and regards, Janak >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Mary Ann Pigora >ARA/CFD >Sent: Monday, August 13, 2007 4:13 PM >To: [EMAIL PROTECTED] >Subject: RE: [ULC-developer] keep-alive and session timeout > > > >Hi Janak, > >I am using a developer license, and ULC version 6.1. > >I was testing with multiple clients on one machine, but memory and cpu >usage on the machine was low. The ceiling on the number of clients >seems to go up when I have the clients spread across several machines. >Is there more of a network bottleneck on the client side? > >Thanks, >Mary Ann > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Janak Mulani >Sent: Monday, August 13, 2007 5:52 AM >To: [EMAIL PROTECTED] >Subject: RE: [ULC-developer] keep-alive and session timeout > >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(Servl >etCo >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(Con >nect >orCommand.java:24) > at >com.ulcjava.container.servlet.client.ConnectorCommand.execute(ConnectorC >omma >nd.java:9) > at >com.ulcjava.container.servlet.client.ServletConnector.executeCommand(Ser >vlet >Connector.java:84) > at >com.ulcjava.container.servlet.client.ServletConnector.sendRequests(Servl >etCo >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].[E >MSTA >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(Cont >aine >rCommand.java:13) > at >com.ulcjava.container.servlet.server.RemoveSessionCommand.handleRequestC >onte >nt(RemoveSessionCommand.java:6) > at >com.ulcjava.container.servlet.server.ContainerCommand.execute(ContainerC >omma >nd.java:32) > at >com.ulcjava.container.servlet.server.ServletContainerAdapterHelper.b(Ser >vlet >ContainerAdapterHelper.java:147) > at >com.ulcjava.container.servlet.server.ServletContainerAdapterHelper.servi >ce(S >ervletContainerAdapterHelper.java:121) > at >com.ulcjava.container.servlet.server.ServletContainerAdapter.service(Ser >vlet >ContainerAdapter.java:5) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at >org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica >tion >FilterChain.java:252) > at >org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt >erCh >ain.java:173) > at >org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv >e.ja >va:213) > at >org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv >e.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:1 >48) > at >org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:425) > at >org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler.process(AjpApr >Prot >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 >_______________________________________________ >ULC-developer mailing list >[email protected] >http://lists.canoo.com/mailman/listinfo/ulc-developer _______________________________________________ ULC-developer mailing list [email protected] http://lists.canoo.com/mailman/listinfo/ulc-developer
