ERROR: "FATAL ERROR in native method: processing of -javaagent failed" When Starting Up P6 EPPM Managed Servers
(Doc ID 2474656.1)
Last updated on MARCH 22, 2022
Applies to:
Primavera P6 Enterprise Project Portfolio Management - Version 15.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
When attempting to start up P6 EPPM and the Node Manager, the following error occurs:
ERROR
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:386)
at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:401)
Caused by: java.lang.NoSuchMethodError: java.util.ArrayList$Itr.(Ljava/util/ArrayList;Ljava/util/ArrayList$1;)V
at java.util.ArrayList.iterator(ArrayList.java:834)
at java.util.Collections$UnmodifiableCollection$1.(Collections.java:1039)
at java.util.Collections$UnmodifiableCollection.iterator(Collections.java:1038)
at sun.util.locale.provider.LocaleProviderAdapter.findAdapter(LocaleProviderAdapter.java:282)
at sun.util.locale.provider.LocaleProviderAdapter.getAdapter(LocaleProviderAdapter.java:254)
at java.util.Calendar.createCalendar(Calendar.java:1662)
at java.util.Calendar.getInstance(Calendar.java:1613)
at com.mercury.diagnostics.common.logging.DefaultLogFactory$1.(DefaultLogFactory.java:46)
at com.mercury.diagnostics.common.logging.DefaultLogFactory.getLog(DefaultLogFactory.java:43)
at com.mercury.diagnostics.common.loader.ModuleLoader.getPropertiesFile(ModuleLoader.java:359)
at com.mercury.diagnostics.common.loader.ModuleLoader.getPropertiesFile(ModuleLoader.java:333)
at com.mercury.diagnostics.common.loader.ModuleLoader.access$000(ModuleLoader.java:51)
at com.mercury.diagnostics.common.loader.ModuleLoader$1.run(ModuleLoader.java:174)
at java.security.AccessController.doPrivileged(Native Method)
at com.mercury.diagnostics.common.loader.ModuleLoader.initializeEverything(ModuleLoader.java:170)
at com.mercury.diagnostics.common.loader.ModuleLoaderSingletonFactory$InitRunnable.run(ModuleLoaderSingletonFactory.java:178)
at com.mercury.diagnostics.common.loader.ModuleLoaderSingletonFactory.runInitialization(ModuleLoaderSingletonFactory.java:85)
at com.mercury.diagnostics.common.loader.ModuleLoaderSingletonFactory.getModuleLoader(ModuleLoaderSingletonFactory.java:63)
at com.mercury.opal.capture.JavaProbe.getModuleLoader(JavaProbe.java:95)
at com.mercury.opal.capture.jdk15.agent.ProbeClassFileTransformer.(ProbeClassFileTransformer.java:62)
at com.mercury.opal.capture.jdk15.agent.InstrumentationAgent.premain(InstrumentationAgent.java:66)
... 6 more
FATAL ERROR in native method: processing of -javaagent failed
STEPS
The issue can be reproduced at will with the following steps:
1. Installed a higher version of Java JDK than what is specified in the tested configurations document
2. Create and configure WebLogic domain
3. Attempt to start up P6 EPPM
4. Error is displayed and the Node Manager cannot start
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |