[
https://issues.apache.org/jira/browse/ODE-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517993
]
Richard Taylor commented on ODE-166:
------------------------------------
In regards to the RC1 email, the issue below shouldn't stop 1.1 RC1, at
least not on my account. Also thanks for the info on Axis2 1.3, looking
forward to the upgrade. - Rich
> After undeploying a process its WSDL is still available and executing it
> result in NPE
> --------------------------------------------------------------------------------------
>
> Key: ODE-166
> URL: https://issues.apache.org/jira/browse/ODE-166
> Project: ODE
> Issue Type: Bug
> Components: Axis2 Integration
> Affects Versions: 1.1
> Environment: Axis2 distro
> JDK 1.5.0_11
> WinXPx64
> Reporter: Richard Taylor
>
> After deploying a process into the "processes" folder (via file system, if it
> matters), then undeploying it (via the file system again), its WSDL is still
> available for download. Also if you try to execute that service (one could
> assume it is available since its WSDL is), the null pointer exception below
> occurs. I haven't confirmed that this also happens when deploying via web
> services, but by comparing the source of the two deployers, I would expect
> the same behavior.
> INFO [BpelServerImpl]: Process
> {urn:xmlns:attachmate:composite-services}Echo-1
> has been unregistered.
> WARN [BpelDAOConnectionImpl]: Couldn't find mex 4611686018427387903 for
> cleanup
> .
> ERROR [AxisServlet]: java.lang.NullPointerException
> java.lang.NullPointerException
> at
> org.apache.ode.axis2.ODEService.onAxisMessageExchange(ODEService.java
> :146)
> at
> org.apache.ode.axis2.hooks.ODEMessageReceiver.invokeBusinessLogic(ODE
> MessageReceiver.java:68)
> at
> org.apache.ode.axis2.hooks.ODEMessageReceiver.receive(ODEMessageRecei
> ver.java:49)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:506)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReq
> uest(HTTPTransportUtils.java:328)
> at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:2
> 55)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491
> )
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:3
> 67)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.jav
> a:185)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:1
> 81)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:6
> 89)
> at
> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.
> java:114)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:1
> 39)
> at org.mortbay.jetty.Server.handle(Server.java:285)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:45
> 7)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnectio
> n.java:765)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:628)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:357)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.ja
> va:329)
> at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool
> .java:475)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.