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=17795>. 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=17795 NPE in SOAPMonitorService - Race Condition? Summary: NPE in SOAPMonitorService - Race Condition? Product: Axis Version: current (nightly) Platform: All OS/Version: Windows XP Status: NEW Severity: Minor Priority: Other Component: Samples AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] As seen at startup under Tomcat4.18 java.lang.NullPointerException at org.apache.axis.monitor.SOAPMonitorService$ServerSocketThread.run(SOA PMonitorService.java:228) at java.lang.Thread.run(Thread.java:536) This particular line is the accept() statement in :- while (server_socket != null) { try { Socket socket = server_socket.accept(); **HERE** new Thread(new ConnectionThread(socket)).start(); } catch (IOException ioe) {} } So, to get the NPE the server_socket variable has to be set at entry to the loop, then unset shortly thereafter. This usually imples a race condition to me.
