Re: Wonder JavaMonitor
Re: Wonder JavaMonitor
- Subject: Re: Wonder JavaMonitor
- From: Chuck Hill <email@hidden>
- Date: Fri, 10 Jun 2011 19:10:35 -0700
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.
Chuck
--
Chuck Hill Senior Consultant / VP Development
Come to WOWODC this July for unparalleled WO learning opportunities and real peer to peer problem solving! Network, socialize, and enjoy a great cosmopolitan city. See you there! http://www.wocommunity.org/wowodc11/
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden