You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Shammy Chen (JIRA)" <ji...@apache.org> on 2009/01/19 13:23:59 UTC
[jira] Created: (ODE-493) ConcurrentModificationException occured
in memdao implementation of ODE when heavily loaded
ConcurrentModificationException occured in memdao implementation of ODE when heavily loaded
-------------------------------------------------------------------------------------------
Key: ODE-493
URL: https://issues.apache.org/jira/browse/ODE-493
Project: ODE
Issue Type: Bug
Components: BPEL Runtime
Affects Versions: 1.2
Environment: JAVA 5.0+
Reporter: Shammy Chen
ConcurrentModificationException occured in memdao implementation of ODE when heavily loaded,see error log for details:
java.util.ConcurrentModificationException
at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
at java.util.AbstractList$Itr.next(AbstractList.java:343)
at org.apache.ode.bpel.memdao.CorrelatorDaoImpl._removeRoutes(CorrelatorDaoImpl.java:125)
at org.apache.ode.bpel.memdao.ProcessInstanceDaoImpl.removeRoutes(ProcessInstanceDaoImpl.java:398)
at org.apache.ode.bpel.memdao.CorrelatorDaoImpl.removeRoutes(CorrelatorDaoImpl.java:92)
at org.apache.ode.bpel.engine.PartnerLinkMyRoleImpl.invokeInstance(PartnerLinkMyRoleImpl.java:215)
at org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:208)
at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(BpelProcess.java:372)
at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:326)
at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:373)
at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:337)
at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:1)
at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:174)
at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:335)
at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:1)
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:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-493) ConcurrentModificationException occured
in memdao implementation of ODE when heavily loaded
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665220#action_12665220 ]
Rafal Rusin commented on ODE-493:
---------------------------------
Can you give reproduction steps (possibly with some process examples)?
> ConcurrentModificationException occured in memdao implementation of ODE when heavily loaded
> -------------------------------------------------------------------------------------------
>
> Key: ODE-493
> URL: https://issues.apache.org/jira/browse/ODE-493
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.2
> Environment: JAVA 5.0+
> Reporter: Shammy Chen
> Attachments: memdao_err.log
>
>
> ConcurrentModificationException occured in memdao implementation of ODE when heavily loaded,see error log for details:
> java.util.ConcurrentModificationException
> at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
> at java.util.AbstractList$Itr.next(AbstractList.java:343)
> at org.apache.ode.bpel.memdao.CorrelatorDaoImpl._removeRoutes(CorrelatorDaoImpl.java:125)
> at org.apache.ode.bpel.memdao.ProcessInstanceDaoImpl.removeRoutes(ProcessInstanceDaoImpl.java:398)
> at org.apache.ode.bpel.memdao.CorrelatorDaoImpl.removeRoutes(CorrelatorDaoImpl.java:92)
> at org.apache.ode.bpel.engine.PartnerLinkMyRoleImpl.invokeInstance(PartnerLinkMyRoleImpl.java:215)
> at org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:208)
> at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(BpelProcess.java:372)
> at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:326)
> at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:373)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:337)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:1)
> at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:174)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:335)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:1)
> 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:885)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-493) ConcurrentModificationException occured
in memdao implementation of ODE when heavily loaded
Posted by "Shammy Chen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shammy Chen updated ODE-493:
----------------------------
Attachment: memdao_err.log
> ConcurrentModificationException occured in memdao implementation of ODE when heavily loaded
> -------------------------------------------------------------------------------------------
>
> Key: ODE-493
> URL: https://issues.apache.org/jira/browse/ODE-493
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.2
> Environment: JAVA 5.0+
> Reporter: Shammy Chen
> Attachments: memdao_err.log
>
>
> ConcurrentModificationException occured in memdao implementation of ODE when heavily loaded,see error log for details:
> java.util.ConcurrentModificationException
> at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
> at java.util.AbstractList$Itr.next(AbstractList.java:343)
> at org.apache.ode.bpel.memdao.CorrelatorDaoImpl._removeRoutes(CorrelatorDaoImpl.java:125)
> at org.apache.ode.bpel.memdao.ProcessInstanceDaoImpl.removeRoutes(ProcessInstanceDaoImpl.java:398)
> at org.apache.ode.bpel.memdao.CorrelatorDaoImpl.removeRoutes(CorrelatorDaoImpl.java:92)
> at org.apache.ode.bpel.engine.PartnerLinkMyRoleImpl.invokeInstance(PartnerLinkMyRoleImpl.java:215)
> at org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:208)
> at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(BpelProcess.java:372)
> at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:326)
> at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:373)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:337)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:1)
> at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:174)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:335)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:1)
> 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:885)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-493) ConcurrentModificationException occured
in memdao implementation of ODE when heavily loaded
Posted by "Shammy Chen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665114#action_12665114 ]
Shammy Chen commented on ODE-493:
---------------------------------
I think JPA implementation of DAO have the same problem,and we have encountered this before.
> ConcurrentModificationException occured in memdao implementation of ODE when heavily loaded
> -------------------------------------------------------------------------------------------
>
> Key: ODE-493
> URL: https://issues.apache.org/jira/browse/ODE-493
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.2
> Environment: JAVA 5.0+
> Reporter: Shammy Chen
> Attachments: memdao_err.log
>
>
> ConcurrentModificationException occured in memdao implementation of ODE when heavily loaded,see error log for details:
> java.util.ConcurrentModificationException
> at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
> at java.util.AbstractList$Itr.next(AbstractList.java:343)
> at org.apache.ode.bpel.memdao.CorrelatorDaoImpl._removeRoutes(CorrelatorDaoImpl.java:125)
> at org.apache.ode.bpel.memdao.ProcessInstanceDaoImpl.removeRoutes(ProcessInstanceDaoImpl.java:398)
> at org.apache.ode.bpel.memdao.CorrelatorDaoImpl.removeRoutes(CorrelatorDaoImpl.java:92)
> at org.apache.ode.bpel.engine.PartnerLinkMyRoleImpl.invokeInstance(PartnerLinkMyRoleImpl.java:215)
> at org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:208)
> at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(BpelProcess.java:372)
> at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:326)
> at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:373)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:337)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:1)
> at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:174)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:335)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:1)
> 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:885)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-493) ConcurrentModificationException occured
in memdao implementation of ODE when heavily loaded
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tammo van Lessen updated ODE-493:
---------------------------------
Fix Version/s: 1.3.5
> ConcurrentModificationException occured in memdao implementation of ODE when heavily loaded
> -------------------------------------------------------------------------------------------
>
> Key: ODE-493
> URL: https://issues.apache.org/jira/browse/ODE-493
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.2
> Environment: JAVA 5.0+
> Reporter: Shammy Chen
> Fix For: 1.3.5
>
> Attachments: bpmdemo3-5.zip, memdao_err.log
>
>
> ConcurrentModificationException occured in memdao implementation of ODE when heavily loaded,see error log for details:
> java.util.ConcurrentModificationException
> at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
> at java.util.AbstractList$Itr.next(AbstractList.java:343)
> at org.apache.ode.bpel.memdao.CorrelatorDaoImpl._removeRoutes(CorrelatorDaoImpl.java:125)
> at org.apache.ode.bpel.memdao.ProcessInstanceDaoImpl.removeRoutes(ProcessInstanceDaoImpl.java:398)
> at org.apache.ode.bpel.memdao.CorrelatorDaoImpl.removeRoutes(CorrelatorDaoImpl.java:92)
> at org.apache.ode.bpel.engine.PartnerLinkMyRoleImpl.invokeInstance(PartnerLinkMyRoleImpl.java:215)
> at org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:208)
> at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(BpelProcess.java:372)
> at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:326)
> at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:373)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:337)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:1)
> at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:174)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:335)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:1)
> 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:885)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (ODE-493) ConcurrentModificationException occured
in memdao implementation of ODE when heavily loaded
Posted by "Shammy Chen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665365#action_12665365 ]
Shammy Chen commented on ODE-493:
---------------------------------
The way to reproduce this bug is:
Firstly, create a process with correlations, that is, this process can be invoked several times.
Then , concurrently call this process at different services exported by this process.
You will see this error soon
> ConcurrentModificationException occured in memdao implementation of ODE when heavily loaded
> -------------------------------------------------------------------------------------------
>
> Key: ODE-493
> URL: https://issues.apache.org/jira/browse/ODE-493
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.2
> Environment: JAVA 5.0+
> Reporter: Shammy Chen
> Attachments: bpmdemo3-5.zip, memdao_err.log
>
>
> ConcurrentModificationException occured in memdao implementation of ODE when heavily loaded,see error log for details:
> java.util.ConcurrentModificationException
> at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
> at java.util.AbstractList$Itr.next(AbstractList.java:343)
> at org.apache.ode.bpel.memdao.CorrelatorDaoImpl._removeRoutes(CorrelatorDaoImpl.java:125)
> at org.apache.ode.bpel.memdao.ProcessInstanceDaoImpl.removeRoutes(ProcessInstanceDaoImpl.java:398)
> at org.apache.ode.bpel.memdao.CorrelatorDaoImpl.removeRoutes(CorrelatorDaoImpl.java:92)
> at org.apache.ode.bpel.engine.PartnerLinkMyRoleImpl.invokeInstance(PartnerLinkMyRoleImpl.java:215)
> at org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:208)
> at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(BpelProcess.java:372)
> at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:326)
> at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:373)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:337)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:1)
> at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:174)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:335)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:1)
> 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:885)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-493) ConcurrentModificationException occured
in memdao implementation of ODE when heavily loaded
Posted by "Shammy Chen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shammy Chen updated ODE-493:
----------------------------
Attachment: bpmdemo3-5.zip
My ODE process to interact with tempo(modified),I think it won't help much to you
> ConcurrentModificationException occured in memdao implementation of ODE when heavily loaded
> -------------------------------------------------------------------------------------------
>
> Key: ODE-493
> URL: https://issues.apache.org/jira/browse/ODE-493
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.2
> Environment: JAVA 5.0+
> Reporter: Shammy Chen
> Attachments: bpmdemo3-5.zip, memdao_err.log
>
>
> ConcurrentModificationException occured in memdao implementation of ODE when heavily loaded,see error log for details:
> java.util.ConcurrentModificationException
> at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
> at java.util.AbstractList$Itr.next(AbstractList.java:343)
> at org.apache.ode.bpel.memdao.CorrelatorDaoImpl._removeRoutes(CorrelatorDaoImpl.java:125)
> at org.apache.ode.bpel.memdao.ProcessInstanceDaoImpl.removeRoutes(ProcessInstanceDaoImpl.java:398)
> at org.apache.ode.bpel.memdao.CorrelatorDaoImpl.removeRoutes(CorrelatorDaoImpl.java:92)
> at org.apache.ode.bpel.engine.PartnerLinkMyRoleImpl.invokeInstance(PartnerLinkMyRoleImpl.java:215)
> at org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:208)
> at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(BpelProcess.java:372)
> at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:326)
> at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:373)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:337)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:1)
> at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:174)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:335)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:1)
> 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:885)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (ODE-493)
ConcurrentModificationException occured in memdao implementation of ODE
when heavily loaded
Posted by "Shammy Chen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665365#action_12665365 ]
shammychen edited comment on ODE-493 at 1/20/09 12:53 AM:
-----------------------------------------------------------
The way to reproduce this bug is:
Firstly, create a process with correlations, that is, this process can be invoked several times(so CorrelatorDaoImpl can take its responsibility).
Then , concurrently call this process at different services exported by this process.
You will see this error soon
was (Author: shammychen):
The way to reproduce this bug is:
Firstly, create a process with correlations, that is, this process can be invoked several times.
Then , concurrently call this process at different services exported by this process.
You will see this error soon
> ConcurrentModificationException occured in memdao implementation of ODE when heavily loaded
> -------------------------------------------------------------------------------------------
>
> Key: ODE-493
> URL: https://issues.apache.org/jira/browse/ODE-493
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.2
> Environment: JAVA 5.0+
> Reporter: Shammy Chen
> Attachments: bpmdemo3-5.zip, memdao_err.log
>
>
> ConcurrentModificationException occured in memdao implementation of ODE when heavily loaded,see error log for details:
> java.util.ConcurrentModificationException
> at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
> at java.util.AbstractList$Itr.next(AbstractList.java:343)
> at org.apache.ode.bpel.memdao.CorrelatorDaoImpl._removeRoutes(CorrelatorDaoImpl.java:125)
> at org.apache.ode.bpel.memdao.ProcessInstanceDaoImpl.removeRoutes(ProcessInstanceDaoImpl.java:398)
> at org.apache.ode.bpel.memdao.CorrelatorDaoImpl.removeRoutes(CorrelatorDaoImpl.java:92)
> at org.apache.ode.bpel.engine.PartnerLinkMyRoleImpl.invokeInstance(PartnerLinkMyRoleImpl.java:215)
> at org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:208)
> at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(BpelProcess.java:372)
> at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:326)
> at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:373)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:337)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:1)
> at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:174)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:335)
> at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:1)
> 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:885)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.