[ODE-610] Process Blocks although ExtensionContext::complete() is called from AbstractAsyncExtensionOperation

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0
• Fix Version/s: 2.0
• Component/s: BPEL Runtime
• Environment: Tomcat 5.5 / derby db / ODE Trunk Rev. 766164
• Assignee: Tammo van Lessen
• Reporter: Christian Fonden
• Created: 24/May/09 14:18
• Updated: 24/May/09 18:06
• Resolved: 24/May/09 18:06

Description

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]
=====================================================

Issue Links

• relates to: ODE-606 Process blocks although Async Extension Operation is marked completed or completedWithFault