Re: WebService or Session Timeout
Re: WebService or Session Timeout
- Subject: Re: WebService or Session Timeout
- From: Chuck Hill <email@hidden>
- Date: Tue, 05 Oct 2004 22:22:18 -0700
Gerald,
>From your description, I will guess that you were using Direct Connect when
in development mode. This is one of the reasons I often rail/rant against
Direct Connect as a dangerous crutch. Things that work, or work in a
certain way, no longer do once the application is deployed. Anguish and
gnashing of teeth result. But enough about me.
I've never seen this with a web service, but I am assuming it is the same
problem. When the adaptor receives a request it connects to the
application, sends the request, and waits for the response. Each of these
three steps has a timeout. If the timeout expires, the request is sent to
another instances if there is one. While nice in theory, this only works
for sessionless (or session independent) direct actions. Component actions
sent to a different instance produce the dreaded session expired error.
OK, that is not quite true. If you have implemented distributed sessions
then it would work, but implementing that is a tad problematic. Best not
go down that path. Once the request has been bounced through all available
instances, the result is the no instance available error.
OK, so what to do? The best solution is to make your processing fast
enough that the timeouts are not exceeded. The next option is to increase
the connect and receive timeouts in JavaMonitor. I've not found the send
timeout to ever be a problem. The WOLongResponsePage is often suggested
for use in this situation with browser requests. I don't know what the
parallel is for web services.
Hope that was of some use.
Chuck
At 05:06 PM 05/10/2004 -0600, Gerald Hanks wrote:
>I have an interesting problem. I have an application that uses a
>webservice to retrieve pdf documents to be sent to my users. I have a
>page that has a couple of buttons on it that the user can click on to
>receive one of two pdfs. Clicking on either button causes the
>webservice to retrieve the pdf into an NSData object which is stored as
>a global variable in the page holding the buttons. After retrieving
>the pdf the method returns null. I overrode the appendToReponse method
>to see if there was pdf data waiting to be sent and if so it changes
>the content type and puts the pdf content into the response.
>
>This all works wonderfully on my dev box. I can retrieve pdf after pdf
>with no problems at all. When I deploy the application I run into
>problems. I am only able to retrieve one or two pdf documents before
>every response ends in a session expired page or an error page telling
>me that there is no instance available. I can simply click the back
>button and refresh the page or browse to another page in my app to see
>that my application is active as well as the session. Does anyone have
>any advice or direction that I may take in trying to debug this
>problem?
>
>--gerald
>
> _______________________________________________
>Do not post admin requests to the list. They will be ignored.
>Webobjects-dev mailing list (email@hidden)
>Help/Unsubscribe/Update your Subscription:
e.net
>
>This email sent to email@hidden
>
--
Chuck Hill email@hidden
Global Village Consulting Inc. http://www.global-village.net
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden