Description:
Modifying the Global Policy Based Workflow for Events Fails with:
<Please see attached file for image>
Example Use Case:
Configuration Example:
<Please see attached file for image>
<Please see attached file for image>
Details:
The problem itself is a JBoss configuration problem.
The issue is caused by adding the Java command-line option: XX:+AggressiveOpts to the JAVA_OPTS environment variable in the JBOSS_HOME/bin/run.sh file.
This is an experimental Java command-line option that is NOT supported by Identity Minder.
The above command line option is added to the following line in the section of the run.sh file that is modified by Identity Minder:
JAVA_OPTS="$IDM_OPTS -Djava.security.policy=workpoint_client.policy -Xms256m
-Xmx1024m -XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=50m"
The above line is how the JAVA_OPTS would be set in the script that is added to the JBoss run.sh file (note the above line is without the addition of the XX:+AggressiveOpts option).
The JBoss boot.Log will show proof of using the Java command-line XX:+AggressiveOpts option.
The Identity Minder run.sh script is initiated during the JBoss startup and updates the Identity Minder log with the JAVA_OPTS value, along with other JBoss startup information.
Logging example showing that the XX:+AggressiveOpts option is being used:
INFO [ServerInfo] -Dprogram.name=default -Djava.security.policy=.\workpoint_client.policy -Xms256m -Xmx1024m -XX:MaxPermSize=256m -XX:+AggressiveOpts -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:ReservedCodeCacheSize=50m -Djava.endorsed.dirs=C:\jboss-5.1.0.GA\lib\endorsed
Solution:
To Resolve this issue:
Update the JBOSS_HOME/bin/run.sh file to no longer include XX:+AggressiveOpts in the JAVA_OPTS value.