Re: Weird JavaMonitor wotaskd behavior on Snow Leopard
Re: Weird JavaMonitor wotaskd behavior on Snow Leopard
- Subject: Re: Weird JavaMonitor wotaskd behavior on Snow Leopard
- From: Tusker <email@hidden>
- Date: Wed, 28 Jul 2010 21:57:54 -0700
On Jul 28, 2010, at 8:59 PM, Chuck Hill wrote:
On Jul 28, 2010, at 6:14 PM, Tusker wrote:
WARN NSLog - Unable to establish a connection to port 2001 on
this host. Perhaps this port is already in use by another
WebObjects application instance.
Jul 28 18:04:59 testpp[N/A] (ERXNSLogLog4jBridge.java:43) WARN
NSLog - <WOApplication>: Cannot be
initialized.java.lang.reflect.InvocationTargetException
Jul 28 18:04:59 testpp[N/A] (ERXNSLogLog4jBridge.java:43) WARN
NSLog - A fatal exception occurred: <WOApplication>: Cannot be
initialized.
[2010-7-28 18:4:59 PDT] <main>
com.webobjects.foundation.NSForwardException
I looked at the SpawnofWotaskd.log further:
Something even more weird further up in the logs
Jul 28 18:04:59 N/A[N/A] (ERXNSLogLog4jBridge.java:43) WARN NSLog
- WOApplication Error: Failed to rename previously existing
WOOutputPath file: /Library/WebObjects/Logs/testpp-1
.....
Jul 28 18:04:59 N/A[N/A] (ERXNSLogLog4jBridge.java:46) DEBUG NSLog
- WOAdaptorURL=http://localhost/cgi-bin/WebObjects
....
Jul 28 18:04:59 N/A[N/A] (ERXNSLogLog4jBridge.java:46) DEBUG NSLog
- com.webobjects.pid = 3140
I set the HTTP Adaptor to my other server in JavaMonitor, not
localhost. Is WOAdaptorURL set correctly above.
I prefer it to have a FQDN for deployment boxes.
Well, that what I did. I entered the FQDN for my server where the
WOAdaptor sits. I did this in JavaMonitor. But WOAdaptorURL still
points to http://localhost/cgi-bin/WebObjects in the logs.
Could this be the problem?
The pid that I see in the activity monitor that starts is not 3140,
it's 3120?
That is probably just the process stopping after "Cannot be
initialized" and wotaskd re-launching it. Or something else has
started another copy of it. I think I have seen the case where
wotaskd and the app did not agree on WOHost and so wotaskd thought
it did not launch and so kept trying to start it. You might be
seeing that. JavaMonitor won't report it as running until it starts
responding to direct JavaMonitor requests (/womp/ urls)... IIRC.
I'm still unclear on how to set WOHost. I'll try this again next.
Chuck
On Jul 28, 2010, at 6:01 PM, Mark Ritchie wrote:
On 28/Jul/2010, at 5:43 PM, Tusker wrote:
When I hit the start button in JavaMonitor for the application I
see a process start but JavaMonitor reports it as not starting.
What's logged in SpawnofWotaskd.log?
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
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