JCO connection failure

Hi Friends,
I am getting the below error in integration engine
"communication failure during JCO call".
Pls help me how to resolve this issue.
Regards,
Suresh.

Hello
this is very generic error, more details must be known to solve the issue, if you are having this problem with your RFC communication channel, goto communicatin channel monitoring in RWB and there you would have complete details of why this error is occuring, do post back with those details to have clear understanding of the problem.
Moreover try creating an ABAP connection to R/3 system to which connection is being made and check if you are able to access the system altogether or not, for this follow the following step:
login to your PI server from SAP GUI with user PISUPER
got t-code SM59
Create destination with type: 3
provide ip address of your R/3 system in target host and instance number in respective field
save and execute "Connection test"
this will let you know if you are altogether able to access the R/3 system for PI server.

Similar Messages

  • HOW to handle JCO connection failure

    if i have a JCO connection.....to process the RFC function...
    when i call the function...the job leave to R3 to do the rest...
    yet ..the connection broken..at this time..
    the is no result return..and consequency receive the
    RFC_ERROR_COMMUNICATION exception...
    how do i handle this kind of situation....
    what should R3 SHOULD DO..
    let's say i have a jco connection
    the connection broken during processing...how do i return the error message to the java program
    the error include....RFC_SYSTEM_FAILURE ,RFC_ERROR_COMMUNICATION
    Message was edited by:
            yzme yzme

    Yzme,
    You have already got answers how to catch this exception.
    Next processing depends on application-specific nature of RFC: whether or not call is idempotent, in simple words -- submitting same request doesn't hurt.
    This comes from the fact that network failure may occurs when transferring request (hence no background processing performed) or when returning response (hence function already executed).
    For idempotent calls there is also an option for automatic re-tries finite number of times. For non-idempotent calls the only option is to display error to user in friendly format.
    An idempotent call is a call that can be executed more than once on the server without undesirable side effects. Take for example Create / Read / Update / Delete operations. Obviously, read is idempotent while it doesn't alter data at all. You may treat Delete as idempotent up to certain extent -- just handle "record not exists" gracefully. Create and Update are not good candidates -- re-submitting same request typically leads to serious problems like duplicate entries or data inconsistency.
    Valery Silaev
    SaM Solutions
    http://www.sam-solutions.net

  • Random JCO Communication Failure Error

    Dear All,
    I am facing the weird issue of JCo connection failures. I am facing the error of Max no of conversations excedeed. If i am testing it then it is giving me error. But after some time if i check it again it will be successful and also ping will be also successful for the JCo. I am facing for all JCo which we have created in the Portal System.
    We have 3 landscape system here. In my Development and Quality this type of error is coming which is very randomly.
    In our Production server its not coming.
    So i am very confused why this type of random behaviour is of JCo Connection.
    Regards,
    Dhruv Shah

    Hi Dhruv,
    If you are using WD application, then you should use disconnectIfAlive() in finally block of try-catch while executing RFC model.
    Please check the Web Dynpro Best Practices: [How to Configure the JCo Destination Settings|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/user-interface-technology/wd%20java/7.0/portal%20integration/how%20to%20configure%20the%20jco%20destination%20settings.pdf] that will helps you identify maximum pool size, connections and timeout etc.
    Also refer to JCo Pool Configuration and http://help.sap.com/saphelp_nw04/helpdata/en/3a/3b1b40fcdd8f5ce10000000a155106/content.htm
    Hope it helps
    Regards
    Arun

  • Error while obtaining JCO connection.

    Hi I'm trying to put in place since BW-SEM RSPLAN the transaction, I'm pointing at my portal from the transaction RSPLSA
    But when it signs the user gets the message Error while obtaining JCO connection.
    I was reviewing my WebDynpro on my site by following these steps:
    1 I will http://portal:port
    2 I clicked Webdynpro
    3 I click on Content Administrator
    I clicked on 4 Maintain JCO destinations
    and then I log shows the following:
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
        at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:485)
        at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:480)
        at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:699)
        at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:663)
        ... 39 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type     HTML Client
    User agent     Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
    Version     null
    DOM version     null
    Client Type     ns7
    Client Type Profile     nn7
    ActiveX     disabled
    Cookies     enabled
    Frames     enabled
    Java Applets     enabled
    JavaScript     enabled
    Tables     enabled
    VB Script     enabled
    Server
    Web Dynpro Runtime     Vendor: SAP, build ID: 7.0014.20071210061512.0000 (release=645_VAL_REL, buildtime=2007-12-10:05:23:29[UTC], changelist=470565, host=pwdfm101), build date: Wed Oct 01 12:15:02 CDT 2008
    J2EE Engine     7.00 patchlevel 109886.44
    Java VM     IBM J9 VM, version:2.3, vendor: IBM Corporation
    Operating system     AIX, version: 5.3, architecture: ppc64
    Session & Other
    Session Locale     en_US
    Time of Failure     Thu Nov 06 16:00:23 CST 2008 (Java Time: 1226008823202)
    Web Dynpro Code Generation Infos
    sap.com/tcwdtools
    No information available     null
    sap.com/tcwddispwda
    No information available     null
    sap.com/tcwdcorecomp
    No information available     null
    Detailed Error Information
    Detailed Exception Chain
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
         at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:485)
         at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:480)
         at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:699)
         at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:663)
         at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.wdDoInit(JCOConnectionsDetails.java:121)
         at com.sap.tc.webdynpro.tools.explorer.wdp.InternalJCOConnectionsDetails.wdDoInit(InternalJCOConnectionsDetails.java:262)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    What should I do??

    Hi Antonio,
    Follow the below note for Jco related troubleshooting.
    https://service.sap.com/sap/support/notes/919850
    Are you able to see the 4 Jco connections green?
    Regards,
    Debasis.

  • Jco connection error while calling Custom FM in CRM Internet Sales Application

    Hi ,
    I am trying to do some customisation in the CRM ISA 4.0 development component.
    Have followed the steps given in the Development and Extension Guide and tutorial PDF
    Steps done for Custom RFC Call
    1.       Create RFCs
    2.       Edit file backendobject-config.xml in folder project_root\b2b_z\WEB-INF\xcm\customer\modification:-
    3.       BackendBusinessObject Jco -
    4.       BusinessObject -
    5.       Edit file bom-config.xml in folder project_root\b2b_z\WEB-INF\xcm\customer\modification
    6.       BusinessObjectManager BoM
    7.       BackendAware-
    8.       config.xml - to add custom actions
    9.       Action  creation
    10.     Page : Order_change.jsp.
    The backend is the CRM system while making a call to the CRM system the connection to the CRM system is not working .
    Similar to what is given in the tutorial the  getDefaultJCoConnection() is used .
    But gettting null at the JCO connection.
    JCO.Function func = getDefaultJCoConnection().getJCoFunction(‘CRM_ISA_SHOP_GETLIST’);
    This is how my custom FM is being called.
    Can someone help me with what may be the possible reason for this call failure.
    While debugging and checking it shows null pointer exception in the JCo connection .
    Thanks
    Chinju

    Hi Hamendra,
    When the code debugging was done in Java then we got just the NullPointerException for the JCo.
    In the nwa log shows
    where BackendBusinessObjectBaseSAP is the standard Java Class in the ISA
    Error at
    com.sap.isa.core.eai.sp.jco.BackendBusinessObjectBaseSAP.getDefaultJCoConnection(BackendBusinessObjectBaseSAP.java:46)
    Thanks
    Chinju

  • Can't create JCO connection in Portal7 for ESS1.0

    Hi,
    I am in the Process of setting up ESS/MSS Rel 1.0 in Portal 7. The Portal is a WebAS ABAP+JAVA system.
    First step after installing Portal, I configured the SLD and created the Technical systems.  The sld is running and I have tested the sld from the Content Administrator->WebDynpro-> check SLD. It results sld successfully tested and I am able to start the sld also.
    After that I deployed the Business packages for ESS/MSS and selfservices via SDM.
    Now I am trying to create the JCO connection in the Content Administrator->WebDynpro->create/maintain JCO Connections, it throws the following error
    500   Internal Server Error
      Web Dynpro Container/SAP J2EE Engine/6.40 
    Failed to process request. Please contact your system administrator.
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
        at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
        ... 45 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
    Version null
    DOM version null
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:41:58[UTC], changelist=413534, host=pwdfm101), build date: Fri Aug 31 20:55:03 GMT+08:00 2007
    J2EE Engine 7.00 patchlevel
    Java VM Java HotSpot(TM) Server VM, version:1.4.2_15-b02, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: x86
    Session & Other
    Session Locale en_US
    Time of Failure Tue Sep 11 17:54:15 GMT+08:00 2007 (Java Time: 1189504455341)
    Web Dynpro Code Generation Infos
    sap.com/tcwdtools
    No information available null
    sap.com/tcwddispwda
    No information available null
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
         at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
         at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:236)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    This is very urgent, can any one of u help me on this....
    Thanks

    Hi,
    I am running Netweaver 7 and ERP2005.
    J2EE support pack is 9. The sap note that you mentioned is for NW2004 and our system is running on NW2004s.
    Now I am trying to reconfigure the sld. In case if you can suggest me another solution, I will be very happy to try that out...
    Thanks for your reply
    Edited by: Rakesh Bothra on Apr 20, 2011 4:23 AM

  • Not able to create JCO Connection

    Hi,
    I have created a new technical system 'Wed As ABAP" in SLD.Now while creating the JCO connection I am getting java.lang.NullPointerException the small detail of which are as given
    500   Internal Server Error
      Web Dynpro Container/SAP J2EE Engine/6.40 
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:985)
        at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
        ... 45 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727)
    Version null
    DOM version null
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0007.20060331081328.0000 (release=645_VAL_REL, buildtime=2006-03-31:06:24:04[UTC], changelist=396896, host=pwdfm101), build date: Mon Apr 23 17:10:46 GMT+05:30 2007
    J2EE Engine 7.00 patchlevel
    Java VM Java HotSpot(TM) Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
    Operating system Windows XP, version: 5.1, architecture: x86
    Session & Other
    Session Locale en_US
    Time of Failure Fri Apr 27 15:35:45 GMT+05:30 2007 (Java Time: 1177668345279)
    Web Dynpro Code Generation Infos
    sap.com/tcwdtools
    No information available null
    sap.com/tcwddispwda
    No information available null
    sap.com/tcwdcorecomp
    No information available null .
    Can anybody please tell why this error has occured?
    Regards,
    Pawan

    Hi,
    Refer the below link
    Download the Content from OSS, then import via SLD = Content Maintenance.
    https://service.sap.com/sap/support/notes/669669
    There are other related notes relating to CIM errors.
    Thanks,
    RamuV

  • How to Alert RFC connection failure via message mapping? Kindly Help!

    Hi Experts,
        I have a JMS - XI - RFC scenario.
    JMS receives the Rosattenet PIP contents and sends it to RFC function module in remote SAP R/3 system.
       I have a requirement where I have to monitor RFC connection failure because of the remote R/3 system being down. I have to send a email alert where the subject contains the PIP number to understand for which PIP the connection failed.
      The PIP number exists in the PIP content at the interface.
      If I use the Alert configuration in the runtime workbench for monitoring then I cannot dynamically pass the PIP number.
      Only way I think of triggering alert is in the message mapping via a Java UDF.
      But I am not sure how can I do this? How do I check in the UDF if RFC connection has failed? Is this the correct approach?
      How to acheive my requirement? Note that my email subject content is dynamic bacause if PIP number.
    Please help!
    Thanks
    Gopal
    Message was edited by:
            gopalkrishna baliga

    Hi Gopal,
    what version/sps of XI are u running?
    The easiest way to do what u want inside a UDF is to
    1. use JCo to try estabilish a connection to the remote SAP System
    2. if that fails, use JavaMail to send an email message
    Let your UDF work on the PIP number, accepting it as input, and (maybe) returning it as output if everything goes ok. Otherwise break the mapping execution as described by Michal in one of his last weblog (using Dynamic Configuration).
    Note that the above method doesn't guarantee that the message will be actually delivered, as some seconds could last between your check and the real RFC delivery operated by the Adapter Engine...
    I am evaluating a way to do the same with Alert Framework. I will let you know the result!
    Cheers,
    Alex

  • Random JCO Communication Failure Error after Hardware Migration

    Greetings experts,
    we had a migrated our XI server to new hardware and had couple of SLD related issues which were solved by the migration team. However, we are getting JCO communication failure very frequent whenever we use JCO from JAVA to call an RFC. The weird thing, if you restarted the message it will be successful.
    The error message in the message monitor :
    "COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection"
    Any idea to solve this random issue?

    Hi again,
    the number of connection was increased to 200 but with no effects. Also, the user used to connect is a system user which does not need a ticket.
    This is my connection code
                   mConnection = JCO.createClient("600", // Client
              "USER", // Username
              "PASSWORD", // Password
              "EN", // Language
              "hostname", // Host
              "01"); // System Number
    do I need to add anything else if I am using a clustered system?

  • Mapping: JCO Communication Failure

    Hi Experts,
    I am working on a scenario PROXY<-->PI<-->SOAP.
    When i trigger the proxy from SPROXY, the message gets stuck in PI with an error Mapping: JCO Communication Failure. I have checked the RFC destinations AI_RUNTIME_JCOSERVER and AI_VALIDATION_JCOSERVER in the PI system, both of which are successfully connected. the correct entiry is also maintaine in sxmb_adm.
    I am not sure what could be the issue otherwise. I am not sure if we are missing any configuration on the PI side.
    Any idea how can i get this resolved.
    Thanks in advance.
    Regards
    Tanzoom

    Hi Tanzoom,
    You get this kind of error when there are lots of messages to be processed simultaneously.  Every message mapping needs one connection. If all 10 available connections are blocked from other messages you get this kind of error. Try increasing the the number of processes in VisualAdmin.
    Also refer this below blog
    http://scn.sap.com/blogs/saprouter/2012/08/07/jcocommunicationfailure
    Best Regards,
    Monikandan.

  • System Error due to JCO communication failure? during mapping

    in my JDBC-XI-Proxy scenario,
    there is BPM with a transformation step,
    in that step, during execution it gives Jco failure error, and particularly when the payload is very large....
    my question is:
    1.  how JCo communication failure occurs in case of mapping??
    2. why its only when the payload is huge??

    Sudheep,
    1, The Mapping is alaways executed in the Java Stack. And so win the runtime there needs to be a connection between the ABAP stack and the Java Stack for the Mapping to get exectued. The TCP IP Connection AI_RUNTIME_JCOSERVER is used for this purpise in SM59.
    2. When the payload is huge , there can be a over flow of the java Heap memory and this needs to be increased. Ask your Basis team to increase the java heap size if you do not want to face this issue.
    Regards
    Bhavesh

  • Unable to create the JCO connections in webdypro (JAVA) No SLD Connection

    HI All,
    In webdynpro i am unable to create standard JCo connections. create Jco connections and Maintain Jco COnnections are disabled. when i click any of the standard content of the Jco connections it displays error message No sld check. But SLD is running fine. I have checked in Visual Admin there also SLD supplier is running fine.
    But i am unable to create or maintain the Standard content of the JCo Destinations.
    Thank You,
    Mahesh C

    Hi ,
    I am having all admin rights. And also i have checked in Check SLD Connection. It showing the error connection to SLD Could not opened successfully. But SLD is running fine and i have checked in Visual admin SLD datasupplier is running fine.
    When i check in the log of the SLD there it is showing
    #2852 11/18/2008 18:27:18.265 [SAPEngine_Application_Thread[impl:3]_29] FATAL com.sap.lcr.cimsrv.CIMOMServlet: SLD initialization failure, can not set up cluster-wide event notification. Please check your JMS provider for errors.
    Thrown:
    com.sap.sld.api.wbem.exception.CIMException: CIM_ERR_FAILED: Failed to initialize cluster notification. Please check your JNDI service and JMS provider for errors.
    Is that i need to change the CIM content?
    I could not able to get clue on this.
    Thank You,
    Mahesh C

  • Meta JCo connection issue - cannot have 2 systems for ESS????

    I have a finance R/3 system and also an HR R/3 System.
    I need to be able to use the FI system for the timesheet ESS screens and the HR system for the others.  I have used the iView Application parameter as documented;
    (sap-wd-arfc-useSys=SAP_R3_HumanResources:FIN&sap-wd-arfc-useSys=SAP_R3_HumanResources_MetaData:FIN)
    The JCo destinations have been configured and do work ....
    However the problem is that the meta data jco connection that is used first appears to be cached and is then used going forward for every subsequent screen. 
    Therefore if I leave the menu screens as they are by default my timesheet screen won't work because the meta connection has been opened to the HR system and therefore the meta and data connections now don't match - even though the parameter has been set as above the configuration is ignored.
    I get the following error message
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException:
    Accessing System DE7 is not possible because RFC Metadata was retrieved
    using System DH7. Please assure you have configured the RFC Connections
    properly. A Server restart may be necessary!
    So if I change the menu to use the finance system then the timesheet screen will work but none of the HR screens will work. (same error with the systems reversed)
    Is there any way of getting this to behave properly and make sure that the right Jco connection is used.  It is very frustrating because the configuration is correct, I just need to be able to force the applications to use the the Jco destination that has been defined for the iView.
    Regards
    Marina

    Hi, I have created new iview for Who's Who and put the below in Application Parameters:
    sap-wd-arfc-useSys=SAP_R3_HumanResources:UTL&sap-wdarfc-useSys=SAP_R3_HumanResources_MetaData:UTL&sap-wd-arfc-useSys=WD_MODELDATA_DEST:UTL&sap-wd-arfc-useSys=WD_RFC_METADATA_DEST:UTL&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics:UTL&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics_MetaData:UTL
    The Home Page Framework is working fine. but when clicking on the who's who service the below error is there:
    The initial exception that caused the request to fail, was: java.lang.NullPointerException at com.sap.pcuigp.tracking.BTrackingComp.isValuePackSystem(BTrackingComp.java:290) at com.sap.pcuigp.tracking.BTrackingComp.onInit(BTrackingComp.java:206) at com.sap.pcuigp.tracking.wdp.InternalBTrackingComp.onInit(InternalBTrackingComp.java:173) at com.sap.pcuigp.tracking.BTrackingCompInterface.onInit(BTrackingCompInterface.java:115) at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface.onInit(InternalBTrackingCompInterface.java:124) ... 75 more See full exception chain for details. System Environment Client Web Dynpro Client Type HTML Client User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30) Version null DOM version null Client Type msie7 Client Type Profile ie6 ActiveX enabled Cookies enabled Frames enabled Java Applets enabled JavaScript enabled Tables enabled VB Script enabled Server Web Dynpro Runtime Vendor: SAP, build ID: 7.0103.20081111115141.0000 (release=NW701_03_REL, buildtime=2008-12-07:13:19:14[UTC], changelist=51958, host=pwdfm246), build date: Mon Dec 20 02:32:06 CST 2010 J2EE Engine 7.01 PatchLevel 56102. Java VM IBM J9 VM, version:2.3, vendor: IBM Corporation Operating system AIX, version: 6.1, architecture: ppc64 Session & Other Session Locale en_US Time of Failure Wed Feb 09 14:56:21 CST 2011 (Java Time: 1297284981490) Web Dynpro Code Generation Infos sap.com/pb SapDictionaryGenerationCore 7.0103.20071003090459.0000 (release=701_SP_REL, buildtime=2008-11-05:19:55:10[UTC], changelist=463950, host=PWDFM201.wdf.sap.corp) SapDictionaryGenerationTemplates 7.0103.20071003090459.0000 (release=701_SP_REL, buildtime=2008-11-05:19:55:16[UTC], changelist=463950, host=PWDFM201.wdf.sap.corp) SapGenerationFrameworkCore 7.0103.20071003090713.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:07[UTC], changelist=463957, host=PWDFM201.wdf.sap.corp) SapIdeWebDynproCheckLayer 7.0103.20080730170941.0000 (release=701_SP_REL, buildtime=2008-11-05:20:00:15[UTC], changelist=494993, host=PWDFM201.wdf.sap.corp) SapMetamodelCommon 7.0103.20071003091208.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:51[UTC], changelist=463971, host=PWDFM201.wdf.sap.corp) SapMetamodelCore 7.0103.20071003091208.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:46[UTC], changelist=463971, host=PWDFM201.wdf.sap.corp) SapMetamodelDictionary 7.0103.20071003090530.0000 (release=701_SP_REL, buildtime=2008-11-05:19:52:58[UTC], changelist=463951, host=PWDFM201.wdf.sap.corp) SapMetamodelWebDynpro 7.0103.20080730170953.0000 (release=701_SP_REL, buildtime=2008-11-05:19:57:29[UTC], changelist=494995, host=PWDFM201.wdf.sap.corp) SapWebDynproGenerationCTemplates 7.0103.20081105123737.0000 (release=701_SP_REL, buildtime=2008-11-05:20:06:40[UTC], changelist=507414, host=pwdfm201) SapWebDynproGenerationCore 7.0103.20080730170941.0000 (release=701_SP_REL, buildtime=2008-11-05:20:00:20[UTC], changelist=494993, host=PWDFM201.wdf.sap.corp) SapWebDynproGenerationTemplates 7.0103.20081105123737.0000 (release=701_SP_REL, buildtime=2008-11-05:20:06:40[UTC], changelist=507414, host=pwdfm201) sap.com/tcwddispwda No information available null sap.com/pb_api SapDictionaryGenerationCore 7.0103.20071003090459.0000 (release=701_SP_REL, buildtime=2008-11-05:19:55:10[UTC], changelist=463950, host=PWDFM201.wdf.sap.corp) SapDictionaryGenerationTemplates 7.0103.20071003090459.0000 (release=701_SP_REL, buildtime=2008-11-05:19:55:16[UTC], changelist=463950, host=PWDFM201.wdf.sap.corp) SapGenerationFrameworkCore 7.0103.20071003090713.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:07[UTC], changelist=463957, host=PWDFM201.wdf.sap.corp) SapIdeWebDynproCheckLayer 7.0103.20080730170941.0000 (release=701_SP_REL, buildtime=2008-11-05:20:00:15[UTC], changelist=494993, host=PWDFM201.wdf.sap.corp) SapMetamodelCommon 7.0103.20071003091208.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:51[UTC], changelist=463971, host=PWDFM201.wdf.sap.corp) SapMetamodelCore 7.0103.20071003091208.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:46[UTC], changelist=463971, host=PWDFM201.wdf.sap.corp) SapMetamodelDictionary 7.0103.20071003090530.0000 (release=701_SP_REL, buildtime=2008-11-05:19:52:58[UTC], changelist=463951, host=PWDFM201.wdf.sap.corp) SapMetamodelWebDynpro 7.0103.20080730170953.0000 (release=701_SP_REL, buildtime=2008-11-05:19:57:29[UTC], changelist=494995, host=PWDFM201.wdf.sap.corp) SapWebDynproGenerationCTemplates 7.0103.20081105123737.0000 (release=701_SP_REL, buildtime=2008-11-05:20:06:40[UTC], changelist=507414, host=pwdfm201) SapWebDynproGenerationCore 7.0103.20080730170941.0000 (release=701_SP_REL, buildtime=2008-11-05:20:00:20[UTC], changelist=494993, host=PWDFM201.wdf.sap.corp) SapWebDynproGenerationTemplates 7.0103.20081105123737.0000 (release=701_SP_REL, buildtime=2008-11-05:20:06:40[UTC], changelist=507414, host=pwdfm201) sap.com/tcwdcorecomp No information available null Detailed Error Information Detailed Exception Chain java.lang.NullPointerException at com.sap.pcuigp.tracking.BTrackingComp.isValuePackSystem(BTrackingComp.java:290) at com.sap.pcuigp.tracking.BTrackingComp.onInit(BTrackingComp.java:206) at com.sap.pcuigp.tracking.wdp.InternalBTrackingComp.onInit(InternalBTrackingComp.java:173) at com.sap.pcuigp.tracking.BTrackingCompInterface.onInit(BTrackingCompInterface.java:115) at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface.onInit(InternalBTrackingCompInterface.java:124) at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface$External.onInit(InternalBTrackingCompInterface.java:198) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084) at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:219) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:273) at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.onInit(InternalFcEmployeeServicesInterface.java:198) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.onInit(InternalFcEmployeeServicesInterface.java:258) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084) at com.sap.xss.hr.wiw.FcWiwBusinessLogicComp.onInit(FcWiwBusinessLogicComp.java:217) at com.sap.xss.hr.wiw.wdp.InternalFcWiwBusinessLogicComp.onInit(InternalFcWiwBusinessLogicComp.java:414) at com.sap.xss.hr.wiw.FcWiwBusinessLogicCompInterface.onInit(FcWiwBusinessLogicCompInterface.java:115) at com.sap.xss.hr.wiw.wdp.InternalFcWiwBusinessLogicCompInterface.onInit(InternalFcWiwBusinessLogicCompInterface.java:298) at com.sap.xss.hr.wiw.wdp.InternalFcWiwBusinessLogicCompInterface$External.onInit(InternalFcWiwBusinessLogicCompInterface.java:358) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084) at com.sap.xss.hr.wiw.selection.VcWiwSelectionComp.onInit(VcWiwSelectionComp.java:212) at com.sap.xss.hr.wiw.selection.wdp.InternalVcWiwSelectionComp.onInit(InternalVcWiwSelectionComp.java:206) at com.sap.xss.hr.wiw.selection.VcWiwSelectionCompInterface.onInit(VcWiwSelectionCompInterface.java:162) at com.sap.xss.hr.wiw.selection.wdp.InternalVcWiwSelectionCompInterface.onInit(InternalVcWiwSelectionCompInterface.java:144) at com.sap.xss.hr.wiw.selection.wdp.InternalVcWiwSelectionCompInterface$External.onInit(InternalVcWiwSelectionCompInterface.java:220) at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564) at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438) at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196) at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110) at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108) at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215) at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200) at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73) at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860) at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220) at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1289) at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356) at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549) at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:593) at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:865) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:219) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

  • User Id creation for Jco connections

    Hi,
        Need to create a user for verifying the Jco connections. Please help me with the steps of creation and how can it restricted only for verifying the connections.
    Thanks

    Hi Daneil,
    Best way is to do it yourself.
    1 - Create a user having full access (SAP_ALL and SAP_NEW and RFC Full access as well).
    2 - Set up the JCO connection with this user ID.
    3 - Put a trace (ST01) on this user ID and then test the connection.
    4 - Analyze the trace file and create a role having all the access pulled in the trace.
    5 - remove all the access from the above user and assign the role created in 4.
    6 - Put a trace once again on this user Id, just to ensure that if there is a miss in any authorization(failure) then you will be able to capture that as well. Update the role accordingly.
    Hope this helps.

  • JCO connection pool is exhausted

    hi
    I am using RFC module in my web dynpro application. When the application is used for sometime, the JCO connection will get exhusted. The JCO connection will not release itself. I can't find any method in web dynpro to release the connection manually. How can I solve this problem?

    Hi,
    What is scope of the connection. View properties of MODELDATA and METADATA  destinations.
    You can change the scope of the connection..
    or
    wdContext.current<BAPI INPUT>Element().modelObject().modelInstance().disconnectIfAlive();
    For more ways , give a forum search.. There are a lot of close forum posts.. Gud luc..
    Regards
    Bharathwaj

Maybe you are looking for

  • Is there a way to control the number of consumed messages from JMS?

    Hi everyone, I have a BPEL process that is consumes messages from a foreign queue, performs a transformation, and passes it to Oracle Apps. I'm curious if there is a way to control the number of messages consumed at a time for processing. For example

  • Ipod touch not recognized by anything

    I have had my ipod touch for almost a year now and it has been working great. Until a couple months ago. It is not recognized by any computer in my house, so I can't charge it or put new songs on it. iTunes doesn't show up when I plug it in, i get no

  • Why can't I download apps onto my iPod touch?

    What is

  • Satellite A200 and Windows 7 64bit - How someone test it?

    Has anyone test and works with it. I have *A200 23W* with 4 gb memory, vista sp2 installed and i want to have a clear install on *windows 7 but 64bit version*. What do you think about?

  • Adobe Reader XI インストール後 "an internal error occurred" と表示が出て開けない.

    OS:windows7 pro Adobe ReaderⅪをインストールしたところ."an internal error occirred" と表示が出て開かなくなってしまいました. 何度か.アンインストール.インストールを繰り返してみましたが.変わりありませんでした. ネットで検索しても.レジストリを書き換えてください.などと出てきます. PC初心者なので.PCがおかしくなっても困るので.レジストリは極力変更したくありません. どうすれば直せるでしょうか.ご教授のほどよろしくお願いいたします.