|
Problem |
After a fix pack update on a WebSphere® Application Server
installation with Wily Introscope installed, the Application Servers with
Wily Introscope might fail to start. |
|
Cause |
The failure occurs because the Wily configuration is
dependent upon a boot-class-prepend definition. The following is an
example of this:
<boot-classpath-prepend>/app/WebSphere/AppServer/wily/
connectors/AutoProbeConnector-1.3.1_05_Sun_Microsystems_Inc.jar:/
app/WebSphere/AppServer/wily/connectors/AutoProbeConn.jar:/
app/WebSphere/AppServer/wily/ext/ProbeBuilder.jar:/
app/WebSphere/AppServer/wily/Agent.jar:/app/WebSphere/
AppServer/wily/ext/LeakHunter.jar:/app/WebSphere/AppServer/
wily/SQLAgent.jar</boot-classpath-prepend>
|
The first .jar in the boot-class-prepend has a JDK™-specific name, such
as the following:
wily/connectors/AutoProbeConnector-<JVM
Version>.jar:<path-to-Agent.jar>
|
The following is seen in the native_stderr.log file:
JVMXM008: Error occurred while
initializing System ClassException in thread "main" Could not create the
Java virtual machine. |
|
|
Solution |
The AutoProbeConnector that works with your specific Java™
virtual machine (JVM™) is created using the
CreateAutoProbeConnector.jar. tool that comes with Wily's
product. More information on this is located in the Wily documentation
referenced below. After the new connector is created or the
boot-class-prepend changed, the Application Server starts normally.
There is greater detail in the Introscope ProbeBuilder Configuration
Options section in the Wily 5 Introscope Installation and Configuration
Guide v5 release 5.0, page 114, in the Introscope installation
documentation. Use search terms prepend or JVM Version or
AutoProbeConnector for best results within the Wily documentation.
Refer to your Introscope installation media or contact Wily for further
information. |
|
|