BPEL Process Instance Hangs When received a Fault

Hello.
I have this BPEL Workflow:
Principal
|
|---> BS_Insert_Upip_Data
| |
| |---> BS_getUtenteFromRNUIntoUPIP
| |
| |---> saveUtente
| ...
|
|---> setEpisodio
|
My problem consist in the following:
When BS_Insert_Upip_Data received a fault from BS_getUtenteFromRNUIntoUPIP or saveUtente, it hangs.
This is a sample of the XML from audit tab that I received. The name of the process are different from the above, but the struck is the same.
I have mark as Bold the Fault message. Another thing, the call of process BS_getUtenteFromRNUIntoUPIP don't appear on BPEL Console.
Can any one give me an help ?
Thanks
<audit-trail>
<event sid="0" cat="2" type="2" n="0" date="2008-10-23T14:44:39.626+01:00">
<message>New instance of BPEL process "BS_Insert_Upip_Data" initiated (#"23338496").</message>
</event>
<event sid="BpPrc0.1" cat="1" type="2" label="process" n="1"
date="2008-10-23T14:44:39.667+01:00" psid="0">
<message>cr</message>
</event>
<event sid="BpTry0.2" cat="1" type="2" n="2"
date="2008-10-23T14:44:39.667+01:00" psid="BpPrc0.1">
<message>cr</message>
</event>
<event sid="BpSeq0.3" cat="1" type="2" label="sequence" n="3"
date="2008-10-23T14:44:39.667+01:00" psid="BpTry0.2">
<message>cr</message>
</event>
<event sid="BpSeq0.3" cat="2" type="2" wikey="23338496-BpRcv0-BpSeq0.3-1"
label="receiveInput" n="4" date="2008-10-23T14:44:39.668+01:00">
<message>Received "inputVariable" call from partner "client"</message>
<details>
<inputVariable>
<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
name="payload">
<BS_Insert_Upip_DataProcessRequest xmlns:ns1="http://xmlns.oracle.com/BS_Insert_Upip_Data"
xmlns="http://xmlns.oracle.com/BS_Insert_Upip_Data">
<ns1:input>
<ns1:Utente>
<ns1:Num_Cartao_Sns>123456</ns1:Num_Cartao_Sns>
<ns1:Problemas/>
<ns1:Medicamentos_Cronicos/>
</ns1:Utente>
<ns1:Episodio>
<ns1:Num_Episodio>987654321</ns1:Num_Episodio>
<ns1:Cod_Inst_Saude>654321</ns1:Cod_Inst_Saude>
<ns1:Dta_Admissao>2008-08-22T11:27:00</ns1:Dta_Admissao>
<ns1:Dta_Consulta/>
<ns1:Dta_Alta/>
<ns1:Cod_Destino/>
<ns1:Cod_Inst_Saude_Destino/>
<ns1:Cod_Medico>12112</ns1:Cod_Medico>
<ns1:Notas_Medicas/>
<ns1:Dta_Obs/>
<ns1:Cod_Prioridade_Triagem/>
<ns1:Cod_Local>U</ns1:Cod_Local>
<ns1:Des_Local>Urgencia</ns1:Des_Local>
<ns1:Causas/>
<ns1:Diagnosticos/>
<ns1:Medicacao/>
<ns1:Mcdts/>
<ns1:Procedimentos/>
</ns1:Episodio>
</ns1:input>
</BS_Insert_Upip_DataProcessRequest>
</part>
</inputVariable>
</details>
</event>
<event sid="BpScp0.4" cat="1" type="2" label="Insere_Utente_Upip" n="5"
date="2008-10-23T14:44:39.668+01:00" psid="BpSeq0.3">
<message>cr</message>
</event>
<event sid="BpTry1.5" cat="1" type="2" n="6"
date="2008-10-23T14:44:39.668+01:00" psid="BpScp0.4">
<message>cr</message>
</event>
<event sid="BpSeq2.6" cat="1" type="2" label="sequence" n="7"
date="2008-10-23T14:44:39.668+01:00" psid="BpTry1.5">
<message>cr</message>
</event>
<event to="Invoke_BS_getUtenteFromRNUIntoUpip_InputVariable" sid="BpSeq2.6"
cat="2" type="1" wikey="23338496-BpAss1-BpSeq2.6-1"
label="Client_Input_Into_BS_getUtenteFromRNUIntoUpip" n="8"
date="2008-10-23T14:44:39.668+01:00">
<message>Updated variable "Invoke_BS_getUtenteFromRNUIntoUpip_InputVariable"</message>
<details>
<Invoke_BS_getUtenteFromRNUIntoUpip_InputVariable>
<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
name="payload">
<BS_getUtenteFromRNUIntoUPIPProcessRequest xmlns:ns1="http://xmlns.oracle.com/BS_getUtenteFromRNUIntoUPIP"
xmlns="http://xmlns.oracle.com/BS_getUtenteFromRNUIntoUPIP">
<ns1:Num_Cartao_Sns>178924781</ns1:Num_Cartao_Sns>
</BS_getUtenteFromRNUIntoUPIPProcessRequest>
</part>
</Invoke_BS_getUtenteFromRNUIntoUpip_InputVariable>
</details>
</event>
<event sid="BpSeq2.6" cat="2" type="4"
label="Invoke_BS_getUtenteFromRNUIntoUpip"
wikey="23338496-BpInv0-BpSeq2.6-2"
partnerWSDL="http://www:80/orabpel/develop/BS_getUtenteFromRNUIntoUPIP/1.0/BS_getUtenteFromRNUIntoUPIP?wsdl"
n="9" date="2008-10-23T14:45:54.823+01:00">
<message>Faulted while invoking operation "process" on provider "BS_getUtenteFromRNUIntoUPIP".</message>
<details>
<messages>
<input>
<Invoke_BS_getUtenteFromRNUIntoUpip_InputVariable>
<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
name="payload">
<BS_getUtenteFromRNUIntoUPIPProcessRequest xmlns:ns1="http://xmlns.oracle.com/BS_getUtenteFromRNUIntoUPIP"
xmlns="http://xmlns.oracle.com/BS_getUtenteFromRNUIntoUPIP">
<ns1:Num_Cartao_Sns>178924781</ns1:Num_Cartao_Sns>
</BS_getUtenteFromRNUIntoUPIPProcessRequest>
</part>
</Invoke_BS_getUtenteFromRNUIntoUpip_InputVariable>
</input>
<fault>
<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
<part name="summary">
<summary>when invoking locally the endpoint
'http://www:80/orabpel/develop/BS_getUtenteFromRNUIntoUPIP/1.0',
; nested exception is:
javax.resource.ResourceException:
RollbackException: Transaction has been marked for
rollback: Timed out</summary>
</part>
<part name="detail">
<detail>javax.resource.ResourceException:
RollbackException: Transaction has been marked for
rollback: Timed out</detail>
</part>
</remoteFault>
</fault>
</messages>
</details>
</event>
<event sid="BpSeq2.6" cat="2" type="4" wikey="23338496-BpInv0-BpSeq2.6-2"
label="Invoke_BS_getUtenteFromRNUIntoUpip" n="10"
date="2008-10-23T14:45:54.824+01:00">
<message>"{http://schemas.oracle.com/bpel/extension}remoteFault" has been
thrown.</message>
<details>
<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
<part name="summary">
<summary>when invoking locally the endpoint
'http://www:80/orabpel/develop/BS_getUtenteFromRNUIntoUPIP/1.0',
; nested exception is: javax.resource.ResourceException:
RollbackException: Transaction has been marked for
rollback: Timed out</summary>
</part>
<part name="detail">
<detail>javax.resource.ResourceException: RollbackException:
Transaction has been marked for rollback: Timed out</detail>
</part>
</remoteFault>
</details>
</event>
<event sid="BpSeq2.6" cat="1" type="2" n="11"
date="2008-10-23T14:45:54.824+01:00">
<message>cl</message>
</event>
<event sid="BpCAl0.7" cat="1" type="2" label="catchAll" n="12"
date="2008-10-23T14:45:54.824+01:00" psid="BpScp0.4">
<message>cr</message>
</event>
<event sid="BpSeq1.8" cat="1" type="2" label="sequence" n="13"
date="2008-10-23T14:45:54.824+01:00" psid="BpCAl0.7">
<message>cr</message>
</event>
<event to="outputVariable" sid="BpSeq1.8" cat="2" type="1"
wikey="23338496-BpAss0-BpSeq1.8-1" label="Assign_Output" n="14"
date="2008-10-23T14:45:54.825+01:00">
<message>Updated variable "outputVariable"</message>
<details>
<outputVariable>
<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
name="payload">
<BS_Insert_Upip_DataProcessResponse xmlns="http://xmlns.oracle.com/BS_Insert_Upip_Data">
<Result_Code>-1</Result_Code>
<Result_Msg/>
</BS_Insert_Upip_DataProcessResponse>
</part>
</outputVariable>
</details>
</event>
<event to="outputVariable" sid="BpSeq1.8" cat="2" type="1"
wikey="23338496-BpAss0-BpSeq1.8-1" label="Assign_Output" n="15"
date="2008-10-23T14:45:54.825+01:00">
<message>Updated variable "outputVariable"</message>
<details>
<outputVariable>
<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
name="payload">
<BS_Insert_Upip_DataProcessResponse xmlns="http://xmlns.oracle.com/BS_Insert_Upip_Data">
<Result_Code>-1</Result_Code>
<Result_Msg>[BS_Insert_Upip_Data] Erro a Executar o
BS_getUtenteFromRNUIntoUPIP.</Result_Msg>
</BS_Insert_Upip_DataProcessResponse>
</part>
</outputVariable>
</details>
</event>
<event sid="BpSeq1.8" cat="2" type="2" wikey="23338496-BpRpl0-BpSeq1.8-2"
label="Reply_Output" n="16" date="2008-10-23T14:45:54.825+01:00">
<message>Reply to partner "client".</message>
<details>
<outputVariable>
<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
name="payload">
<BS_Insert_Upip_DataProcessResponse xmlns="http://xmlns.oracle.com/BS_Insert_Upip_Data">
<Result_Code>-1</Result_Code>
<Result_Msg>[BS_Insert_Upip_Data] Erro a Executar o
BS_getUtenteFromRNUIntoUPIP.</Result_Msg>
</BS_Insert_Upip_DataProcessResponse>
</part>
</outputVariable>
</details>
</event>
</audit-trail>

We have tested this same scenario for several services and are experiencing the same result... timing out instead of returning the fault. This is a critical issue for us and would prevent us from implementing this software.

Similar Messages

  • BPEL process times out when SOAP-ENV:Fault is received from service.

    Hi - I have a BPEL process identical to one in 10.1.2.0.2. If I execute the same test, the BPEL console displays the following on the console for version 10.1.2.0.2.
    <Response>Clientwhen invoking endpointAddress 'http://galileo.wlgore.com:5555/soap/default', [ISS.0088.9134] Exception occurred while processing the body of the messageAxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client faultSubcode: faultString: [ISS.0088.9134] Exception occurred while processing the body of the message faultActor: http://galileo.wlgore.com:5555/soap/default faultNode: faultDetail: {http://www.webMethods.com/2001/10/soap/encoding}exception: <className>com.wm.pkg.art.error.DetailedServiceException</className>
         <message lang="">[ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service GORE_DSI_Services.AdaptorService:WorkOrderCompletion. BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. javax.resource.ResourceException: BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplateImpl.execute(BSFNExecuteTemplateImpl.java:306) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplate.execute(BSFNExecuteTemplate.java:134) at com.wm.adk.cci.interaction.WmInteraction.execute(WmInteraction.java:70) at com.wm.pkg.art.ns.AdapterServiceNode.invokeService(AdapterServiceNode.java:596) at com.wm.pkg.art.ns.ARTNSService.baseInvoke(ARTNSService.java:47) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:155) at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:324) at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:580) at com.wm.lang.flow.FlowState.step(FlowState.java:438) at com.wm.lang.flow.FlowState.invoke(FlowState.java:403) at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1749) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:113) at com.wm.app.b2b.server.Service.doInvoke(Service.java:607) at com.wm.app.b2b.server.Service.doInvoke(Service.java:556) at wm.server.soap.envelope(soap.java:98) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:287) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:128) at com.wm.app.b2b.server.HTTPSOAPHandler._process(HTTPSOAPHandler.java:457) at com.wm.app.b2b.server.HTTPSOAPHandler.process(HTTPSOAPHandler.java:111) at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:298) at com.wm.util.pool.PooledThread.run(PooledThread.java:105) at java.lang.Thread.run(Thread.java:534) </message>
    </Response>
    With this version, however, we either receive "java.lang.IllegalStateException: "Cannot call setRollbackOnly() current thread is NOT associated with a transaction" or a timeout error.
    I captured the return message from both servers and it is identical (shown below):
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema">
         <SOAP-ENV:Body>
              <SOAP-ENV:Fault>
                   <faultcode>SOAP-ENV:Client</faultcode>
                   <faultstring>[ISS.0088.9134] Exception occurred while processing the body of the message</faultstring>
                   <faultactor>http://galileo.wlgore.com:5555/soap/default </faultactor>
                   <detail xmlns:webM="http://www.webMethods.com/2001/10/soap/encoding">
                        <webM:exception>
                             <webM:className>com.wm.pkg.art.error.DetailedServiceException</webM:className>
                             <webM:message xml:lang="">="">[ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service GORE_DSI_Services.AdaptorService:WorkOrderCompletion. BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. javax.resource.ResourceException: BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplateImpl.execute(BSFNExecuteTemplateImpl.java:306) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplate.execute(BSFNExecuteTemplate.java:134) at com.wm.adk.cci.interaction.WmInteraction.execute(WmInteraction.java:70) at com.wm.pkg.art.ns.AdapterServiceNode.invokeService(AdapterServiceNode.java:596) at com.wm.pkg.art.ns.ARTNSService.baseInvoke(ARTNSService.java:47) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:155) at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:324) at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:580) at com.wm.lang.flow.FlowState.step(FlowState.java:438) at com.wm.lang.flow.FlowState.invoke(FlowState.java:403) at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1749) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:113) at com.wm.app.b2b.server.Service.doInvoke(Service.java:607) at com.wm.app.b2b.server.Service.doInvoke(Service.java:556) at wm.server.soap.envelope(soap.java:98) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:287) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:128) at com.wm.app.b2b.server.HTTPSOAPHandler._process(HTTPSOAPHandler.java:457) at com.wm.app.b2b.server.HTTPSOAPHandler.process(HTTPSOAPHandler.java:111) at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:298) at com.wm.util.pool.PooledThread.run(PooledThread.java:105) at java.lang.Thread.run(Thread.java:534)</webM:message>
                        </webM:exception>
                   </detail>
              </SOAP-ENV:Fault>
         </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    Thanks,
    RM

    We have tested this same scenario for several services and are experiencing the same result... timing out instead of returning the fault. This is a critical issue for us and would prevent us from implementing this software.

  • BPEL Processes are Hanging.......

    Hi,
    I am using BPEL 10.1.2.0.2 version. The logic am implementing in BPEL process is a frontend application will invoke BPEL process.BPEL will take some inputs from frontend and invokes a procedure in database using DbAdapter.BPEL will pull the output of the procedure and will pass the same to Frontend.
    The logic being implemented in procedures is select and update depends on the requirement.
    We completed our development and moved to UAT and everything is running fine.From past one week we are facing a problem that BPEL processes are hanging when they are invoked both from BPEL console and Frontend. The process neither displaying any output nor throwing any exception.
    After bouncing the BPEL servers everything is coming to normal.I didn't found any error log in both domain.log and OraBPEL~OC4j_BPEL~default_island.log files.
    Our BPEL Environment has 2 BPEL Mid Tiers connected via a loadbalancer
    whether it could be related to cache size or datasource connections ????
    Please suggest what could be the problem...........
    Thanks
    Chandra

    Check the timeouts on the firewalls. Also look at Dead Connection Detection (DCD) on the database server. You will need to turn on your DCD to keep your JDBC connections alive.
    Pete

  • In-Flight BPEL Process Instances not getting Completed

    Hi,
    I have BPEL P.M. 10.1.3.1.0 running. In BPEL Console I can see few process in
    In-Flight BPEL Process Instances section. But in realty those process should be in completed section. When I login as bpeladmin in worklist application, I see those process are in completed status.
    What can be issue? Any one come across this? Any patch available from metalink to resolve this?
    Need help resolving this issue.
    Regards,
    Jigar

    I see this too sometimes. In my case it's mostly due to the fact that the first activity that takes places after the callback fails. E.g. a transform that fails with a type error.
    Check the bpel domain log file to find any errors in your bpel that's receiving the callback. There's probably something wrong with an assign or transform there.
    The domain logfile can be found @: $ORACLE_HOME/bpel/domains/<your_domain>/logs/domain.log
    HTH,
    Bas

  • BPEL process instance getting created twice

    Hi,
    We have B2B - BPEL integration developed using AQ and we are using this for importing 850 Purchase Orders. It is a simple flow involving dequeuing 850 transaction message by the AQ adapter and processing the message through Receive, Transform and Invoke activities to invoke a PL/SQL procedure to insert data into the Order Management Open Interface tables.
    The issue we are facing is that the BPEL process instance is getting generated twice resulting in duplicate rows in the interface tables.
    Please if any one faced this kind of issue, let me know the solution.
    Regards,
    Balu

    This issue is closed. We were able to identify to cause for the issue. The EDI document came in with two POs which generated two separate messages.

  • BPEL Console In-Flight BPEL Process Instances

    Hi!
    We are using BPEL Console 10.1.3.4.0 to monitor all BPEL Processes, but we cannot see any In-Flight BPEL Process Instances in the Dashboard.
    Can anybody tell me what's wrong
    Thanks in advance!
    /Nick

    So, you have BPEL flows that are starting and completing, but do you have any flows that you think will run long enough for you to see them on In-flight section of the dashboard.
    In our project, the only flows that I typically see there are flows that are waiting on a receive, or on a "wait activity", other flows synchronous/asynchronous do not execute for long enough for them to be visable as being in-flight, unless I 'catch' then just after they have started.

  • Process chain hangs when reaching AND process before Attribute Change Run

    Hi Experts,
    I have the following problem. For some reason my master data attribute process chain hangs when it reaches the AND process variant right before the Attribute Change Run. It does not go anywhere from that point.
    Thank you

    hi AG,
    if this is hanging daily at the same place without proceeding further, and with out giving the instance for the same. then the better way is to replace that AND process in the chain with the new AND process. and then check and activate ur chain. this wil solve ur problem.
    if this is the first time that happend to u, then check the previous load status, if any of the load has failed and u didnt turned the status of the process then also this can happen. So please do check it and act accordingly. If u cannt find the resolution then please run ur changerun manually.
    u can use RSPC_PRCESS_FINISH FM to convert the status of any process. for this u need to give instance and variant details. and then if u execute, then chain will continue further.
    Hope this will help you.
    thanks
    Vishnu

  • Error in posting message to BPEL process instance

    Hi
    There is following Error associated with BPEL Process while invoking another BPEL Process called-Request For Invoice Information The SOA Server Log associated with this error is as follows-
    [2012-11-06T10:08:37.157+05:30] [soa_server1] [ERROR] [] [oracle.soa.services.workflow.task] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 74be42f58e7a71c3:-749bd11d:13abbc92686:-8000-000000000000c717,1:31260] [APP: soa-infra] <.> Error in posting message to BPEL process instance.[[
    Error in posting message to BPEL process instance 200458 for callback operation onTaskCompleted. The task is associated with workflow default/RequestForInvoiceInformation!1.0/RequestForInvoiceInformationHumanTask.
    This could be caused if the BPEL instance is terminated. If it is not, this is possibly a system error.
    ORABPEL-30015
    Error in posting message to BPEL process instance.
    Error in posting message to BPEL process instance 200458 for callback operation onTaskCompleted. The task is associated with workflow default/RequestForInvoiceInformation!1.0/RequestForInvoiceInformationHumanTask.
    This could be caused if the BPEL instance is terminated. If it is not, this is possibly a system error.
         at oracle.bpel.services.workflow.task.impl.WorkflowCallback.onTaskComplete(WorkflowCallback.java:113)
         at oracle.bpel.services.workflow.task.impl.TaskService.invokeCallbacks(TaskService.java:6911)
         at oracle.bpel.services.workflow.task.impl.TaskService.performPostActionOperation(TaskService.java:7628)
         at oracle.bpel.services.workflow.task.impl.TaskService.localHandleRoutingSlipInterpretationResult(TaskService.java:3564)
         at oracle.bpel.services.workflow.task.impl.TaskService.handleRoutingSlipInterpretationResult(TaskService.java:3688)
         at oracle.bpel.services.workflow.task.impl.TaskService.evaluateRoutingSlipTaskAssignment(TaskService.java:3490)
         at oracle.bpel.services.workflow.task.impl.TaskService.updateTaskOutcomeAndEvaluateRoutingSlip(TaskService.java:3445)
         at oracle.bpel.services.workflow.task.impl.TaskService.updateTaskOutcome(TaskService.java:3153)
         at oracle.bpel.services.workflow.task.impl.TaskService.updateTask(TaskService.java:2011)
         at sun.reflect.GeneratedMethodAccessor1826.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
         at java.lang.reflect.Method.invoke(Method.java:601)
         at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
         at oracle.bpel.services.workflow.common.WorkflowServiceCacheEventAdvice.invoke(WorkflowServiceCacheEventAdvice.java:91)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at oracle.bpel.services.workflow.test.workflow.ExceptionTestCaseBuilder.invoke(ExceptionTestCaseBuilder.java:155)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at oracle.bpel.services.common.dms.MethodEventAspect.invoke(MethodEventAspect.java:70)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at oracle.bpel.services.common.dms.MethodPhaseEventAspect.invoke(MethodPhaseEventAspect.java:82)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
         at $Proxy246.updateTask(Unknown Source)
         at oracle.bpel.services.workflow.task.ejb.TaskServiceBean.updateTask(TaskServiceBean.java:214)
         at sun.reflect.GeneratedMethodAccessor1825.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
         at java.lang.reflect.Method.invoke(Method.java:601)
         at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.oracle.pitchfork.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:34)
         at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
         at com.oracle.pitchfork.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:42)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
         at $Proxy307.updateTask(Unknown Source)
         at oracle.bpel.services.workflow.task.ejb.TaskServiceBean_399vcw_EOImpl.__WL_invoke(Unknown Source)
         at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
         at oracle.bpel.services.workflow.task.ejb.TaskServiceBean_399vcw_EOImpl.updateTask(Unknown Source)
         at oracle.bpel.services.workflow.task.ejb.TaskServiceBean_399vcw_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: java.lang.NullPointerException
         at oracle.fabric.CubeServiceEngine.post(CubeServiceEngine.java:626)
         at oracle.integration.platform.blocks.mesh.AsynchronousMessageHandler.doCallbackPost(AsynchronousMessageHandler.java:76)
         at oracle.integration.platform.blocks.mesh.MessageRouter.post(MessageRouter.java:195)
         at oracle.integration.platform.blocks.mesh.MeshImpl.post(MeshImpl.java:215)
         at sun.reflect.GeneratedMethodAccessor1589.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
         at java.lang.reflect.Method.invoke(Method.java:601)
         at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
         at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
         at $Proxy310.post(Unknown Source)
         at oracle.bpel.services.workflow.fabric.WorkflowServiceEngine.postToMesh(WorkflowServiceEngine.java:1560)
         at oracle.bpel.services.workflow.fabric.WorkflowServiceEngine.doCallback(WorkflowServiceEngine.java:1683)
         at oracle.bpel.services.workflow.task.impl.WorkflowCallback.postToFabric(WorkflowCallback.java:346)
         at oracle.bpel.services.workflow.task.impl.WorkflowCallback.onTaskComplete(WorkflowCallback.java:109)
         ... 58 more
    Thanks
    Snehal

    The log entry shows that user : WALMART is missing on your user-properties.xml file.
    Please check that you have this user properly configured with jazn. Which version of BPEL you are using and what are the changes you are trying to do to the deployed project ?

  • API / Webservice to access the state information of a bpel process instance

    Hi,
    i have a question about the ccBPM runtime API.
    Is there a API or Webservice provided by SAP XI/PI, which accesses the state information of a bpel process instance.
    "access" means:
    1. At which activity is the current process instance located
    2. Access to the context information of the process
    Thanks and best regards
    Di

    Hi Swarup,
    Thanks for your quick reply.
    I designed a simple BPM process with less than 10 activities. To monitor the process running state i want to build a small AddOn instead of using the standard xi monitoring tool because of its complexibility.
    Thus i am looking for some useful informations about a api or webservice provided direktly by sap, which enables me to access (read only) the state information of a process instance. for exmaple at which activity is the current process instance located?
    Best regards
    Di

  • How to update the payload of a BPEL process instance

    Hi I have another question.
    How do I update the payload of a BPEL process instance without the activity being a Human Task. I know there are ton's of example showing how to update the payload of a user task using BPEL API's. But in my case I need to update the payload of a BPEL process instance which has no human task.

    Thanks
    For confirming that the payload in the BPEL process instance is read-only. Now I can see what alternatives I come up with besides the DB save option.
    Guys if you can take the time to answer/comment on another question I have posted in this forum that will be great
    here is the link
    Multi step Human Task
    Regards,
    Jayesh Nazre
    MCSD, MCSE, SCJP, PMP

  • How to handle no of BPEL process Instances

    Hi,
    I am facing issue at my cleint. Here is the scenario
    1) I have Business Event
    2) BPEL is subscribed to event using Oracle Application Adapter
    3) No every time new message comes in queue, causes new BPEL process Instances
    4) So suppose there are 1 million message per day then BPEL Server is dying.
    What is the best way to handle it?

    This is managed via the dspMaxThreads and ReceiverThreads parameters, by default these are set to poor values, dspMaxThreads by default is set to 100 (domain level) whereas by default ReceiverThreads is set to 40. According to the performance guide the total of dspMaxThreads for all domains should be <= ReceiverThreads, so making some adjustment to the dspMaxThreads parameter should help.

  • When is an BPEL process instance created? Multiple creations?

    Assume I have a BPEL process which a
    RECEIVE at first, then some assignments and finally a PICK.
    In the first RECEIVE and the later PICK I can enable the checkbox
    "create instance". What is the difference?
    When I call the BPEL process from the BPEL console it is instanciated. Ok.
    But what happens if the workflow arrives at the PICK?
    Is it instantiated again?
    How comes?
    Similar question: Assume I disable "create instance" in the first RECEIVE
    and enable it only in the later PICK. Does the BPEL process start only
    from the PICK stage and disregard the preceeding commands ?
    Peter

    Hi,
    The createInstance flag tells the bpel engine it has to create a new instance of this process, and not to correlate the message to a created bpel instance.
    If you insert a pick with createInstance attribute, your process will be hang for ever. You won't be able to send a valid message to you pick since all your messages will go to the first receive activity.
    For your other question, activities other than start activities (scope,sequence, empty, receive, pick) must not be performed before start activities.
    The bpel process should not even build since all your previous activities won't be after a start activity (except if these are <empty> ...).
    Raphaƫl
    http://bpelsoa.blogspot.com

  • Avoid persistent faulted BPEL process instances in database

    Hello All,
    I have a doubt relative to Memory Optimization, I've configured a BPEL process like a transient process using these lines:
    <property name="bpel.config.inMemoryOptimization">true</property>
    <property name="bpel.config.completionPersistPolicy">off</property>
    My problem starts when I have a faulted instance, because this instance creates a row in the CUBE_INSTANCE table in the database and I have the requiriment of avoid persistent instances in datase.
    If I change the the value of completionPersistPoliciy property to fault, the behaviour is the same...
    <property name="bpel.config.inMemoryOptimization">true</property>
    <property name="bpel.config.completionPersistPolicy">faulted</property>
    Anybody knows how to avoid persistent faulted instances?
    Thanks in advance,
    Edited by: luismiguelfdez on Mar 26, 2012 1:59 AM

    When an unhandled fault happens regardless of these flags, bpel will persist the audit information for the instance, so cube_instance table has a record and EM could show this in meaningful way.
    Docs should be updated in SOA PS5(11.1.1.6.0) release with above information.

  • How does a BPEL process instance know it has been cancel()ed?

    The javadoc for the IInstanceHandle cancel() method says, "When an activity is cancelled, the performer of the activity is notified of the cancellation and is given an opportunity to rollback or cancel any work that has already been done on behalf of the activity."
    How exactly is the performer of the activity notified? Some kind of fault? Can one code a "cancel handler" in the BPEL process, or is the "rollback or cancel" all done behind the scenes?
    Either a full answer or a pointer to the appropriate documentation (which I haven't yet been able to find) would be fine. Thanks.

    The BPEL instance can be canceled via the BPEL API or via console (Abort instance) or due to an error. Then the BPEL Process Manager will detect this and cancel the running instance. The instance will do a transaction rollback, depending if it was a global (XA) or local transactions. This whole mechanism is executed behind the scenes.
    Marc

  • BPEL process instance not created - Error

    I have a BPEL Process that was working fine until I added a couple of sequence activities and I think thats when this problem started. Its wierd.
    I have an XML fragment assigned to a variable and when I add a sequence and deploy it, it creates an instance but gives me the XML value error which is because of the whitespaces it adds in the bpel source. I then remove the whitespaces and deploy it. It doesn't create and instance. I add the whitespaces in and deploy it, instance gets created and gives me an error message, but when I fix the whitespaces and deploy it, instance doesn't get cretaed and I see the below message in the domain.log.
    Also when I try to create an instance from the BPEL console it gives me a message saying 'Instance is being cretaed asynchronously'. My process is not an asynchronous process. I'm not sure what is happening.
    ORABPEL-05002
    Message handle error.
    An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
         java.lang.Exception: No Exception - originate from:
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:152)
         at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
         at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
         at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
         at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
         at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
         at java.lang.Thread.run(Thread.java:534)
    Appreciate all your help.
    Thanks
    -Prapoorna

    If you try what Anirudh suggested you may be able to get some more information.
    I am guessing the problem is with the second operation of your web service. You can try throwing a try / catch any exception (bad standards, but sometimes useful for tracking down a problem) in your web service function and returning the exception values.
    You can also try throwing a catchall in your BPEL process and use ora:getFaultAsString() to receive the error message. If you are using 10.1.3.1 this requires patch 5672007

Maybe you are looking for