cancel
Showing results for 
Search instead for 
Did you mean: 

Starting JAVA side of CRM failing when starting on failover system

Former Member
0 Kudos

We are trying to start up our CRM production system on our failover LPAR. The ABAP side starts no problem, but the JAVA side is not starting and in the dev_server0 and std_server0.out logs we are getting the following error:

Exception in thread "(unnamed thread)" java/lang/NoSuchMethodError: java/lang/ClassLoader.callerClassLoader()Ljava/lang/ClassLoader;

at java/lang/Class.forName(Class.java:118)

at java/lang/ref/ReferenceQueue.class$ (ReferenceQueue.java:28)

at java/lang/ref/ReferenceQueue.<clinit> (ReferenceQueue.java:28)

at java/lang/J9VMInternals.initializeImpl (Native Method)

at java/lang/J9VMInternals.initialize (J9VMInternals.java:196)

at java/lang/Class.<clinit> (Class.java:1631)

at java/lang/J9VMInternals.initializeImpl (Native Method)

at java/lang/J9VMInternals.initialize (J9VMInternals:java:196)

JVMJ9VM015W Initialization error for library jclscar_23(14): JVMJ9VM009E J9VMDllMain failed

We do have Wily configured on this system. We are also trying to remove the Wily parameters, however, we cannot open the config tool. We have removed them from the instance.properties file, but when we start the system again, the instance.properties file contains the Wily parameters again.

Is there another place for the configtool settings? Also, has anyone seen this error that is listed above?

Any help would be great.

Thanks,

Dale Dingmann

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

I am also facing the same issue in BI. Please let me know how the problem got resolved.

JVMJ9VM015W Initialization error for library jclscar_23(14): JVMJ9VM009E J9VMDllMain failed

OS: AIX

DB: Oracle

SAP: BI

Suraj

Former Member
0 Kudos

Hello,

We actually had to recreate the system catalog views with the following commands:

WRKOBJ SAP<sid>DB/SYS*

CALL QSYS2/QSQXRLF PARM(DLT SAP<sid>DB)

CALL QSYS2/QSQXRLF PARM(CRT SAP<sid>DB)

That solved our issue.

Let me know if that worked for you.

Former Member
0 Kudos

Hi Dale,

what one can see from the error stack is that no SAP class is involved. So you're probably right pointing to the Wily instrumentation although I don't have seen exactly this error yet. The other possibility that would come to my mind is that something is wrong with the installation of the Java LICPGM.

However, first one should rule out Wily. And, as you've experienced, instance.properties will always be overwritten at bootstrap time so you need to get configtool running to change the settings. What's the problem here?

Have you opened a ticket at SAP for that?

Best regards,

Christoph