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

Similar Messages

JCO Call - Executing SAP Transactions

I'm trying to execute one transaction - providing the necessary input i.e. Creating a Service Entry sheet.
However, the return message indicated that it is erroneous - throwing the message "Service specifications in wrong structure".
Does this imply that the import parameters (tables etc) are somewhat wrongly input?
Anyone encountered this before?

Hi
calling BAPI_ENTRYSHEET_CREATE.
passing in
Importparameter = ENTRYSHEETHEADER
TABLES = ENTRYSHEETACCOUNTASSIGNMENT, ENTRYSHEETSERVICES, ENTRYSHEETSRVACCASSVALUES.
When I commented out ENTRYSHEETSERVICES and ENTRYSHEETSRVACCASSVALUES, I can create the service entry sheet. So I am suspecting it's either these 2 tables that are giving me the problem. Yet to know what - we wont need to populate most values in those 2 tables no?
Thanks

JCO Call - Executing SAP Transaction

I'm trying to execute one transaction - providing the necessary input i.e. Creating a Service Entry sheet.
However, the return message indicated that it is erroneous - throwing the message "Service specifications in wrong structure".
Does this imply that the import parameters (tables etc) are somewhat wrongly input?
Anyone encountered this before?

Hi
calling BAPI_ENTRYSHEET_CREATE.
passing in
Importparameter = ENTRYSHEETHEADER
TABLES = ENTRYSHEETACCOUNTASSIGNMENT, ENTRYSHEETSERVICES, ENTRYSHEETSRVACCASSVALUES.
When I commented out ENTRYSHEETSERVICES and ENTRYSHEETSRVACCASSVALUES, I can create the service entry sheet. So I am suspecting it's either these 2 tables that are giving me the problem. Yet to know what - we wont need to populate most values in those 2 tables no?
Thanks

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]

Error when executing the transaction SXMB_IFR (PI 7.00)

Hello All,
When I am executing the transaction SXMB_IFR I am getting the following message in the bottom.
The message is "Enterprise Services Builder address not maintained" and nothing is opened, I mean I am in the initial screen only.
And when I tried to check ditectly using URL "http://<hostname>:<port>/rwb/index.jsp" and tried to click on " Component Monitoring " it is giving the error "java.lang.NullPointerException" .
And when I tried to click on "Performance Monitoring" it is giving the error as follows
"5 Message(s) : SLD agent unable to specify domain - Error class com.sap.aii.rwb.exceptions.BuildLandscapeException: No System Landscape Directory registered - Attempt to create JCo connection object failed for domain null - Integration Server unable to specify a JCo client - No component names available from Integration Server - "
Can any body tell me how to correct this error.
Thanks,
Sekhar.

Hi Sekhar,
Have you tried SLDCHECK
All the service User/Password are maintained in exchange
profile(not advisable to change though)
http://<hostname>:5<sys_number>00/exchangeProfile
If ur changing it u might need restart of Web AS.
Run transaction SLDCHECK and see if ur getting any errors.
also check this link for sldcheck
http://help.sap.com/saphelp_nw04/helpdata/en/78/20244134a56532e10000000a1550b0/frameset.htm
Connection to SLD does not work
Connection to SLD does not work
/thread/202496 [original link is broken]
Please go through the following link:
Problem with SLD connection
Problem with SLD connection
Also,
http://help.sap.com/saphelp_nw04/helpdata/en/78/20244134a56532e10000000a1550b0/content.htm
Step 41 "configuring system landscape directory" runs forever during instal
It was solved with OSS note 764176.
Please read OSS note carefully.
connection to SLD failed
Reward points if this helps
Regards
Pragathi.

POP capabilities are gotten in authorization mode, and not transaction mode

I am using Javamail in an email client that requires UIDL support for POP3 servers. There are some servers that return the UIDL capability only in transaction mode, not in authorization mode (eg. pop.aol.com). I am unable to connect to such servers once I upgraded to javamail 1.4.4, since it is now looking at the capabilities before executing the UIDL command. However, it gets the capabilities in authorization mode, and servers like the one above do not send the UIDL capability in this mode. If the capabilities were refreshed in transaction mode (once login was done), UIDL would be returned. This looks like a bug. Is there a workaround for this?

This definitely looks like a bug in AOL's server, please report it to them.
RFC 2449 says:
   A capability description MUST document in which states the capability
   is announced, and in which states the commands are valid.
   Capabilities available in the AUTHORIZATION state MUST be announced
   in both states.
   If a capability is announced in both states, but the argument might
   differ after authentication, this possibility MUST be stated in the
   capability description.
   (These requirements allow a client to issue only one CAPA command if
   it does not use any TRANSACTION-only capabilities, or any
   capabilities whose values may differ after authentication.)
6.8. UIDL capability
   CAPA tag:
       UIDL
   Announced states / possible differences:
       both / noThis says to me that the UIDL capability, if supported, must be announced in both states
and must not change between states.
You can set the session property mail.pop3.disablecapa to "true" to disable the use of the CAPA
command, which will cause it to assume UIDL is supported.

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.
<b>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
</b>

Error sending IDOC from JCO Client to PI AEX 7.3.1

Hi All
We have a requirement to send an IDOC from a non SAP System to our ECC via PI AEX :
JCO.Client --> PI AEX --> SAP ECC
At this time, we are testing this scenario with a JAVA Client with JCO Library (3.0.10).
Destination to PI is OK
Destination to our SAP ECC (for IDocRepository) is OK
But by sending the IDOC to PI we are getting the following error, Exception is raised on the PI System and sent back to the JCO Client :
com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: while trying to invoke the method java.lang.Object.hashCode() of an object loaded from local variable 'key' (raised by system <extern>|PiSystem)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:670)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.execute(MiddlewareJavaRfc.java:1881)
    at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:1120)
    at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:953)
    at com.sap.conn.jco.rt.RfcDestination.execute(RfcDestination.java:1465)
    at com.sap.conn.jco.rt.AbapFunction.execute(AbapFunction.java:319)
    at com.sap.conn.idoc.jco.JCoIDoc.send(JCoIDoc.java:323)
    at com.sap.conn.idoc.jco.JCoIDoc.send(JCoIDoc.java:353)
    at sap_connector_examples.IDocClientExampleToJavaPO_pbs.main(IDocClientExampleToJavaPO_pbs.java:97)
Caused by: RfcException: [<extern>|PiSystem]
    message: while trying to invoke the method java.lang.Object.hashCode() of an object loaded from local variable 'key'
    Return code: RFC_SYS_EXCEPTION(3)
    error group: 104
    key: RFC_ERROR_SYSTEM_FAILURE
Exception raised by <extern>|PiSystem
PI Destination:
jco.destination.repository_destination=ABAP_AS_WITHOUT_POOL
jco.client.gwhost=PiSystem
jco.client.gwserv=sapgw01
jco.client.tpname=XI_IDOC_DEFAULT_PID
jco.client.type=E
ECC Destination: (ABAP_AS_WITHOUT_POOL)
jco.client.lang=en
jco.client.client=100
jco.client.passwd=****
jco.client.user=User
jco.client.sysnr=00
jco.client.ashost=ECCSystem
We have already set the PI VM System parameter jco.allow_non_abap_partner to 1
ECC User has S_RFC Rolle
I will be thankful for any advise.
Thank You
Regards
Stéphane

Hi
InboundRA (Resource Adapter) is green (Fully available).
What do you mean by maintaining JCO RFC Destination in PI ?
We have set the inboundRA Properties has follow :
ProgramID : XI_IDOC_DEFAULT_PID
DestinationName : XI_IDOC_DEFAULT_DESTINATION
Local: true
mutliRepository : ED1=XI_IDOC_DEFAULT_DESTINATION_ED1;ES4=XI_IDOC_DEFAULT_DESTINATION_ES4;MD1=XI_IDOC_DEFAULT_DESTINATION_MD1;ES1=XI_IDOC_DEFAULT_DESTINATION_ES1;PD1=XI_IDOC_DEFAULT_DESTINATION_PD1;
GatewayServer and Service are pointing to our PI System
BindingKey : PI_AAE_IDOC
And for each Repository we created a destination in NWA pointing to the corresponding ECC System.
(target host pointing to the ECC System and the Gateway host pointing to the PI System)
Our Installation isn't new but it is the first time we are configuring the System for this scenario:
JCO.client --> PI AEX
Regards
Stéphane

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

Select in read only transaction mode / insert in write mode

hello,
i have a following question: i have 2 db, one is rdb and one oracle
im extracting data out of table out of rdb and inserting them into oracle via OWB;
however this is run in read-write mode and causes locks in rdb; the only way to prevent locks is to run a select statement that accesses rdb in 'read only' transaction mode;
my question is: is this possible to split up the select and insert statements of oracle into 2 different transaction modes, so that select statement is run in 'read-only' mode and insert in 'write' mode?
i appreicate tips on how this could be achieved
thx
rgds

Hello,
is this something like:
insert into oracle_table (select * from rdb_table@rdb_link);
Then it is easy, you just need to use an sql init file for your OCI Service. Create a file, e.g. sql_init.ini that contains this line:
declare transaction read only;
Then alter your service so that it sees the sql init file, e.g.:
SQLSRV> alter service <your OCI service> sql_init_file sql_init.ini
The service owner must have the privileges to read the file. You need to restart the OCI service.
Then a statement of the above kind results in a read only transaction on Rdb side, and the insert on Oracle side is done.
I hope your SQL/Services version is a recent one (actual version is 7.3.1), because of this (from the SQL/Services Release Notes 7.2.0.1):
5.4.25 Declare Transaction in SQL Init File Being Overridden
In releases of OCI Services for Oracle Rdb prior to 7.2.0.1, if a DECLARE
TRANSACTION statement was executed in the SQL initialization file of a service, it would
be overridden by a DECLARE TRANSACTION statement executed later by OCI Services
for Oracle Rdb. Toward the end of the connection setup, OCI Services for Oracle Rdb would
execute a DECLARE TRANSACTION statement to set the default transaction
characteristics to be close to Oracle default transaction characteristics. This would supersede
any DECLARE TRANSACTION statement in the SQL initialization file. Starting with
release 7.2.0.1, OCI Services for Oracle Rdb recognizes that a DECLARE TRANSACTION
statement has been executed and will not execute another one.
Regards
Wolfgang
P.S.: It is always better to place Rdb related questions in our communities at https://communities.oracle.com/portal/server.pt/community/rdb_product_family_on_openvms . Those are watched by Rdb Engineering and Support. It was by pure chance that I saw this forum thread.

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

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

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

Timeout Error in Call Transaction on Asynchronous Abap Proxy

Hi Gurus!!
We have a problem with a Call Transaction on Asynchronous Abap Proxy. When the process of Call Transaction (transaction CO02) takes more than 10 minutes, the process is cancelled with sy-subrc 1001 and the Abap Proxy continues with the execution. Strangely, there is a short dump in ST22 on transaction CO02, although on the ABAP Proxy we don't get any dump.
When this process is called from a Background Job no dumps are get.
Somebody knows if there is a problem with the Asynchronous ABAP Proxy executing CALL TRANSACTION statementent?
Thanks and regards,
Manuel.

and the message after recording is
Number               1
Transaction          F-22
SY-SUBRC             0
Messages
FB01                SAPMF05A                                0301WEZ001                066
FB01                SAPMF05A                                0300WEZ001                066
FB01                SAPMF05A                                0300EEZ001                073
I F5 573                   Correct the error reported before on the next screen
FB01                SAPMF05A                                0300WEZ001                066
FB01                SAPMF05A                                0300EEZ001                073
I F5 573                   Correct the error reported before on the next screen
FB01                SAPMF05A                                0330WEZ001                066
FB01                SAPMF05A                                0301WEZ001                066
FB01                SAPMF05A                                0301WEZ001                066
FB01                SAPMF05A                                0301WEZ001                066
S F5 312                   Document 100001677 was posted in company code 3100

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

Similar Messages

Maybe you are looking for