Re: WebObjects web service server stops responding at ~250 calls. Pourquoi???
Re: WebObjects web service server stops responding at ~250 calls. Pourquoi???
- Subject: Re: WebObjects web service server stops responding at ~250 calls. Pourquoi???
- From: Chuck Hill <email@hidden>
- Date: Fri, 27 May 2005 14:04:48 -0700
Have you tried getting a thread dump from the application when it stops
responding? That might show something. Also put log messages in
Application.dispatchRequest and in your code so you can try and
determine where it stops.
Chuck
On May 27, 2005, at 1:57 PM, Garrett Snider wrote:
Update: I installed a deployment license to get rid of the 100 per
minute question. It chugs along happily for 250 calls and then the
web service just stops responding. Any other ideas? Has anyone
done stress testing on Apple's Web Services via Web Objects?
tks,
-g
On May 27, 2005, at 10:50 AM, Garrett Snider wrote:
I'm going to try the deployment license, but I had already throttled
it, with the same result. It's also a synchronous test case running,
so the queue shouldn't build up.
-g
On May 26, 2005, at 5:17 PM, Alan Ward wrote:
my guess is that (since you keep sending requests) the stalled request
handling causes the
queue to start filling. Once you hit the max queue size you'll start
getting bad responses.
Either throttle your requests to 100 per minute or get a deployment
license.
On May 26, 2005, at 3:06 PM, Garrett Snider wrote:
Context: I'm using simple service calls (like an echo web service)
and using the WSMakeStubs tool, ala the Calculator web services
example
(http://developer.apple.com/documentation/WebObjects/Web_Services/
index.html#//apple_ref/doc/uid/TP30001019).
The web service simply stops regarding the client as someone worthy of
doing business after a certain number of calls. No console errors, no
server error messages, nothing that I can find.
Now, I don't see any server setting that would affect this, though it
easy to imagine that such a setting exists somewhere. The license is
also a developer license and seems to be the source of some throttling
behavior of the server (see my additional notes below)
Any ideas out there in WebObjects land?
Thanks for the help.
-garrett
--- additional notes regarding this:
the client will chug along and hit the server about 200 times (the
exact number varies) at which point the server will throttle the
action w/ this message:
<WorkerThread3> MTA: Worker Object[3]: request limit hit: stalling
and wait about 3-4 seconds and then resume.
(This seems to be a liscence limitation, as rec'd this log message
just now.)
[2005-05-26 11:43:44 EDT] <WorkerThread7> Exceeded license request
limit - request processing temporarily stalled. RequestLimit = 100
TPM]. This message appears only once.
[2005-05-26 11:43:44 EDT] <WorkerThread7> MTA: Worker Object[7]:
request limit hit: stalling
The client contunies to send messages up until the 250th message
(exact, each time) at which point the server will send back bad data
(null values, or something similar).
Again: This problem happens consistently and always at the 250th
message.
(For the 'echo' service, it happens consistently at the 222nd call)
_______________________________________________
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
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
village.net
This email sent to email@hidden
--
Practical WebObjects - a book for intermediate WebObjects developers
who want to increase their overall knowledge of WebObjects, or those
who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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