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,
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
I think it is just softlinked. Do you not have past versions here:
~ chuck$ ls /System/Library/Frameworks/JavaVM.framework/Versions/
1.3 1.3.1 1.4 1.4.2 1.5
1.5.0 1.6 1.6.0 A Current
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
Hi Greg,
You mean LaunchDeamons folder right?
It may not be your issue though.
I'd use the wiki page about deployment and check each points.
Do you have wotaskd running on port 1085?
Xavier
On 1 juil. 2013, at 21:09, Greg Lappen g...@lapcominc.com wrote:
Hello,
We have a WebObjects app
Hi Greg,
can you start WOMonitor manually? Try to execute
/System/Library/WebObjects/JavaApplications/JavaMonitor.woa/JavaMonitor
(if you are using the original Apple WOMonitor, or the one from Wonder wherever
you've installed it)
Does the log (defined in your LaunchDaemon's
Hi
We have exactly the same problem: some Apple updates were applied yesterday on
a client's Snow Leopard server (I don't know exactly what), and now wotaskd and
JavaMonitor won't start automatically. We got the kCGErrorFailure message at
one point: now I just see 'Exited with exit code (1)'.
Thanks for the info Liz. I did what you said, but when the monitor page
opens in the browser and I try to start my app, it never starts. Nothing
relevant appears in the log files :(
On Mon, Jul 1, 2013 at 5:20 PM, Elizabeth Lynch l...@plsys.co.uk wrote:
Hi
We have exactly the same problem:
Hi Greg,
On 1 Jul 2013, at 23:36, Greg Lappen wrote:
Thanks for the info Liz. I did what you said, but when the monitor page
opens in the browser and I try to start my app, it never starts. Nothing
relevant appears in the log files :(
Check the application permissions, especially the
Change the default JVM to an earlier version.
On 2013-07-01, at 2:40 PM, Bogdan Zlatanov wrote:
Hi Greg,
On 1 Jul 2013, at 23:36, Greg Lappen wrote:
Thanks for the info Liz. I did what you said, but when the monitor page
opens in the browser and I try to start my app, it never starts.
Hi Greg
The executable needs to be owned by appserver:appserveradm, so do something
like:
cd /Library/WebServer/Applications
chown -R appserver:appserveradm MyApp
and then see if it will start via Monitor.
LIz
On 1 Jul 2013, at 22:40, Bogdan Zlatanov
Hi
I have followed gsbr...@umich.edu 's suggestion of installing the Wonder
wotaskd and JavaMonitor, and this has solved the problem on our client's server.
You can download these from the jenkins site at:
http://jenkins.wocommunity.org/job/Wonder/lastSuccessfulBuild
After copying
How does one do that? I like this solution as it will put us back exactly
where we were before the update, just not sure how to do it as it looks
like we only have one version of the JDK on there: 1.6.0_51_b11-457. It
looks like the update from Apple overwrote the old JDK 1.6.0 with the new
one
13 matches
Mail list logo
