Hi Joshua,

To supplement what Chuck said, and as I have had the same problem, you
may need to edit /etc/hosts which must match what there is in your Hosts
JavaMonitor tab.
Technicaly in the hostname columm you have the host.domain and the ip so
in /etc/hosts you should have a line which looks like : ip  host.domain
host (or ip host.domain host2.domaine2  host host2 if your server have
several dns names).

For example if you added the host myserv.mydomain.com in JavaMonitor
the /etc/hosts should be :
127.0.0.1   myserv.mydomain.com localhost.localdomain localhost myserv
aaa.bbb.ccc.ddd myserv.mydomain.com myserv
(Localhost must already be defined correctly in /etc/hosts)


Aurelien


Chuck Hill wrote:
> Hi Joshua,
> 
> This can happen if wotaskd is not running or if wotaskd, the woadaptor,
> and JavaMonitor don't agree on the host name.  First, check that wotaskd
> is running:
> 
> sudo lsof -i tcp:1085
> 
> You are looking for a line like
> java    199 root    6u  IPv6 0x025eff38      0t0  TCP
> [::127.0.0.1]:webobjects (LISTEN)
> 
> If that is running,
> sudo touch /tmp/logWebObjects
> make a few requests to the application, and then look in
> /tmp/WebObjects.log to see what host name it is referring to and for any
> useful error messages.
> 
> Finally, look in JavaMonitor to see what the configured host name is. 
> If you want to try to force host name consistency (I have to running in
> dev mode so that I can use localhost), then edit
> /System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/Resources/Properties
> and add a line like this (using the correct host name):
> WOHost=localhost
> 
> When you do this, you will also need to edit
> /System/Library/WebObjects/Adaptors/Apache/apache.conf and edit the
> WebObjectsConfig line so that it uses the same host name that wotaskd does.
> 
> 
> HTH
> Chuck
> 
> 
> 
> On Sep 26, 2006, at 11:23 AM, Joshua Archer wrote:
> 
>> Hey everyone,
>>
>> I seem to be having a weird issue with my WebObjects instance and I
>> thought I'd float it by the group to see if there's something that
>> seems obvious. The problem started showing up after our system admin
>> performed a system update on the box, including the Security update
>> 2006-005, quicktime 7.1.3, and itunes 7x (for completeness).
>> Basically, I can't access my running apps through the adaptor (port 80
>> just tells me that the the requested application is not available),
>> but if I go directly to the application (port 2001), it comes up fine.
>> Could the security update have changed some firewall setting, or made
>> some tweak that would cause this to occur? I'm not even sure how to
>> fix the problem, so I thought I'd ask the collective wisdom of the group.
>>
>> Thanks,
>>
>> Joshua

-- 
Aurélien Minet
Univerisité René Descartes
Direction des Systemes d'Information

 _______________________________________________
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 archive@mail-archive.com

Reply via email to