Time out error on Receiver adapter : Sync application request expired

Hi ,
I am getting the following error in the Audit log of the Adapter Engine . The scenario is a sync BPM scenario.
It is a receiver adapter which is connecting to a NON SAP System.
Delivering the message to the application using connection tc_adapter_http://ecs.com/pi/ERPXPDM_4_TCENT failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Sync application request expired.. Setting message to status failed.
The messages have failed status. The error occured only once and did not get repeated.
Please help me in finding the cause of the same.
I think it is due to the Non sap system not responding at that particular instance. Please clarify.
regards,
Yashwanth.

Refer these-
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747?quicklink=index&overridelayout=true
/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi (Refer the Note section)
http://help.sap.com/saphelp_nw04s/helpdata/en/ca/7c5c41fe06cf1ee10000000a155106/content.htm

Similar Messages

Sync application request expired

Delivering the message to the application using connection ZENGIN_http://cresco-es.co.jp/sap/xi/adapter/zengin failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Sync application request expired.. Setting message to status failed.
getting the above error.
using zengin we are getting the data into sap through PI.

Hi,
Even then if you want , you can increase in production it will just ask for one RFC adapter service to restart and takes only 10-20 sec to restart.
Thanks!

MessageExpiredException: Sync application request expired..

Hi,
we are calling a SOAP HTTP AXIS receiver (web service) HTTP. Sometimes the service providers request
takes 3 minutes to reply and we get the following exception :
com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Sync application request expired.. Setting message to status failed.
I've set timeout parameter to 300000 milliseconds for parameter timeout of AF_Adapters/axis/AFAdapterBean but the timeout is still less... is there another place I need to increase the timeout.
Thanks.
Thierry

Your guess is as good as mine, but the question to answer here is, why is the response taking 3 minutes. If this is by design, then you may want to look at the design and see if asynchronous messaging works better for you. Playing with timeout will only lead you to a point but with 3 minutes of delay in a synchronous service is simply unacceptable even if there is no human being on the consumer side.
Thanks
KK

Time out error in receiver soap adapter

Hi,
My scenario is file to soap file with out BPM.I am using a currency converter wsdl.
I am getting a time out error in soap receiver channel.
Do i need to change the time out parameter?Where do i change that?Please help me to solve it out.
Following are the errors in the soap communication channel.
SOAP: call failed: java.net.ConnectException: Connection timed out
SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Connection timed out: java.net.ConnectException: Connection timed out
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connection timed out: java.net.ConnectException: Connection timed out
Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Connection timed out: java.net.ConnectException: Connection timed out. Setting message to status failed.
Regards
Divia

Hi Prateek,
Thanks for your replay. I am able to open the URL from XI/PI.
I tried by testing the same URL by using XI 3.0, its working fine and i am getting required data, but in PI 7.1 i am getting an error.
Error is:
In MONI:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection refused: connect
In RWB:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect
What could be the reason?
Regards,
Venu

Time-out error in DB adapter

Hi,
I am getting the following error in my bpel process.
Non Recoverable System Fault :
Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'merge' failed due to: DBWriteInteractionSpec Execute Failed Exception. merge failed. Descriptor name: [InsertHeader_MTMS.Erpo2027H]. Caused by java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 299 seconds BEA1-08880C41104C3DCB072F at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1523) at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1415) at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:438) at weblogic.jdbc.jta.DataSource.connect(DataSource.java:395) at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:355) at oracle.toplink.jndi.JNDIConnector.connect(JNDIConnector.java:123) at oracle.toplink.jndi.JNDIConnector.connect(JNDIConnector.java:84) at oracle.toplink.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:153) at oracle.toplink.internal.databaseaccess.DatasourceAccessor.connectInternal(DatasourceAccessor.java:273) at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connectInternal(DatabaseAccessor.java:230) at oracle.toplink.internal.databaseaccess.DatasourceAccessor.reconnect(DatasourceAccessor.java:478) at oracle.toplink.internal.databaseaccess.DatabaseAccessor.reconnect(DatabaseAccessor.java:1342) at oracle.toplink.internal.databaseaccess.DatasourceAccessor.incrementCallCount(DatasourceAccessor.java:251) at oracle.toplink.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:511) at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:467) at oracle.toplink.threetier.ServerSession.executeCall(ServerSession.java:447) at oracle.toplink.internal.sessions.IsolatedClientSession.executeCall(IsolatedClientSession.java:117) at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:193) at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:179) at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.selectOneRow(DatasourceCallQueryMechanism.java:603) at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectOneRowFromTable(ExpressionQueryMechanism.java:2526) at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectOneRow(ExpressionQueryMechanism.java:2496) at oracle.toplink.queryframework.ReadObjectQuery.executeObjectLevelReadQuery(ReadObjectQuery.java:424) at oracle.toplink.queryframework.ObjectLevelReadQuery.executeDatabaseQuery(ObjectLevelReadQuery.java:874) at oracle.toplink.queryframework.DatabaseQuery.execute(DatabaseQuery.java:674) at oracle.toplink.queryframework.ObjectLevelReadQuery.execute(ObjectLevelReadQuery.java:835) at oracle.toplink.queryframework.ReadObjectQuery.execute(ReadObjectQuery.java:397) at oracle.toplink.queryframework.ObjectLevelReadQuery.executeInUnitOfWork(ObjectLevelReadQuery.java:899) at oracle.toplink.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2741) at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1079) at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1063) at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1022) at oracle.tip.adapter.db.DBInteraction.executeOutboundWrite(DBInteraction.java:983) at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:232) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.executeJcaInteraction(JCAInteractionInvoker.java:302) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeJcaReference(JCAInteractionInvoker.java:518) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeAsyncJcaReference(JCAInteractionInvoker.java:501) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAEndpointInteraction.performAsynchronousInteraction(JCAEndpointInteraction.java:479) at oracle.integration.platform.blocks.adapter.AdapterReference.post(AdapterReference.java:235) at oracle.integration.platform.blocks.mesh.AsynchronousMessageHandler.doPost(AsynchronousMessageHandler.java:142) at oracle.integration.platform.blocks.mesh.MessageRouter.post(MessageRouter.java:194) at oracle.integration.platform.blocks.mesh.MeshImpl.post(MeshImpl.java:204) at sun.reflect.GeneratedMethodAccessor1865.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:296) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:177) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144) at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy185.post(Unknown Source) at oracle.fabric.CubeServiceEngine.postToMesh(CubeServiceEngine.java:770) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:251) at com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke(InvokeHandler.java:1009) at com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke(InvokeHandler.java:512) at com.collaxa.cube.engine.ext.common.InvokeHandler.handle(InvokeHandler.java:123) at com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:63) at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseBPELActivityWMP.java:157) at com.collaxa.cube.engine.CubeEngine._performActivity(CubeEngine.java:2585) at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2444) at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1121) at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:73) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220) at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:322) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4497) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4428) at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:685) at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:682) at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:356) at sun.reflect.GeneratedMethodAccessor1911.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) 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.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104) at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:88) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413) at oracle.security.jps.wls.JpsWeblogicEjbInterceptor.runJaasMode(JpsWeblogicEjbInterceptor.java:61) at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:106) at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:105) at sun.reflect.GeneratedMethodAccessor801.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) at com.bea.core.repackaged.springframework.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69) 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.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37) at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:55) at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50) 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 $Proxy172.handleInvoke(Unknown Source) at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.java:241) at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:35) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:142) at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:82) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: weblogic.transaction.TimedOutException: Transaction timed out after 299 seconds BEA1-08880C41104C3DCB072F at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1521) ... 109 more . ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
My BPEL is
Gettingfile(using FTP adapter)-->Using the flow activity,i am inserting data into two different tables using two database adapter.In one db adapter,operation is Insert or merge and for the 2nd db adapter operation is 'Insert' only.
Please help me on this!!

Thanks Ajay!!!
My file contains around 3000 records.Is that a problem?
my Requirement-->
BPEL will read a file which contains Header table and line table records(sales order).While inserting,BPEL should insert Header records to header table and lines records to line table.So I am using two DB adapters one for Header and other one for Lines table.
For Header DB adapter I am using Merge operation and Lines table DB adapter I am using Insert opertaion.
File Content which BPEL will read is contains the records as follows:
ORDER_NUMBER~REQUEST_DATE~SOLD_TO_ORG_ID~CUST_PO_NUMBER~SHIP_FROM_ORG_ID~CUSTOMER_NAME~SHIP_TO_ADDRESS1~SHIP_TO_ADDRESS2~SHIP_TO_CITY~SHIP_TO_POSTAL_CODE~SHIP_TO_STATE~SHIPPING_METHOD_CODE~FREIGHT_TERMS_CODE~SHIPPING_INSTRUCTIONS~PACKING_INSTRUCTIONS~HEADER_ID~LINE_NUMBER~INVENTORY_ITEM_ID~ORDERED_QUANTITY~UNIT_SELLING_PRICE~HEADER_STATUS~LINE_STATUS~LINE_REUEST_DATESCHEDULE_SHIP_DATELINE_SHIP_FROM_ORG_ID~OPERATING_UNIT~CUSTOMERNAME
41100016~2010-10-06~1040~12214124ASAFAS~97~Finance Test~Test Address 1-WHD~Test Address 2-WHD~Hyderabad~~AP~~PREPAID AND CHARGE~~~1724~1~509501~1~60~A~A~2010-10-06~2010-10-18~01~WHD~
41100017~2010-06-08~1040~214145566~97~Finance Test~1100 Abernathy Road~~Atlanta~30328~GA~000001_AACT_L_LTL~PREPAID AND CHARGE~~~1726~1~ITEM1~1~1241~A~A~2010-06-08~2010-06-10~01~WHD~
41100025~2010-06-17~1100~test-13234~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2350~1~419473~1~999.18~A~A~2010-06-17~2010-06-17~02~WHD~
41100026~2010-06-17~1100~test-132341~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2356~1~419473~1~999.18~A~A~2010-06-17~2010-06-17~02~WHD~
41100027~2010-06-17~1100~TEST2221~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2360~1~419473~1~999.18~A~A~2010-06-17~2010-06-17~02~WHD~
41100028~2010-06-17~1100~test123~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2362~1~419466~1~999.18~A~A~2010-06-17~2010-06-17~02~WHD~
41100029~2010-06-17~1100~TEST2222~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2369~1~419473~1~999.18~A~A~2010-06-17~2010-06-17~02~WHD~
41100030~2010-06-17~1100~test12345~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2371~1~419473~1~999.18~A~A~2010-06-17~2010-06-17~02~WHD~
41100030~2010-06-17~1100~test12345~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2371~2~419466~1~999.18~A~A~2010-06-17~2010-06-17~02~WHD~
41100031~2010-06-17~1100~test123456~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2378~1~419473~1~999.18~A~A~2010-06-17~2010-06-17~02~WHD~
41100031~2010-06-17~1100~test123456~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2378~2~419466~1~999.18~A~A~2010-06-17~2010-06-17~02~WHD~
41100032~2010-06-17~1100~testetetet~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2382~1~419473~1~999.18~A~A~2010-06-17~2010-06-17~02~WHD~
41100032~2010-06-17~1100~testetetet~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2382~2~419466~1~999.18~A~A~2010-06-17~2010-06-17~02~WHD~
41100033~2010-06-17~1100~test1234566~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2391~1~419473~1~999.18~A~A~2010-06-17~2010-06-17~02~WHD~
41100033~2010-06-17~1100~test1234566~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2391~2~419466~1~999.18~A~A~2010-06-17~2010-06-17~02~WHD~
41100034~2010-06-17~1100~test1234567~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2398~1~419473~1~999.18~A~A~2010-06-17~2010-06-17~02~WHD~
41100034~2010-06-17~1100~test1234567~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2398~2~419466~1~999.18~A~A~2010-06-17~2010-06-17~02~WHD~
41100035~2010-06-17~1100~test12345678~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2401~1~419473~1~999.18~A~A~2010-06-17~2010-06-17~02~WHD~
41100035~2010-06-17~1100~test12345678~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2401~2~419466~1~999.18~A~A~2010-06-17~2010-06-17~02~WHD~
41100022~2010-06-10~1040~123~~Finance Test~1100 Abernathy Road~~Atlanta~30328~GA~000001_BESTWAY_T_STANDARD~PREPAID AND CHARGE~~~1852~1~1125-001~10~100~A~A~2010-06-10~2010-06-10~01~WHD~
41100037~2010-06-18~1100~test12345678~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2490~1~419473~1~999.18~A~A~2010-06-18~2010-06-18~02~WHD~
41100037~2010-06-18~1100~test12345678~100~MENARDS~101 Main~~Atlanta~30328~GA~~PREPAID~~~2490~2~419466~1~999.18~A~A~2010-06-18~2010-06-18~02~WHD~
41100038~2010-06-18~1519~OTM Test -11~97~BLACK'S WHOLESALE~1200 Abernathy RD NE~~Atlanta~30328~GA~000001_USIT_T_STANDARD~PREPAID AND CHARGE~~~2544~2~594200~1~445.84~A~A~2010-06-18~2010-06-18~01~WHD~
41100040~2010-06-18~1519~OTM Test -15~97~BLACK'S WHOLESALE~1200 Abernathy RD NE~~Atlanta~30328~GA~000001_USIT_T_STANDARD~PREPAID AND CHARGE~~~2651~1~594200~1~445.84~A~A~2010-06-18~2010-06-18~01~WHD~
41100042~2010-06-18~1519~OTM Test -16~97~BLACK'S WHOLESALE~1200 Abernathy RD NE~~Atlanta~30328~GA~000001_USIT_T_STANDARD~PREPAID AND CHARGE~~~2660~1~594200~1~445.84~A~A~2010-06-18~2010-06-18~01~WHD~
41100043~2010-06-18~1519~OTM Test -17~97~BLACK'S WHOLESALE~1200 Abernathy RD NE~~Atlanta~30328~GA~000001_USIT_T_STANDARD~PREPAID AND CHARGE~~~2661~1~594200~1~445.84~A~A~2010-06-18~2010-06-18~01~WHD~
41100044~2010-06-18~1519~OTM Test -18~97~BLACK'S WHOLESALE~1200 Abernathy RD NE~~Atlanta~30328~GA~000001_USIT_T_STANDARD~PREPAID AND CHARGE~~~2664~1~594200~1~445.84~A~A~2010-06-18~2010-06-18~01~WHD~
41100045~2010-06-18~1519~OTM Test -18~97~BLACK'S WHOLESALE~1200 Abernathy RD NE~~Atlanta~30328~GA~000001_USIT_T_STANDARD~PREPAID AND CHARGE~~~2665~1~594200~1~445.84~A~A~2010-06-18~2010-06-18~01~WHD~
41100048~2010-06-19~6775~test-HD~97~THE HOME DEPOT~MERCH. #33292~112 BEN AVON HEIGHTS RD.~PITTSBURGH~15237~PA~~COLLECT~~~2877~1~320342~10~934.09~A~A~2010-06-19~2010-06-19~01~WHD~3558820
41100048~2010-06-19~6775~test-HD~97~THE HOME DEPOT~MERCH. #33292~112 BEN AVON HEIGHTS RD.~PITTSBURGH~15237~PA~~COLLECT~~~2877~2~494579~23~433.76~A~A~2010-06-19~2010-06-19~01~WHD~3558820
41100101~2010-06-21~6775~84021858~97~THE HOME DEPOT~MERCH #33292~1336 BRITOL PIKE~BENSALEM~19020~PA~~COLLECT~ MUST CALL 48 HOURS PRIOR TO DELIVERY . DEPT #26 RECEIVING DEPT SIGNATURE & DATE REQUIRED______________ DELIVERY TIME IS 17:00 NO DRIVERS ASSISTANCE REQUIRED~ MUST CALL 48 HOURS PRIOR TO DELIVERY . DEPT #26~3220~1~518336~2~248.53~A~A~2010-06-21~2010-06-21~01~WHD~3558256
41100146~2010-05-27~7225~074989~101~BUDGE-MCHUGH SUPPLY CO~124 WEST 4TH ST~~MEDFORD~975010000~OR~000001_BEST_L_LTL~PREPAID AND CHARGE~NO DRIVERS ASSISTANCE REQUIRED~~3265~1~579511~1~363~A~A~2010-06-09~2010-06-21~09~WHD~1007901
Please tell me how can i achieve this Master-Detail requirement,if Merger operation is failing.Now i am using empty BPEL process.
Edited by: DevD on Nov 2, 2010 9:10 PM

SoA Couldnt start- Time Out Error

Hi,
My oracle SOA version is 10.1.3.1. I have created a application ( say sampleApplication) in jdeveloper (webservice from wsdl). When deploying the application to the application server it takes a long time to complete (approx 30 mins) but it gets deployed without error. I got a perm gen error and I stopped the SOA. When started it again after incresing the perm gen size, the SOA couldnt start. Got the following error
<ERROR> <collaxa> <ProcessJob::execute> Attempt (1/15) ... failed to connect ... retrying in 5 seconds ...
<2009-09-11 17:55:13,130> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://myURl....
Maximum attempt of 15 was reached and the SOA failed to restart.
After playing around with the server.xml (trying to remove all application entries and adding it one by one) found that when i removed the sampleApplication's entry from server.xml and tried starting SOA , it worked and it Started fine.
Can any one point what might be the problem in my case.?
Thanks in advance..
(P.S: The other application deployed are developed in the same way as that of sampleApplication. So couldnt see any thing wrong with the sampleApplication. Other application entries in server.xml do not create this problem.)
Edited by: user8655700 on Sep 11, 2009 7:03 AM

Hi James,
Thank You for your suggestion. I have some doubts.
1) You suggested to revert back to old parameter and restart jDEV. What is the parameter i need to revert? I have only changed the max,min and perm size in opmn.xml because I keep getting perm gen error quite often. Did you mean those parameters ?
2)Restarting jDev will solve the issue of longer deployment time for applications. But when I restart the SOA itself, it fails to start.I get the Time out error. On removing the application which took longer time to deploy from server.xml, SOA starts without error. No other changes have been made. So the question is why is the application which is successfully deployed from jdeveloper like many other applications stopping the SOA to start.?
3)Or is the load during SOA startup is high, which results in it failing to start? If so how can I overcome this issue.
Thanks,
Ananth
Edited by: user8655700 on Sep 14, 2009 10:25 PM

Getting Time-Out Error in Sync-Async Bridge

Hi All,
My IP has a Sync-Async Bridge. I have a fork, two senders, two switchs and a transformation step inside the bridge.
If XI takes much time to process the IP, the send step that closes sync-async bridge is not waiting for the message after a particular period and throws time out error to the sender.
Is it possible to increase the waiting time for sync-async bridge?
This IP works correctly 8 out of 10 times. Sometimes the message is sitting permenantly in the queue(smq2) and gives me system failure error.
Can u tell me why this problem happening?
Thanks & Regards,
Senthil.

Dear Michal/Senthil,
Can you pl clear a confusion that i have had for ages...
suppose there is a sync/async bridge ( i understand that it is used for sync business system too async BS communcation )
where we have 4 steps
sync receive - > async send -> async receive -> sync send..
i do understand that async send and async receive are combined through correlation
but i do not understand how do they work..
i mean when async send say send a file to a target system...does async receive reads a file from the same folder based on the corelation or wat...
basically can you pls explain me how do the steps 2 and 3 above work
Edited by: Tarang Shah on Mar 3, 2009 12:51 PM

SOAP Adapter: Connection time out error

Hi Guys,
I do it one scenario for Proxy to webservice Asynchronous . I have send the input details through Proxy. In Sxmb_Moni shows success message. But Receiver side doesn't reach the payload. Because receiver side (Soap Adapter) shows connection time out error. But i have given correct URL and SOAP Action in receiver communication channel. Please give some suggestions to solve that issues. Please don't refer links.
Thanks & Regards
Vijay

hi
this is a time out error
increase the timeout value by specifying the parameter
XI.Timeout in the module parameter of soap Adapter
OR
1. This is because of TimeOut. The default timeout value for synchronous calls is 5
minutes. You can increase this value by setting parameter XI.Timeout in the module parameter table of
the SOAP adapter. The value must be given in milliseconds. For example, value 600000
represents the timeout value of 10 minutes. This parameter is not recognized in systems prior to SP13.
2.The Other Options is send the queue id with your request message.
http://host:port/XISOAPAdapter/MessageServlet?channel=p:s:c
&version=3.0&...&QueueId=xxxxxxxxxxxxxxxx
where xxxxxxxxxxxxxxxx is an ABAP queue ID.
3.Check your RWB message monitoring.
Is there any system failure message and holding message be there.
If then clear the messages.
4. Increase the time out parameter for HTTP in your altova xml spy.Defaultly it will be very low.

Transaction Time out error in EJB while using Websphere Application Server.

Hi All,
I am using Websphere Application server and getting the transaction time out error. By default the transaction time out is 120 second. I am using session bean for doing a set of transaction. These set are dynamically generated. Is there any way to set the transaction time out for only this session bean to infinite ?
Thanks in advance
Vivek

Hi,
According to WAS 6 , every opened connection has to be commited (or rolledback) explicitly (didnt try autocommit) before closing. Even if all you have done with that connection is a SELECT Query.
This has apparently solved the same problem I was getting. implement it and see whether it helps you.

Time Out error in deploying EJB in Sun's application server

I am facing the problem of time out error in sun's application server when deploy tool and application server is running in the same system. can any one solve my problem

Hi,
How big is your EJB application? i.e. how many EJBs do you have?
Would you please try to deploy your application using the command line tool "asadmin" and see if it is also hanging? This will help us to tell if the deployment process that is hanging or the deploytool itself that is hanging. The "asadmin" tool is located under $INSTALL_HOME/bin.
Thanks,
Q^2

BPC Optimization Server Time Out error message

We’re using BPC 7.5 MS and on patch level 111.02
There’s two front-end servers and one back-end.
When completing a full optimization with compression on an application we immediately get the optimization popup screen with no processing information only a “Server Time Out” error message.
Optimization was taking a long to time run and sometimes timed out. To try and resolve this issue we have just updated indexes and statistics and during our test in production we now receive the “Server Time Out” error message immediately. However, the records from tbl.Factwb and tbl.Fac2 did move to the tbl.Fact.
Our development environment test ran fine.
Any suggestions?
Thanks.

Hi Michael,
please look in the logs maybe you will found more informations regarding the timeout and eventually share it.
There are several notes about a timeout in 10 version,
1394533 - 'Server Time Out' error when performing Modify Application, Full Process of a dimension, or Full Optimize this is related with NLB
but it could be also related with the web.config 1628908 - How to fix Optimize with compress time-out failure
or if you reach the max number of connection
1635749 - Error Message: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool
Regards
Roberto

Time Out Error in BPEL

Hi,
We are trying to invoke a Web Service from BPEL Process (10.1.3.3.0) and we received below time out error message in em console.
</part></Invoke_1_setJobPostingXML_InputVariable></input><fault><remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Read timed out</summary>
Problem here is this error is not coming for all the invocation. For ex. We have posted the input payload at 3:15:34PM today and it thrown an error at 3:45:12 PM with above message. Also its not huge load hitting their server as we are calling the webservice once in 4-5 mins and if we repost the same message, its posting without any issue. This time out error comes 4-5 times daily and want to understand why it occurs everyday.
1. Will BPEL receive an error if we post huge payload to web service?
2. Do we need to set some waiting time to receive the response after posting the data to Web service?
3. Other possible scneario's for timeout error?
Thanks,
Saravana

Hi Saravana,
It's likely to be a problem at the remote side or a network latency/communication problem...
How can you affirm "its not huge load hitting their server"? Your service may not be the only source of load...
Cheers,
Vlad

Time out error on deploying to SAP-J2EE engine.

I got a problem while deploying to SAP-J2EE engine using ant. It takes a lot of time and then throws a time out error.
The problem is with the web.xml file pointing to a DTD in the internet, I have pasted some part of the web.xml below,
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
<web-app>
    <display-name>MyPay</display-name>
    <description>MyPay</description>
Once I write down the DTD description in the web.xml itself, it works fine.
I have pasted the error trace below,
j2eedeploy:
     [echo] Deploying to Local environment...
     [echo] C:\Java\Projects/MyPay/dist/MyPay.ear
BUILD FAILED
C:\Java\Projects\MyPay\build.xml:445: java.lang.RuntimeException: ERROR: ID90507: Error occured during getting EARDescriptor : Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.ConnectException: Connection timed out: connect
Exception is :
java.io.IOException: Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.ConnectException: Connection timed out: connect
     at com.sap.engine.lib.xml.parser.URLLoaderBase.resolveEntity(URLLoaderBase.java:148)
     at com.sap.engine.lib.xml.parser.XMLParser.scanDTD(XMLParser.java:1271)
     at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2795)
     at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
     at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
     at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
     at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
     at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
     at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
     at com.inqmy.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:127)
     at com.inqmy.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:120)
     at com.inqmy.services.servlets_jsp.descriptor.jar.WebWar.getWebDescriptor(WebWar.java:98)
     at com.inqmy.deploy.tool.deployer.ExtendedEarReader.loadDescriptorFromFile(ExtendedEarReader.java:175)
     at com.inqmy.deploy.tool.deployer.ExtendedEarReader.getFullEarDescriptor(ExtendedEarReader.java:104)
     at com.inqmy.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:355)
     at com.inqmy.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:325)
     at com.pg.sap.deploy620.SAPDeploy620Manager.process(SAPDeploy620Manager.java:84)
     at com.pg.ant.tasks.j2ee620.J2ee620EngineDeployTask.execute(J2ee620EngineDeployTask.java:40)
     at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
     at org.apache.tools.ant.Task.perform(Task.java:364)
     at org.apache.tools.ant.Target.execute(Target.java:341)
     at org.apache.tools.ant.Target.performTasks(Target.java:369)
     at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
     at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
     at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
     at org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32)
     at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
     at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423)
     at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137)

Thanks for your reply Kalyan,
The problem seems to be with my system, because I had run the same ant script in another system and it deployed successfully.
The problem does not seem to be with the dtd, whereas it seems that the SAP-J2EE engine is not able to open the link to the dtd giving a time out error.
Is it possible to switch off the validation process of the SAP-J2EE engine of an xml with the dtd?

HTTP time out Error in BPM.....

Hi
Error Description:
We have created a Sync-Async Bridge BPM scenario in XI.
In the BPM scenario we are calling the web service, and if the response from the web service is an error message then we have retry in a loop up to 24 times after wait for every 1 min.
We are sending the data to the web service using a proxy created in the R/3 system.
We are getting the time out error in the R/3 system.
We have changed the following parameters in XI.
In SXMB_ADM of XI we have set the value for the following parameter.
Category                      parameter                                                                    current value
SA_COMM                    CHECK_FOR_ASYNC_RESPONSE_TIMEOUT                120
In SXMB_ADM of R/3 we have set the value for the following parameter.
Category                      parameter                                                                    current value
RUNTIME                      HTTP_TIMEOUT                                                            120
When we put the value as 120 for the above parameters and we try for 2 times in the BPM process, then it is sending the response back to the R/3 system after completing the whole BPM process.
But when we increase the no of retries in the BPM process then it is not sending the response back to the R/3 system in the same way, at that time we are getting the error in SXMB_MONI of R/3 system as given below.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
-   
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="500" p2="Timeout" p3="" p4="">HTTP.HTTP_STATUS_CODE_NEQ_OK</SAP:Code>
<SAP:Text language="EN">HTTP status code 500 : Timeout</SAP:Text>
</SAP:ErrorHeader>
Please provide the solution for the same.
Many Thanks
Rinku Gangwani

Hi Prateek,
Thanks for your replay. I am able to open the URL from XI/PI.
I tried by testing the same URL by using XI 3.0, its working fine and i am getting required data, but in PI 7.1 i am getting an error.
Error is:
In MONI:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection refused: connect
In RWB:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect
What could be the reason?
Regards,
Venu

TIME OUT error in ECC SM58

hi All,
We have sent some 2000 Idocs from ECC,
my scenario is FILE to FILE.
I am collecting all the idocs into a file using IDOC XML port..
File havnt reached XI.. even not created in application server ... all idoc are stuck in ECC side.. when i go to SM58.. getting error like TIME OUT error ...
Please help guys.. how i can sent those.... 2000 stuck Idocs?

Hi Sam,
check the 'Timeouts in PI' section in the PI Troubleshooting Guide -
[#1060264 PI Troubleshooting Guide 7.1|http://service.sap.com/sap/support/notes/1060264]
Regards
Kenny

Time out error on Receiver adapter : Sync application request expired

Similar Messages

Maybe you are looking for