On Apr 16, 2009, at 12:20 PM, Mark Ritchie wrote:
On 16-Apr-09, at 2:54 PM, Chuck Hill wrote:
You might also be thinking of this (unrelated) section in
/System/Library/WebObjects/Adaptors/Apache2.2/apache.conf
# To enable the WOAdaptorInfo page with restricted access,
# uncomment the next two lines and set the user and password
# To access the WOAdaptorInfo page with restricted access,
# use a URL like: http://webserver/cgi-bin/WebObjects/WOAdaptorInfo?user+password
.
# WebObjectsAdminUsername user
# WebObjectsAdminPassword password
Hey Chuck!
That's a good point! Perhaps Frank is mixing them up? Either way,
enabling the WOAdaptorInfo page and turning on adaptor logging are
vital to tracking down why it's not working! For example, on that
solaris problem with Apache2 and Apache2.2, turned out that
Apache2.2 required fqdn for the app servers where as Apache2 did
not. Weird shit but then there were multiple virtual hosts and
external vs internal addresses so were lots of opportunity for
confusion. It was resolved by looking at the adaptor logs which
clearly show'd the problem.
That gives me a headache just reading it. :-) I agree completely:
knowing how to enable and interpret the adaptor logs is central to
sorting out any problem like this.
Chuck
Regards,
M.
__
Mark Ritchie
Cocoa and WebObjects Developer
Diamond Lake Consulting Inc.
Toronto, Ontario, Canada
--
Chuck Hill Senior Consultant / VP Development
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-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
