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=27555>. 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=27555 DOM call via JNI Invocation can crash calling program [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Additional Comments From [EMAIL PROTECTED] 2004-03-19 19:29 ------- Well if multiple threads from the application which uses your plug-in causes concurrent access to the virtual machine (I assume you only create one instance with the JNI Invocation API) and if you're only accessing one instance of the DOM in that virtual machine then you're going to run into this problem. I've only observed it when multiple threads attempt to concurrently read NodeLists from the same DOM even when all the NodeLists being traversed are unique. There's a caching mechanism which was added to improve performance of iterative lookups to NodeLists. Every time you read, it writes something back and potentially fetches or returns the cache to a pool. Collisions in the pool or when simultaneously reading from and writing to the cache will cause NullPointerExceptions. See the discussion on bug #27454 about thread-safety. I'm marking this as a duplicate because I believe you're seeing this behaviour for the same reason. If you disagree, please reopen with more information. *** This bug has been marked as a duplicate of 27454 *** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
