We did a test using Apache SOAP and Tomcat server. We set the session timeout to 15 minutes. We set number of sessions to 10 We set the scope of the deployed service to "Request"
We ran a client connecting 20 times and got "Null pointer" exceptions after the 10th call. The log indicted that we had run out of sessions. When we looked in the code, we saw that the session is never invalidated after the request completes (it should be invalidated in a finally block). This gives the effect of "Request" scope hanging around until the session times out. Since the apps set with "Request" scope can't be accesses, you have dead sessions hanging around until the session times out. We have modified the RPCRouterServlet class to invalidate session if the scope is "Request". When testing this by looking at the SOAP sessions from the manager/list servlet, the sessions no longer consumes all available sessions. Can a developer validate this assumption? Also, if it is an error, when might the code be patched and released. Is anyone else having this problem? And is this the right place to submit a bug/code change?? See attached code. <<RPCRouterServlet.java>>
RPCRouterServlet.java
Description: Binary data
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
