You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Rick.Todo (JIRA)" <ji...@apache.org> on 2010/01/26 06:18:35 UTC

[jira] Updated: (ODE-697) Versioning doesn't Works and NPE occured.

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

Rick.Todo updated ODE-697:
--------------------------

    Attachment: incomplete.patch

I modified "org.apache.ode.bpel.engine.BpelEngineImpl" like "incomplete.patch".
Then, we could start newer version.
but, if there was still running process-instance of older version,
that older process-instance could not recieve  any request, so eventHandler did not work.
Please teach us how to fix it.

> Versioning doesn't Works and NPE occured.
> -----------------------------------------
>
>                 Key: ODE-697
>                 URL: https://issues.apache.org/jira/browse/ODE-697
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>    Affects Versions: 1.3.3
>         Environment: Windows
>            Reporter: Rick.Todo
>         Attachments: incomplete.patch
>
>
> I deployed new versions of processes via deployment web service, older process became "RETIRED"
> but When I sended request to start the process, NullPointerException occured.
> 2009-11-11 14:33:20.640+0900,ERROR,,localhost,,,,,null,"java.lang.NullPointerException
> 	at org.apache.ode.axis2.ODEService.onAxisMessageExchange(ODEService.java:162)
> 	at org.apache.ode.axis2.hooks.ODEMessageReceiver.invokeBusinessLogic(ODEMessageReceiver.java:69)
> 	at org.apache.ode.axis2.hooks.ODEMessageReceiver.invokeBusinessLogic(ODEMessageReceiver.java:63)
> 	at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100)
> 	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
> 	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
> 	at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> 	at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56)
> 	at org.apache.catalina.valves.RequestFilterValve.process(RequestFilterValve.java:269)
> 	at org.apache.catalina.valves.RemoteAddrValve.invoke(RemoteAddrValve.java:81)
> 	at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:406)
> 	at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47)
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> 	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568)
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
> 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
> 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
> 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> 	at java.lang.Thread.run(Thread.java:619)
> Both new ACTIVE process and older RETIRED process are in target list in MessageExchange.
> Should ode send request to only ACTIVE request?
> and it appears that BrokeredMyRoleMessageExchangeImpl#getOperation always return null.

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