On Jun 10, 2011, at 7:10 PM, Chuck Hill wrote: On Jun 10, 2011, at 7:07 PM, Klaus Berkling wrote: On Jun 10, 2011, at 5:43 PM, Chuck Hill wrote: There are some security checks around the IP address. See WOHostUtilities in Wonder for what is probably the fix for your problem:
* <p>This class replaces the WebObjects version to support loading a new IP as a local IP to the local hosts list. * This will authorize that IP to send management requests, like stopping the application, or * turning on the refuse new instance setting. This is necessary if WO does not automatically * add the needed IP to the local host list. It happens when you use private IPs and * is recognized as a problem on multi-homed linux servers.</p>
Thanks. This sounds a lot like my issue (now why did I not find the thread...).
I added this line:
er.extensions.WOHostUtilities.localhostips=(10.0.0.20,192.168.10.96)
The 10... address is private, the 192... address is 'public.'
No luck. Is er.extensions.WOHostUtilities already used in wonder's JavaMonitor or do I need to add it?
That property is for the app, not JavaMonitor. It tells the app that it is OK to obey admin actions from that address.
Ha ha ha. I had added it to wotaskd for the same reason, wotaskd being the 'app'. I also added it to our app for good measure. I'm laughing because, if our app were a Wonder app, this would be trivial, but it's not so ... sigh. I will revisit this later then.... I'll (ab)use a HelloWorld app.
Time to go home. Thanks Chuck!!
kib
"We keep moving forward, opening new doors, and doing new things, because we're curious and curiosity keeps leading us down new paths." Walt Disney
Klaus Berkling Web Application Dev. & Systems Analyst DynEd International, Inc.
|