Skip to Content

Solution Manager 7.2 environment variables for JAVA instance

Nov 22, 2016 at 01:29 PM


avatar image


I have/had a running Solution Manager 7.2 system. I was working on an issue connecting managed systems, so I shut everything down and restarted the system. The JAVA instance starts up, but the connection isn't working. Looking at the dev_server0 log, I am seeing the following:

F ********************************************************************************

J JVMX version - Oct 3 2016 11:12:11 - 61_REL - optU - linux amd64 - 6 - bas2:277985 (mixed mode)

J Error occurred during initialization of VM

J agent library failed to init: instrument

J [Last 4000 events in the event buffer]

J <thread> <time> <id> <description>

J 140341280446208 0.00 0x00000001 Protecting memory with rights 0 [0x00007fa3df0c3000,0x00007fa3df0c4000]

F [Thr 140341280446208] *** LOG => SfCJavaVm: abort hook is called.

Environment variables set are:



java -version shows:

serverxx:smjadm 61> java -version

java version "1.6.0_121"

Java(TM) SE Runtime Environment (build 6.1.095)

SAP Java Server VM (build 6.1.095 25.51-b02, Oct 3 2016 11:12:11 - 61_REL - optU - linux amd64 - 6 - bas2:277985 (mixed mode))

serverxx:smjadm 62> which java


I'm not sure if this is an environment issue or something else. All I know is that the system worked before I shut it down and didn't work after the reboot. I can't find a document showing what environment variables should be set.

Any ideas?


Danny Hearn

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Tom Cenens
Nov 25, 2016 at 06:59 AM

Hi Danny

Do you have a Wily Introscope agent active on that Java stack?

It might cause this issue in case there is something wrong there. See if you can pull out the parameter to start up Wily Introscope agent from the Java stack and then try to start up the stack again.

Best regards


Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hey Tom,

Sorry I lost track of this because management decided to outsource our SAP instances and so the Solution Manager 7.2 project was basically started over fresh by a consultant. I just noticed that I still had a notification on this site.

I never did get the opportunity to try out your suggestion.