We finally solved this problem.
This particular server was running a web service app in Tomcat that
when there was a web service request (web service SOAP message post)
on this app, it would make another request (web service SOAP message
post) on another page within the same web application on the same
virtual host. It appears that this "callback" scenario was causing
WebObjects to fail but only when Tomcat was restarted. The second
request was being performed via the SOAP with Attachments API for
Java (SAAJ). It must have been caused by a low-level network/socket
problem. Removing the "callback" request fixed the problem. We moved
the app and virtual host cname to another server and the problem
would follow the app and cname. If we had the web service app on two
servers but the second request from each was going to the server with
virtual host cname, then webobjects would fail on the server with the
virtual host cname.
Restarting WebObjects or the server did not fix the problem once it
had begun happening. However, deactivating and the reactivating the
primary ethernet port on the server would get WebObjects working again.
Tim
On 22/07/2008, at 11:54 AM, D Tim Cummings wrote:
We have been getting "No Instance Available" from all our
WebObjects apps running on one of our OS X Server 10.5.4 servers,
but no problems on our other servers configured the same way. We
have Tomcat 5.5 installed on these servers using the Apple supplied
mod_jk.so. The WebObjects apps are wo5.3.3/wonder4 apps with
embedded frameworks deployed using the Apple supplied woadaptor and
wotaskd and javamonitor from wo5.4.2.
The "No Instance Available" problem will not show for several hours
and then suddenly it will start happening on most, but not all,
requests. Doing odd things such as turning on, or turning off
debugging enabled, or enabling WODirectConnect for the instances
seem to get them working again. We can reproduce starting the
problem by calling one of the WebObjects apps which in turn calls a
web service running in tomcat and then returns a response (in this
case a dynamically generated PDF file). When this web service in
tomcat is on the same server as the webobjects app calling it, the
problem starts.
We are currently working around the problem by moving the
webobjects app to a different server to the tomcat web service. If
anyone has any other ideas, please let me know.
The only other thing I can think that is unusual about our setup is
that we use multiple virtual hosts, a different one for each
webobjects app. So we can't use the same host name for the
webobjects apps and wotaskd, which apparently is a common cause of
"No Instance Available".
Cheers
Tim
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-
[EMAIL PROTECTED])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/timcu%
40tpg.com.au
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
