• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Applications respond "Access Denied" to wotaskd
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Applications respond "Access Denied" to wotaskd


  • Subject: Re: Applications respond "Access Denied" to wotaskd
  • From: Jeremy Rosenberg <email@hidden>
  • Date: Mon, 3 Nov 2008 14:31:55 -0800

Direct Connect was explicitly disabled, so I think that meant it was enabled. But it doesn't seem to matter whether I specifically enable or disable it in WOMonitor. I know if I don't explicitly disable it in our other installation it won't permit me to refuse new sessions. But it still will accept a hard terminate.

The password lines in the apache.conf are commented out.

I'm not seeing anything in any log files. I tried trussing the output of the actual application itself but I can't see anything unusual (like a file being opened or something) between the request to terminate and the access denied response.

We do package up our apps with all the WebObjects dependencies right in the application's Resources/Java library so that we don't have to install any WebObjects or Wonder libraries on the server. This allows us to update some applications to new versions without touching others. I started to wonder if the problem might be that there are .jars missing from the server that the application needs to handle this stuff. I tried adding WOMonitorSupport to the application classpath in case it needed it, but that didn't help. We are using WebObjects 5.3 and Wonder 5-5.3 (I grabbed the WOMonitorSupport jar from WO 5.4)

Jeremy


On Nov 3, 2008, at 12:43 PM, Chuck Hill wrote:


On Nov 3, 2008, at 12:26 PM, Jeremy Rosenberg wrote:

Hi List

We are trying to set up a new server, we have JavaMonitor running on the web server with the apache connector and wotaskd running on the app server.

JavaMonitor starts up applications just fine via the web interface. But when we try to stop an app via the JavaMonitor interface (either by clicking the red button or turning refuse new sessions on) nothing happens.

I trussed the wotaskd process on the app server and found that it is receiving the message to "STOP" from JavaMonitor and then using womp/instanceRequest to tell the application process to "TERMINATE" or "REFUSE" but the application seems to be replying with "NO" and "Access Denied" as the error message.

Is this making sense to anyone? What kind of permission is the application looking for? I'm not terribly proficient with truss so I might be misinterpreting what I am seeing.


Is Direct Connect disabled?

Look in  /System/Library/WebObjects/Adaptors/Apache/apache.conf

Are any passwords set?

Chuck


-- 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@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Applications respond "Access Denied" to wotaskd (From: Jeremy Rosenberg <email@hidden>)
 >Re: Applications respond "Access Denied" to wotaskd (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: Setting up horizontal inheritance
  • Next by Date: Re: Setting up horizontal inheritance
  • Previous by thread: Re: Applications respond "Access Denied" to wotaskd
  • Next by thread: EOFetchSpecification that locks objects like 'SELECT FOR UPDATE NO WAIT'
  • Index(es):
    • Date
    • Thread