message "Failure to contact xserve2.local-1085"
message "Failure to contact xserve2.local-1085"
- Subject: message "Failure to contact xserve2.local-1085"
- From: Denis Stanton <email@hidden>
- Date: Tue, 16 Nov 2004 20:16:15 +1300
Can anyone tell me why we get this error message from JavaMonitor every few days on two busy servers?
If we got it immediately on startup I would understand. It would mean that we had not started wotaskd. We are getting this on two servers that are running wostaskd happily for some hours or days and then they hit this state. JavaMonitor is no longer able to report on the running instances.
If I try and start wotaskd after the error appears it responds with:
[2004-11-16 20:05:25 NZDT] <main> Unable to establish a connection to port 1085 on this host. Perhaps this port is already in use by another WebObjects application instance.
So if the system is configured well enough for wotasakd, womonitor and JavaMonitor to co-operate for hours or days, why does it stop responding, and if port 1085 cannot be reused because it is still in use why does the message indicate that it cannot be contacted?
All systems are Mac OS X 10.3.6 Server on XServe. WebObjects 5.2.3. The test server ( a G4, not an XServe, but still running OS X Server) doesn't do this, and come to think it another server didn't do it until we upgraded from an eMac to an XServe. I see no reason to blame the XServes, but then I don't know why this happens at all. As far as I know the only cure is to reboot the server although I guess it would be possible to figure identify and kill one or more processes and then start wotaksd again.
Denis Stanton
Denis Stanton
email@hidden
Home: +64 9 533 0391
mobile: +64 21 1433622 _______________________________________________
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