Xbootclasspath/p is not supported in BPM Enterprise 4.3.3
Article ID: KB0070198
Updated On:
| Products | Versions |
|---|---|
| TIBCO BPM Enterprise (formerly TIBCO ActiveMatrix BPM) | 4.3.3 |
Description
If Xbootclasspath/p is set via the JVM arguments in a BPMNode, then while upgrading to 4.3.3 the following symptoms are seen -
- After ActiveMatrix (AMX) Platform upgrade to 3.4.2, the BPMNode fails to start. The following error is logged in TIBCO Configuration Tool (TCT) logs -
TIBCO-AMX-TOOLS-PATCHMGR-000601: One or more Host instances have not started or they are still starting. Make sure all Host instances have started. Start a Host instance manually if it has not started.
- tibcohost logs contain the following error -
[Node-output-handler-BPMNode] [INFO ] [] com.tibco.amx.hpa.NodeOutput.BPMNode - -Xbootclasspath/p is no longer a supported option.
[Node-output-handler-BPMNode] [INFO ] [] com.tibco.amx.hpa.NodeOutput.BPMNode - Failed to create the Java VM
- When starting the BPMNode process manually from the command line it results with -
-Xbootclasspath/p is no longer a supported option.
creationResult = -6
Failed to create the Java VM
Cause:
BPM Enterprise 4.3.3 uses Java 11. The JVM argument - -Xbootclasspath/p is no longer supported in Java 11.
Environment
Resolution
Step 1 - Take a backup and remove Xbootclasspath/p from JVM arguments on all BPMNodes
Step 2 - Upgrade BPM to 4.3.3
Step 3 - Post-upgrade add Xbootclasspath/a to the same path
For example -
-Xbootclasspath/a:"C:/bpme/home/amx/3.4/tools/gregoriancalendarpatch/com.sun.org.apache.xerces.internal.jaxp.datatype-patched.jar"
Issue/Introduction
Feedback
