9.4 Modifying the JBoss configuration

The JBoss Application Server is configured using various XML configuration files. JBoss must be shut down before editing any of these configuration files. If JBoss is running and these files are changed, JBoss will probably crash. JBoss also has a few configuration files that are formatted as .property files. You must ensure that the .property files are saved as UNIX text files on Linux or Solaris if you edit these files on Windows environments at any time.

For single-server installations, you may use jboss profile located at [appserver root] \standalone\configuration as a template. For cluster installations, use jboss profile located at [appserver root] \domain\ as a template.

It is recommended that you make a copy of the profile (all or standard) and make changes to the copied profile.

9.4.1 Modify the JBoss configuration

Perform the following steps to modify the JBoss configuration to customize JBoss for LiveCycle.

  • Modify EAR file class-loading isolation

  • Modify the standalone.conf.bat file (Windows)

  • Modify standalone.conf (Linux and Solaris)

9.4.1.1 Modify EAR file class-loading isolation

  1. Open the [appserver root] /server/<profile_name>/deployers/ejb-deployer-jboss-beans.xml file in an editor.

  2. Locate <property name="CallByValue"> and change the value to true .

  3. Save and close the file.

  4. Open the [appserver root] /server/<profile_name>/deployers/ear-deployer-jboss-beans.xml file in an editor.

  5. Locate <property name="isolated"> and change the value to true .

  6. Locate <property name="CallByValue">false</property> and change the value to true .

  7. Save and close the file.

  8. Open the [ appserver root ]/server/<profile_name>/conf/jboss-service.xml file in an editor.

  9. Locate <attribute name="CallByValue">false</attribute> and change the value to true .

  10. Save and close the file.

9.4.1.2 Modify the standalone.conf.bat file (Windows only)

  1. Open the [appserver root] /bin/standalone.conf.bat file in an editor.

  2. Delete the text in bold in the following line and add the memory arguments for 32-bit and 64-bit JVM, as applicable. 

    set "JAVA_OPTS=-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true"
    • Memory argument for 32-bit JVM: 
       set "JAVA_HEAP_ARGS=-Xms1024m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=192m"
    • Memory argument for 64-bit JVM: 
      set "JAVA_HEAP_ARGS=-Xms1024m -Xmx2048m -XX:PermSize=256m -XX:MaxPermSize=512m -XX:+UseCompressedOops"

  3. Add the following line. 

    set "JAVA_OPTS=%JAVA_OPTS% %JAVA_HEAP_ARGS%"
  4. Add the following argument for 32-bit and 64-bit JVM: 
    set "JAVA_OPTS=%JAVA_OPTS% -Dadobeidp.serverName=server1 -Dfile.encoding=utf8 -Djava.net.preferIPv4Stack=true" 
set "JAVA_OPTS=%JAVA_OPTS% -DentityExpansionLimit=10000" 
set "JAVA_OPTS=%JAVA_OPTS% -XX:+HeapDumpOnOutOfMemoryError"

  5. (Optional) Modify JBoss Application Server to run in IPv6 mode as follows:

    • Locate and modify -Djava.net.preferIPv4Stack=false

    • Insert the string -Djava.net.preferIPv6Stack=true

    Note: If the application server log contains the following error on startup, remove the value for the IPv6 stack and set the IPV4 value back to true :

    “13:37:44,488 WARN [HANamingService] Failed to start AutomaticDiscovery java.net.SocketException: bad argument for IP_MULTICAST_IF: address not bound to any interface at java.net.PlainDatagramSocketImpl.socketSetOption(Native Method)at java.net.PlainDatagramSocketImpl.setOption(PlainDatagramSocketImpl.java:260)”

  6. Save and close the file.

9.4.1.3 Modify the standalone.conf file (JBoss with Solaris 10, Red Hat 5.5, 64-bit only)

Solaris JDKs from Sun require an additional argument to use 64-bit features. Without this configuration change, the Sun JDK defaults to 32-bit support only.

Note: If you're running JBoss as a non-root user, use -Djava.io.tmpdir="location" to set the location of the temporary directory to a directory to which you have access.

  1. Open the [appserver root] /bin/run.conf file in an editor.

  2. Locate the section starting with:

    if [ "x$JAVA_OPTS" = "x" ]; then

    Modify the section to look like: 

    if [ "x$JAVA_OPTS" = "x" ]; then 
   #JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true" 
    JAVA_OPTS="$JAVA_OPTS -Xms1024m -Xmx2048m -XX:MaxPermSize=512m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true" 
    JAVA_OPTS="$JAVA_OPTS -Dadobeidp.serverName=server1 -Dfile.encoding=utf8 -Djava.net.preferIPv4Stack=true" 
    JAVA_OPTS="$JAVA_OPTS -DentityExpansionLimit=10000" 
    JAVA_OPTS="$JAVA_OPTS -XX:+UseCompressedOops -XX:+HeapDumpOnOutOfMemoryError"
    Note: Ensure that this entry appears as a single line in the run.conf file.

  3. (optional)Modify JBoss Application Server to run in IPv6 mode as follows:

    • Locate and modify -Djava.net.preferIPv4Stack=false

    • Add -Djava.net.preferIPv6Stack=true

  4. Save and close the file.

// Ethnio survey code removed