Ryan, I used to get the same thing. I don't think we ever figured out exaclty why it's happening. Can you "catch" the exception and just ignore it? it doesnt seem to really affect the behavior during shutdown. I spent many days trying to trace the cause of it and couldn't run it down, maybe someone else might know but I definately don't (of course I didn't have a java debug setup....) What I do know is that the threads USED to not completley shutdown, they'd just stay around, and during my shutdown/restart (which was C++ JNI interface to the xmlrpc) I would end up with dnagling threads... Eventually you;ll run out thread handles, so we made some changes to make sure that the threads did die during shutdown and that may have unintentionally created a null pointer access. Look in WebServer and see if there isn't some check that could be added onto any pointer dereferences to check for null, that way whenever the access happened (obviously it is happening prior to the final shutdown of that particular thread) it could just slide by until shutdown completed. ashley
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 02, 2002 10:38 AM To: [EMAIL PROTECTED] Subject: Null Pointer Exception From: Ryan D. Cuprak I am just curious if I am doing something wrong. I am getting a null point exception upon the shutdown of my webserver (below). Prior to calling shutdown I remove all handlers. Don't quite know what to make of this. -Ryan java.lang.NullPointerException at org.apache.xmlrpc.WebServer.run(WebServer.java) at java.lang.Thread.run(Thread.java:484)
