Hide Forgot
The start, stop, and restart operations exposed by the JBoss AS 4 and 5 plug-in have a hard-coded time-out value. In some environments, an AS5 instance may take several minutes to fully start depending on what is being deployed and how many CPUs are available. In is not uncommon for an AS5 instance to take more then 5 minutes to fully start, especially within a development environment. This poses a problem for the start, stop, and restart operations if they are used to bring up or down the AS instance. This request is to move the STOP_WAIT_MAX and START_WAIT_MAX hard-coded values to the plug-in configuration so that the values can be overridden by the user if necessary. This would apply to both the JBoss AS4 and AS5 plug-in. These values are currently defined in: org.rhq.plugins.jbossas.JBossASServerOperationsDelegate org.rhq.plugins.jbossas5.ApplicationServerOperationsDelegate As: private static final long STOP_WAIT_MAX = 1000L * 150; // 2.5 minutes private static final long START_WAIT_MAX = 1000L * 300; // 5 minutes
Applied fix for AS5,AS4 and Tomcat plugins to master. commit hash: 61aaf4428de45f616e720a5f05a00ad0968b0ba8 commit hash: 2f689feaccf45c2ffcf58ee136e3e59a4fbd2999 These plugins now allow configuration of server start/stop MAX_TIME values in minutes to override the default if set.
verifying configurable timeouts on RHQ 4.0 RC #2
Bookkeeping - closing bug - fixed in recent release.