Skip to Content
avatar image
Former Member

JVM crashes with segmentation fault

When running SAP jobs through the xbp interface we are experiencing JVM crashes periodically. We are 100% java, so the likely culprit is the xbp interface that ends up calling dlls. Has anyone else run into this problem and knows a workaround? There are times when we might be running 40-50 jobs concurrently, so there be a threading issue in the SAP libs. We are using the most recent release of spajco.jar, sapjcorfc.dll, and librfc32.dll.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Jan 18, 2007 at 07:22 PM

    I am having the same set of issues, did you figure it out? We are running Weblogic8 and it runs fine on a V240 Solaris machine, but crashes on a T2000 Solaris box. Any ideas? We are using it for the JCO.Server features.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      We were having our JVM crashing problems on AIX. We are making the calls from our java scheduling application. We use the xbp 2.0 scheduler interface to start and monitor SAP jobs. We have seen different issues on Solaris and windows (deadlocks at high volumes of concurrent jobs). What solved the AIX JVM crashes was upgrading the to 1.4.2 JVM. At least we haven't seen any cores for a couple of weeks in testing, but we get the deadlocks there also. If you bump into the deadlock issue, and find a work-around, let me know.