Re: Adaptor problems in Eclipse. No Instance Available
Re: Adaptor problems in Eclipse. No Instance Available
- Subject: Re: Adaptor problems in Eclipse. No Instance Available
- From: Art Isbell <email@hidden>
- Date: Wed, 2 Apr 2008 11:12:08 -1000
On Apr 2, 2008, at 9:56 AM, Helmut Schottmüller wrote:
since a few hours my WO httpd adaptor seems to be broken. I'm
getting getting constant "No Instance Available" messages when I am
trying to run my projects with webserver connect from Eclipse.
If a "No instance available" response occurs after 30 seconds, the
default timeout to receive a response from an instance, then the
instance is taking more than 30 seconds to process the request. This
is usually due to database activity. Frequently, lots of faults are
firing resulting in many one-object fetches (batch fetch). Or maybe
there are fetches on huge DB tables without good indexes (add
indexes). Or maybe fetches involve huge many-table joins.
If you can't fix the performance problem, then you can increase the
HTTP adaptor's receive timeout. I don't know how to do this in Web
server connect mode during development. I have worked around my
ignorance by configuring an instance of this app using JavaMonitor,
increasing the receive timeout for this app in JavaMonitor, and then
launching from Eclipse with the "-WOPort <port>" launch argument in
which <port> is the port of the instance that JavaMonitor assigned.
This will allow the HTTP adaptor to get the receive timeout setting
for the process listening on this port from the SiteConfig.xml file.
If a "No instance available" response occurs almost immediately, then
something else is wrong. I don't know what that "something else"
might be.
Aloha,
Art
_______________________________________________
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