Publish Engineering Change Order Throws Com.Oracle.Bpel.Client.Delivery.Receivetimeoutexception with R12 E-Business Suite

(Doc ID 1194129.1)

Last updated on MARCH 08, 2017

Applies to:

Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite - Version 2.5 to 11.1 [Release 2.5 to 11.1]
Information in this document applies to any platform.

Symptoms

When running the "Publish Engineering Change Order Updates" process to send ECO changes back to Agile, the request errors out with no obvious message in the concurrent request log. However, if we look at the BPEL domain.log, we see that it is throwing the execption:

<2010-07-30 12:59:10,465> <WARN> <wsif> WSIF0012W: Default port used for '{http://xmlns.oracle.com/EnterpriseServices/Core/EngineeringChangeOrder/V1}ESB_EngineeringChangeOrderEBS_Service' is not fixed depending on port names
<2010-07-30 12:59:49,190> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "delivery": Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.
com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.
at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:109)
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:592)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
at com.evermind.server.ThreadState.runAs(ThreadState.java:693)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:3
..
at java.lang.Thread.run(Thread.java:595)
Caused by: com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.
at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:576)
at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:465)
at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:134)
at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:95)
... 47 more



Additionally, the process instances in the BPEL console seems to be stuck waiting on the response from "UpdateECOEbizReqABCSImpl-ECOEBS".

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms