DO NOT REPLY [Bug 19949] New: - NullPointerException in AxisServletBase.getEngineEnvironment

[bu...@apache.org]

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=19949>.
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=19949

NullPointerException in AxisServletBase.getEngineEnvironment

           Summary: NullPointerException in
                    AxisServletBase.getEngineEnvironment
           Product: Axis
           Version: 1.1beta
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Deployment / Registries
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: johann.schipfer@siemens.com
                CC: jasnell@us.ibm.com


Sun ONE AS7 reloads ALL deployed web modules whenever a WAR file is deployed or 
undeployed, e.g. (snippet from server.log):

[27/Feb/2003:14:47:11] INFO (25770): CORE3276: Installing a new configuration
[27/Feb/2003:14:47:13] INFO (25770): WEB0100: Loading web module [sms-soap-if] 
in virtual server [server1] at [/sms-soap-if]
[27/Feb/2003:14:47:13] INFO (25770): WEB0100: Loading web module [test-gui] in 
virtual server [server1] at [/test-gui]
[27/Feb/2003:14:47:13] INFO (25770): WEB0100: Loading web module [ud-soap-if] 
in virtual server [server1] at [/ud-soap-if]
[27/Feb/2003:14:47:17] INFO (25770): CORE3280: A new configuration was 
successfully installed

>From this point on, all our AXIS based Web Services are broken (if at least one 
soap request was handled before). When trying to access it, the stacktrace 
below appears in server.log. After an application server restart everything 
works fine, until another arbitrary WAR file is deployed or undeployed.

I guess this bug could be equal to or related to Bug 14807, although I'm not 
sure. Also with AXIS-1.1RC2 all SOAP servlets are broken after the (un-)
deployment of an arbitrary WEB application, the only difference is that the 
NullPointerException doesn't appear in server.xml. Our workaround is to restart 
the application server after each WAR deployment, but this won't be reasonable 
for our customers, therefore this issue is critical for us.

[27/Feb/2003:14:47:50] SEVERE (25770): StandardWrapperValve[AxisServlet]: 
servlet.service() for servlet AxisServlet threw exception
java.lang.NullPointerException
        at org.apache.axis.transport.http.AxisServletBase.getEngineEnvironment
(AxisServletBase.java:285)
        at org.apache.axis.transport.http.AxisServletBase.getEngine
(AxisServletBase.java:208)
        at org.apache.axis.transport.http.AxisServletBase.getEngine
(AxisServletBase.java:187)
        at org.apache.axis.transport.http.AxisServlet.doPost
(AxisServlet.java:698)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
        at org.apache.axis.transport.http.AxisServletBase.service
(AxisServletBase.java:339)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at org.apache.catalina.core.StandardWrapperValve.invokeServletService
(StandardWrapperValve.java:720)
        at org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:309)
        at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:505)
        at org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:212)
        at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:505)
        at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:203)
        at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:505)
        at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process
(NSAPIProcessor.java:157)
        at com.iplanet.ias.web.WebContainer.service(WebContainer.java:598)