[ 
https://issues.apache.org/jira/browse/ODE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matthieu Riou updated ODE-294:
------------------------------

    Fix Version/s:     (was: 1.3)
                   2.0

> missingRequest fault is not propagated as JBI fault
> ---------------------------------------------------
>
>                 Key: ODE-294
>                 URL: https://issues.apache.org/jira/browse/ODE-294
>             Project: ODE
>          Issue Type: Bug
>          Components: JBI Integration
>    Affects Versions: 1.1.1
>         Environment: FUSE ESB 3.3.0.2
>            Reporter: Mateusz Nowakowski
>             Fix For: 2.0
>
>
> Situation:
> - some error occurs before receive activity (for example not initialized 
> variable is used  inside assign activity)
> - some runtime fault is thrown (for example uninitializedVariable fault)
> - catchAll activity catchs fault and handles it, 
> - reply activity is performed, but reply fails with 
> {http://docs.oasis-open.org/wsbpel/2.0/process/executable}missingRequest
> - what is worse this error is not propagated to the JBI and whole transaction 
> stall
> Below are logs from servicemix.log:
> 15:34:11,809 | DEBUG | pool-3-thread-1 | REPLY                    | 
> .apache.ode.bpel.runtime.REPLY   45 | <reply>  partnerLink=OPartnerLink#115, 
> operation=Operation: name=SomeServiceNameRQ
> style=REQUEST_RESPONSE,1
> Input: name=null
> Message: name={someURL}SomeServiceNameInput
> Part: name=body
> elementName={someURL}SomeServiceNameRQ
> Output: name=null
> Message: name={someUrl}SomeServiceNameOutput
> Part: name=body
> elementName={someUrl}SomeServiceNameRS
> 15:34:11,809 | DEBUG | pool-3-thread-1 | utstandingRequestManager | 
> gine.OutstandingRequestManager  177 | ==release: RID {RequestIdTuple 
> partnerLink={PartnerLinkInstance 
> partnerLinkDecl=OPartnerLink#115,scopeInstanceId=0},opName=SomeServiceNameRQ,mexId=}
>  not found in {}
> 15:34:11,809 | ERROR | pool-3-thread-1 | REPLY                    | 
> .apache.ode.bpel.runtime.REPLY   69 | 
> org.apache.ode.bpel.common.FaultException: 
> {http://docs.oasis-open.org/wsbpel/2.0/process/executable}missingRequest
> 15:34:11,809 | DEBUG | pool-3-thread-1 | SCOPE                    | 
> .ode.bpel.runtime.SCOPE$ACTIVE  291 | ({OCatch faultName=null, 
> faultVariable=null},TerminationChannel:FH#13,ParentScopeChannel:FH#14): has 
> no fault handler for 
> {http://docs.oasis-open.org/wsbpel/2.0/process/executable}missingRequest; 
> scope will propagate FAULT!
> 15:34:11,809 | DEBUG | pool-3-thread-1 | BpelProcess              | 
> .engine.BpelRuntimeContextImpl  199 | ProcessImpl completed with fault 
> '{http://docs.oasis-open.org/wsbpel/2.0/process/executable}missingRequest'
> 15:34:11,809 | DEBUG | pool-3-thread-1 | ProcessDaoImpl           | 
> ode.bpel.memdao.ProcessDaoImpl  147 | Removing completed process instance 0 
> from in-memory store.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to