cancel
Showing results for 
Search instead for 
Did you mean: 

An unexpected error has been detected by SAP Java Virtual Machine

former_member182034
Active Contributor
0 Kudos

Dear,

I getting below error when I am trying to install SAP on SUSE 15.7


May 25, 2015 1:02:43 PM [Info]: >> # An unexpected error has been detected by SAP Java Virtual Machine:

May 25, 2015 1:02:43 PM [Info]: >> #

May 25, 2015 1:02:43 PM [Info]: >> #  SIGSEGV (0xb) at pc=0x00007ffdee5d87f0, pid=4557, tid=140727796692752

May 25, 2015 1:02:43 PM [Info]: >> #

May 25, 2015 1:02:43 PM [Info]: >> # Java VM: SAP Java Server VM (6.1.006 Oct 13 2009 00:24:23 - 61_REL - optU - linux amd64 - 6 - bas2:127656 (mixed mode))

May 25, 2015 1:02:43 PM [Info]: >> # Problematic frame:

May 25, 2015 1:02:43 PM [Info]: >> # C  [ld-linux-x86-64.so.2+0x137f0]  _dl_x86_64_save_sse+0x30 (sp=0x00007ffdbe54cd98) (pc=0x00007ffdee5d87f0)

May 25, 2015 1:02:43 PM [Info]: >> #

May 25, 2015 1:02:43 PM [Info]: >> #

An error report file with more information is saved as:

May 25, 2015 1:02:43 PM [Info]: >> # /mediasap/IM_LINUX_X86_64_702/hs_err_pid4557.log

May 25, 2015 1:02:45 PM [Info]: >> #

May 25, 2015 1:02:45 PM [Info]: >> # If you would like to submit a bug report, please visit:

May 25, 2015 1:02:45 PM [Info]: >> #   http://service.sap.com/support

May 25, 2015 1:02:45 PM [Info]: >> #

May 25, 2015 1:02:45 PM [Info]: >> Closed input stream

May 25, 2015 1:02:45 PM [Error]: java.net.SocketException: Connection reset

May 25, 2015 1:02:45 PM [Error]: java.net.SocketException: Connection reset

May 25, 2015 1:02:45 PM [Info]: >> Closed input stream

May 25, 2015 1:02:45 PM [Error]: GUI terminated with return code 134

May 25, 2015 1:02:45 PM [Error]: Network input/output exception has occurred: Connection reset

I tried to run sapinst(latest SWPM) with SAPJVM 4,6 and 7 but still face facing same error.

Regards,

Accepted Solutions (1)

Accepted Solutions (1)

former_member182657
Active Contributor
0 Kudos

Hi Abdul,


Problematic frame:

May 25, 2015 6:07:20 PM [Info]: >> # C  [ld-linux-x86-64.so.2+0x136a0]  _dl_x86_64_save_sse+0x30 (sp=0x00007f914b5a9018) (pc=0x00007f917b6736a0)

Your issue is completely related with ld-linux-x86-64.so.2+0x136a0 ,seems issue relates with OS as well as with packages.

As a workaround could you follow the steps as like,before execution of sapinst.exe,export the parameter LD_BIND_NOW=1 e.g


export LD_BIND_NOW=1

After that share the results once again.

This is completely a workaround,may do the trick here.

Regards,

former_member182034
Active Contributor
0 Kudos

Dear Gaurav,

issue has been resolved after putting this parameter.

export LD_BIND_NOW=1

would you put some light on it why we set this parameter?

Regards,

former_member182657
Active Contributor
0 Kudos

Hi Abdul,

It's unbelievable that a workaround can do the magic,anyways would like to share things on magical parameter LD_BIND_NOW = 1.

Before this issue i too was also not aware about this parameter & it's outcomes,on searching more on the issue i found something from the Red Hat Support Portal


4.6. Dynamic Libraries Loading

When developing your MRG Realtime program, consider resolving symbols at startup. Although it can slow down program initialization, it is one way to avoid non-deterministic latencies during program execution.

Dynamic Libraries can be instructed to load at system startup by setting the LD_BIND_NOW variable with ld.so, the dynamic linker/loader.

The following is an example shell script. This script exports the LD_BIND_NOW variable with a non-null value of 1, then runs a program with a scheduler policy of FIFO and a priority of 1.

#!/bin/sh

   

LD_BIND_NOW=1

export LD_BIND_NOW

&

Checking for run-time compatibility


Suppose you have been supplied with an updated version of a dynamically linked library. You have already compiled your program with the previous version; the link editor has checked it for undefined symbols, found none, and created an executable. Therefore, you should not have to link your program again. The dynamic linker will simply use the definitions in the new version of the dynamically linked library to satisfy unresolved external references in the executable.

Suppose further that this is a database update program that takes several days to run. You want to be sure that your program does not fail in a critical section because a symbol that was defined by the previous version of the dynamically linked library is no longer defined by the new version. You want the information that the link editor gives you -- that your executable is compatible with the dynamically linked library -- without having to link edit it again.

There are two ways you can check for run-time compatibility. The command ldd (``list dynamic dependencies'') directs the dynamic linker to print the pathnames of the dynamically linked library on which your program depends:

ldd prog

When you specify the -d option to ldd, the dynamic linker prints a diagnostic message for each unresolved data reference it would encounter if prog were executed. When you specify the -r option, it prints a diagnostic message for each unresolved data or function reference it would encounter if prog were executed.

You can do the same thing when you execute your program. Whereas the dynamic linker resolves data references immediately at run time, it normally delays resolving function references until a function is invoked for the first time. Normally, then, the lack of a definition for a function is not apparent until the function is invoked. By setting the environment variable LD_BIND_NOW

LD_BIND_NOW=1 export LD_BIND_NOW

before you execute your program, you direct the dynamic linker to resolve all references immediately. In that way, you can learn before execution of main() begins that the functions invoked by your process actually are defined.

For me it was just a workaround to overcome such type of issues.

Regards,

Gaurav

Former Member
0 Kudos

Glad to see that your problem has been resolved successfully.But can you attach output of the command

# gdb -batch -ex 'file /lib64/ld-linux-x86-64.so.2' -ex 'disassemble _dl_x86_64_save_sse'

?

former_member182034
Active Contributor
0 Kudos

hi Roman,

thanks for taking interest, Please find required information.

Former Member
0 Kudos

Thanks for the reply. In any case it is highly desirable to update glibc package to avoid such problems in the future as this bug relates to core functionality of dynamic shared objects loading and resolving.

former_member182034
Active Contributor
0 Kudos

Dear Roman,

yesterday, i have updated the glibc.

Regards,

Answers (6)

Answers (6)

former_member182657
Active Contributor
0 Kudos

If possible please share hs_err_pid4394.log

Thanks,

former_member182034
Active Contributor
0 Kudos

hi Gaurav,

please find attached file.

former_member182657
Active Contributor
0 Kudos

Hi Abdual,


There are latest JVM and its Patch.

SAP JVM  > SSAPJVM6_9-10006989.SAR

JVM Patch > SAPJVM6_76-10006989.SAR

may i hv to try with above SAP JVM.

Yes it would be best to give a nice try by using latest ones as same is suggested in SAP Note 1305395


Normally a sourcecode fix for the SAP JVM crash is necessary, which is delivered with a SAP JVM patch. When a crash occurs with an old version of the SAP JVM, it is very likely that the crash is already fixed in a current version.

Regards,

former_member182657
Active Contributor
0 Kudos

Hi,

Is log file hs_err_pid.log exists on the system,if yes please share.

Thanks,

Former Member
0 Kudos

Are you sure that you are using latest SWPM? Also do use SAP JVM that is packaged in SWPM tool.

former_member182034
Active Contributor
0 Kudos

Dear Roman,

both SWPM and JVM are latest.

Dear Gaurav,

I have already checked both notes

As Per this Note: 1305395 - SAP JVM crash: How to identify and what to do

I have set below value in /etc/security/limits.conf

coredumpsize unlimited

Startup Framework 7.10 with PL 135 or higher (note 1288859)

Startup Framework 7.11 with PL 22 or higher (note 1240240)

would you put some light on above startup Framework, because both note also point to JVM?


As Per this note:1708424 - Upgrade fails on startup with SAPJVM 6.1.00.6 error

Upgrade Issue is resolved with SAP JVM 6.1 while i m trying to install the system.

There are latest JVM and its Patch.

SAP JVM  > SSAPJVM6_9-10006989.SAR

JVM Patch > SAPJVM6_76-10006989.SAR

may i hv to try with above SAP JVM.

Regards,

Former Member
0 Kudos

Which version of SWPM tool are you using? Can you provide full output from sapinst start? Which linux release and version are you using? Make sure you have installed latest version of glibc package.

former_member182034
Active Contributor
0 Kudos

hi Roman,

SWPM

70SWPM10SP08_0-20009701.sar

Linux SUSE Release

openSUSE 11.3 (x86_64)

VERSION = 11.3

glibc

I just install the glibc via yast -i and retry but still face attached issue.

former_member182657
Active Contributor
0 Kudos

Hi,


May 25, 2015 2:44:22 PM [Info]: /tmp/sapinst_exe.4334.1432547057/jre/bin/java -XX:+HeapDumpOnOutOfMemoryError -Xmx256M -cp /tmp/sapinst_exe.4334.1432547057/JAR/instgui.jar SDTGui host=localhost port=21212 service=SAPinstService -noauth

Have you checked above.

former_member182034
Active Contributor
0 Kudos

hi Gaurav,

I am working on SUSE after a long time,would you share the file name where i have to increase this Memory?

Last line of file


  139894862059280                 2.27  0x000021c9    | Defining class '???' with 1562 bytes

  139894862059280                 2.27  0x000021c8    Defining class '???' with 2804 bytes

  139894862059280                 2.27  0x000021c7    Linked class '???'

  139894862059280                 2.27  0x000021c6    Started linking of class '???'

  139894862059280                 2.27  0x000021c5    Successfully defined class '???'

time: Mon May 25 14:44:26 2015

elapsed time: 4 seconds

-----------  H E A P   C H E C K  -----------

Suspension of other threads succeeded.

Heap corruption found in object at address 0x00007f3bb84514a8. Class of object is not in the reserved heap memory area (0x006e006900720080).

-------  H E A P   C O R R U P T E D  -------

Regards,

Former Member
0 Kudos

Are you sure that openSUSE linux is supported by SAP? Please provide the following information:

1) linux kernel release installed;

2) output of env command;

3) which type and version of SAP system you are trying to install.

former_member182034
Active Contributor
0 Kudos

Dear,

1) linux kernel release installed;

3) which type and version of SAP system you are trying to install.

I just trying to run the different sapinst but SAP GUI opened for while and closed and faced these error. sapinst will ask the kernel DVD after successfuly run the sapinst.

2) output of env command;

please  find attached env.



Regards,


Former Member
0 Kudos

Unset SAPINST_JRE_HOME environment variable and check again. Attach output from sapinst again.

former_member182034
Active Contributor
0 Kudos

hi,

I removed the EV, please check attached

Regards,

Former Member
0 Kudos

It seems to be a bug with glibc version installed. Try to update it to latest version available for your OS. But again openSUSE is not supported by SAP.

former_member182657
Active Contributor
0 Kudos

Hi Abdul,


Java VM: SAP Java Server VM (6.1.006 Oct 13 2009 00:24:23 - 61_REL - optU - linux amd64 - 6 - bas2:127656 (mixed mode))

For this could you check with SAP Note   1708424 - Upgrade fails on startup with SAPJVM 6.1.00.6 error

Hope this will help you.

Good luck !!

former_member182657
Active Contributor
0 Kudos

Hi,

Hope you searched SAP Note   1305395 - SAP JVM crash: How to identify and what to do

Please follow & share the results.

Regards,