You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Sean Ahn (JIRA)" <ji...@apache.org> on 2009/05/20 19:59:45 UTC

[jira] Commented: (ODE-608) NPE during ONE-WAY-invoke because of clean-up category 'messages'

    [ https://issues.apache.org/jira/browse/ODE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711257#action_12711257 ] 

Sean Ahn commented on ODE-608:
------------------------------

Heiko,

the on-the-fly clean-up of runtime data on trunk is not really ready. I migrated the functionality from the 1.x branch. But, all the test cases are still disabled and there are still some small fixes to migrate from 1.x.

If you really need the clean-up functionality, I would recommend that you use 1.x.

When the clean-up is ready on trunk, I'll resolve this jira issue after testing.


> NPE during ONE-WAY-invoke because of clean-up category 'messages' 
> ------------------------------------------------------------------
>
>                 Key: ODE-608
>                 URL: https://issues.apache.org/jira/browse/ODE-608
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>    Affects Versions: 2.0
>         Environment: Linux, Jetty/Tomcat5.5
>            Reporter: heiko rath
>            Assignee: Sean Ahn
>             Fix For: 2.0
>
>
> We've defined some invokes. The last invoke is a ONE-WAY-invoke. 
> Also we've defined the following cleanup:
> <cleanup on="success" >
>    <category>instance</category>
>    <category>variables</category>
>    <category>messages</category>
>    <category>correlations</category>
>    <category>events</category>
> </cleanup>
> Wenn the ONE-WAY-invoke is called we get a 
> java.lang.NullPointerException
> 	at org.apache.ode.il.epr.WSAEndpoint.<init>(WSAEndpoint.java:49)
> 	at org.apache.ode.axis2.soapbinding.SoapExternalService.writeHeader(SoapExternalService.java:270)
> 	at org.apache.ode.axis2.soapbinding.SoapExternalService.invoke(SoapExternalService.java:144)
> 	at org.apache.ode.axis2.MessageExchangeContextImpl.invokePartnerUnreliable(MessageExchangeContextImpl.java:68)
> 	at org.apache.ode.bpel.engine.PartnerLinkPartnerRoleImpl$UnreliableInvoker.run(PartnerLinkPartnerRoleImpl.java:345)
> 	at org.apache.ode.bpel.engine.ODEProcess$ProcessRunnable.run(ODEProcess.java:1215)
> 	at org.apache.ode.bpel.engine.BpelServerImpl$ServerRunnable.run(BpelServerImpl.java:927)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:619)
> If we're removing the category 'messages' in the cleanup-tag, we don't get the NPE.

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