Re: Request Scope does not invalidate the session at the end of therequest, long-lived sessions hang until timeout causing out-of-sessions error.

idate the session at the end of therequest, long-lived sessions hang until timeout causing out-of-sessions error. > Hi Scott and all > > I am also deploying applications on top (routed by > MessageRouterServlet). It seems that, during our stress test, the > MessageRouterServl

[Fwd: Re: Request Scope does not invalidate the session at the end of therequest, long-lived sessions hang until timeout causing out-of-sessions error.]

Hi all I am also deploying applications on top (routed by MessageRouterServlet).  It seems that, during our stress test, the MessageRouterServlet is creating a lot of Session objects and exceeding the servlet container's limit. Since my 'application' can just run within the request and do

Client Timeout

In my java code:       Call oCall = new Call();       oResponse = oCall.invoke(url);   These rpcs usually last for 5 or more hours because it is doing some batch processing. But if the network connection is broken in the middle of the invocation, but the call will not return an exception, i

Re: Bug in timeout with SOAP to ssl socket

This patch has been made to CVS. On 31 Mar 2003 at 15:25, Paul G. Weiss wrote: > Hi. > > Sorry for the interruption. I joined the list to post a patch, because I > didn't know to whom to address it. > > If I call setTimeout on a Call where the url is an https url, it dies with > a NullPointe

Bug in timeout with SOAP to ssl socket

Hi. Sorry for the interruption. I joined the list to post a patch, because I didn't know to whom to address it. If I call setTimeout on a Call where the url is an https url, it dies with a NullPointerException. The problem is in SSLUtils.java. Change: sslSocket = (SSLSock

client timeout

procedure finishes, the soapserver causes an exception to be thrown because it cant send a response to the client. the client in turn does not know if the network is still alive, and waits forever for the server's response. i cant set Call's timeout because it might timeout too early, e

Re: Request Scope does not invalidate the session at the end of therequest, long-lived sessions hang until timeout causing out-of-sessions error.

ew nightly build. Scott Nichol - Original Message - From: "Pradhan, Chirag" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, July 30, 2002 5:58 PM Subject: Request Scope does not invalidate the session at the end of the request, long-lived sessions hang u

Re: Request Scope does not invalidate the session at the end of therequest, long-lived sessions hang until timeout causing out-of-sessions error.

, 2002 5:58 PM Subject: Request Scope does not invalidate the session at the end of the request, long-lived sessions hang until timeout causing out-of-sessions error. > We did a test using Apache SOAP and Tomcat server. > > We set the session timeout to 15 minutes. > We set number of se

Request Scope does not invalidate the session at the end of the request, long-lived sessions hang until timeout causing out-of-sessions error.

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

timeout

Hello every body, I am new in soap processing. I specified a timeout for my SOAP method invocation by using : ** SOAPHTTPConnection shc; shc = new SOAPHTTPConnection(); shc.setTimeout(5000); //<-- 5 seconds Call call = new Call(); call.setSOAPTransp

timeout

Hello every body, I am new in soap processing. I specified a timeout for my SOAP method invocation by using : ** SOAPHTTPConnection shc; shc = new SOAPHTTPConnection(); shc.setTimeout(5000); //<-- 5 seconds Call call = new Call(); call.setSOAPTransp

SOAP client timeout

Title: SOAP client timeout Hi, We are using SOAP client to access a web service. Our client works through VAJ on WIN 2000. The same code behaves unpredictably on unix. We tried runnig it through Websphere 3.5.3 and also as a stand alone java client. When we set timeout, it sometimes aborts