I checked the path, it's good. On the new Xserve running 10.4 server,
in apache.conf, the first active line is
LoadModule WebObjects_module /System/Library/WebObjects/Adaptors/
Apache/mod_WebObjects.so
I noticed that it is missing my other Xserve's (running 10.3 server)
second line next to that one
AddModule mod_WebObjects.c
But apparently that's common in all post 10.3 set ups (checked on
different machines running 10.4)
I feel like I should be more specific as to what the problem is:
JavaMonitor and wotaskd are both running (that's 100% confirmed), if I
launch my woa app from terminal, it works and loads fully (up to
Waiting for requests) and is usable, but when I try to launch via
JavaMonitor, it hangs for a while and dies (never actually working).
I just confirmed wotaskd is running as root.
WOAdaptor logging is still not working despite touching /tmp/
logWebObjects after doing the su command to run as root (I also
removed the # in front of WebObjectsLog /tmp/WebObjects.log Debug in
apache.conf; that's good, right? Rebooted several times).
I'm confused and I'm sure it's something minor I'm missing. Without
proper logging to fall back onto, I cannot troubleshoot efficiently.
Everything seems fine, it's just not working (localhost:1085 reports
wotaskd is running fine and it has all the good information, my
SiteConfig.xml file seems perfect, paths are good). I do not want to
waste anybody's time either, I was just hoping I was not alone having
trouble migrating from 10.3 server to 10.4 server and that some of you
guys encountered similar problems and had some fixes. I appreciate
your input and will be continuing to troubleshoot further.
Thank you all for your help.
Kind Regards,
Pascal
On 7-Dec-07, at 1:35 PM, Chuck Hill wrote:
On Dec 7, 2007, at 6:33 AM, Pascal Lamontagne wrote:
Hi guys,
We are struggling to get our applications running on Mac OS X
Server 10.4 with WebObjects 5.3 (latest updates) in our test local
environment. If we launch them manually from the terminal, they are
working. JavaMonitor and Wotaskd are running (confirmed) on default
ports (56789 and 1085 respectively).
Our host is good (Available YES) and permissions all seem fine
(Siteconfig.xml belongs to appserver:appserveradm). Our current
deployment setup is WO 5.2.3 on OS X Server 10.3.9 and everything
is configured the same way (aside from the obvious path differences
between 10.3 and 10.4).
I am unable to get any logging information from the typical sudo
touch /tmp/logWeObjects; no WebObjects.log file is ever generated
(worked fine in the 10.3 environment).
You want woadaptor logging, right? Not log messages from the
applications that wotaskd/JM launches?
A permissions problem seem unlikely on /tmp.
Check the path in /System/Library/WebObjects/Adaptors/Apache/
apache.conf
# Note: To enable logging, touch '/tmp/logWebObjects' as the
administrator user (usually root).
#
# The following line is the default:
# WebObjectsLog /tmp/WebObjects.log Debug
Any ideas on what could be different in 10.4 from 10.3 server?
Everything is default, apache.conf is set to localhost:1085 10 and
it is working in Mac OS X 10.4 with WO 5.3 on a non server on the
same local network (machine is off when we conduct tests obviously
not to cause issues with two JavaMonitors on the same subnet). The
only difference is one is Mac OS X 10.4 (working) and the other is
Mac OS X Server 10.4 (not working). I'm baffled!
I'd start with the above. Also check that you are really using
mod_webobjects and not the CGI adaptor. IIRC the apache.conf file
was missing a LoadModule or AddModule for mod_webobjects.
Chuck
--
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
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
