Re: WOAdaptor build and test
Re: WOAdaptor build and test
- Subject: Re: WOAdaptor build and test
- From: Patrick Middleton <email@hidden>
- Date: Tue, 12 Apr 2016 14:04:29 +0000
- Thread-topic: WOAdaptor build and test
On 12/04/2016 12:48, "webobjects-dev-bounces+pmiddleton=email@hidden on behalf of Paul Yu" <webobjects-dev-bounces+pmiddleton=email@hidden on behalf of email@hidden> wrote:
>Chuck
>
>If I have Apache 2.4 running and I can access it, and I can access JavaMonitor and I can access WOTaskd, and when I tick ON in JavaMonitor I can tail -f App-1 and see the app initializing then can I assume that mod_WebObjects is working?
>
>The app is dying at Migration but that’s not what I’m testing right now…
>
>Paul
I suggest you would be better off using the techniques documented in the administrator's notes in the apache.conf file in the project for the adaptor you've built and installed;
"Note: To enable logging, touch '/tmp/logWebObjects' as the administrator user (usually root)."
and also the stuff about the WOAdaptorInfo page. The WOAdaptorInfo page is generally not helpful when it's getting its configuration by polling wotaskd and you don't have any apps running cleanly, but, being able to see it at all is a hint that mod_WebObjects is working. (mod_WebObjects is nothing to do with launching or managing application instances; it's about being able to connect to them indirectly via Apache.)
One of my techniques for deployment is to get my app instances configured and running, use Monitor to get the XMLConfigDoc, save that to disk, then reconfigure the WOAdaptor to use that ('File Configuration') instead of polling wotaskd ('Host List Configuration'), because then access to my applications is not lost if/when wotaskd hangs.
-- Patrick
_______________________________________________
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