Timeout during long JCO runtimes

Hi all,
I have a webdynpro application that connects to backend SAP systems. If the R/3 functional module or BAPI runs for a long time, my webdynpro screen goes blank after 60-70 seconds.
Where can I set the timeout setting to be greater? Is this a J2EE config or frontend IE?
Thanks and regards,
faB

Hi,
What I have done is put a 9 minute wait (loop) in the R/3 function module to test how long the webdynpro will also wait. That means the function module is still running when the webdynpro "goes blank". I have set the max waiting time and the connectiontimeout parameters to 10 minutes (600 seconds).
The reason I am doing this is that in some cases - when a lot of data is sent to r/3 - it may take several minutes to the function module to run. Therefore, I need to make sure that the frontend (or portal) doesn't loose the connection.
the error log defaultTrace.trc shows:
"14:20:59:667 , /Applications/SL/UTIL , 05/24/2005 , get data source CVERS failed! Trying SAP/BC_UME... , Error , com.sap.sl.util.cvers.impl.DBConnector"
fyi: when I set the function module wait time to 50 seconds, everything is fine. but anything much over a minute causes the error.
thanks for your help so far.
cheers,
faB
Message was edited by: faB

Similar Messages

Timeout during allocate of Vertex RFC

Hi Guys.
Im facing this odd issue after an offline backup is completed and brings the system.
As you can see the Vertex RFC is no longer working and displays a timeout issue after a Sales programs tries to reach it.
Also when testing the RFC is unable to initialize.
M *****************************************************************************
M *
M * LOCATION    SAP-Gateway on host etgrws01.entegris.com / sapgw20
M * ERROR       timeout during allocate
M *
M * TIME        Tue Dec 28 16:43:08 2010
M * RELEASE     640
M * COMPONENT   SAP-Gateway
M * VERSION     2
M * RC          242
M * MODULE      gwr3cpic.c
M * LINE        1854
M * DETAIL      no connect of TP /boltons/D01/vertex/3.3/TransLink/verrfc from
M *              host etgrws01.entegris.com after 22 sec
M * COUNTER     6378
M
A RFC 1448 CONVID 40614370
A   * CMRC=27 DATA=0 STATUS=0 SAPRC=242 ThSAPECMINIT
A RFC> ABAP Programm: CL_XTAX_RULES_RFC=============CP (Transaction: VA02)
A RFC> User: VMESENBR (Client: 200)
A RFC> Destination: VERTEX (handle: 3, , )
A *** ERROR => RFC ======> CPIC-CALL: 'ThSAPECMINIT' : cmRc=27 thRc=242
Timeout during connection setup. Please check partner availability
[abrfcio.c    7933]
A *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1464
CPIC-CALL: 'ThSAPECMINIT' : cmRc=27 thRc=242
Timeout during connection setup. Please check partner availability
DEST =VERTEX
HOST =etgrws01
PROG =/boltons/D01/vertex/3.3/TransLink/verrfc
[abrfcio.c    7933]
That /boltons/D01/vertex/3.3/TransLink/verrfc is located on the same server as the SAP application, so i cannnot figure out why is showing partner not available/timeouts, when is pinging a program on the same server.
I have tried restarting the Dispatcher
rfc/use_gwstart =1
Increased CPIC timeout value gw/cpic_timeout =120 (Increased CPIC timeout)
I have also searched thru these notes but still no luck
Note 581509 - Reasons for timeout during allocate
Note 638701 - Starting RFC servers takes too long
Note 948636 - Starting executables locally using RFC
The only workaround for this, is restarting the SAP Application, in order to have the RFC working again, but this seems an overkill to fix an RFC Ping Issue.
All ECC Systems have the same program version and configuration but only Dev system is facing this.
The whole point of this, is why when the system is shut down in order to perform an offline backup causes this, and the only way to fix this, is shutting down/start up the system again.
If you have some ideas of what could be causing this, it's would be highly appreciated.
Martin

Hi Martin,
We are experiencing the same issue with SAP/Vertex. Can you let me know how you resolve this? Did you change the SAP gateway timeout parameter? If so, which one is it?
Your help on this is greatly appreciated.
Thanks much!
Best regards,
Cyanna

Javax.transaction.SystemException: Timeout during commit processing

          In my Workshop 8.1 SP2 project I have a Custom Java Control whose methods I call
          from my JPF. From that custom control I create a remote connection to a Weblogic
          6.1 Application server. I execute remote methods and get the expected objects
          back with no problem. The problem is that I cannot return that object from my
          custom control back to my jpf. As soon as the method's return statement is executed,
          the process hangs for a considerable period of time and then throws the following
          Exception:
          An error has occurred:
          Exception while commiting Tx : Name=[EJB com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.core.request.Request)],Xid=BEA1-0005BF0F3E6E72419698(655489),Status=Unknown,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
          since begin=217,seconds left=42983,XAServerResourceInfo[BMResourceManager]=(ServerResourceInfo[BMResourceManager]=(state=new,assigned=none),xar=null),SCInfo[midway+cgServer]=(state=active),SCInfo[prdsdomain+prdsserver]=(state=active),properties=({weblogic.transaction.name=[EJB
          com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.core.request.Request)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=cgServer+172.23.83.174:7001+midway+t3+,
          XAResources={},NonXAResources={})],CoordinatorURL=prdsserver+172.23.4.109:7041+prdsdomain+t3+);
          nested exception is:
          javax.transaction.SystemException: Timeout during commit processing
          Start server side stack trace:
          javax.transaction.SystemException: Timeout during commit processing
          at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:243)
          at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:189)
          at weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68)
          at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          caused by: : javax.transaction.SystemException: Timeout during commit processing
          Start server side stack trace:
          javax.transaction.SystemException: Timeout during commit processing
          at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:243)
          at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:189)
          at weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68)
          at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          As soon as I take out RMI calls from my custom control's code, I can return any
          object I want back to my JPF. Here is the what I am thinking is happenning.
          The system that runs on Weblogic 6.1 manages its own transactions and begins a
          new transaction every time a session bean residing on that server is invoked.
          In addition, Weblogic 8.1 starts an internal transaction when the Custom Java
          Control makes a call. Could there be some kind conflict? If yes, is it possible
          to disable transactions from the Java Control?
          Thank you very much
          Alex Mayzlin


Horst,
          "aa aa" <[email protected]> wrote in message news:20701457.1093414960276.JavaMail.root@jserv5...
          > we are getting the same Exception. As nobody replied to your question, it would be interesting, if you found any solution
          yourself?
          >
          > Additional info:
          > We are also getting these error messages from BEA when testing connections in pool before and after the exception:
          >
          > <20.08.2004 19.32 Uhr CEST> <Error> <JDBC> <BEA-001112> <Test "SELECT count(*) FROM invoice" set up for pool "ABCConnection Pool"
          failed with exception: "java.sql.SQLException: ORA-01591: lock held by in-doubt distributed transaction 4.47.141655".>
          Generally it's a good idea to use Oracle's system DUAL table
          for testing connections on reserve. Try to change your ABCConnection
          connection pool configuration to use DUAL as the test table
          instead of "invoice".
          Regards,
          Slava Imeshev

Timeout during commit processing

Hi All,
I am facing time out exception on test environment. It is clustered environment with 2 nodes. I have set trust domain between the two weblogic domains.
In one of my EJB method having tranaction attrbiute set as Required. In this method I also make a remote ejb call to different system for which I have set Trust.
When i execute this method , I see all my debug statement entering the method and exiting the method, after it exits my method , my client still waiting on response from this method and finally he get the java.rmi.RemoteException.
Detailed exception as below....
java.rmi.RemoteException: EJB Exception: ; nested exception is:
     com.bea.control.ServiceControlException: <xml-fragment xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"> <faultcode> SOAP-ENV:Client </faultcode> <faultstring> Exception while commiting Tx : Name=[EJB com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.core.request.Request)],Xid=BEA1-0074571ED882A67DA1E5(11375621),Status=Committing,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=118,seconds left=2,XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=committed,assigned=NodeOne),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@190af6,re-Registered = false),SCInfo[p2pDomain+NodeOne]=(state=committed),SCInfo[mycompany+NodeOne]=(state=committing),properties=({weblogic.transaction.name=[EJB com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.core.request.Request)], weblogic.jdbc=t3://192.168.86.61:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=NodeOne+192.168.86.61:7001+p2pDomain+t3+, XAResources={},NonXAResources={})],CoordinatorURL=NodeOne+192.168.86.61:7001+p2pDomain+t3+); nested exception is:
     javax.transaction.SystemException: Timeout during commit processing </faultstring> <detail>
Exception while commiting Tx : Name=[EJB com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.core.request.Request)],Xid=BEA1-0074571ED882A67DA1E5(11375621),Status=Committing,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=118,seconds left=2,XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=committed,assigned=NodeOne),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@190af6,re-Registered = false),SCInfo[p2pDomain+NodeOne]=(state=committed),SCInfo[mycompany+NodeOne]=(state=committing),properties=({weblogic.transaction.name=[EJB com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.core.request.Request)], weblogic.jdbc=t3://192.168.86.61:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=NodeOne+192.168.86.61:7001+p2pDomain+t3+, XAResources={},NonXAResources={})],CoordinatorURL=NodeOne+192.168.86.61:7001+p2pDomain+t3+); nested exception is:
     javax.transaction.SystemException: Timeout during commit processing </detail></xml-fragment>
     at weblogic.ejb20.internal.EJBRuntimeUtils.throwRemoteException(EJBRuntimeUtils.java:102)
     at weblogic.ejb20.internal.BaseEJBHome.handleSystemException(BaseEJBHome.java:307)
     at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:263)
     at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.java:140)
     at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:56)
     at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:161)
     at com.bea.wlw.runtime.core.dispatcher.ServiceHandleImpl.invoke(ServiceHandleImpl.java:436)
     at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl._invoke(WlwProxyImpl.java:326)
     at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl.invoke(WlwProxyImpl.java:315)
     at $Proxy17.updatePurchaseOrder(Unknown Source)
     at newpageflow1.Newpageflow1Controller.begin(Newpageflow1Controller.jpf:75)
     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.bea.wlw.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:1519)
     at com.bea.wlw.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:1445)
     at com.bea.wlw.netui.pageflow.FlowController.internalExecute(FlowController.java:776)
     at com.bea.wlw.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:211)
     at com.bea.wlw.netui.pageflow.FlowController.execute(FlowController.java:606)
     at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
     at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:1354)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
     at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:650)
     at com.bea.wlw.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:527)
     at com.bea.wlw.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:152)
     at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
     at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:293)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
     at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:326)
     at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.superForward(PageFlowRequestProcessor.java:1301)
     at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor$DefaultHttpRedirector.forward(PageFlowRequestProcessor.java:1317)
     at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.doForward(PageFlowRequestProcessor.java:1199)
     at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:637)
     at com.bea.wlw.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:527)
     at com.bea.wlw.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:152)
     at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
     at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:293)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6724)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Caused by: com.bea.control.ServiceControlException: <xml-fragment xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"> <faultcode> SOAP-ENV:Client </faultcode> <faultstring> Exception while commiting Tx : Name=[EJB com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.core.request.Request)],Xid=BEA1-0074571ED882A67DA1E5(11375621),Status=Committing,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=118,seconds left=2,XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=committed,assigned=NodeOne),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@190af6,re-Registered = false),SCInfo[p2pDomain+NodeOne]=(state=committed),SCInfo[mycompany+NodeOne]=(state=committing),properties=({weblogic.transaction.name=[EJB com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.core.request.Request)], weblogic.jdbc=t3://192.168.86.61:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=NodeOne+192.168.86.61:7001+p2pDomain+t3+, XAResources={},NonXAResources={})],CoordinatorURL=NodeOne+192.168.86.61:7001+p2pDomain+t3+); nested exception is:
     javax.transaction.SystemException: Timeout during commit processing </faultstring> <detail>
Exception while commiting Tx : Name=[EJB com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.core.request.Request)],Xid=BEA1-0074571ED882A67DA1E5(11375621),Status=Committing,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=118,seconds left=2,XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=committed,assigned=NodeOne),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@190af6,re-Registered = false),SCInfo[p2pDomain+NodeOne]=(state=committed),SCInfo[mycompany+NodeOne]=(state=committing),properties=({weblogic.transaction.name=[EJB com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.core.request.Request)], weblogic.jdbc=t3://192.168.86.61:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=NodeOne+192.168.86.61:7001+p2pDomain+t3+, XAResources={},NonXAResources={})],CoordinatorURL=NodeOne+192.168.86.61:7001+p2pDomain+t3+); nested exception is:
     javax.transaction.SystemException: Timeout during commit processing </detail></xml-fragment>
     at com.bea.wlw.runtime.core.control.ServiceControlImpl.invoke(ServiceControlImpl.jcs:1233)
     at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:377)
     at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
     at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
     at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:248)
     at com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:85)
     at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:224)
     at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:103)
     at com.bea.wlwgen.StatelessContainer_ly05hg_ELOImpl.invoke(StatelessContainer_ly05hg_ELOImpl.java:99)
     at com.bea.wlwgen.GenericStatelessSLSBContAdpt.invokeOnBean(GenericStatelessSLSBContAdpt.java:62)
     at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
     at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
     at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:168)
     at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:46)
     ... 53 more
appreciated any help on this .....
hitesh

Hi skrai,
          From the moment the begin call is made, the timer starts ticking independently of the flow of your processing. When the timeout expires, the Transaction Manager will roll the transaction back. The first you hear of that happening may be when calls you make in the thread associated with the transaction start to throw exceptions, since it is not possible to propagate a rolled-back transaction (what would be the point, the results of the call will not persist under any circumstances?).
          Therefore suspending a transaction has no impact whatsoever on its timeout; it simply breaks the association between transaction and thread. If your code suspends a transaction and then goes to sleep for a week, it should expect to find that the transaction has timed out while it slept.
          So when U invoke an EJB with "NotSupported" tx attribute, the clock with the tx manager is still ticking.
          Hope my explanation helped to resolve your issue.
          Thanks
          -Rais

Error when starting parser: timeout during allocate / CPIC-CALL:'TfSAPCMRC'

Hello experts.
When I try to preview or refresh a Crystal Report document built on a BEx query I get the following error msg:
Database connector error: BAPI Error #0. Error when starting parser: timeout during allocate / CPIC-CALL: 'TfSAPCMRCV'.
We have done as suggested in "SAP Note 1032461 - MDX parser does not start", but without success.
This is what we've tried so far:
replaced the file "librfc32.dll" (in C:\Windows\System32 and C:\Windows\SysWOW64) with the new version mentioned in Note 413708.
tested the connection in SM59 - non successful
tested the report query with transaction MDXTEST - non successful
tried to start the mdxparser manually on server - non succesful, error msg: "The application failed to initialise.."
We have the following config:
MS server 2003 SP2 x64 ed.
SAP logon 7.20
MS SQL server 2005
CR 2008
new librfc32.dll version 7200.1.39.6461
Any ideas on what to try next would be highly appreciated!
Cheers, IngA

Hi Ingo.
We have only one application server.
I registered the new version of the file C:\windows\SysWOW64\librfc32.dll with regsvr32.exe successfully. I've also tried to copy the new file to the same directory as the mdxsvr.exe-file is located, but it made no difference.
Should I remove all other copies of librfc32.dll and only keep the one in folder C:\Windows\SysWOW64, or maybe register them all with regsvr32.exe?
--IngA
Edited by: Ingeborg Andreassen on Nov 5, 2010 10:36 AM

RFC ERROR       timeout during allocate

Hi all,
We are trying to connect our ECC 6.0 system to ECC 5.0 system thru RFC we get the following error. Both the systems are available running
Timeout during connection setup. Please check partner availability
[abrfcio.c    8139]
A *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 2799
CPIC-CALL: 'ThSAPOCMINIT' : cmRc=27 thRc=242
Timeout during connection setup. Please check partner availability
DEST =RQ3CLNT300
HOST =168.189.35.139
SERV =sapdp11
GWHOST =dcecqv1
GWSERV =sapgw02
[abrfcio.c    8139]
A TH VERBOSE LEVEL FULL
A ** RABAX: end RX_GET_MESSAGE
M
M Wed May 14 05:41:59 2008
M
M *****************************************************************************
M *
M * LOCATION    SAP-Gateway on host dcecqv1 / sapgw02
M * ERROR       timeout during allocate
M *
M * TIME        Wed May 14 05:41:59 2008
M * RELEASE     700
M * COMPONENT   SAP-Gateway
M * VERSION     2
M * RC          242
M * MODULE      gwr3cpic.c
M * LINE        1872
M * DETAIL      no connect of TP sapdp11 from host cpchrpq1.clorox.com after
M *              20 sec
M * COUNTER     1679
M *
M *****************************************************************************
M
A RFC 2318 CONVID 77332474
A   * CMRC=27 DATA=0 STATUS=0 SAPRC=242 ThSAPCMINIT
A RFC> ABAP Programm: RSRFCPIN (Transaction: SM59)
A RFC> User: DDIC (Client: 300)
A RFC> Destination: RQ3 (handle: 2, , {482AC1FF-A0EE-2871-E100-0000A8BD2A0B})
we have mentioned the system no, hostname..every thing correctly
Any help
Thanks
Senthil

Hi Senthil,
I had faced a similar issue working with my previous company. Upgrading the kernel had done the trick. I am not sure of the SAP note but please check Note, 827872 - Work process waits for registered RFC server
Regards,
Atul Lotlikar.

Timeout during allocate / CPI-C error CM_RESOURCE_FAILURE_RETRY

Bonjour,
i receve an error message "timeout during allocate / CPI-C error CM_RESOURCE_FAILURE_RETRY"
when testing an REC destination (SM59), when i see on SM21 i find :
R49 Communication error, CPIC return code 027, SAP return code 456
R64 > CPI-C function: CMINIT(SAP)
can you help me ?
Thank's

Hi,
In SM21 you try to find out the corresponding Work processor(WP) No. , as per your bellow error,
"R49 Communication error, CPIC return code 027, SAP return code 456
R64 > CPI-C function: CMINIT(SAP) "
Now you go to that corresponding WP trace like dev_w(xx) in usr/sap/SID/DV.../work directory. Check what exactly happend during that error, try to find some Notes based on that.
Regards,
Hari.

ERROR: timeout during allocate

Dear All,
When i am establish RFC from Dev to Pro, i am getting Error in SM59 is "ERROR: timeout during allocate"
Here i am copying my dev_rd log please help me to solve this problem
Thu Oct 29 18:33:29 2009
***LOG Q0I=> NiPConnect2: connect (78: Connection timed out) [nixxi.cpp 2823]
ERROR => NiPConnect2: SiPeekPendConn failed for hdl 11 / sock 21
    (SI_ECONN_REFUSE/78; I4; ST; 171.31.111.98:3365) [nixxi.cpp    2823]
LOCATION    SAP-Gateway on host pspdscmd / sapgw60
ERROR       partner 'pspdciscp:sapgw65' not reached
TIME        Thu Oct 29 18:33:29 2009
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -10
MODULE      nixxi.cpp
LINE        2823
DETAIL      NiPConnect2
SYSTEM CALL connect
ERRNO       78
ERRNO TEXT Connection timed out
COUNTER     4435

Please check out the following SAP Note; a collection of all notes for this type of connection error:
[Note 581509 - Reasons for "timeout during allocate"|https://service.sap.com/sap/support/notes/581509]
Regards,
Dipanjan

Timeout during allocate error

Currently our production system SAP R/3 4.6B is having one CI and two application server. When enduser tries to upload a document from desktop to SAP, getting CALL_FUNCTION_RECEIVE_ERROR.
The CI works fine but when tried the same ftp to upload from app servers it is
giving error.
The details of CALL_FUNCTION_RECEIVE_ERROR is as follows:
Error text........... "timeout during allocate"
Description.......... "no connect of TP sapftp from host %%SAPGUI%%
after 22
sec"
System call.......... " "
Module............... "gwr3cpic.c"
Line................. 5763
The error occurs in FM FTP_CLIENT_TO_R3
000160 perform check_destination using rfc_destination.
000170
000180 set extended check off.
000190 call function 'FTP_CLIENT_TO_R3' destination rfc_destination
000200 exporting fname = fname
000210 importing error = cerror length = blob_length
> tables blob = blob.
000230 set extended check on.
I have followed the instruction of SAP note 313325 and displayed the
dev_ftp file.
trc file: "dev_ftp", trc level: 2, release: "640"
Thu Jan 04 16:26:31 2007
[1876] sccsid:@(#) $Id: //bas/640_REL/src/krn/ftp/ftpmain.c#8 $ SAP
@(#) $Id: //bas/640_REL/src/krn/ftp/ftp.c#5 $ SAP
@(#) $Id: //bas/640_REL/src/krn/ftp/ftpcmd.c#4 $ SAP
[1876] FTP Start : argc - 6 a0 - sapftp
/H/sxxxxap2 sapgw01 67900565 CPIC_TRACE=2 IDX=35
[1876] RFC DLL loaded
[1876] Environment SAP_CODEPAGE = 1100
[1876] RFC Version 640
[1876] Install server functions
[1876] Call RfcAccept
[1876] RfcError - key: RFC_ERROR_COMMUNICATION
message: CPIC-CALL: 'CMACCP'
LOCATION    CPIC (TCP/IP) on local host
ERROR       hostname 'sxxxxap2' unknown
TIME        Thu Jan 04 16:26:31 2007
RELEASE     640
COMPONENT   NI (network interface)
VERSION     37
RC          -2
MODULE      ninti.c
LINE        336
DETAIL      NiPGetHostByName2: hostname 'sxxxxap2' not found
SYSTEM CALL gethostbyname_r
COUNTER     1
[1876] FTP Stop
The error message in their to some extent matches with
SAP note solution 211365. The root cause described that "hostname is protected by router or firewall" does not coincide since Central DB server is working and not the application server scenario.
My questions is , will the instance profile parameter change will fix it?
abap/hostname_for_sapgui= hostname of APP server
How sapftp works in CI alone and not in application server?
The SM59, setting for SAPFTP is as follws:
Connection Type T
Start On : FrontEnd work station
Security options inactive.
Has anyone has experienced this before?

Please check out the following SAP Note; a collection of all notes for this type of connection error:
[Note 581509 - Reasons for "timeout during allocate"|https://service.sap.com/sap/support/notes/581509]
Regards,
Dipanjan

Using RS with SAP Netweaver - Timeout during allocate /CPIC 'ThSAPCMRCV'

Hi All,
I am trying to connect to a remote SAP BI server from my local SQL server 2005 Reporting Services. I was able to view all info objects in the query builder but when I try to drill down and view members / drag and drop to create a query / preview the RS report, I get the following error ,
u201CError occurred retrieving child nodes - error occurred when starting the parser - timeout during allocate: /CPIC-CALL 'ThSAPCMRCV' u201D.
I have SAP front end and business explorer installed on my system. We also have the latest patches on SAP BI server.
I tried changing the timeout value but dint help.
Any help is appreciated.
Many Thanks,
Chitra

Hi
I think you should post this in basis and security forum.
Cheers
Chanda

RSTPTEST , RFC ping failed RFC error text: timeout during allocate / CPIC-C

Hi all,
I was transporting the request in my landscape last week and all of sudden transports in acceptance system is not working and I am getting a error message as
Could not start transport control program tp
Message no. TP608 Diagnosis
There was an attempt to start the transport control program tp using the local RFC interface. An error occurred here.
Error code: 4
RFC error text: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'
Meaning of the error codes:
03 RFC system failure
04 RFC communication failure
System Response
The function terminates. Details about the error can be found in the trace file of the Gateway Monitor (SMGW).
SMGW logs are as follows:
Tue Jun 16 12:04:28 2009
ERROR => GwISearchPartner: timeout, partner LU: >hostname<, TP: >M:\usr\sap\SID\DVEBMGS00\exe\tp.EXE< [gwr3cpic.c 6135]
ERROR => GwISearchPartner: HOST: hostname conv ID: 50323660 [gwr3cpic.c 6148]
, This is the 3 system landscape, common transport directory in development system.
Actions taken:
Restarted the systems (PRD queue is working but not acceptance queue)
DIR_TRANS and Permission were given already and able to ping from all the sytem
Host and service entry were maintained already.
RFC connections were woring fine without errors
I have seen many threads but none of the thread is solved my problem.
Please suggest
Vijay

Hello,
Thanks fpr your reply and I tried the steps which you said and the result is same error for both the options.
1 & 2 Answers :
Could not start transport control program tp
Message no. TP608 Diagnosis
There was an attempt to start the transport control program tp using the local RFC interface. An error occurred here.
Error code: 4
RFC error text: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'
Meaning of the error codes:
03 RFC system failure
04 RFC communication failure
System Response
The function terminates. Details about the error can be found in the trace file of the Gateway Monitor (SMGW).
SMGW logs are as follows:
Tue Jun 16 12:04:28 2009
ERROR => GwISearchPartner: timeout, partner LU: >hostname<, TP: >M:\usr\sap\SID\DVEBMGS00\exe\tp.EXE< http://gwr3cpic.c 6135
ERROR => GwISearchPartner: HOST: hostname conv ID: 50323660 http://gwr3cpic.c 6148
I think this is not able to contact the domain controller.
But I can see the checks are fine from checking the transport directory.
Vijay

RFC error text: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'

I am having this error pop up very frequently on some new SAP systems. This will randomly happen and keep us from being able to release transports and import them in STMS. I receive the following error:
There was an attempt to start the transport control program tp using the local RFC interface.
An error occurred here.
Error code: 4
RFC error text: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'
- When I check the Transport Tool (STMS: import queue> check> transport tool) I get the following information:
timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456#Time
out during connection setup (check that partner exists
- When checking the TP System Log I receive the same error. The RSTPTEST report does not give any additional information. SM21 shows a warning and an error:
Warning:
Communication Error, CPIC return code 020, SAP Return code 456
Dialog Process No. 000
Problem cl: SAP web AS problem
Package: STSK
Further Details:
Module Name: thxxhead
Line: 7488
Error Text: 020456
Caller: ThRecei
Error:
Problem cl: transaction problem
Package: STTO
All of these errors are only pointing to a time out. I cannot figure out why this is happening. I checked the TMS RFC connection in SM59 and they are fine. I have been able to work around this issue in 2 different ways. First, I can delete the files in the "\trans\tmp" directory on the server. Sometimes this resolves the error. Else I have to restart the system.
I need to understand where this issue is coming from and how to resolve it. It is becoming more and more frequent. Thank you for your help!

Hi,
i have had similar issues during this week. After looking for a solution everywhere i found out that i didn't set up the FQDN on this system.
Symptoms were:
se38 > RSTPTEST timed out sometimes(not always)
sm59 > TCP/IP connections > CALLTP_WindowsNT > test connections timed out sometimes (again, not always)
STMS Overview > Systems: I was not always able to distribute and activate configuration from the Domain controller via Extras > Distribute and Activate Configuration (it died on the mentioned system)
Transports failed mostly with the same error.
The error log was somewhere deep in ST11. It could not resolve our FQDN.
The solution, for me, was to add our FQDN to the WINDIR\System32\drivers\etc\hosts file.
We upgraded the kernel as well (from 7.20 patch 046 to most current) but this didn't help.
The FQDN is a concatenation of computer name and dns suffix of the network (if you have none, you can add one via rightclick on the used network adapter>ipv4>properties>Advanced>DNS tab, so in the end the host file looked like
127.0.0.1 localhost computer-name.ourSuffix.com
After this line has been added, the error stopped and the transports work again.
I hope it helps. Good luck.

STMS distribution error - timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'

Hello All
i am trying to confugreu STMS but i am facing this error when i am tryin to distribute the same,
System   EC2              Command TMS_PM_DISTRIBUTE_PROFILE
Client   000              Service tp Profile Service
User     TMSADM           Start    Online
Date     20.10.2009       Function TMS_PS_WRITE_PROFILE_TO_DISK
Time     17:36:23         Message SET_CODEPAGE_FAILED
description : Could not start transport control program tp
detail error is as below if i press on more information
Could not start transport control program tp
Message no. TP608 Diagnosis
There was an attempt to start the transport control program tp using the local RFC interface. An error occurred here.
Error code: 4
RFC error text: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'
Meaning of the error codes:
03 RFC system failure
04 RFC communication failure
System Response
The function terminates. Details about the error can be found in the trace file of the Gateway Monitor (SMGW).
some of the posts on forum suggested i should try from same domain i tried but in vain, then i updated the SAP kernel from 7.01 sp 14 to sp 55. but i am still facing the problem.
i created this system recently using system copy based upon export image of a system (ABAP stack ) but using ABAP+Java during export process (by mistake). then we tried to build system using import (ABAP stack only i know its weird but its up and running). I assume we should have builf export imgae using ABAP method but some how due to lack of time we proceeded this way.
The main problem i see is TP RFC . The output from prgram RSTPTEST is as below
everythign is fine except below entries
under RFC destination
EFC ping - timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456#Time out during connection setup (check that partner exists
under TP call
RFC link and Offline Call shws me the same error as RFC ping. and there is no output from tp version and DB connect.
Can anybody please help me on the same.
Mani

Hello All,
thanks a lot for you reply, i want to clear some point here
- I have no other physical attached to the system, i created other system as virtual system.
- to Sunny - i allready went through that thread and upgraded my Kernel also accordign to thread but problem still persist.
- to Anil .. i did as u said but nothing changed after that.
here is the log from trans log file
4 ETW000 r3trans.exe version 6.14 (release 701 - 12.06.09 - 15:20:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time   : 20.10.2009 - 17:37:33
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: r3trans.exe -d
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [dev trc     ,00000] Tue Oct 20 17:37:37 2009                                               12584 0.012584
4 ETW000 [dev trc     ,00000] db_con_init called                                                        65 0.012649
4 ETW000 [dev trc     ,00000] create_con (con_name=R/3)                                                401 0.013050
4 ETW000 [dbcon.c     ,00000] *** ERROR => Invalid profile parameter dbms/type (or environment variable dbms_type) = <undef>, cannot load DB library
4 ETW000                                                                                160 0.013210
2EETW169 no connect possible: "connect failed with DBLI_RC_LOAD_LIB_FAILED."
i have dbms/type = mss in profile parameters
I am still getting the same error.
Mani

MDX Error: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' (NW 7.0)

Hello everyone,
while trying to execute an MDX Statement on NW 7s SAP BI i ran into the "timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'" error.
I searched these forums for a solution an found SAP Note 1032461.
The Problem is: it only applys to older versions of the NetWeaver. NW 7 seems to have a new RFC library.
Is there another solution for this problem in NW 7?

I found the solution.
The note was right, but i used the wrong .dll.

STMS error - Timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'

Dear Experts,
We are facing issue in releasing or importing TRs.
1.When releasing TRs in DEV server, it is showing error message "Could not start control program TP" on status bar. But repeating the same process went successful.
2. While Importing TRs into QAS, at the time of refreshing queue/adjusting import queue, it pops-up error " timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' .But after repeating same process, TRs were impoted successfully.
We had performed the following in DEV & QAs:
1. Upgraded kernel to patch level 137.
2. After that replaced TP & R3trans with latest patch levels 169.
3. Re-configured STMS
4. Restarted Server.
Also checked,
(i). Report RSTPTEST in se38- sometimes successful; sometimes error :"timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' (ii). RFC "CALLTP_WindowsNT" in sm59 Connection is OK.
Please help.
Thank you in advance.
Regards

Hi,
Check below link if it helps:
Re: STMS
Pls also check below things :
- check that the "Gateway Options" are maintained in SM59 and the sapdp00/sapgw00 are maintained in the etc/services files. SAP Note 52959
- Please check SAP Note 773830 if you are on a cluster environment.
For the error regarding timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' please check SAP Notes 581509, 566566.
Thanks,
Rupali

Timeout during long JCO runtimes

Similar Messages

Maybe you are looking for