Question:
How do we find the JCO version installed in the BC / SAP integration environment? I mean everything is installed and I have joined the group as a new guy. While i can find BC is 4.6 corefix2, sp1 and sp2 clearly in the server log, how do we see the same for JCO.
Basically we are experiencing server crash after upgrading the software from SAP BC 4.6 to Corefix2, s1 and sp2. Based on some of the forum Q&A, we understand there is a bug in JCO 2.1.2. How do we find the version of this JCO component which is installed in our system?
shiva/Chari
Answer:
Hello,
I had a problem with JCo 2.1.2 crash in SAP BC 47 with SP2.
Resolution was that I get JCo patch which upgrade it to 2.1.3. Patch was supplied from SAP as resoultion of my customer message.
Youcan se JCo version in administration interface of SAP BC Server. Go to Adapters > SAP and look under "About". In section "Environment" there is info about JCo.
If you have problems that you cannot see "SAP" under "Adapters" tab start SAP BC Server through command line with option "-log none". In passing data you will see info about JCo and reason why it crashed.
HTH
Gordan
Answer:
Ciao Gordan,
The JCo that are you refering is SAP Java Connector 2.0 Patch Level 10
https://websmp101.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000035277&
Thanks & regards
Boss
Answer:
Hello,
No, SAP BC Server 4.7 uses JCo 2.1.2 not 2.0.10, but error was something similar as in note 682686 point 3 for 2.0.10.
As SAP support explained to me if optional tables were empty error was thrown. Even table was optional, JCo was trying to access memory for that table and crashed.
I got patch directly from SAP support and only for required operating systems. Now SAP BC Server is showing info about JCo version as 2.1.3.
HTH
Gordan
Answer:
Hi Gordan,
thank you very much, now is all clear.
Regards
Boss
Answer:
Hi Gordan,
Sorry, an other thing ......
If I run BC Server 4.7 Core Fix 2 and SP2 on W2K environment, I need also the JCo 2.1.3
Thanks again
Boss
Answer:
Hello,
JCo 2.1.3 is necessary if you upgrade SAP BC Server 4.7 to SP2.
If you do so open Customer Message on service.sap.com and somebody from SAP support will send you update. Until you receive update workarround is to downgrade to SP1 (recommended to me by SAP support).
I have both windows and linux versions but do not know if O can send you due to the licensing.
I do not understand why they did not post update for now on SAP BC pages on service .sap.com
HTH
Gordan
Answer:
hi gordan,
i'm using business connector 4.6 with core fix2, sp1 & sp2. JCO version is 2.0.8.
this is the configuration i have in the clients place. is this configuration is ok. because my server is getting down often. i checked the license key and updated the expired licence key. then also i'm facing the same problem.
can u suggest me in this regard.
thnks.
Answer:
Hi Arun,
If you want to remain in BC 4.6 you can try to upgrade to :
Server Core Fix 4 and Service Release 6.
I suggest you to use Sun JVM Java Version 1.4.2_02 (48.0)
Maybe you can solve your problem.
Take care
Boss
Answer:
hi boss,
thnks for ur reply.
before i do the changes as per ur advise i need few clarifications.
according to webmethods best practices, jvm 1.2.2 is used for compilation and 1.3.1 for execution. if i use 1.4.2_02 (48.0) will there be any impact?
also i'm getting some error (especially in JCO) in the error log like:
1) 2004-03-09 15:30:40 GMT+08:00 com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: EDI: Table passed to EDI_SEGMENTS_ADD_BLOCK is empty.
2) 2004-03-12 15:35:56 GMT+08:00 com.sap.mw.jco.JCO$Exception: (120) JCO_ERROR_EXTENSION: JCO.Server could not create server function 'IDOC_INBOUND_ASYNCHRONOUS'
3) 2004-03-12 15:35:56 GMT+08:00 com.sap.mw.jco.JCO$Exception: (123) JCO_ERROR_FUNCTION_NOT_FOUND: Server repository could not create function template 'IDOC_INBOUND_ASYNCHRONOUS'
4) 2004-03-12 17:05:08 GMT+08:00 com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: connection closed without message (CM_NO_DATA_RECEIVED)
5) 2004-03-13 16:43:50 GMT+08:00 com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Sat Mar 13 16:43:50 GMT+08:00 2004.
also i want to know how to see the error codes and description for that (like the one which u can see in the above jco errors, like (104),(123),(129) etc..).
thnks.
Answer:
hi gordan,
i'm using business connector 4.6 with core fix2, sp1 & sp2. JCO version is 2.0.8.
this is the configuration i have in the clients place. is this configuration is ok. because my server is getting down often. i checked the license key and updated the expired licence key. then also i'm facing the same problem.
can u suggest me in this regard.
thnks.
i'm trying to use business connector 4.6 with core fix1,4 & SR3,6. JCO version is 2.1.4.
Linux- 2.4.22
when i do - "Add server"
error.log:
---( Start )---
2004-11-25 09:14:29 java.lang.reflect.InvocationTargetException:JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
default_cpc_mode
2004-11-25 09:14:29 java.lang.reflect.InvocationTargetException: JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
default_cpc_mode
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:334)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:712)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:499)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:456)
at com.wm.app.b2b.server.SessionInvoke.run(Session.java:635)
at com.wm.util.pool.PooledThread.run(C:/NT/Perforce/basis/4.1.0-terra/module/core/source/com/wm/util/pool/PooledThread.java:103)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.reflect.InvocationTargetEx
---------------
where's my mistake?