Troubleshooting
Problem
The server fails to start in profile mode.
Symptom
When trying to start the server in profile mode, the console view displays the following error message:
ADMU3011E: Server launched but failed initialization
In addition, the server log file, native_stderr.log file, displays the following error message:
JVMJ9TI001E Agent library JPIBootLoader could not be opened. (The specified module could not be found.)
JVMJ9VM015W Initialization error for library j9jvmti24(-3): JVMJ9VM009E J9VMDllMain failed
Could not create the Java virtual machine.
You can find the native_stderr.log file in the
<WAS_INSTALL_ROOT>\profiles\<profileName>\logs\<serverName> directory, where <WAS_INSTALL_ROOT> is the installation directory WebSphere®Application Server, <profileName> is the name of your WebSphere Application Server profile and <serverName> is the name of your server. For example:
C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1\native_stderr.log
Cause
The required profiling libraries cannot be located. This could be caused by environment variables not being set to contain the required libraries for profiling on server or the bitness of Rational Application Developer does not match with that of the WebSphere Application Server that is being profiled.
Diagnosing The Problem
Verify the JVMJ9TI001E error exists in the server log file, native_stderr.log.
Resolving The Problem
See the Setting up environment variables to profile a server topic for instructions to setup the required environment variables. A link to this help topic is available under the Related URL section of this document.
Note: The product documentation describes the behavior of v7.5.5.2 and later release. You will need to update to Rational Application Developer v7.5.5.2 or later to get the behavior described in that topic. If you are using an earlier release and you are not sure about which environment variables are required, then set all the environment variables specified in that topic to ensure that you will not encounter this problem.
Note: Ensure that the bitness of the application you are profiling matches that of Rational Application Developer. Because Rational Application developer is running in 32-bit, you can only use it to profile 32 bit WebSphere Application Server.
Related Information
Was this topic helpful?
Document Information
Modified date:
19 August 2022
UID
swg21319688