This just means that one or more instances were too slow in responding. Either they are busy or deadlocked.
There is an interesting patch to the Wonder version here: http://issues.objectstyle.org/jira/browse/WONDER-567 I have not looked at the details of this yet. Chuck On Aug 10, 2010, at 1:15 PM, Lon Varscsak wrote: > Every now and then, Monitor wigs out and displays the behavior in this > image ( http://grab.by/5PZb ). It complains it can't connect to > wotaskd (but all the running apps are fine), and all of the images are > broken. The direct image urls (that are fed through the monitor > applicatino) return "An Internal Server Error Has Occurred.". > > Eventually, without doing a thing it will clear itself up and work fine. > > Any ideas? Nothing on the server seems out of whack during these > times (load is good, memory is good, disk space is good, etc). > > Thanks, > > Lon > > P.S. -- Running WO 5.4.3 with the stock version of JavaMonitor. > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/chill%40global-village.net > > This email sent to [email protected] -- 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
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
