JCO Client Problem

Hello,
Im having a problem with JCo client connection. I am doing some BW queries that are bringing back a significant amount of data. Every now and then JCo crashes (bringing down the JVM as well) and this error message is dumped to the screen.
JCO [JNI-LAYER] cannot load backtrace library [jcobtrace.dll]
===== BEGIN DUMP =============================================================
Error Message: Illegal memory access. [54]
Exception Rec: EXCEPTION_ACCESS_VIOLATION (0xc0000005) at 0x341FC99D - memory at 0x00000000 could not be written.
Does anybody know what might be causing this? I would very much appreciate any help on this.
Thanks,
Corey

I've added the stack trace as well if that is of any help to someone.
[code]http-8081-Processor 16 id=63 idx=0x78 tid=3460 lastJavaFrame=0x2FCFF3BC
Thread Stack Trace:
     at [email protected]+763()@0x341FC99D
     at Javacom_sap_mw_jco_rfc_MiddlewareRFC_nativeSetMode@12+6533()@0x341F3EFD
     at Javacom_sap_mw_jco_rfc_MiddlewareRFC_nativeSetMode@12+9731()@0x341F4B7B
     at [email protected]+2007()@0x341FC0EC
     at com/sap/mw/jco/rfc/MiddlewareRFC$Client.nativeExecute(Lcom/sap/mw/jco/JCO$Client;Ljava/lang/String;Lcom/sap/mw/jco/JCO$ParameterList;Lcom/sap/mw/jco/JCO$ParameterList;Lcom/sap/mw/jco/JCO$ParameterList;Lcom/sap/mw/jco/JCO$ParameterList;Ljava/lang/String;Ljava/lang/String;I)V(Native Method)
     at com/sap/mw/jco/rfc/MiddlewareRFC$Client.execute(Lcom/sap/mw/jco/JCO$Client;Ljava/lang/String;Lcom/sap/mw/jco/JCO$ParameterList;Lcom/sap/mw/jco/JCO$ParameterList;Lcom/sap/mw/jco/JCO$ParameterList;Lcom/sap/mw/jco/JCO$ParameterList;Ljava/lang/String;Ljava/lang/String;I)V(MiddlewareRFC.java:1211)
     at com/sap/mw/jco/JCO$Client.execute(Ljava/lang/String;Lcom/sap/mw/jco/JCO$ParameterList;Lcom/sap/mw/jco/JCO$ParameterList;Lcom/sap/mw/jco/JCO$ParameterList;Lcom/sap/mw/jco/JCO$ParameterList;Ljava/lang/String;Ljava/lang/String;I)V(JCO.java:3684)
     at com/sap/mw/jco/JCO$Client.execute(Lcom/sap/mw/jco/JCO$Function;)V(JCO.java:3129)[/code]

Similar Messages

DynamicRFCException with JCO.client problem

Hi,
Iam trying to execute an RFC from webdynpro.Iam getting the following error.So as a result i dont get any result as expected on my screen as the RFC is not getting executed due to JCO problem.Please kindly let me know the reason.In the last line of the exception it talks about user authentication.I dont have any idea whats the reason.This happens as soon as my bapi execute statement in my controller is executed.
could not create JCOClientConnection for logical System: WD_MODELDATA_DEST - Model: class com.test.Getmodel. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error connecting using JCO.Client: null at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModel.prepareExecute(DynamicRFCModel.java:179) at com.test.Getmodel.bapi_Ben_Bus3029_Get_Evt_List(Getmodel.java:141) at com.test.Bapi_Ben_Bus3029_Get_Evt_List_Input.doExecute(Bapi_Ben_Bus3029_Get_Evt_List_Input.java:137) at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92) at com.avid.benefits.Benefitscust.executebapi(Benefitscust.java:128) at com.avid.benefits.wdp.InternalBenefitscust.executebapi(InternalBenefitscust.java:162) at com.avid.benefits.AvidusbenefitsView.wdDoInit(AvidusbenefitsView.java:97) at com.avid.benefits.wdp.InternalAvidusbenefitsView.wdDoInit(InternalAvidusbenefitsView.java:129) 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.bindRoot(ViewManager.java:579) at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295) at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183) at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291) 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.doGet(DispatcherServlet.java:46) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) 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(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Caused by: com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCException: Could not create JCOClientConnection for logical System: WD_MODELDATA_DEST - Model: class com.test.Getmodel. Please assure that you have configured the RFC connections and/or logical system name properly for this model! at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModel.getCurrentlyUsedJcoClient(AiiModel.java:210) at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModel.prepareExecute(DynamicRFCModel.java:170) ... 42 more Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection. at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:152) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.getJCOClientConnection(WDSystemLandscape.java:30) at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModel.getCurrentlyUsedJcoClient(AiiModel.java:189) ... 43 more Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for 'WD_MODELDATA_DEST' at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:649) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:476) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:233) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:218) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:129) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150) ... 45 more Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: User not authenticated - unable to establish JCO connection with SSO. at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:584) ... 50 more
Error connecting using JCO.Client: null
Error connecting using JCO.Client: null: Could not create JCOClientConnection for logical System: WD_MODELDATA_DEST - Model: class com.test.Getmodel. Please assure that you have configured the RFC connections and/or logical system name properly for this model!: Error while obtaining JCO connection.: Failed to resolve connection parameter for 'WD_MODELDATA_DEST': User not authenticated - unable to establish JCO connection with SSO.

Hi Swathi,
The problem may be with JCo destinations. If you have authorization in Portal, navigate to Content Administration -> Web Dynpro.
In the left side you can see deployed web dynpro applications. Check in local, sap, or any of your custom namespace. Browse & select to your application. Right side you can see JCo destinations for your application. If they are in green color , means they are created. If not, ask your basis team to create them. If they are n green color, ping and test them. if they are working fine or not.
If they are fine, try to deploy after you have logged into the portal.
Regards,
Siva

JCo Client Programming and Error Handling

Hi all,
I was wondering if anybody could help me out with some advice on error handling when writing code to send messages to SAP via a JCo Client, particularly IDocs.
I understand from my reading that IDocs are always sent asyncronously to the SAP system from JCo, using JCO.Client.send(). So it is possible (and I have some test code working to do this) to force an exception with say a malformed IDoc, and catch the exception in my code.
But due to the asyncronous nature of the send functionality for IDoc, I cannot see any way of getting back any "business level" exceptions (e.g. Order Number does not exist, Unknown Material, etc.)
So my question is, is it possible to receive any of these type of error messages when sending IDocs to an SAP system using JCo? Perhaps by setting up a JCo Server with the correct error/exception listeners to receive these messages - but are they even sent out in the way?
If not what is the process for handling them?
It is of course possible to look in the SAP system using txn WE02 and see the problem/error but that does not help me to propagate this back to the sending application or to maintain state alignment between the two apps.
Any advice much appreciated!!
Chris

Hi Anil,
you should check on those trheads:
<a href="https://www.sdn.sap.com/irj/sdn/thread?messageID=3104772&#3104772">https://www.sdn.sap.com/irj/sdn/thread?messageID=3104772&#3104772</a>
<a href="https://www.sdn.sap.com/irj/sdn/thread?messageID=579794&#579794">https://www.sdn.sap.com/irj/sdn/thread?messageID=579794&#579794</a>
Regards,
Gianluca Barile

Error connection using JCO.Client

Hello all,
I got the following problem "Error connection using JCO.Client" and don't know what's wrong. All connections works at the content administration when I test the connection.
Can anyone help me please?
Best regards
Petra

Hi,
I almost tested the JCO connection with the 'test' button successfully at the content administrator. I tested again and it still works. And I have a stand alone webdynpro application (no portal).
Now I got the following error message after completing the coding with 'e.printStackTrace().'.

"Error connection using JCO.Client:null"
"[Ljava.lang.StackTraceElement:@60db08"
"Could not create JCOClientConnection for logical System:WD_MODELDATA_DEST - Model: class impersonalaccout.intro.model.Z_Fh0002_Datenverwaltung.Please assure that you have configured the RFC connections and/or logical System"
"com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCException:Error connection using JCO.Client:null"
"com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCException: Could not create JCOClientConnection for logical System: WD_MODELDATA_DEST - Model:class impersonalaccout.intro.model.Z_Fh0002_Datenveraltung.Please ***"
Can anyone explaine me what's wrong?
Bye
Petra

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

Error connecting JCO.Client

Hello!
I've got a little problem with Adaptive RFC calls: After exactly 10 times executing my call I always get the following Exception:
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error connecting using JCO.Client: null
Has anybody by any chance got an idea why or how to handle this problem?
Thank you very much in advance!
Best Regards

Hi
Well its a simple problem of connection pooling. In your JCO connection settings change the maximum connections to 200. It will work.
well what i would advice is that 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 :).
Hope that helps you.
regards
ravi

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

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

JCo encoding problem

Hi,
I have a problem where a login over JCo fails when I have the character u20AC in the password.
This is a bit strange, because the JCo Client itself has the UTF-16 encoding, and the password is UTF-8. The password is UTF-8 because it also contains Ä which works.
I set up a test password with umlauts, and all umlauts seem to work. Everytime I have a u20AC or even &, the login fails.
I tried setting "jco.client.unicode" to 1, but this didn't seem to work. I am not even sure the property "jco.client.unicode" even exists, although there is a "jco.server.unicode" which in my case is not helpful - I'm creating a client, not a server.
The remote SAP System is a Unicode system by the way.
Any ideas? Oh, I am using JCo 2.1.8.
T00th

Stefan,
thanks a lot for the explanation, now we know at least what happens. As this seems so crappy though, I cannot help but rant a little...
If JCo would do the logon with UTF-16/Unicode by default, you won't be able to logon to a Non-Unicode system without specifying the jco.client.codepage parameter.
Not really as long as a proper code page conversion from UTF-16 to the code page used by the system would've been implemented on the server side. Instead of choosing codepage 1100 the more natural choice seems UTF-8.
As far as I know since application server 6.10 the server "knows" about Unicode (e.g. see [here|http://help.sap.com/saphelp_nw04/helpdata/en/cb/56453c3ff4110ee10000000a11405a/frameset.htm]). Anyhow, if I understood you correctly you can actually set the code page for the logon data using jco.client.codepage, but what happens when you use Unicode codepages on non-Unicode systems?
OSS note [794411 - Supported codepages of SAP Java Connector 2.1 and 6.x|https://service.sap.com/sap/support/notes/794411] seems to list the supported codepages for JCo 2.1.x (stops at 2.1.5 though, maybe no changes after that). UTF-8 is not listed (i.e. 4110), yet no error occurs when I specify this on JCo 2.1.8 when connecting to a non-Unicode SAP 4.7 system (kind of expected an exception).
Finally OSS note [975768 - Deprecation of Java features with non-Unicode Backend|https://service.sap.com/sap/support/notes/975768] seems to put an end to all that madness. Well let's hope JCo follows and deprecates the jco.client.codepage parameter as soon as possible...
Here's something funny though: When using JCo 3.0.5 I get client codepage 1100 when connecting to a non-Unicode 4.7 system and client codepage 4102 when connecting to a Unicode ECC 6.0 system (without setting jco.client.codepage). So maybe this is just a concern for JCo 2.x, but still it seems odd that we have codepage references in JCo 3.0.5 (DestinationDataProvider.JCO_CODEPAGE, JCoCustomDestination.setCodepage(String) and others).
Cheers, harald

JCO.Client.execute() in transactional mode (asynchronously) crashed

Trying to call JCO.Client.execute("STFC_CONNECTION", input, output, tid) on fresh new SAP NetWeaver Developer Studio installation I receive the following:
An unexpected error has been detected by HotSpot Virtual Machine:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x10008e7b, pid=3392, tid=3416
Java VM: Java HotSpot(TM) Client VM (1.5.0_03-b07 mixed mode, sharing)
Problematic frame:
C [sapjcorfc.dll+0x8e7b]
An error report file with more information is saved as hs_err_pid3392.log
If you would like to submit a bug report, please visit:
http://java.sun.com/webapps/bugreport/crash.jsp
JCO [JNI-LAYER] cannot load backtrace library [jcobtrace.dll]
Just mentioned that declaration has 'tables' parameters, not output.
public void execute(java.lang.String name,
 JCO.ParameterList input,
 JCO.ParameterList tables,
 java.lang.String tid)
Should this work at all, is the problem caused by Java 1.5, or <your suggestions here...>?

Hi,
I recommend at least to use the latest available JCo patch level which was JCo 2.1.10.
Besides, JCo 2.1 was never officially supported by SAP for any JVM higher than version 1.4 - and you are using version 1.7. Meanwhile JCo 2.1 is completely out of SAP support.
I suggest to start with migrating your application and use JCo 3.0 instead.
Best regards,
Stefan

Create JCO Client in JSP

Hi all,
I have the following problem: How I can create the JCOClient in the JSP? In the AbstractPortalContent I use this code
IJCOClientService clientService = (IJCOClientService request.getService("jcoclient");
IJCOClientPoolEntry poolEntry;
try
poolEntry = clientService.getJCOClientPoolEntry("SAP_cFolders", request);
}catch (Exception e)
response.write("Error obtaining connection: " + e);
return;
JCO.Client client = null;
client = poolEntry.getJCOClient();
client.connect();
In the JSP I don't able to create the JCO.Client.
Someone can help me?
Thanks in advance,
Stefano

hi,
I am giving u the sample code of the application which i had done in Abstract portal component u try this for establishing JCO connection
hope this helps...
public class calingrfc extends AbstractPortalComponent
     private JCO.Client jcoClient;
      Rfccaling_PortType insFunc = new Rfccaling_PortType();
      Ztrng_Show_Input ip = new Ztrng_Show_Input();
      Ztrng_Show_Output op = new Ztrng_Show_Output();
    public void doContent(IPortalComponentRequest request, IPortalComponentResponse response)
// try {
//     this.connect();
//      insFunc.messageSpecifier.setJcoClient(jcoClient );
//     String temp = request .getParameter("text1");
//      ip.setTrainingid1(temp);
//} catch (RuntimeException e) {
//     // TODO Auto-generated catch block
//     e.printStackTrace();
//     private void connect() {
//                    try {
//                         jcoClient =
//                              JCO.createClient("700","developer","satyam","EN","sap02","01");
//                              jcoClient.connect();
//                    } catch (Exception e) {
//                         System.out.println("Error connecting to SAP ::" + e.getMessage());
//                         e.printStackTrace();
//     private void disconnect() {
//                    try {
//                         jcoClient.disconnect();
//                    } catch (Exception e) {
//                         System.out.println(
//                              "Error dis-connecting to SAP ::" + e.getMessage());
//                         e.printStackTrace();

What happens if JCO.Client object not disconnected?

Hi All,
Can anyone tell me what happens if a JCO.Client( which is connected to SAP) is not disconnected? Will it be connected? or JCO disconnects it after sometime? or SAP itself disconnects it?
JCO.Client client = JCO.createClient(....);
client.connect();
If I run this simple code and leave it, what will happen to the connection opened?
Thanks in advance.

We are using JCO with SAP J2EE and have found something strange. We are setting the idle_timeout property and the SAP user is logging off, however we accumulate DISCONNECTED sessions in the SAP gateway. If the gateway limit is reached, additional connections fail. We used a modified version of the sample program to isolate the problem.
Test Program:
import java.io.IOException;
import com.sap.mw.jco.*;
public class Test {
 public static void main(String args[]) {
 byte instring[] = new byte[20];
 JCO.Client jcoClient = JCO.createClient("200", "user", "password", "EN",
 "bhha.na.pg.com", "00");
 jcoClient.setProperty("idle_timeout","60");
 jcoClient.connect();
 System.out.print("Read:");
 System.out.flush();
 try {
 System.in.read(instring);
 } catch (IOException e) {
 e.printStackTrace();
During 60 second period, transaction smgw shows the following information as expected. There is also a logged in user in SM04.
 44 7BWGF21 javaw t0331 CONNECTED <unknown 99703871 INT 15:13:10 0 0
After 60 seconds, the user disappears from SM04, however the smgw connection goes to a disconnect state as follows.
 44 7BWGF21 javaw t0331 DISCONNECT <unknown 99703871 INT 15:14:44 0 0
This session stays in this state until the enter key is pressed and the java app terminates. This is problem with a J2EE server app were the java process does not terminate.
Thanks,
Harry

JCO.Client not connected in repository call (EP7)

Hi guys,
please can someone help me with this error msg?
I dont understand why we getting this error msg, for some users they can run reports and others get this msg.
500 Internal Server Error
BEx Web Application
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:
JCO.Client not connected in repository call
com.sap.mw.jco.JCO$Exception: (102) JCO_ERROR_COMMUNICATION: JCO.Client not connected in repository call
at com.sap.mw.jco.JCO$Repository.getVersion(JCO.java:20290)
at com.sap.mw.jco.JCO$Repository.queryFunctionInterface(JCO.java:20630)
at com.sap.mw.jco.JCO$Repository.queryFunctionInterface(JCO.java:20351)
at com.sap.mw.jco.JCO$Repository.getFunctionInterface(JCO.java:20465)
at com.sap.mw.jco.JCO$BasicRepository.getFunctionTemplate(JCO.java:19533)
Details: Full Exception Chain
System Environment
Server
BI Java Release: 7 - Patch level: 0000000009 - Description: BI Web Applications Java - Additional info: - Production mode: true
BI ABAP unknown
Java Virtual Machine Java HotSpot(TM) 64-Bit Server VM - Sun Microsystems Inc. - 1.4.2_12-b03
Operating System Linux - ia64 - 2.6.9-22.0.1.EL
Full Exception Chain
Log ID 0012799E22D40054000001AF00006B9400042A20B9AF8861
com.sap.ip.bi.base.exception.BIBaseRuntimeException: JCo exception thrown when connecting to system "SAP_BW"
 at com.sap.ip.bi.base.application.service.rfcproxy.impl.jco640.Jco640Proxy.createFunction(Jco640Proxy.java:87)
 at com.sap.ip.bi.base.application.service.impl.application.ApplicationSettingsService.initializeProperties(ApplicationSettingsService.java:130)
 at com.sap.ip.bi.base.application.service.impl.application.ApplicationSettingsService.initialization(ApplicationSettingsService.java:124)
 at com.sap.ip.bi.base.application.impl.Application.createService(Application.java:477)
 at com.sap.ip.bi.base.application.impl.Application.getProperty(Application.java:624)
 at com.sap.ip.bi.base.application.impl.Application.initialization(Application.java:229)
 at com.sap.ip.bi.base.application.ApplicationFactory.createApplication(ApplicationFactory.java:132)
 at com.sap.ip.bi.base.application.ApplicationFactory.createApplication(ApplicationFactory.java:63)
 at com.sap.ip.bi.webapplications.runtime.impl.Page.constructPage(Page.java:729)
 at com.sap.ip.bi.webapplications.runtime.impl.Page.<init>(Page.java:647)
 at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.createPage(Controller.java:504)
 at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:911)
 at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:851)
 at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:380)
 at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:21)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
 at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
 at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
 at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
Many thanks in advance
Jo-lize

Hi, you can fix the problem ?
i have same problem in BI7 and EP7, when launch Template Installer.
Create Destination in ABAP Import not successful Element 'SAPConfigLib.DES.Unclassified.createRfcDestination':!BrokerImport.import_of_element_failed!!BrokerImport.Fehler!com.sap.tc.lm.ctc.cul.cpi.exceptions.CPIBaseException: <Localization failed: ResourceBundle='com.sap.tc.lm.ctc.cul.cpi.CPIResourceBundle', ID='com.sap.tc.lm.ctc.cul.cpi.BaseException_BASE_EXCEPTION', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.tc.lm.ctc.cul.cpi.BaseException_BASE_EXCEPTION:com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaServiceWriter.writeElement!BrokerImport.LINE!157-:com.sap.tc.lm.ctc.cul.broker.BrokerImport.importElement.86
-:com.sap.tc.lm.ctc.cul.broker.BrokerImport.importElement.128
-:com.sap.tc.lm.ctc.cul.broker.BrokerImport.importElement.128
-:com.sap.tc.lm.ctc.cul.serviceimpl.importservice.CULConfigurationImport.importConfiguration.96
-:com.sap.tc.lm.ctc.ccl.templateinstaller.StepExecuter.run.41
Element 'SAPConfigLib.DES.Unclassified.createRfcDestination':Error during executing Java Reflection:JCO.Client not connected in repository call

JCO Client Problem

Similar Messages

Maybe you are looking for