Vivek, The Apache SOAP client software *can* maintain sessions by storing a cookie sent from the server, then sending that cookie with subsequent requests to the same server. For this to work, the client must have the maintenance of session state enabled (which it is by default), and it must keep using the same SOAPHTTPConnection (since that is where sessions are "remembered"). Since you are seeing the timeouts, I suspect that client requests are not sending the cookie (and therefore become part of their own session). Have you looked at the messages on the wire to confirm that the cookie is being included?
On 14 Jan 2003 at 11:16, Dandekar, Vivek wrote: > Hi Everybody, > > We have set <session-timeout> 30 </session-timeout> in web.xml of soap > > context under tomcat 4.1.18. The problem is sessions are timing out > > exactly after 30 minutes even if we send transactions after initial SOAP > > session was established. Scope of Web service deployed is session. > > Basically lasttimeAccessed is not changing even if we access our > > webservice class using StandardSessionManager... > > > > Any ideas on how we can call access() method every time a new request is > > received so that SOAP session will not timeout on 30 minutes but it will > > time-out based on last accessed time+30 minutes. We put a <listner-class> > > in web.xml but it gets notified exactly after 30 minutes since session was > > created... > > > Is it necessary to write our own SessionManager that will set > lastAccessedtime every time we access the webservice class? > > > Environment: Linux 7.3/Tomcat 4.1.8/soap.war ... > > > > Thanking you in advance. Any help would be appreciated.. > > > > Vivek. > > > > > This e-mail message is for the sole use of the intended recipient(s) and may > contain confidential and privileged information of Transaction Network > Services. Any unauthorized review, use, disclosure or distribution is > prohibited. If you are not the intended recipient, please contact the > sender by reply e-mail and destroy all copies of the original message. > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > This e-mail message is for the sole use of the intended recipient(s) and may > contain confidential and privileged information of Transaction Network > Services. Any unauthorized review, use, disclosure or distribution is > prohibited. If you are not the intended recipient, please contact the > sender by reply e-mail and destroy all copies of the original message. > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > Scott Nichol -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
