PI07237: UPDATE JBOSS SERVER TEMPLATE WITH NEW START AND STOP OPTIONS

8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• Two suggestions to improve jboss server template.
  
  1. Add "-b <JBOSS_HOST>" executable argument in start operation.
  
  In current jboss server template, the default start operation
  is:
  -Executable: "${JBOSS_HOME}/bin/run.sh"
  -Executable arguments: "-c ${JBOSS_PROFILE}"
  
  But in fact, when operation jboss 6.0 or above, the start
  operation MUST have argument "-b
  
  hostname" to specify that the jboss server can be started
  remotely.
  
  2. Change executable argument to "-s
  service:jmx:rmi:///jndi/rmi://<JBOSS_HOST>:1090/jmxrmi" in
  
  stop operation.
  
  In current jboss server template, the default stop operation is:
  -Executable: "${JBOSS_HOME}/bin/shutdown.sh"
  -Executable arguments: "-s jnp://localhost:1099"
  
  But in fact, the stop command arguments should be "-s
  
  service:jmx:rmi:///jndi/rmi://<JBOSS_HOST>:1090/jmxrmi"
  

Local fix

• na
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server with managed JBoss servers.          *
  ****************************************************************
  * PROBLEM DESCRIPTION: JBoss 6.0 server start and stop         *
  *                      operations need manual edit.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When using JBoss 6.0 or higher, the server start and stop
  operations require manual edit. These settings should be
  correct by default, thus requiring no manual edit.
  

Problem conclusion

• The code was updated to use the more currently expected
  settings for the JBoss server start and stop operations.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.2.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP