[ 
https://issues.apache.org/jira/browse/AXIS2-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Deepal Jayasinghe resolved AXIS2-3497.
--------------------------------------

    Resolution: Fixed

Please check with latest Axis2 release .

> NPE Accesing Service During Bringup
> -----------------------------------
>
>                 Key: AXIS2-3497
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3497
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: deployment, transports
>    Affects Versions: 1.3
>         Environment: Linux Fedora Core 4, Geronimo 1.0, JRE 1.5.0_12
>            Reporter: Al Ski
>            Assignee: Deepal Jayasinghe
>            Priority: Critical
>
> We have a web service that is brought up in a Geronimo / Jetty container. If 
> there is a client trying to access the service endpoint as the service is 
> being brought up, we see:
> Feb  7 21:26:45 localhost.localdomain org.mortbay.jetty.context./rmf: WARN 
> /rmf/services/RevaManagementService:
> Feb  7 21:26:45 localhost.localdomain java.lang.NullPointerException
> Feb  7 21:26:45 localhost.localdomain     at 
> org.apache.axis2.transport.http.AxisServlet.createMessageContext(AxisServlet.java:602)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.apache.axis2.transport.http.AxisServlet.createMessageContext(AxisServlet.java:664)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:116)
> Feb  7 21:26:45 localhost.localdomain     at 
> javax.servlet.http.HttpServlet.service(HttpServlet.java:615)
> Feb  7 21:26:45 localhost.localdomain     at 
> javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.apache.geronimo.jetty.JettyServletHolder.handle(JettyServletHolder.java:99)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.mortbay.jetty.servlet.JSR154Filter.doFilter(JSR154Filter.java:170)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.mortbay.http.HttpServer.service(HttpServer.java:909)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
> Feb  7 21:26:45 localhost.localdomain     at 
> org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
> The service endpoint then fails to come online even though the admin 
> application shows it as active. Deactivating and reactivating the service 
> doesn't bring the service up either. If you access the service endpoint you 
> get:
> <soapenv:Reason xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
>     <soapenv:Text xml:lang="en-US">The service cannot be found for the 
> endpoint reference (EPR) /rmf/services/RevaManagementService</soapenv:Text>
> </soapenv:Reason>
> The client is a single threaded client making a "ping" type request looking 
> for the service which never comes online.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to