[
https://issues.apache.org/jira/browse/ODE-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847079#action_12847079
]
David McLure commented on ODE-779:
----------------------------------
We are still seeing this same issue in both ODE 2.0 Beta 2, as well as the
latest stable build - ODE 2 Beta3 snapshot build #253.
I can reproduce the problem with the single line of code (<cleanup on="always"
/>) added to the helloWorld2 deploy.xml file just as is shown in the online web
site documentation in the User Guide:
<process name="pns:HelloWorld2">
<active>true</active>
<provide partnerLink="helloPartnerLink">
<service name="wns:HelloService" port="HelloPort"/>
</provide>
<cleanup on="always" />
</process>
This bug is wreaking havoc for us because completed process instances
eventually clog up the Derby database and bring the system to its knees with no
way to clean it up short of redeploying ODE from scratch. Given that there is
no working (documented) alternative to the embedded Derby database (see Jira
ODE-775), this bug is blocking a huge number of other bugs for us.
> NullPointerException in One ways cleanup
> ----------------------------------------
>
> Key: ODE-779
> URL: https://issues.apache.org/jira/browse/ODE-779
> Project: ODE
> Issue Type: Bug
> Components: Axis2 Integration
> Affects Versions: 1.3.3
> Environment: ODE -1.3.3 + TOMCAT 6
> Reporter: leo.meng
> Attachments: CleanedUpOne-Way.zip
>
>
> I am using ode 1.3.3, and Instance Data Cleanup like below.
> <process name="pns:XXXX">
> ...
> <cleanup on="always" />
> </process>
> I got NullPointerException.
> You can see the mail:
> http://mail-archives.apache.org/mod_mbox/ode-user/200908.mbox/%[email protected]%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
