Hi Richard,
I just got out from this boring problem - the always repeating
"...scheduled job event...".
The solution is rather simple: inserting a single line in the
deploy.xml file of your process. For example:
<process name="pns:HelloWorld2">
<active>true</active>
<provide partnerLink="helloPartnerLink">
<service name="wns:HelloService" port="HelloPort"/>
</provide>
<cleanup on="always" /> <!-- <<<<==== this line -->
</process>
Then restart Tomcat(or re-deploy the process) and it'll be OK. :-)
P.S. I found out this solution at the ODE online document:
http://ode.apache.org/user-guide.html#UserGuide-InstanceDataCleanup
Regards
Wenfeng
======= 2009-01-21 02:04:43 您在来信中写道：=======
>Hi,
>
>I deploy my BPEL processes on ODE 1.2 from the BPEL Designer recently ported on
>Ganymede.
>
>When I stop and launch again my "Ode v1.x Server" to deploy new BPEL process, I
>observe in the log console that old process instances are always deployed.
>
>The logs related on these old instance are on the same model :
>Received a scheduled job event for active process
>{http://www.exemple.com/}Process-XXX; rescheduling job hqejbhcnphr3xa0lkp1jq3
>
>When I open the URL : http://localhost:8080/ode/services/listServices, I can
>list also my old services. It's like if services were persistent between two
>ODE
>startup.
>
>My question is :
>How can I delete these old instances (manually, which files to delete,
>other...)
>? There is no administration tool (i.e.: management console) to do that.
>
>Richard.
>
= = = = = = = = = = = = = = = = = = = =
致
礼！
ZHAO Wenfeng
[email protected]
2009-01-21
