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=19949>. 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=19949 ------- Additional Comments From [EMAIL PROTECTED] 2006-01-11 12:26 ------- Hi! I've just run in the same issue with JBoss 3.2.6, Jetty 5.1.x and Axis 1.3, debuged it and found one thing which is very difficult to do in a j2ee environment that supports reloading: ClassLoaders are chached in static variables by AxisProperties. Now since jdk 1.2 class reloading works that way, that classes loaded by the system class loader can not be reloaded and classes loaded by some different class loader are discarded when the class loader is garbaged and can then be loaded again by a new class loader. We configured JBoss+Jetty to use context class loaders before using system class loaders (the later one is the default). Background: This gives us the possibility (as long as we don't use axis) to deploy the same web application several times with different name and different code (production, test, old customer x version, etc) in the same server. When undeploying a web application, the web app context class loader becomes invalid (WEB-INF classes + lib should be deleted), but Axis with commons-discovery still tries to use it - which causes the NPE. Since I don't know a way to see from outside, if a class loader is still valid, I suggest you completely remove the class loader caching. -- 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.
