| Author |
java.lang.IllegalStateException: WEB3424: createSession: Too many active sessions
|
tina garg
Greenhorn
Joined: Feb 04, 2011
Posts: 1
|
|
I am getting below exception in logs and when and how is coming i have no clue.Server is weblogic
java.lang.IllegalStateException: WEB3424: createSession: Too many active sessions
at org.apache.catalina.session.StandardManager.createSession(StandardManager.java:343)
at org.apache.catalina.connector.HttpRequestBase.doGetSession(HttpRequestBase.java:1369)
at org.apache.catalina.connector.HttpRequestBase.getSession(HttpRequestBase.java:1325)
at org.apache.catalina.connector.HttpRequestFacade.getSession(HttpRequestFacade.java:214)
at org.apache.catalina.connector.HttpRequestFacade.getSession(HttpRequestFacade.java:224)
at org.apache.jasper.runtime.PageContextImpl._initialize(PageContextImpl.java:138)
at org.apache.jasper.runtime.PageContextImpl.initialize(PageContextImpl.java:114)
at org.apache.jasper.runtime.JspFactoryImpl.internalGetPageContext(JspFactoryImpl.java:181)
at org.apache.jasper.runtime.JspFactoryImpl.getPageContext(JspFactoryImpl.java:154)
at _jsps._portalunavailable_jsp._jspService(_portalunavailable_jsp.java:52)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
at com.iplanet.ias.web.jsp.JspServlet$JspServletWrapper.service(JspServlet.java:687)
at com.iplanet.ias.web.jsp.JspServlet.serviceJspFile(JspServlet.java:459)
at com.iplanet.ias.web.jsp.JspServlet.service(JspServlet.java:375)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:771)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:322)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:218)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:209)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:157)
at com.iplanet.ias.web.WebContainer.service(WebContainer.java:579)
|
 |
Sunny Bhandari
Ranch Hand
Joined: Dec 06, 2010
Posts: 446
|
|
A quick Google search shows me this:
Limiting HTTP Sessions
An administrator can limit the number of active HTTP sessions based on detection of a low-memory condition. This is useful in avoiding out of memory exceptions.
WebLogic Server refuses requests that create new HTTP sessions after the configured threshold has been reached. In a WebLogic Server cluster, the proxy plug-in redirects a refused request to another Managed Server in the cluster. A non-clustered server instance can re-direct requests to alternative server instance.
The servlet container takes one of the following actions when maximum number of sessions is reached:
If the server instance is in a cluster, a 503 response is sent back. The behavior after this response is sent is determined by your load balancer or proxy server.
You set a limit for the number of simultaneous HTTP sessions in the deployment descriptor for the Web Application. For example, the following element sets a limit of 12 sessions:
<session-descriptor> <max-in-memory-sessions>12</max-in-memory-sessions> </session-descriptor>
|
 |
 |
|
|
subject: java.lang.IllegalStateException: WEB3424: createSession: Too many active sessions
|
|
|