ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 34516] - Java ant task crashes JVM if not forked
Date Tue, 19 Apr 2005 10:48:55 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34516>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34516





------- Additional Comments From stevel@apache.org  2005-04-19 12:48 -------
Sergey,

I dont think this is something we can handle. JNI code means that native
libraries are loading, and if there is something wrong there, then the JVM is
formally toast. Note also that JNI libs are outside what classloaders get up to;
if a DLL is loaded in one classloader, that is the only lib instance that is
loaded into that process, for the duration of that JVM. If tests are loading and
unloading things, I can imagine stuff getting confused.

My recommendation is fork, dont worry about the possible performance hit. That
way you can also be sure that different tests run with new DLLs loaded. There is
also some JVM system property you can set to point to the library location; no
need to copy the library into the PATH.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message