SiteMinder : Unable to start web agent option pack: -Xbootclasspath/p is no longer a supported option.
search cancel

SiteMinder : Unable to start web agent option pack: -Xbootclasspath/p is no longer a supported option.

book

Article ID: 452650

calendar_today

Updated On:

Products

SITEMINDER

Issue/Introduction

Post updating to latest JDK below error is observed in the server log file while startup the services.

-Xbootclasspath/p is no longer a supported option.Error: Could not create the Java Virtual Machine.Error: A fatal exception has occurred. Program will exit.I

 

Environment

Webagent Option Pack version : R12.52 SP1 CR11.

Application Server : Wildly 9.x

Cause

The error message indicates that the -Xbootclasspath/p option is deprecated and no longer supported in newer Java versions (typically Java 9 or higher). This is a common issue when running older application server configurations (e.g., WildFly) with modern Java runtimes.

Resolution

The error can be resolved by modifying the startup configuration (e.g., standalone.conf or standalone.bat):

-> Replace -Xbootclasspath/p with -Xbootclasspath/a:

-> Update your existing paths in the JAVA_OPTS configuration to use the /a (append) suffix instead of the unsupported /p (prepend) prefix.

-> Add Required System Properties: Include the following properties in your JAVA_OPTS to ensure the logging subsystem and agent packages are correctly         recognized:

-Djboss.modules.system.pkgs=org.jboss.logmanager,org.jboss.byteman,com.wily,com.wily.*
-Dsun.util.logging.disableCallerCheck=true

Example Configuration Update: Your corrected JAVA_OPTS line should look similar to this:

bash

JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=org.jboss.logmanager,com.wily,com.wily.* -Dsun.util.logging.disableCallerCheck=true -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Xbootclasspath/a:$(ls ${JBOSS_HOME}/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-.jar):$(ls ${JBOSS_HOME}/modules/system/layers/base/org/wildfly/common/main/wildfly-common-.jar)"

Note : Always test configuration updates first in a non-production environment. Take a backup of your configuration files (e.g., standalone.conf) before implementing changes in production.