Why would native code in a java process fail - but only if started by wotaskd?
Why would native code in a java process fail - but only if started by wotaskd?
- Subject: Why would native code in a java process fail - but only if started by wotaskd?
- From: Hugi Thordarson <email@hidden>
- Date: Thu, 20 Aug 2009 15:40:31 +0000
OK, a little brain teaser.
I have a WO server - a G4 Mac Mini running current Leopard/Java 5, WO
5.4, PWO nightly etc. - all in all, a pretty up to date environment.
If I restart this WO server, all applications will run fine
immediately afterwards. However, if I stop/start an application in
JavaMonitor, code that calls native code stops functioning. DNS-
lookups, some AWT-stuff, some functionality that uses javax.crypto -
all will fail with various exceptions. The only common denominator
I've found is that failure happens when the app attempts to run native
code.
But. If I run the application from the CLI, everything functions as
expected.
In both cases, applications are running as "root" so permission
problems seem implausible.
This one's got me stumped, so - any ideas?
Cheers,
- Hugi
// Hugi Thordarson
// http://hugi.karlmenn.is/
_______________________________________________
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