/usr/sbin/ipconfig waitall is already part of the default startup
script for wotaskd and JavaMonitor but it didn't work on Snow Leopard
for some reason.
Did some more research and seems like using the Network Reachability
Framework API can be used for this and other launchd Daemons.
Turns out that it was the launchd launch daemon. It was starting
wotaskd and JavaMonitor before setting up the network for the machine
resulting in weird behavior. Adding sleep 15 to the wotaskd and
JavaMonitor init script solved the problem. I'm looking into a better
way of doing
We had a similar problem with Tomcat starting before network was
ready. We solved the problem by putting
/usr/sbin/ipconfig waitall
in the tomcat startup script. This might help here, and be a bit more
reliable than just sleeping for 15 seconds.
Tim
On 03/08/2010, at 9:22 AM, Tusker
I thought that was fixed since 10.5something
On Aug 2, 2010, at 4:22 PM, Tusker wrote:
Turns out that it was the launchd launch daemon. It was starting wotaskd and
JavaMonitor before setting up the network for the machine resulting in weird
behavior. Adding sleep 15 to the wotaskd and
I'm still unclear on how to set WOHost. I'll try this again next.
open this file:
/System/Library/WebObjects/JavaApplications/JavaMonitor.woa/Contents/Resources/Properties
and add
WOHost=whateverhostyouwant.com
and do the same for
On 28/Jul/2010, at 9:53 PM, Tusker wrote:
Both look normal
drwxrwxr-x 25 _appserver _appserveradm 850 Jul 28 18:04
/Library/WebObjects/Logs/
db1p:Logs admin$ ls -lard /Library/WebObjects/Logs/testapp-1
-rw-r--r-- 1 _appserver _appserveradm 1385 Jul 28 18:05
On Jul 28, 2010, at 9:57 PM, Tusker wrote:
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:
On 28/Jul/2010, at 9:57 PM, Tusker wrote:
I'm still unclear on how to set WOHost. I'll try this again next.
For wotaskd and JavaMonitor, I usually set the WOHost in their respective
launchd config files.
Something like: /Library/LaunchDaemons/com.apple.webobjects.wotaskd.plist
and
We have seen this behaviour intermittently (1 in 20 restarts) when
restarting OS X 10.5 XServes. Our solution has been to restart them
again. Sounds like your problem is more than intermittent so this may
not work for you.
Another solution to a similar problem is to deactivate the
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
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
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
Hi
On 07/28/2010 07:54 PM, 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
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
Le 2010-07-28 à 19:29, Tusker a écrit :
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
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.
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
On Jul 28, 2010, at 4:34 PM, Pascal Robert wrote:
Le 2010-07-28 à 19:29, Tusker a écrit :
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
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.
On 28/Jul/2010, at 4:29 PM, Tusker wrote:
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
I'm using the DNS domain which resolves to the IP of the machine. I
just got the DNS setup today in reverse as well. I was using
the .local address before.
On Jul 28, 2010, at 4:43 PM, Chuck Hill wrote:
What are you using for the host name? It needs to DNS resolve to
primary IP of this
On Jul 28, 2010, at 5:10 PM, Tusker wrote:
I'm using the DNS domain which resolves to the IP of the machine. I just got
the DNS setup today in reverse as well. I was using the .local address
before.
This is a fun puzzle! See below.
On Jul 28, 2010, at 4:43 PM, Chuck Hill wrote:
Looks fine to me. Here is the output from term before I hit the start
application button:
sh-3.2# ps auxwww | grep 2001
root 2443 0.0 0.0 2435036580 s000 R+5:31PM 0:00.00
grep 2001
sh-3.2# sudo lsof -i tcp:2001
sh-3.2#
sh-3.2#
sh-3.2# sudo lsof -i tcp:2001
sh-3.2# sudo
java2532 _appserver 80u IPv6 0xff80350ce760 0t0 TCP
[::xx.xxx.xxx.71]:49639-[::xx.xxx.xxx.71]:webobjects (ESTABLISHED)
So that line shows that wotaskd and the instance are talking to each other, so
I guess the problem lies in JavaMonitor.
Do :
ps auxwww | grep 56789
ps
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?
___
Do not post admin requests to the
I'm not using the default Javamonitor port. I'm using 57913.
db1p:~ admin$ ps auxwww | grep 57913
_appserver76 0.0 0.5 3024004 113680 ?? Ss4:19PM
0:07.48 /usr/bin/java -XX:NewSize=2m -Xmx64m -Xms32m -
DWORootDirectory=/System -DWOLocalRootDirectory= -DWOUserDirectory=/ -
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
Do you have multiple IPs on this server? Check also in /var/log/system.log for
DNS warnings.
I'm not using the default Javamonitor port. I'm using 57913.
db1p:~ admin$ ps auxwww | grep 57913
_appserver76 0.0 0.5 3024004 113680 ?? Ss4:19PM 0:07.48
/usr/bin/java
Hey!
On 28/Jul/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 -
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:
On Jul 28, 2010, at 6:34 PM, Mark Ritchie wrote:
Hey!
On 28/Jul/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]
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]
31 matches
Mail list logo
