JCo Server Programming

          I'm using SAP JCo version 2.0.8 to integrate with SAP 4.6C I'm familiar with using
          JCo as a client calling SAP, but currently I'm trying to setup JCo as a server
          on Weblogic. Does anyone have some insights in how to do this and would like
          to share this with us?
          Thanks!

Hi,
I've recently come upon this page in the JCo documentation:
http://help.sap.com/saphelp_nw04/helpdata/en/b0/46e13d82fcfb34e10000000a114084/frameset.htm
Does that help answering your questions?

Similar Messages

JCo server programming, properties and connection settings

Greetings, SAP professionals.
The reason I come to this forum is that I'm hoping to gain some insights into the use of the SAP Java Connector (JCo). I am a developer who was tasked with making a new component for a systems integration application. As is typical of integration software, our app can link together various different systems using a variety of protocols, as well as providing the means to apply business logic on messages passed from one location to another. We already have a connector acting as an SAP client which was implemented using JCo. Now, we were asked to develop a new component: a server capable of accepting RFCs from a remote SAP system acting as client. The server is to be created using the JCo classes, so basically an extension of JCo.Server, with some logic for creating function templates from configuration files.
However, while I'm understanding the structure of the Java API, it's not entirely clear to me just what the classes do. I've found the JavaDoc for JCo to be mostly descriptive of the interface of classes and methods, but not really explaining what these achieve, or how. So I'm hoping to be set straight, as I fear I'm kind of misunderstanding the functionality of JCo... Being mainly an integrations developer, I unfortunately often have to settle for gaining a superficial knowledge of a variety of systems to quickly interface with them, so I don't have any prior knowledge of SAP but still need to be able to implement something with JCo without too much delay.
The most important question I have is this: when a JCO.Server implementation is started, does it act as a fully standalone component capable of receiving calls, or does it merely act as a sort of listener for some main SAP system? I'm not talking about a reliability on the two .dll files (or .so for Linux) that are required for the use of JCo, I just wish to know if the JCo package is entirely self-sufficient for server functionality or if it is intended to be linked to some SAP system.
A second problem I have is that the parameters passed to various constructors aren't clear to me... I'm not familiar with SAP terminology, nor have I worked with any client apps that make use of an SAP system.
The meaning of client strings, gwhost, gwservice, ashost, system IDs and program IDs mostly elude me, especially when it comes to knowing what client parameters must match what server parameters.
In order to familiarize myself with the classes, I've tried playing around with them a bit trying to create a small test app that first starts a JCO.Server instance, then tries to make a remote function call to it with a JCO.Client (within the same class, for simplicity and debugging purposes). I was wondering if this actually makes sense... Would a JCo client be capable of connecting to a JCo server, all running purely in Java, or is that nonsense?
To eliminate some common troubleshooting options, I'll quicly describe the steps I've taken:
Both librfc32.dll and sapjcorfc.dll were placed in the Windows system32 folder. Maybe only librfd32 needs to be placed there, but I copied both anyway to make sure.
The directory containing the jar file and both dll files is included in my environment path variable.
I've added a line to the C:\Windows\system32\drivers\etc\services file as follows:
sapgw00 3300/tcp #SAP System Gateway Port
I've opened port 3300 in my Windows firewall. In fact, I also tested with the firewall completely turned off.
However, I do not manage to get my test class to work. I've tried ports 3300, 3200 and 3600. I've tried various permutations of the client and server properties. I've tried removing the line from the services file, which would prompt the client to state upon connecting that the service "sapgw00" is unknown. When I add it back in, the error changes to "partner not reached", so it is definitely picking something up.
The server itself starts just fine, but connecting through a client doesn't work. My class source code is posted below. Maybe what I'm trying to do doesn't make any sense, but at the moment it's my best guess.
I realize this is a pretty long post and the class, while not exactly big, also implies a bit of reading of its own. But if anyone could give me any answers that are new to me, I'd be hugely grateful. Right now I'm kind of stuck, and just setting up the service and letting our customer test on it is a somewhat slow approach that can't match developing and testing on one and the same host.
Preliminary thanks to everyone who took the effort to read this.
//Start of code
import java.util.Properties;
import com.sap.mw.jco.IFunctionTemplate;
import com.sap.mw.jco.IMetaData;
import com.sap.mw.jco.IRepository;
import com.sap.mw.jco.JCO;
public class Test {
 public static void main(String[] args) {
 Test test = new Test();
 ServerThread serverThread = test.new ServerThread();
 serverThread.start();
 while(!serverThread.isReady) {
 try {
 Thread.sleep(5000);
 } catch(final InterruptedException i) {
 System.out.println("Rudely awakened");
 try {
// JCO.Function func = getSampleFunction(test, "STAY");
// serverThread.server.handleRequest(func);
// System.out.println(func.getExportParameterList().toXML());
// func = getSampleFunction(test, "STOP");
// serverThread.server.handleRequest(func);
// System.out.println(func.getExportParameterList().toXML());
 final Properties clientProps = getClientProps();
 JCO.Client client = JCO.createClient(clientProps);
 client.connect();
 IRepository rep = JCO.createRepository("1", client);
 IFunctionTemplate templ = rep.getFunctionTemplate("TEST_FUNC");
 JCO.Function function = templ.getFunction();
 function.getImportParameterList().setValue("STAY", "FIELD1");
 client.execute(function);
 JCO.Function function2 = templ.getFunction();
 function2.getImportParameterList().setValue("STOP", "FIELD1");
 client.execute(function2);
 } catch(final Exception e) {
 e.printStackTrace(System.out);
 serverThread.requestStop();
 while(serverThread.isAlive) {
 try {
 Thread.sleep(5000);
 } catch(final InterruptedException i) {
 System.out.println("Rudely awakened");
 } finally {
 private static Properties getClientProps() {
 final Properties props = new Properties();
 props.setProperty("jco.client.client", "100");
 props.setProperty("jco.client.user", "");
 props.setProperty("jco.client.passwd", "");
 props.setProperty("jco.client.lang", "");
 props.setProperty("jco.client.sysnr", "00");
 props.setProperty("jco.client.ashost", "/H/localhost/S/sapgw00");
 props.setProperty("jco.client.gwhost", "localhost");
 props.setProperty("jco.client.gwserv", "sapgw00");
 return props;
 public class ServerThread extends Thread {
 public void run() {
 isAlive = true;
 IRepository repos = new TestRepository("testrep");
 repos.addFunctionInterfaceToCache(getFunctionInterface());
 server = new TestServer(repos);
 server.start();
 System.out.println("Server successfully started");
 isReady = true;
 while(!stop) {
 try {
 Thread.sleep(1000);
 } catch(final InterruptedException i) {
 System.out.println("Wouldn't let me sleep...");
 stop = server.stopRequested;
 server.stop();
 isAlive = false;
 System.out.println("Server successfully stopped");
 public void requestStop() {
 server.requestStop();
 public TestServer server;
 public boolean isReady = false;
 public boolean isAlive = false;
 public class TestServer extends JCO.Server {
 public TestServer(IRepository rep) {
 super("localhost", "sapgw00", "PROGID", rep);
 public void handleRequest(JCO.Function fct) {
 try {
 JCO.ParameterList importParams = fct.getImportParameterList();
 final String importXML = importParams.toXML();
 System.out.println("XML representation of import parameters: ");
 System.out.println(importXML);
 final String input = importParams.getString("FIELD1");
 System.out.println("FIELD1 value: " + input);
 JCO.ParameterList exportParams = fct.getExportParameterList();
 if(input.equals("STOP")) {
 exportParams.getField("FIELD2").setValue("OK");
 stopRequested = true;
 catch(JCO.AbapException ex) {
 throw ex;
 catch(Throwable t) {
 throw new JCO.AbapException("SYSTEM_FAILURE", t.getMessage());
 public boolean checkAuthorization(String functionName, int authorMode, String partner, byte[] key) {
 System.out.println(functionName + " " + partner);
 return true;
 public void requestStop() {
 stopRequested = true;
 public boolean stopRequested = false;
 public class TestRepository extends JCO.BasicRepository implements IRepository {
 public TestRepository(String name) {
 super(name);
 public static IMetaData getFunctionInterface() {
 JCO.MetaData metaData = new JCO.MetaData("TEST_FUNC");
 metaData.addInfo("FIELD1", IMetaData.TYPE_STRING, 4);
 metaData.setFlags(0, IMetaData.IMPORT_PARAMETER);
 metaData.addInfo("FIELDX", IMetaData.TYPE_STRING, 8);
 metaData.setFlags(1, IMetaData.IMPORT_PARAMETER & IMetaData.OPTIONAL_PARAMETER);
 metaData.addInfo("FIELD2", IMetaData.TYPE_STRING, 2);
 metaData.setFlags(2, IMetaData.EXPORT_PARAMETER);
 return metaData;
 public static JCO.Function getSampleFunction(Test test, String s) {
 TestRepository testRep = test.new TestRepository("testrepository");
 testRep.addFunctionInterfaceToCache(getFunctionInterface());
 JCO.Function func = testRep.getFunctionTemplate("TEST_FUNC").getFunction();
 func.getImportParameterList().setValue(s, "FIELD1");
 return func;
 private static boolean stop = false;

If I understood you correctly, you want to provide a "service" that can be called from SAP. To provide this service you've chosen to implement an (external) RFC server program via JCo. One common method for RFC server programs is to register in SAP on the gateway - you do this by supplying the three parameters
<ol>
<li>jco.server.gwhost - SAP gateway host on which the server should be registered (so this would be the server name or IP address of the SAP gateway; localhost is only correct, if your RFC server program runs on the same server as the SAP gateway)</li>
<li>jco.server.gwserv - Gateway service, i.e. the port on which a registration can be done</li>
<li>jco.server.progid - Program ID under which your RFC server program can be reached (free, made-up case sensitive name, that should represent the service your RFC server is providing)</li>
</ol>
So essentially you're creating a listener, that is registered in SAP and waits for any invocations. Within SAP they will define a RFC destination, which basically represents a TCP/IP connection pointing to the SAP gateway where you registered with the given program ID. If you want more details, check the SAP help pages for <a target="_blank" href="http://help.sap.com/saphelp_nw04/helpdata/en/22/04262b488911d189490000e829fbbd/content.htm">RFC destinations</a> (you're looking for destination type T, see explanations <a target="_blank" href="http://help.sap.com/saphelp_nw04/helpdata/en/22/042652488911d189490000e829fbbd/content.htm">here</a>).
Usually gateway host and service (port) are given to you by the SAP basis folks and you tell them which program ID you're using. They will then enter those parameters in an RFC destination of type T in SAP. So no need for any of the client parameters you've mentioned. Although, I'd like to repeat, it's usually handy to also have SAP logon parameters maintained on your RFC server program, so that you can utilize the repository data from SAP (might be irrelevant in your case).
Hope this clarifies it a bit...

JCo Server - ABAP to NWJ2EE - Metadata Access

Hi Friends,
we are here in a project, which also deals to fetch data from an external non ABAP system. The calling system is a 4.6C. We therefore use the JCo server service (registered RFC connection), which can be called by the 4.6C system. Basicly it works, but we discovered, that currently we get a single point of failure, because we have to provide repository information (connection information) within the visual admin.
The help page
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/b0/46e13d82fcfb34e10000000a114084/frameset.htm">SAP JCo Server Programming</a> and its examples, would lead us to provide connection properties, e.g. within the coding. Therefore, within visual admin, section "JCo RFC Provider", JNDI name, program ID and connection properties are maintained. The J2EE application therefore use those predefined entries. When starting the first request to JCo server, metadata are being read from repository, which here must be the calling system (our 4.6C system). Within the repository section, you can only provide dedicated application server login information, not e.g. a load balanced one. Thus this is for reasons of high availability, a single point of failure. An ABAP instance itself is not HA required, because you can use multiple of them. The message service itself but is HA required.
Now after this long explanation my question:
Are we on the right way, using e.g. visual admin to define the registered server programs, etc - or is there a more integrated, flexible integration possible?
Perhaps, we need only the correct entry point of documentation or workshops, to direct our project developers to the right way.
All information I found about higher integration was only for Web Dynpro - and therefore for JCo client integration. But this is not our scenario.
thanks a lot in advance for your replies,
reiner leibig

You might benefit by reading the JCO pdf delivered with the jco download from sapservice.com....(free)....
Usually it is easier to define the structure and the function interface as an SAP function even if there is no body (abap to java). This means that the JCO will read correctly all the metainformation about the function. You then call the function as an RFC specifying the host...
Have fun...
In your case I would read carefully the example (getting the company code info etc...)
It shows how to manipulate the table returned by ABAP...

JCO Server Instances

We have developed JCO Server program ,so that the ABAP calls the JCO Server program,so that we can set values in the Export Parameters of the RFM.This I wrote using the Example5 code,but I need to understand ,that if we define two or three instances of JCO.Server,what does it actually mean,does the ABAP program automatically calls these instances,how is the calls to JCO.Server made and to which server,how is that determined.
Our scenario: We have written exit routines for our sales order creation,and we want to override the price of the material ,obtaining from a separate database.So exit routines,RFMS which calls the handleRequest method of Server.How do we acheive concurrency in the request to Servers.

Not quite sure if this is what you were asking, but..
Is the JCO server program registered at the gateway?
If so, and you run several instances which all use the same program ID, SAP gateway will load-balance the calls.
http://help.sap.com/saphelp_nw04/helpdata/en/51/aea438ec2a7e26e10000009b38f8cf/content.htm

Where to find JCo server examples under NW04

I am using NW04 and do not know where to look for or download demos showing how to set up a JCo server program that can be called into using ABAP. I have seen references to a JCo.zip file, but that file seems to have been pulled from the downloads. Can someone tell me where I can download sample programs?

Hi,
you can download Jco (and yes, documentation and examples are included in the download package) from SAP Service Marketplace at: http://service.sap.com/connectors -> SAP Java Connector -> Tools & Services and then select the Jco version you need from the right hand side frame.

JCO.Server Error while trying to execute a RFC program from SAP

Hi,
We are connecting to an external registered server program from SAP via Web Methods.
The external server program is registered with the SAP Gateway. We have created a TCP/IP RFC destination and are able to connect to the destination successfully via SM59.
An RFC function is created in SAP and is called using the syntax CALL FUNCTION "/NGN/BAPI_STRE_SEARCH_PROCESS" DESTINATION 'PRDB2B'. We have also handled the COMM_FALIURE and SYSTEM_FALIURE exceptions in the function call.
We are monitoring the gateway via SMGW and see a connection log to the RFC destination as below
Number - 10
LUname - dev01
TPName - sapgw00
User - KRAORANE
Status - CONNECTED
Symbolic - PRDB2B
Conversation - 86520353
Prot - REG
SAP return code - 0
CPIC rtn code - 0
The external program returns results as expected.
However sometimes the RFC fails and returns the message JCO.Server could not create server function /NGN/BAPI_STRE_SEARCH_PROCESS.
We are not able to figure what exactly is causing this error. Any help will be highly appreciated.
-Kiran

Hi,
Please see the below links..
JCO.Server Error while trying to execute a RFC program from SAP
Re: JCO.Servcer could not find server function
Re: JCO.Server could not find server function 'SET_SLD_DATA'
/people/kathirvel.balakrishnan2/blog/2005/07/26/remote-enable-your-rfchosttoip-to-return-host-ip-to-jco
Re: interfacing SAP with an existing java applications
http://help.sap.com/saphelp_nw04/helpdata/en/47/80f671ee6e4b41b63c0fe46bd6e4f8/content.htm
http://www.sapgenie.com/faq/jco.htm
Regards
Chilla..

Calling JCO RFC Server program from JCO RFC client

Hi,
I have an RFC registered server program which implements JCO.Server. It seems to be working fine, when called from SAP.
For testing purposes, I was trying to write a JCO client program which would take the place of the SAP client.
This program opens a connection to the RFC server and executes a function e.g.
JCO.Client client = JCO.createClient("xx.yy.com", "sapgw35", "MYPROGID");
client.connect();
client.execute(function);
The RFC server program receives the call fine, when I test with a simple function which has no table parameters. However when I tried a more complex function with table parameters, I get an serverExceptionOccurred from the RFC server program:
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: connection closed without message (CM_NO_DATA_RECEIVED)
    at com.sap.mw.jco.rfc.MiddlewareRFC$Server.nativeListen(Native Method)
    at com.sap.mw.jco.rfc.MiddlewareRFC$Server.listen(MiddlewareRFC.java:1368)
    at com.sap.mw.jco.JCO$Server.listen(JCO.java:6805)
I have tried to initialize the repositories in both server and client programs correctly, so that the function is in the cached function list and the table structures in the cached structures list before the function is invoked. But I am not sure if there is still something I am missing, so any ideas would be welcome.
Thanks,
Richard

JCO example 5 is a very good one for server side programming.
try the example,somethings you 'd better make clear.
1) JCO.server
2) repositories--data mapping
3) parameters: export import,table...
further topic:
1) JCO pool
2) tRFC,qRFC
After you have success in Client side programming,try example 5.
Regards

JCO - RFC_ERROR_SYSTEM_FAILURE: com/sap/mw/jco/JCO$Server

Hi,
I call from Java an ABAP RFC and this RFC in turn call back the Java stack and it fails.
At Java side I get:
#1#com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: com/sap/mw/jco/JCO$Server
     at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516)
     at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1515)
     at com.sap.mw.jco.JCO$Client.execute(JCO.java:3996)
     at com.sap.mw.jco.JCO$Client.execute(JCO.java:3544)
     at com.sap.sup.admin.setup.SolManRfcAdapter.getJabapLandscape(SolManRfcAdapter.java:787)
     at com.sap.sup.admin.setup.SetupUpgrader.execute(SetupUpgrader.java:52)
At ABAP side I get:
Category               ABAP Programming Error
Runtime Errors      CALL_FUNCTION_REMOTE_ERROR
ABAP Program      CL_DIAGLS_SMSY_FACTORY========CP
Application Component SV-SMG-DIA
Date and Time        21.09.2009 17:50:59
Short text
     "com/sap/mw/jco/JCO$Server"
Is it allowed to call JAVA -> ABAP -> JAVA from JCO point of view?
Thanks in advance!
Regards,
Serge.

Hi Serge,
Two doubts:
- Does your RFC work when you call it directly from the SE37 puting the same input parameters used by Java application?
- Was the RFC changed after the coding of Java application? If so, the interface between Java and RFC must be regenerated.
Regards,
Rodrigo.

RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA'

Hi, All
the system is PI 7.0 EHP1 oraclei Win2003 server, I configured SLD but I run RZ70, having error "RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA' ". I know there are lot of tread about this error, but none of themsolve my problem. all JCO, RFC connections and SDL DATA supplier(VA) seem OK. error message in SM21 is "Could not send SLD data"
detail from SM21
The system could not send the data that has been collected automatical
for the System Landscape Directory (SLD). Check whether the gateway
configured in transaction RZ70 has been started and whether the SLD
bridge has been registered with this gateway.
You can use transaction SM59 to check this in the sending system for t
implemented RFC destinations. The RFC destinations have the standard
names "SLD_UC" for Unicode sending systems and "SLD_NUC" for non-Unico
sending systems. If a different RFC destination has been entered in
RZ70, check this destination instead.
You can use the Gateway Monitor to check the target gateways. In ABAP
systems, this monitor is started with transaction SMGW, or you can use
the external SAP program "gwmon". Check whether the specified gateway
has an active registration.
OF COURSE I checked RFC of SLD_UC and SMGW
any different ideas
Regards
ABH

Hi
Please check the following notes are implemented
Note 906454
Note 907729
You may be aware but if you are not --->RZ70 creates the required SLD* RFCs during runtime - therefore if you have defined these RFCs manually first using the same namespace you can get RFC conflicts which result in a failed submission
Please also check the user in the RFC is known to both systems and has required authorization to write to SLD
Generally with SLD you have to install or select a suitable gateway to handle incoming data supply traffic
Also the gateway you are using has be known to SLD and reflected in RZ70 - i.e these defintions have to be the same
It is also recommended to delete all references to SLD_* RFCs in data supplier and target SLD
after a failed submission attempt to allow RZ70 to recreate these consistently once the above has been checked
Best wishes
Stuart

"jco.server.unicode" is gone in JCO 3.0.5??!!

Recently we have migrated from   JCO 2.1.8 to 3.0.5.   Currently we are witnessing some problems with communications from non-Unicode Sap systems.
In the previous version (JCO 2.1.8) JCoIDoc.Server had a property "jco.server.unicode" in the latter one the property is gone.
AS far as I understand, JCo3 Server based on the data sent form a client recognizes encoding and applies proper conversion. However when we try to establish a non-Unicode connection ( from a Unicode enabled system), through setting In the SM59 transaction (tab MDMP & Unicode) u201ECommunication Type with Target Systemu201D to Non-Unicode, we are getting the following error :
com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "??????????????????
????????å å" with extension "     SAPCFL CF5CL          ???" is unavailable.
        at com.sap.conn.idoc.rt.DefaultIDocDocument.(JCoIDocDocument.java:92)
        at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:170)
        at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:80)
        at com.sap.conn.idoc.jco.JCoIDoc$DefaultJCoIDocRuntime.createIDocDocumentList(JCoIDoc.java:144)
        at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:107)
        at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:153)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3300)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2780)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2598)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2489)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2310)
        at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:277)
        at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:337)
        at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:238)
        at java.lang.Thread.run(Thread.java:619)
11:15:20,062 ERROR Sap server details
Class: com.syncron.bpe.engine.extinterface.sap.idoc.SapIDocServer
Program id: GIM
Thread name: JCoServerThread-1
Registered (at gateway) connection count: 5
Max thread count: 1
Exception occured
com.sap.conn.jco.JCoException: (104) RFC_ERROR_SYSTEM_FAILURE: IDocException occurred (raised by system karbie-nc6400|a_rfc)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:639)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2395)
        at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:277)
        at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:337)
        at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:238)
        at java.lang.Thread.run(Thread.java:619)
Caused by: RfcException: karbie-nc6400
    message: IDocException occurred
    Return code: RFC_FAILURE(1)
    error group: 104
    key: RFC_ERROR_SYSTEM_FAILURE
Exception raised by karbie-nc6400|a_rfc
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2785)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2598)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2489)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2310)
        ... 4 more
Caused by: RfcException: karbie-nc6400
    message: IDocException occurred
    Return code: RFC_FAILURE(1)
    error group: 104
    key: RFC_ERROR_SYSTEM_FAILURE
Exception raised by karbie-nc6400|a_rfc
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3329)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2780)
        ... 7 more
Caused by: com.sap.conn.idoc.IDocRuntimeException: IDocException occurred
        at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:151)
        at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:153)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3300)
        ... 8 more
Caused by: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "???????
???????????????????å å" with extension "     SAPCFL CF5CL          ???" is unavailable.
        at com.sap.conn.idoc.rt.DefaultIDocDocument.(JCoIDocDocument.java:92)
        at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:170)
        at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:80)
        at com.sap.conn.idoc.jco.JCoIDoc$DefaultJCoIDocRuntime.createIDocDocumentList(JCoIDoc.java:144)
        at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:107)
        ... 10 more
With JCO 2.1.8 we used to solve it through setting the mentioned "jco.server.unicode"   to 1, in the current one it seems that there is not much to configure regarding encoding.
Please advice.

In unicode ABAP backend systems you always have to set the destination in SM59 to "Unicode" if the communication partner is JCo. There is no choice for setting the Non-Unicode option. It won't work.
JCo3 does not require a manual setting of the "jco.server.unicode" property any longer. Therefore the property has been deleted. In JCo3 you don't have to take care for this anymore.

JCO server problems

Hello,
We've developed JCO server which serve as a bridge between SAP R/3 and MS SQL database system. In R/3 system is created TCP/IP destination and JCO server connects to this destination as a registered program.
In our test environment everything works fine. In customer production environment I face this behaviour:
After installation of solution it works. But after "some time", when I try to test destination in SM59 and I've got this error:
SM59 - test connection
connection to partner broken / CPI-C error CM_PRODUCT_SPECIFIC_ERROR
COMPONENT      NI (network interface)
COUNTER        2422932
ERROR TEXT     Connection reset by peer
ERROR NUMBER   232
MODULE         niuxi.c
LINE           1204
RETURN CODE    -6
What is interesting, problem persist, if i turn off JCO server (I expect error message, that no program is registered!),.... so I change the registered program ID (in SM59), change this in configuration of JCO server - it works.. but again after some time I've got that error.
R/3 version is 4.6c
Can you give suggestions, how to solve this problem (where should be the problem)?
Thanks for any answer.
Best Regards,
Juraj

Hi,
It gives me the correct IP when I ping yes. It's only when the SLD tries to resolve IP via JCO destinations. Yesterday I put in all hosts in my landscape into the hosts file of the SLD, disabled the NIC that it shouldn't be using and restarted.
Still it tries to resolve hosts in my landscape to 10.150.83.XXX. How is this possible??
Thanks - any other ideas?
.: HP

JCO Server implementation questions

Hi experts,
I want to try to create a JCO Server with the JCO 3 library.
I'm kinda lost in all the links I've found since there is still a lot of things from the JCO 2 on the internet and I don't understand everything I'm doing.
Please note that there is already a working Java JCO server with old IBM tools and we need to migrate to JCO 3.
So here are my questions :
What do I have to do exactly in the sm59 transaction ?
Here is what I get in the RSGWLST transaction http://i.imgur.com/IRgAyO8.png http://i.imgur.com/YyfDQbt.png (Loic-PC is my machine so I guess my java jco server is up.) Is everything ok ?
I have followed this link (Java Program for Creating a Server Connection - Components of SAP Communication Technology - SAP Library) to create my java jco server. What exactly are ServerDataProvider.JCO_GWHOST, ServerDataProvider.JCO_GWSERV and above all ServerDataProvider.JCO_PROGID)
How do I testmy Java JCO server ? I understood that I have to call STFC_TRANSACTION in se37 where I put my jco destination (previously set up in sm59 ?) and a string but I have a dump when I'm tying that.
I hope someone can help me, everything is still really blurry to me.
Regards
Here is the code I use to try to connect :
 static String SERVER_NAME1 = "JCO_SERVER";
 static String DESTINATION_NAME1 = "ABAP_AS_WITHOUT_POOL";
 static String DESTINATION_NAME2 = "ABAP_AS_WITH_POOL";
 static
 Properties connectProperties = new Properties();
 connectProperties.setProperty(DestinationDataProvider.JCO_ASHOST, "172.16.200.114");
 connectProperties.setProperty(DestinationDataProvider.JCO_SYSNR, "00");
 connectProperties.setProperty(DestinationDataProvider.JCO_CLIENT, "500");
 connectProperties.setProperty(DestinationDataProvider.JCO_USER, "develop2");
 connectProperties.setProperty(DestinationDataProvider.JCO_PASSWD, "passw0rd");
 connectProperties.setProperty(DestinationDataProvider.JCO_LANG, "en");
 createDataFile(DESTINATION_NAME1, "jcoDestination", connectProperties);
 connectProperties.setProperty(DestinationDataProvider.JCO_POOL_CAPACITY, "3");
 connectProperties.setProperty(DestinationDataProvider.JCO_PEAK_LIMIT, "10");
 createDataFile(DESTINATION_NAME2, "jcoDestination", connectProperties);
 Properties servertProperties = new Properties();
 servertProperties.setProperty(ServerDataProvider.JCO_GWHOST, "sapdevdb02");
 servertProperties.setProperty(ServerDataProvider.JCO_GWSERV, "sapgw00");
 servertProperties.setProperty(ServerDataProvider.JCO_PROGID, "JCOServer");
 servertProperties.setProperty(ServerDataProvider.JCO_REP_DEST, "ABAP_AS_WITH_POOL");
 servertProperties.setProperty(ServerDataProvider.JCO_CONNECTION_COUNT, "2");
 createDataFile(SERVER_NAME1, "jcoServer", servertProperties);

Hi Loic.
The properties GWHost is Gateway Host and GWSERV stands for Gateway Server.
Please look at this link to get more details:
Possible Parameters (SAP Library - Components of SAP Communication Technology)
Could you please put your full code for this class?
I'm saying this because the code you have wrote only creates the propreties file that JCO uses to configure the server but you have to run your server through the main statement.
You have to do something like that on your StfcConnectionHandler class.
public static void main(String[] args) {
 step1SimpleServer();
See my example:
StfcConnectionHandler class--------------------
package main;
import com.sap.conn.jco.JCoException;
import com.sap.conn.jco.JCoFunction;
import com.sap.conn.jco.server.DefaultServerHandlerFactory;
import com.sap.conn.jco.server.JCoServer;
import com.sap.conn.jco.server.JCoServerContext;
import com.sap.conn.jco.server.JCoServerFactory;
import com.sap.conn.jco.server.JCoServerFunctionHandler;
public class StfcConnectionHandler implements JCoServerFunctionHandler {
private static final String SERVER_NAME1 = "YOUR_SERVER_NAME";
public void handleRequest(JCoServerContext serverCtx, JCoFunction function) {
System.out
.println("----------------------------------------------------------------");
System.out.println("call : " + function.getName());
System.out
.println("ConnectionId : " + serverCtx.getConnectionID());
System.out.println("SessionId : " + serverCtx.getSessionID());
System.out.println("TID : " + serverCtx.getTID());
System.out.println("repository name : "
+ serverCtx.getRepository().getName());
System.out
.println("is in transaction : " + serverCtx.isInTransaction());
System.out.println("is stateful : "
+ serverCtx.isStatefulSession());
System.out
.println("----------------------------------------------------------------");
System.out.println("gwhost: " + serverCtx.getServer().getGatewayHost());
System.out.println("gwserv: "
+ serverCtx.getServer().getGatewayService());
System.out.println("progid: " + serverCtx.getServer().getProgramID());
System.out
.println("----------------------------------------------------------------");
System.out.println("attributes : ");
System.out.println(serverCtx.getConnectionAttributes().toString());
System.out
.println("----------------------------------------------------------------");
System.out.println("req text: "
+ function.getImportParameterList().getString("REQUTEXT"));
function.getExportParameterList().setValue("ECHOTEXT",
function.getImportParameterList().getString("REQUTEXT"));
function.getExportParameterList().setValue("RESPTEXT", "Hello World");
static void step1SimpleServer() {
JCoServer server;
try {
server = JCoServerFactory.getServer(SERVER_NAME1);
} catch (JCoException ex) {
throw new RuntimeException("Unable to create the server "
+ SERVER_NAME1 + ", because of " + ex.getMessage(), ex);
JCoServerFunctionHandler stfcConnectionHandler = new StfcConnectionHandler();
DefaultServerHandlerFactory.FunctionHandlerFactory factory = new DefaultServerHandlerFactory.FunctionHandlerFactory();
factory.registerHandler("STFC_CONNECTION", stfcConnectionHandler);
server.setCallHandlerFactory(factory);
server.start();
System.out.println("The program can be stopped using <ctrl>+<c>");
public static void main(String[] args) {
step1SimpleServer();
StepByStepServer class
package main;
import java.io.File;
import java.io.FileOutputStream;
import java.util.Properties;
import com.sap.conn.jco.ext.DestinationDataProvider;
import com.sap.conn.jco.ext.ServerDataProvider;
public class StepByStepServer
 static String SERVER_NAME1 = "SERVER";
 static String DESTINATION_NAME1 = "ABAP_AS_WITHOUT_POOL";
 static String DESTINATION_NAME2 = "ABAP_AS_WITH_POOL";
 static
 Properties connectProperties = new Properties();
 connectProperties.setProperty(DestinationDataProvider.JCO_ASHOST, "ls4065");
 connectProperties.setProperty(DestinationDataProvider.JCO_SYSNR, "85");
 connectProperties.setProperty(DestinationDataProvider.JCO_CLIENT, "800");
 connectProperties.setProperty(DestinationDataProvider.JCO_USER, "farber");
 connectProperties.setProperty(DestinationDataProvider.JCO_PASSWD, "laska");
 connectProperties.setProperty(DestinationDataProvider.JCO_LANG, "en");
 createDataFile(DESTINATION_NAME1, "jcoDestination", connectProperties);
 connectProperties.setProperty(DestinationDataProvider.JCO_POOL_CAPACITY, "3");
 connectProperties.setProperty(DestinationDataProvider.JCO_PEAK_LIMIT, "10");
 createDataFile(DESTINATION_NAME2, "jcoDestination", connectProperties);
 Properties servertProperties = new Properties();
 servertProperties.setProperty(ServerDataProvider.JCO_GWHOST, "binmain");
 servertProperties.setProperty(ServerDataProvider.JCO_GWSERV, "sapgw53");
 servertProperties.setProperty(ServerDataProvider.JCO_PROGID, "JCO_SERVER");
 servertProperties.setProperty(ServerDataProvider.JCO_REP_DEST, "ABAP_AS_WITH_POOL");
 servertProperties.setProperty(ServerDataProvider.JCO_CONNECTION_COUNT, "2");
 createDataFile(SERVER_NAME1, "jcoServer", servertProperties);
 static void createDataFile(String name, String suffix, Properties properties)
 File cfg = new File(name+"."+suffix);
 if(!cfg.exists())
 try
 FileOutputStream fos = new FileOutputStream(cfg, false);
 properties.store(fos, "for tests only !");
 fos.close();
 catch (Exception e)
 throw new RuntimeException("Unable to create the destination file " + cfg.getName(), e);
Regards

JCO server registred in CRM

Hi experts,
We´re calling a JCO server from our CRM 4.0 Instalation and followed the instructions found in some threads, our code looks like:
Start the server
public void startServers()
// Server 1 listens for incoming requests from system 1
// (Change gateway host, service, and program ID according to your needs)
 Properties properties = new Properties();
 properties.setProperty("jco.server.gwhost", "10.0.0.4");
 properties.setProperty("jco.server.gwserv", "sapgw00");
 properties.setProperty("jco.server.progid", "JAVASERVER");
 properties.setProperty("jco.server.unicode", "1" );
 JCO.Server server = new JCO.Server( properties, repository );
 srv[0]=server;
// srv[0] = new Server("10.0.0.4","sapgw00","JAVASERVER",repository);
for (int i = 0; i < srv.length; i++) {
try {
srv.setTrace(true);
srv.start();
catch (Exception ex) {
System.out.println("Could not start server " + srv.getProgID() + ":
" + ex);
 }//try
}//for
When we use the Server constructor we find to get the two system get connected but sumetimes with abnormal behavior, our RFC destination are set to unicode.
If we use the JCO.Server constructor to set our server to unicode, we are only able to get the system connected without receive any message.
Any suggestion?
Thanks in advance.

Hi Jose,
in the line:
properties.setProperty("jco.server.unicode", "1" );
You explicitly set the property to use Unicode. In:
srv[0] = new Server("10.0.0.4","sapgw00","JAVASERVER",repository);
You don't use this option. So I think this is the main reason.
Regards
Gregor

JCO.Server could not find server function 'CONTROL_RECIPE_AVAILABLE'

Hi Experts,
I've been trying to read some of the topics in the forums to find answers about the error JCO.Server could not find server function but still haven't resolve the issue.
Basically, the scenario is from SAP r/3 to PI 7.1 ehp1 (process integration) system.
All of the aforementioned steps we're done.
R/3 (SAP) end
1.) Create RFC destination (T)
2. ) Indicate the program ID
3.) Indicate the server/hostname
4.) Indicate the sap gateway
Test connection was made and it was successful.
SAP PI end.
Integration Directory (Let me skip from the basics and state directly the setup of my senderRFC)
1.) RFC Comm Channel (set as Sender)
2.) Indicated the server hostname (sending system), sap gateway and Program ID (basically what was indicated in RFC setup in SAP end)
3.) RFC Metadata Repository Parameters (In here I used the details of PI environment)..Created user with SAP_ALL profile..I used system without Load Balancing (Parameter, AppServer, SysNo, Logon User, Logon Password, Language and Client)
I was able to test a message from SAP end but still "JCO.Server could not find server function" was the result upon checking sm58.
Did I miss something from my setup and config?

Hi Michal,
I guess there's a big difference with RFC Server Parameters and with RFC Metadata Repository Parameters.
Note: Im using PI 7.1 ehp1
For RFC Server Parameters it includes:
- Application Server (gateway)*
- Application Server Service (gateway)*
- Program ID*
For RFC Metadata Repository Parameters it includes:
- Load Balancing or no Load Balancing (choices)..in here my choice is no Load Balancing
- Application Server*
- System No*
- Logon Language*
- Logon Client*
- Authentication Mode (Use Log-on Data for SAP System or Secure Network Connection for RFC)
if Use Log-on Data for SAP System it includes:
- Logon User*
- Logon Password*
If Secure Network Connection for RFC it includes:
- Quality of Protection
- SNC Partner Name
Looked onto your blogs mentioned several times, but no information on RFC Metadata Repository Parameters.

ABAP process hangs when calling a jCO Server J2EE-available RFC

Hi there
Here's the scenario:
We have deployed a jCO server under the SAP WAS. This jCO server implements two functions. They are both called from ABAP process through RFC. We are using the same RFC destination for both
First function is defined with import/export parameters and the second one only operates with a TABLE parameter.
Incidentally, these functions are captured by the jCO server, which calls an IBM MQ server
First function works fine. Second function hangs and there is not even a timeout so the ABAP process (run on foreground) can stay forever.
The interesting part is that the same application works really fine when called from a Tomcat using a standalon instance of the jCO.
Additional info:
We have noticed that some time after the second function gets called, there are five dumps on the system (the same amount of servers we make available). These are CALL_FUNCTION_SIGNON_REJECTED.
The fun part of the dumps is that the user making the RFC call is a different user that the one we use for the jCO connection, and the client number is '000', instead of the '728' we are using for the connection. Somehow they seem related but we do not know how yet:
Short text
 You are not authorized to logon to the target system (error code 1).
What happened?
 Error in the ABAP Application Program
 The current ABAP program "SAPMSSY1" had to be terminated because it has
 come across a statement that unfortunately cannot be executed.
Error analysis
 RFC (Remote Function Call) sent with invalid
 user ID "%_LOG01% " or client 000.
 User "ARINSO " under client 001 from system "SMD " has tried to carry out an
 RFC
 call under the user ID "%_LOG01% " and client 000 (Note: For releases < 4.0,
 the
 information on caller and caller system do not exist.).
Call Program........."SAPLSMSY_ACTUALIZE_DATA"
Function Module..... "SCSM_SYSTEM_LIST"
Call Destination.... "SM_ET7CLNT000_READ"
Source Server....... "sapwasmd_SMD_10"
Source IP Address... "172.17.82.80"
Termination occurred in the ABAP program "SAPMSSY1" - in
 "REMOTE_FUNCTION_CALL".
 The main program was "SAPMSSY1 ".
 In the source code you have the termination point in line 67
 of the (Include) program "SAPMSSY1".
Any tip or suggestion on where to look at is more than welcome
Thanks in advance,
Miguel

And this is the content of the defaultTrace.0.trc log from the WAS
1.#005056AB04C500440000000200002B0000046B495CA1AF67#1243862737727#com.sap.caf.um.relgrou
ps.imp.principals.RelGroupFactory##com.sap.caf.um.relgroups.imp.principals.RelGroupFactor
y.RelGroupFactory()#######SAPEngine_System_Thread[impl:5]_13##0#0#Info#1#/System/Server#P
lain###sap.com caf/um/relgroups/imp MAIN_NW701P03_C 2846629#
#1.#005056AB04C500240000000100002B0000046B495CCDAAFB#1243862740608#com.sap.engine.library
.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace####n/a##b3
89a8004eaf11dec9b7005056ab04c5#SAPEngine_System_Thread[impl:5]_39##0#0#Error##Plain###Reg
isterNode</Kernel/System Threads Pool/WaitingTasksCount>: com.sap.engine.library.monitor.
mapping.ccms.CcmsConnectorException: 2100850: Invalid configuration group for node'/Kerne
l/System Threads Pool/WaitingTasksCount' (MANAGERS.SThreadPool.WaitingInRequestQueueCount
, max. 40 characters)#
#1.#005056AB04C500240000000200002B0000046B495CCDB4CC#1243862740612#com.sap.engine.library
.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace####n/a##b3
89a8004eaf11dec9b7005056ab04c5#SAPEngine_System_Thread[impl:5]_39##0#0#Error##Plain###Reg
isterNode</Kernel/System Threads Pool/WaitingTasksQueueOverflow>: com.sap.engine.library.
monitor.mapping.ccms.CcmsConnectorException: 2100850: Invalid configuration group for nod
e'/Kernel/System Threads Pool/WaitingTasksQueueOverflow' (MANAGERS.SThreadPool.Waiting4Fr
eeReqQueueSlotCount, max. 40 characters)#
#1.#005056AB04C500240000000300002B0000046B495CCDCDA1#1243862740618#com.sap.engine.library
.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace####n/a##b3
89a8004eaf11dec9b7005056ab04c5#SAPEngine_System_Thread[impl:5]_39##0#0#Error##Plain###Reg
isterNode</Kernel/Application Threads Pool/WaitingTasksCount>: com.sap.engine.library.mon
itor.mapping.ccms.CcmsConnectorException: 2100850: Invalid configuration group for node'/
Kernel/Application Threads Pool/WaitingTasksCount' (MANAGERS.AThreadPool.WaitingInRequest
QueueCount, max. 40 characters)#
#1.#005056AB04C500240000000400002B0000046B495CCDD69B#1243862740620#com.sap.engine.library
.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace####n/a##b3
89a8004eaf11dec9b7005056ab04c5#SAPEngine_System_Thread[impl:5]_39##0#0#Error##Plain###Reg
isterNode</Kernel/Application Threads Pool/WaitingTasksQueueOverflow>: com.sap.engine.lib
rary.monitor.mapping.ccms.CcmsConnectorException: 2100850: Invalid configuration group fo
r node'/Kernel/Application Threads Pool/WaitingTasksQueueOverflow' (MANAGERS.AThreadPool.
Waiting4FreeReqQueueSlotCount, max. 40 characters)#
#1.#005056AB04C500600000001600002B0000046B4960688301#1243862801089#com.sap.slm.exec.messa
ge.SLMApplication#sap.com/tcslmslmapp#com.sap.slm.exec.message.SLMApplication#Guest#0##
n/a##c59827604eaf11de9fb3005056ab04c5#SAPEngine_Application_Thread[impl:3]_0##0#0#Error##
Java###null##
#1.#005056AB04C500730000000000002B0000046B4CF0593ABD#1243878100908#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain###com.sap.mw.jco.JCO$AbapException: (126) 1: Array index out of rang
e: 48#
#1.#005056AB04C500730000000100002B0000046B4CF0594028#1243878100909#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at com.efh.jco.valtran.sap.ValtranRequestHandler.serverExceptionO
ccurred(ValtranRequestHandler.java:164)#
#1.#005056AB04C500730000000200002B0000046B4CF059406B#1243878100910#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at com.sap.mw.jco.JCO.fireServerExceptionOccurred(JCO.java:880)#
#1.#005056AB04C500730000000300002B0000046B4CF05940A3#1243878100910#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at com.sap.mw.jco.JCO$Server.listen(JCO.java:8187)#
#1.#005056AB04C500730000000400002B0000046B4CF05940DB#1243878100910#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at com.sap.mw.jco.JCO$Server.work(JCO.java:8303)#
#1.#005056AB04C500730000000500002B0000046B4CF0594111#1243878100910#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at com.sap.mw.jco.JCO$Server.loop(JCO.java:8250)#
#1.#005056AB04C500730000000600002B0000046B4CF0594143#1243878100910#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at com.sap.mw.jco.JCO$Server.run(JCO.java:8166)#
#1.#005056AB04C500730000000700002B0000046B4CF05941F0#1243878100910#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at java.lang.Thread.run(Thread.java:770)#

JCo Server Programming

Similar Messages

Maybe you are looking for