The solution to the problem is:
1. Do not use the JVMPI with WebSphere Application Server Express V5.0.
2. Upgrade to the full WebSphere Application Server V5.0 product, either
BASE or ND.
3. Upgrade to WebSphere Application Server Express V6.0.
To get the server back to a running state, do the following:
Network Deployment environment:
Use the administrative console to reverse the steps taken to enable
JVMPI.
Steps for this task
- Open the administrative console.
- Click Servers > Application Servers in the console
navigation tree.
- Click the application server for which JVMPI was enabled.
- Click Process Definition.
- Click the Java Virtual Machine.
- Remove -XrunpmiJvmpiProfiler from the Generic JVM
arguments field.
- Click Apply or OK.
- Click Save.
- Start the application server.
Non-federated environment:
Since the application server cannot start, the server.xml file will
need to be modified by hand.
Steps for this task
1. Open the server.xml file in a text editor:
<WASEXPRESS_HOME>/config/cells/DefaultNode/nodes/DefaultNode
/servers/<SERVER_NAME>/server.xml.
2. Find the section for the 'processDefinition':
<processDefinition
xmi:type="processexec:JavaProcessDef"
...genericJvmArguments="-XrunpmiJvmpiProfiler"
</processDefinition>.
3. Remove -XrunpmiJvmpiProfiler from the genericJvmArguments
list.
4. Save the server.xml file.
5. Start the application server. |