• 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: javamonitor and wotaskd won't start after os x updates
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: javamonitor and wotaskd won't start after os x updates

  • Subject: Re: javamonitor and wotaskd won't start after os x updates
  • From: G Brown <email@hidden>
  • Date: Sat, 13 Jul 2013 18:22:04 -0400
Good info.

I think the applications here:

http://jenkins.wocommunity.org/job/Wonder/

do have some bug fixes relative to the apple ones, and they have additional features; so I guess I am happy(?)  I was forced to try the Wonder versions?


Differences between Apple's and Wonder's versions of the deployment tools

wotaskd and JavaMonitor were released by Apple to the community as open source when WebObjects 5.4 was released in 2007. 

They were added to Wonder and improvements and bug fixes were made to the tools. We strongly suggest that you use the Wonder Versions.


http://wiki.wocommunity.org/display/documentation/Wonder+JavaMonitor+and+wotaskd


But its nice to know the apple ones still work.


G Brown
email@hidden




On Jul 13, 2013, at 2:02 PM, Bogdan Zlatanov wrote:

Hi Greg, et al,

I don't know if this is still an issue for you, but after hitting the exact same problem on a Snow Leopard Server after updates, a colleague of mine and I decided to pass -Djava.awt.headless=true to wotaskd and javamonitor and it solved the issues for us. 

Just for reference, we put the parameter in the com.apple.webobjects.wo*.plist so now it looks like this:

<key>ProgramArguments</key>
<array>
<string>wotaskd</string>
+ <string>-Djava.awt.headless=true</string>
 <string>-WOPort</string>
<string>1085</string>
</array> 

HTH,

Bogdan

On 1 Jul 2013, at 21:09, Greg Lappen wrote:

Hello,

We have a WebObjects app running on a Snow Leopard Server.  Some OS X updates were applied recently, and now WebObjects javamontor, wotaskd, and hence our app are not starting up.

I saw this error in /var/log/system.log:

Suspicious setup: User "appserver" maps to user: _appserver

I modified the LaunchAgent plist files so that the user and group name now have dashes in front of them and reloaded the files into launchd with launchctl.  The error I see now is this:

 kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.

This seems like some issue with java not being able to connect to the window server, but I was not able to find any solutions.  Does this look familiar to anyone?

Much thanks,

Greg
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: 
 >javamonitor and wotaskd won't start after os x updates (From: Greg Lappen <email@hidden>)
 >Re: javamonitor and wotaskd won't start after os x updates (From: Bogdan Zlatanov <email@hidden>)

  • Prev by Date: Re: javamonitor and wotaskd won't start after os x updates
  • Next by Date: Re: Create dynamic AjaxTabbedPanelTab in AjaxTabbedPanel with WORepetion
  • Previous by thread: Re: javamonitor and wotaskd won't start after os x updates
  • Next by thread: Re: Broken Javamonitor and wotaskd apps and builds.
  • Index(es):
    • Date
    • Thread