Q: I used WOMonitor to open an application on another host. The messages on the other machine indicate that the process is running, but Monitor says it is not. How can I make Monitor report the application status correctly?
A: This problem occurs when more than one copy of WOMonitor is running on a subnet. The MonitorProxy process on your application server uses Apple's Distributed Objects technology to find and connect to an instance of WOMonitor. If more than one instance of WOMonitor is started on a subnet, a race condition is created, and the WOMonitor instance which responds first is the only one that receives notifications.
You can avoid this problem by specifying the host to which you wish MonitorProxy to report. When you launch MonitorProxy on your application server, use the syntax:
MonitorProxy -mhost monitor_hostname
MonitorProxy will then only try to connect to a Monitor process running on the specified host. If you are not sure to which Monitor process your application is connecting, MonitorProxy will report the hostname whenever a connection is made. Even if no hostname is specified, MonitorProxy will only look for WOMonitor processes within its own subnet.
You can also use the -mhost argument while starting your WebObjects application manually. Any processes you start from within Monitor will have their -mhost argument set automatically.