Jco connection :null

Hi sap gurus
I am using rfc  connection for executing bapi using some jco connections. but if  the jco are being used for one time it is being executed . but when we deploy application another time . the exception is received as dynamicrfcexecution error jco connection:null.
when we change the poolsize it is being . the rfc is executed  for only one time.
please suggest a way to close jco connections . if already present.
Thanks & Regards
prasad

hi , logon mechanism  while creating the JCO Destinations.
Is  Logon Ticket
This is code what iam using for rfc access
Zhr_Emp_List_Input input = new Zhr_Emp_List_Input();
          wdContext.nodeZhr_Emp_List_Input().bind(input); 
     wdContext.nodeZhr_Emp_List_Input().currentZhr_Emp_List_InputElement().setPernr("10" );
          try {
               wdContext.nodeZhr_Emp_List_Input().currentZhr_Emp_List_InputElement().modelObject().execute();
               wdContext.nodeOutput().invalidate();
          } catch (WDDynamicRFCExecuteException e) {
               wdComponentAPI.getMessageManager().reportSuccess(e.toString());
                              // TODO Auto-generated catch block
               e.printStackTrace();
          }finally {          
     wdContext.currentZhr_Emp_List_InputElement().modelObject().modelInstance().disconnectIfAlive();  
for the above code where  Zhr_Emp_List_Input  is the rfc . which will return employee details when we set the Pernr(personal number) to rfc
the exception is
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error connecting using JCO.Client: null
for only one time the rfc is executing . for the other time if we increase the pool size or change the whole jco references for webdynprojava application . we are able to execute the application

Similar Messages

  • Error connecting using JCO.Client: null

    Hi,
    I created a WD app which uses  the RFC FM.  I followed How-To-build-webdynpro.pdf document to create the WD and trying to deploy and run, I see the view page but when I trigger the action via button UI element I get following error as exception in the try catch block of execute method
    In the NWA I see
    Could not create JCOClientConnection for logical System: 'WD_MODELDATA_DEST' - Model
    An exception has occurred: Erorr accessing cache [region]='XCM_SESSION_SCOPE'.
    [EXCEPTION]
    com.sap.isa.core.cache.Cache$Exception: Cannot return access for region 'XCM_SESSION_SCOPE'. Cache is not ready
    I'm using following existing JCO definition by configuring them with correct parameters.  Tested them successfully
    WD_RFC_METADATA_DEST
    WD_MODELDATA_DEST
    What am I missing?  In SM04 tcode I see 2 connections are opened with 2 Megabyte not released for a long time.  I think if connections are released correctly it should drop to 1 megabyte.  Is there anything that I need to do just after execute method as shown below (I have replaced function module with <FM> in below code)
    try {
             wdContext.node<FM>_Input().current<FM>_Get_InputElement().modelObject().execute();
         } catch(Exception exception) {
              msgMgr.reportException(exception.getLocalizedMessage(), false);
          wdContext.nodeOutput().invalidate();
          msgMgr.reportSuccess("Success");
    The error is in the catch block which is displayed on the view page.
    Thanks
    Praveen
    I modified the above code and put in finally block to close the connections as follows, please let me know if this is OK.  I still get error message as "Error connecting using JCO.Client: null" but no additional connections in the SM04 after adding finally block.
    try {
             wdContext.node<FM>_Input().current<FM>_Get_InputElement().modelObject().execute();
         } catch(Exception exception) {
              msgMgr.reportException(exception.getLocalizedMessage(), false);
         }finally {
              // disconnect the connection
              wdContext.<FM>_Get_InputElement().modelObject().modelInstance().disconnectIfAlive();     
    Edited by: Praveen11 on Oct 5, 2009 9:06 AM

    Thanks Satish.
    The issue is resolved.  I think it was to do with permission, as I was running directly from NWDS deploy and run the session didn't have proper authorisation or something that was causing this error.
    When I copy pasted the URL in the correct browser session window I got no error and function module was successfully executed.   However the issue now is that values are not showing up in the view may be to do with mapping context or model  I'll review and post back as different thread.
    Thanks
    Praveen

  • Error connection using  JCO.Client :null

    Hi,
    I have small doubt in JCO connection, can any one help me.
    In WebDynpro  application some time we are getting exception like Error connection using JCO.client : null.
    Connection :200 we are maintained in JCO configuration.
    If I call one RFC useing JCO it will created a session or connection to ECC server, because we are getting exception in server too many sessions to ECC server.  
    Write now we are not using any code to close the connection like.
    SaveModel svModel = (SaveModel)WDModelFactory.getModelInstance(SaveModel.class);
    svModel.disconnectIfAlive();
    If we use the above code it will close the connection or sessions.
    Is it recommended to write the code in every RFC calls or  in final block of all RFC calls ?
    Regards,
    Satya.

    Hi Satya
    /message/1944647#1944647 [original link is broken]
    /message/8499#8499 [original link is broken]
    Please go through this link.Hope it will be helpful for you
    Regards
    Ruturaj

  • JCO - Model Data connection null

    Hi Guys,
    We have a load of 300 concurrent users using 3 adaptive rfc models froma web dynpro project.
    I have set up both JCO Modeldata Destination and RFC Metadata Destination. .For Modeldata Destination, I set up as Message Server.
    JCo Pool Configuration  (default settings)
    Maximal Pool Size : 5
    Maximum Connections: 10
    Connection Timeout (msec.): 10
    Maximum Waiting Time (msec.): 30
    Logon Group: XXXX
    User Authentication: Ticket
    SNC: OFF
    I set up my RFC Metadata Dest as Application Server, User Authetication: Userid/Password.
    (This configuration is suggested by a lot SDN experienced fellows as best practice)
    Also I disconnect the connections immediately after execution in the finally block using
    wdContext.<your model element>().modelObject().modelInstance().disconnectIfAlive();
    But I get the below error after around 100 users logon and run the application.
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error connecting using JCO.Client: null
    I can see from my back end R/3 and also in the web dynpro console the connections still alive  for users and accumulating ..so wondering whats the use of disconnectIfAlive.
    I thought Maximum Connections of 10 in jco pool modeldata should suffice as this is for each usnique and not the total.Am I right here.
    Is there any other settings where I need to  specify that a maximum of around 400 logon is expected
    and jco pool configured accordingly? Also how to close the pool connections immediately when not in use..
    Please advise what I should do to solve this problem.
    Thanks.
    Ashok

    Hi Ashok,
    Why are using three models is there any specific buisness purpose or is it resuable?
    Every model consumes one connection.
    Look at page no. 38 of this document for optimising the use of JCOs in webdynpro
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/705f2b2e-e77d-2b10-de8a-95f37f4c7022
    What is the value of gw/max_conn in your R/3. This decides how many connections is allowed in the backend.
    http://help.sap.com/saphelp_nw04/helpdata/en/80/ee67f9591c442b98b6c81059fb552d/frameset.htm
    /people/sunil.ojha5/blog/2008/02/08/rfc-quota-part-2
    Look at page no. 8 of this document for setting gw/max_conn
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9d1b49ff-0701-0010-53ba-ab1d66794419
    Maximum value for gw/max_conn is 2000. Try to set some value below this.
    Best Wishes
    Idhaya R

  • WDDynamicRFCExecuteException: Error connecting using JCO.Client: null

    Hi
    This is a common problem,I have seen many threads , but following them did not solve my problem.
    I have the JCOs tested successful from WD Admin. When I create a sample WDJ application with RFC model and deploy it to the server, I get
    Exception:com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecution: Error connecting using JCO.Client: null.
    I have checked my binding , I have only one input parameter and the code is
          wdComponentAPI.getMessageManager().reportSuccess("Inside wdInit in Component ctrller");
          Z_Plm44_Obsoleteimpactanalysis_Input input = new Z_Plm44_Obsoleteimpactanalysis_Input();
         wdContext.nodeZ_Plm_Input().bind(input);
         wdContext.createZ_Plm_InputElement(input).setV_Type(wdContext.currentZ_Plm_InputElement().getV_Type());
    Also I have implemented closing the connection
    disconnectifalive
    I contacted the basis team... they tell me that everything is fine from their end. they have tried increasing the JCO connection pools.
    Thanks for your help in advance
    Karthika

    Hi Karthika
    Check this pdf and try to catch WDDynamicRFCExecution in catch block.
    Please put your code in try catch and also import com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecution in your code;
    http://www.sappro.com/downloads/WebDynproJava.pdf
    Re: User has no RFC authorization for function group.
    Hope this will help you.
    thanks
    Arun Jaiswal

  • Error in Connecting to BAPI (Error connecting using JCO.Client: null)

    Hi,
        I am trying to connect to a BAPI to extract data. However, I am getting this error
        Error connecting using JCO.Client: null
        Pls explain the meaning of the error and solution to the problem
    TIA
    Himanshu

    Hi,
    This means you are getting error while executing your model. its not able to use the JCO's.
    as I asked previously check your JCO status... its up and running????
    Here are some threads having same problem
    URGENT :Error connecting using JCO.Client: null
    Model and MetaData configarations  in JCO Connection
    Exception while executing
    PradeeP
    Edited by: pradeep bondla on Jul 31, 2008 11:53 AM

  • Error connecting using JCO.Client: null in xRPM in EP

    Hi Friends,
    I am getting the following error in xRPM through EP
    "Error connecting using JCO.Client: null"
    I can't enter xRPM, but I can enter other Business packages iViews.
    The problem is intermittant and user specific.
    Can you pls provide any input on this ?
    thanks in advance and warm regards
    Purnendu

    Hi Flavio,
    Thanks for your reply.
    The user is created both in the backend as well as in portal.
    The roles are also ok.
    The error I am getting only while accessing xRPM iViews.
    If I restart the instance the error is removed. But it reappears again may be after few days.
    This error is intermittant.
    May be it is related to the Maximum Number of JCo connections in the WebDynpro configuration.
    But I don't have much idea on that.
    Can you pls provide any help on this.
    Warm regards
    Purnendu

  • 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

  • Problems during creation of JCo Connections

    Hi everybody,
    i've a problem while creating JCo Connections in the Content Administrator of me WebAS.
    I can selct the connection i want to maintain, but at the second step, an new window appears and i get the following message. Does anybody have an idea and could help me.
    Best regards,
    Maik.
    An error has occurred:
    "Failed to process the request."
    Please contact your system administrator.
    Hide details
    Web Dynpro client:
    HTML Client
    Web Dynpro client capabilities:
    User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0), 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
    Web Dynpro runtime:
    Vendor: SAP, Build ID: 6.4010.00.0000.20040921144040.0000 (release=630_SP_REL, buildtime=2004-09-21:22:25:54[UTC], changelist=283399, host=PWDFM067)
    Web Dynpro code generators of DC sap.com/tcwdtools:
    No information available
    Web Dynpro code generators of DC sap.com/tcwddispwda:
    No information available
    Web Dynpro code generators of DC sap.com/tcwdcorecomp:
    No information available
    J2EE Engine:
    6.40 patchlevel 86216.32
    Java VM:
    Java HotSpot(TM) Server VM, version: 1.4.2_05-b04, vendor: Sun Microsystems Inc.
    Operating system:
    Windows 2000, version: 5.0, architecture: x86
    Error stacktrace:
    java.lang.NullPointerException

    Hi Henrik,
    I got exactly the same problem has you have with the same version (6.40 SP9). I have opened an OSS message ..
    Best regards,
    Christian DUCRET (SAP BAsis Team)

  • 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

  • How to create a model and JCO connection

    Hi all,
             The Userid and Password given while creating new model at Singleserver/Load balancing tab should be same as the userid and password given while creating JCO connection. i.e in JCO creation  while mapping modeldata to Application data and Metadata to metadata we will give some userid and password.
    will those 2 userids and passwords should be same.
    the error which i am getting is
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error connecting using JCO.Client: null
    Regards
    Padma N

    2 userids and passwords need not be same
    i got similar problem and this is how i resolved
    this is because jco connections are Using SSO and the user who is accessing that webdynpro application is not present in the backend system.
    please make sure user is there in the backend system from which you are getting data
    xxxxxxxxxxxxxxxxxxxxx
    Edited by: Armin Reichert on Feb 18, 2008 7:26 PM

  • URGENT: JCO.Client: null

    Hello
    We're using SAP EP 7.0 with webdynpro connected to SAP R3 4.6C by SapLogon Ticket.
    The connection can be done with certificates for our customers (authentification header) or via logon/password for internal test on our LAN.
    These webdynpro work fine on the LAN but when we connect via the web we have the error below :
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error connecting using JCO.Client: null
    Do you have any idea ?
    It's on our production environment so very urgent )
    Thanks

    Hi
    1.May be JCO's are not configured properly.Check your JCO's are up and running by pinging it in ContentAdmin->WebDynpro.
    2. its a simple problem of connection pooling. In your JCO connection settings change the maximum connections to 200. It will work.it  is good After you execute the Model please release the connection. The reason you are getting this JCO Client null is because the connection is not getting released.
    When you say the following code
    wdContext.current<BAPI_INPUT>.modelObject().execute();
    //Get the reference to the model and release the connection
    If your Model name is say "MO_Mymodel"  then
    MO_Mymodel model = (MO_Mymodel) WDModelFactory.getModelInstance(MO_Mymodel.class);
    model.disconnectIfAlive();
    This should release your connections. Also ensure you release the connections even if there is a exception :).
    Please refer the below forum also:
    Error connection using  JCO.Client :null
    JCO.Client: null
    com.sap.mw.jco.JCO$Exception: (102) JCO_ERROR_COMMUNICATION: JCO.Client not
    Thanks
    susmita

  • Model and MetaData configarations  in JCO Connection

    Hi all,
               while creating new model i used Load Balance option instead of Single Server.So while creating JCO connection what should be selected for ApplicationData and MetaData radio buttons.The error which i am got aftet deploying and running is
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error connecting using JCO.Client: null
    Is this error is because of LoadBalance configarartion while creating JCO for Destinations or at the client num which we gave at the starting step of creating JCO
    Regards
    Padma N

    i got similar problem and this is how i resolved
    this is because jco connections are Using SSO and the user who is accessing that webdynpro application is not present in the backend system.
    please make sure user is there in the backend system from which you are getting data
    xxxxxxxxxxxxxxxxxxxxxxx
    Edited by: Armin Reichert on Feb 18, 2008 7:26 PM

  • JCO.Client: null

    Hi,
       When and why does this occur and how to resolve this?
    Exception: Exception: com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error connecting using JCO.Client: null
    Thanks
    Sumathi

    Hi Sumathi,
    Hope u have properly configured the SLD and  already done the CIM object generation.
    If not ,
    refer this forum ..
    Re: getting a BAPI from an R/3 system
    i have already discussed the step - by step configuration of SLD in this forum .
    The same problem is discussed in this forum . refer this forum.
    Error connecting JCO.Client
    Regards
    Kishor Gopinathan

Maybe you are looking for