DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21522>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21522 NullPointerException doing "new SAXParser()" ------- Additional Comments From [EMAIL PROTECTED] 2003-07-11 20:06 ------- > From the stack trace, this looks like it could be a bug in the JDK you're > using (probably 1.4.x). > What JDK version and vendor are you using? > Could you post the output from 'java -version' to the bug report? I've been using IBM's 1.3.1 and Sun's 1.4.1. Below are the version strings. I believe when the error occurred the tests were run with 1.4.1 on Linux. Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1) Classic VM (build 1.3.1, J2RE 1.3.1 IBM build cxia32131-20020622 (JIT enabled: jitc)) Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-b21) Java HotSpot(TM) Client VM (build 1.4.1-b21, mixed mode) > Does this exception always occur when you try to create a parser, or > does it only happen when you try to create several parsers concurrently? We have only seen this twice in many runs, with many threads creating and using parsers. I assume that creating several parsers simultaneously has something to do with it. Our plan is to stick with 1.3.1 for production, so we'll watch to see if it ever happens using 1.3.1. Thanks for the info. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
