You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Christian Fonden (JIRA)" <ji...@apache.org> on 2009/05/24 16:20:45 UTC
[jira] Created: (ODE-610) Process Blocks although
ExtensionContext::complete() is called from AbstractAsyncExtensionOperation
Process Blocks although ExtensionContext::complete() is called from AbstractAsyncExtensionOperation
---------------------------------------------------------------------------------------------------
Key: ODE-610
URL: https://issues.apache.org/jira/browse/ODE-610
Project: ODE
Issue Type: Bug
Environment: Tomcat 5.5 / derby db / ODE Trunk Rev. 766164
Reporter: Christian Fonden
Whenever a new ExtensionActivity is used by registering its extensionBundle and
it extends the AbstractAsyncExtensionOperation base Classe
and the ExtensionContext::complete()
OR the ExtensionContext::completeWithFault()
Methods are called,
this is not passed to the navigator and the process is being block in this activity.
This Ticket IMO is the same bug as mention in ODE-606.
The ODE Log says nothing but
=========================================
633787 [ODEServerImpl-3] DEBUG org.apache.ode.bpel.engine.BpelInstanceWorker - Finished work for instance {http://localhost:8080/ode/processes/Context4BPELScenarioProcess}Context4BPELScenarioProcess-1#1 in thread Thread[ODEServerImpl-3,5,main]
633788 [ODEServerImpl-4] DEBUG org.apache.ode.bpel.engine.BpelInstanceWorker - Finished work for instance {http://localhost:8080/ode/processes/Context4BPELScenarioProcess}Context4BPELScenarioProcess-1#1 in thread Thread[ODEServerImpl-4,5,main]
633789 [ODEServerImpl-4] DEBUG org.apache.ode.bpel.engine.BpelInstanceWorker - Worker thread Thread[ODEServerImpl-4,5,main] for instance IID 1 ran out of work.
663377 [http-8080-Processor24] ERROR org.apache.ode.axis2.ODEService - Call to {http://localhost:8080/ode/processes/Context4BPELScenarioProcess}Context4BPELScenarioService.process timed out(30000 ms).
java.util.concurrent.TimeoutException [Stacktrace follows]
=====================================================
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-610) Process Blocks although
ExtensionContext::complete() is called from AbstractAsyncExtensionOperation
Posted by "Christian Fonden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Fonden updated ODE-610:
---------------------------------
Component/s: BPEL Runtime
Fix Version/s: 2.0
Affects Version/s: 2.0
> Process Blocks although ExtensionContext::complete() is called from AbstractAsyncExtensionOperation
> ---------------------------------------------------------------------------------------------------
>
> Key: ODE-610
> URL: https://issues.apache.org/jira/browse/ODE-610
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 2.0
> Environment: Tomcat 5.5 / derby db / ODE Trunk Rev. 766164
> Reporter: Christian Fonden
> Fix For: 2.0
>
>
> Whenever a new ExtensionActivity is used by registering its extensionBundle and
> it extends the AbstractAsyncExtensionOperation base Classe
> and the ExtensionContext::complete()
> OR the ExtensionContext::completeWithFault()
> Methods are called,
> this is not passed to the navigator and the process is being block in this activity.
> This Ticket IMO is the same bug as mention in ODE-606.
> The ODE Log says nothing but
> =========================================
> 633787 [ODEServerImpl-3] DEBUG org.apache.ode.bpel.engine.BpelInstanceWorker - Finished work for instance {http://localhost:8080/ode/processes/Context4BPELScenarioProcess}Context4BPELScenarioProcess-1#1 in thread Thread[ODEServerImpl-3,5,main]
> 633788 [ODEServerImpl-4] DEBUG org.apache.ode.bpel.engine.BpelInstanceWorker - Finished work for instance {http://localhost:8080/ode/processes/Context4BPELScenarioProcess}Context4BPELScenarioProcess-1#1 in thread Thread[ODEServerImpl-4,5,main]
> 633789 [ODEServerImpl-4] DEBUG org.apache.ode.bpel.engine.BpelInstanceWorker - Worker thread Thread[ODEServerImpl-4,5,main] for instance IID 1 ran out of work.
> 663377 [http-8080-Processor24] ERROR org.apache.ode.axis2.ODEService - Call to {http://localhost:8080/ode/processes/Context4BPELScenarioProcess}Context4BPELScenarioService.process timed out(30000 ms).
> java.util.concurrent.TimeoutException [Stacktrace follows]
> =====================================================
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ODE-610) Process Blocks although
ExtensionContext::complete() is called from AbstractAsyncExtensionOperation
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tammo van Lessen resolved ODE-610.
----------------------------------
Resolution: Duplicate
Assignee: Tammo van Lessen
If its the same bug, then it should remain the same. see ODE-606
> Process Blocks although ExtensionContext::complete() is called from AbstractAsyncExtensionOperation
> ---------------------------------------------------------------------------------------------------
>
> Key: ODE-610
> URL: https://issues.apache.org/jira/browse/ODE-610
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 2.0
> Environment: Tomcat 5.5 / derby db / ODE Trunk Rev. 766164
> Reporter: Christian Fonden
> Assignee: Tammo van Lessen
> Fix For: 2.0
>
>
> Whenever a new ExtensionActivity is used by registering its extensionBundle and
> it extends the AbstractAsyncExtensionOperation base Classe
> and the ExtensionContext::complete()
> OR the ExtensionContext::completeWithFault()
> Methods are called,
> this is not passed to the navigator and the process is being block in this activity.
> This Ticket IMO is the same bug as mention in ODE-606.
> The ODE Log says nothing but
> =========================================
> 633787 [ODEServerImpl-3] DEBUG org.apache.ode.bpel.engine.BpelInstanceWorker - Finished work for instance {http://localhost:8080/ode/processes/Context4BPELScenarioProcess}Context4BPELScenarioProcess-1#1 in thread Thread[ODEServerImpl-3,5,main]
> 633788 [ODEServerImpl-4] DEBUG org.apache.ode.bpel.engine.BpelInstanceWorker - Finished work for instance {http://localhost:8080/ode/processes/Context4BPELScenarioProcess}Context4BPELScenarioProcess-1#1 in thread Thread[ODEServerImpl-4,5,main]
> 633789 [ODEServerImpl-4] DEBUG org.apache.ode.bpel.engine.BpelInstanceWorker - Worker thread Thread[ODEServerImpl-4,5,main] for instance IID 1 ran out of work.
> 663377 [http-8080-Processor24] ERROR org.apache.ode.axis2.ODEService - Call to {http://localhost:8080/ode/processes/Context4BPELScenarioProcess}Context4BPELScenarioService.process timed out(30000 ms).
> java.util.concurrent.TimeoutException [Stacktrace follows]
> =====================================================
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.