Le 07-03-03 à 09:47, James Cicenia a écrit :
I am so confused with this JavaMonitor and this particular
application.
I have had JavaMonitor running on my browser all day personally
monitoring it.
Well eventually, JavaMonitor seems to die because of one instance
going awry. This
means that the number of sessions, transactions, then never update
and I get the red
message on top that says Failed to contact ....
We had this problem too. It seems that when wotaskd has some problem
talking to a freaked-out instance, all other instances and Monitor
will have problems talking to wotaskd, and you get those errors in
Monitor.
We were able to actually confirm this by looking at the number of
opened sockets to wotaskd (sudo lsof -P | grep 1085), if one of your
apps has more than 5 connections opened to port 1085, you can find
that this instance is almost dead and is slowing wotaskd down.
Like you did, simply killing the problematic instance resolve the
problem.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [email protected]
