Re: JavaMonitor doesn't communicate with instance

On Oct 20, 2004, at 1:27 am, Karoly Szantai wrote:
> My deployment configuration is:
>
> XServe with MacOS X Server 10.2.8 and WO 5.1
> WOAppA: one instance on port 2001
> WOAppB: one instance on port 2002
>
> WOAppA is ok. I can start and stop this instance via JavaMonitor and I 
> see its statistics.
>
> I can start the instance of WOAppB, but I can't stop it via 
> JavaMonitor. Its transaction count and Active Session count on 
> JavaMonitor did not change. The instance is running without any 
> problem.
>
> It seems that JavaMonitor unable to communicate with the instance of 
> WOAppB.
>
I've seen this before, and I've always attributed it to a "too many 
open files" problem that existed until the most recent versions of 
WO/OSX.  Your best bet is to upgrade.  Short of that, killing the app 
and wotaskd (the app so that it gets "cleared", wotaskd because that is 
what is responsible for leaving too many files open) will help 
temporarily, until the next time there are too many open files...


sacha


-- 
Sacha Michel Mallais - 400 lb. chimp
Global Village Consulting Inc.:   http://www.global-village.net/
ObAd: read "Practical WebObjects" <fnord>
http://www.global-village.net/products/practical_webobjects