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: Pascal Robert <email@hidden>
- Date: Wed, 28 Jul 2010 19:53:50 -0400
Le 2010-07-28 à 19:43, Chuck Hill a écrit :
> What are you using for the host name? It needs to DNS resolve to primary IP of this machine. You can't use .local addresses.
And reverse DNS (IP -> name) have to work too.
> Chuck
>
>
> On Jul 28, 2010, at 4:29 PM, Tusker wrote:
>
>> No luck yet.
>>
>> I added WOHost in the additional args for the app in JavaMonitor and added it in launchd. I couldn't even get wotaskd to start with this argument. (see error below)
>>
>> Instead, I left wotaskd as is and changed the application host in JavaMonitor.
>>
>> The WOAdaptor is up and reporting the application running.
>> Javamonitor us up and running
>> Wotaskd is reporting all the configuration changes and I see the applications there as well.
>>
>> I can get to the following url:
>>
>> http://myappdomain:2001/test.woa/wa/
>>
>> but I can't get to
>>
>> http://mywebserverdomain/test.woa/wa
>>
>>
>>
>> I restart the server and try starting the application. This time, I get an error in the SpawnofWotaskd.log which makes no sense. It actually starts a application but JavaMonitor does not see it.
>> JavaMonitor reports a death. But I can get to http://myappdomain:2001/test.woa/wa/
>>
>>
>>
>>
>> Here are the Logs when I start application using JavaMonitor after a server restart.
>>
>> --------------------------------------------------------
>> Jul 28 16:21:55 contactme[N/A] (ERXNSLogLog4jBridge.java:43) 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 16:21:55 contactme[N/A] (ERXNSLogLog4jBridge.java:43) WARN NSLog - <WOApplication>: Cannot be initialized.java.lang.reflect.InvocationTargetException
>> Jul 28 16:21:55 contactme[N/A] (ERXNSLogLog4jBridge.java:43) WARN NSLog - A fatal exception occurred: <WOApplication>: Cannot be initialized.
>> -------------------------------------------------------
>>
>>
>>
>>
>>
>> wotaskd error when adding WOHost:
>>
>> [2010-7-28 13:39:31 PDT] <main> WebObjects version = 5.4.3
>> [2010-7-28 13:39:31 PDT] <main> Unable to establish a connection to port 1085 on this host. Perhaps this port is already in use by another WebObjects application instance.
>> [2010-7-28 13:39:31 PDT] <main> A fatal exception occurred: <WOApplication>: Cannot be initialized.
>> [2010-7-28 13:39:31 PDT] <main> com.webobjects.foundation.NSForwardException [java.lang.reflect.InvocationTargetException] null:<WOApplication>: Cannot be initialized.
>> at com.webobjects.appserver.WOApplication.<init>(WOApplication.java:918)
>> at Application.<init>(Application.java:112)
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
>> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
>> at java.lang.Class.newInstance0(Class.java:355)
>> at java.lang.Class.newInstance(Class.java:308)
>> at com.webobjects.appserver.WOApplication.main(WOApplication.java:547)
>> at Application.main(Application.java:61)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at com.webobjects._bootstrap.WOBootstrap.main(WOBootstrap.java:87)
>> Caused by: java.lang.reflect.InvocationTargetException
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
>> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
>> at com.webobjects.foundation._NSUtilities.instantiateObject(_NSUtilities.java:614)
>> at com.webobjects.appserver.WOApplication.adaptorWithName(WOApplication.java:1316)
>> at com.webobjects.appserver.WOApplication._initAdaptors(WOApplication.java:1386)
>> at com.webobjects.appserver.WOApplication.<init>(WOApplication.java:802)
>> ... 14 more
>> Caused by: com.webobjects.foundation.NSForwardException [java.net.BindException] Can't assign requested address:java.net.BindException: Can't assign requested address
>> at com.webobjects.foundation.NSForwardException._runtimeExceptionForThrowable(NSForwardException.java:41)
>> at com.webobjects.appserver._private.WOClassicAdaptor._initServerSocket(WOClassicAdaptor.java:230)
>> at com.webobjects.appserver._private.WOClassicAdaptor.<init>(WOClassicAdaptor.java:163)
>> at com.webobjects.appserver._private.WOClassicAdaptor.<init>(WOClassicAdaptor.java:171)
>> ... 22 more
>> Caused by: java.net.BindException: Can't assign requested address
>> at java.net.PlainSocketImpl.socketBind(Native Method)
>> at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:365)
>> at java.net.ServerSocket.bind(ServerSocket.java:319)
>> at java.net.ServerSocket.<init>(ServerSocket.java:185)
>> at com.webobjects.appserver._private.WOClassicAdaptor._initServerSocket(WOClassicAdaptor.java:223)
>> ... 24 more
>>
>>
>>
>> On Jul 28, 2010, at 11:54 AM, Simon wrote:
>>
>>> i recently had the misfortune of having to set up a snow leopard deployment and ran into similar problems. remember there are 3 golden URL's to diagnosing deployment issues:
>>>
>>> http://yourdomain/cgi-bin/WebObjects/WOAdaptorInfo
>>> http://yourdomain:1085 // assuming you are running wotaskd on standard port
>>> http://yourdomain:56789 // assuming you are running javamonitor on standard port
>>>
>>> if we ever have deployment issues these are my first 3 ports of call. in particular, make sure the first two are both reporting your running instances. with our snow leopard issues we could see running instance in the wotaskd config, but the WOAdaptorInfo page was reporting nothing ... bingo.
>>>
>>> simon
>>>
>>> On 28 July 2010 19:05, Chuck Hill <email@hidden> wrote:
>>> Use the hostname of the app server in JavaMonitor as the host and also set this in the Properties file with WOHost=.... for the app and wotaskd. Or set WOHost in the additional args for the app in Java Monitor and in the launchd config for wotaskd.
>>>
>>> Did that help?
>>>
>>>
>>> Chuck
>>>
>>> On Jul 28, 2010, at 10:54 AM, Tusker wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm seeing some very bizarre things with javamonitor and wotaskd. I have new clean Snow Leopard servers. I have a 3 machine setup. 1 Websever, 1 Application server (Javamonitor, wotaskd) and 1 database server. I followed the following instructions (http://wiki.objectstyle.org/confluence/display/WO/Programming__WebObjects-Web+Applications-Deployment-Mac+OS+X+Server).
>>>>
>>>> I can initially start up wotaskd and javamonitor. I setup host and my test application using Javamonitor. I can start up my test application fine. Everything works fine, but as soon as I restart the server, I can't start the application that I just setup. Both the wotaskd and javamonitor process start up and I can see them in the Activity Monitor. I modified SpawnOfWotaskd.sh to capture the logs when I hit go. Initially, I see these logs. When I restart the server, these stop as well.
>>>>
>>>> I tried adding -_DeploymentDebugging true to the plist but it will not output the debugging level logs.
>>>>
>>>> Any clues?
>>>>
>>>> Thanks,
>>>> M
>>>
>>>
>>> --
>>> 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
>>>
>>
>
> --
> 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
_______________________________________________
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