[59810] in SAPr3-news

home help back first fref pref prev next nref lref last post

Re: JCO Solaris driver crashes with segmentation fault

daemon@ATHENA.MIT.EDU (Lothar Kimmeringer)
Mon Aug 6 15:15:50 2007

To: sapr3-news@mit.edu
Date: Mon, 6 Aug 2007 21:15:45 +0200
From: Lothar Kimmeringer <news200707@kimmeringer.de>
Message-ID: <rtkbqxrmgojx$.dlg@kimmeringer.de>
Reply-To: news@kimmeringer.de

Sven Vermeulen wrote:

> Our Java application connects to SAP through the JCO drivers on Sun
> Solaris 10. For this, we have the libsapjcorfc.so and librfcccm.so
> available in the LD_LIBRARY_PATH (of course). Our connection works (we
> see some traffic from/to the SAP server when we take a network trace)
> but suddenly fails due to a JVM crash.

Is the crash happening while calling an RFC inside SAP or
are you processing an incoming call using JCO.Server? If it's
the latter you have to make sure that the RFC-metadata fits
the memory-model of the SAP-system that is calling.


> I think that it is string convertion related (non-unicode / unicode?)
> but our SAP people couldn't confirm that this is a difference between
> the SAP servers.

If the SAP-system runs in Unicode no incoming RFC-calls via
JCO.Server would work. You can check the connection-properties
what kind of codepages are set by the class for the server and
the local client. Maybe the SAP-people can see something help-
ful with the values.

> I'm hoping someone here sees this as "oh yes, we had that too, but ...
> solved it" because we are almost out of options.

I can say "yes we already had some fun with JCO", especially
after a customer of our customer has silently switched their
productive system to unicode with aforementioned effect leading
to the failure of sending IDocs via IDOC_ASYNCHRONOUS_INBOUND.

> The one remaining
> thing we're going to do is to run a small test application (have it
> already) that crashes on the SAP servers (except the production one)
> against the production server - but that's of course something our
> process manager isn't happy to allow, even though it shouldn't hurt.

If it's not breaking any confidentiality agreements, you can post the
source here. Maybe better you should switch to a Java-related news-
group as I doubt that many Java-developers are sitting here around
that are not reading there but I know of many Java-developer
reading there but not here ;-)


Regards, Lothar
-- 
Lothar Kimmeringer                E-Mail: spamfang@kimmeringer.de
               PGP-encrypted mails preferred (Key-ID: 0x8BC3CD81)

Always remember: The answer is forty-two, there can only be wrong
                 questions!

home help back first fref pref prev next nref lref last post