standalone.sh hangs in gc log move

Environment

• JBoss Enterprise Application Platform (EAP)
  • 6.4.x
  • 7.0.x
• Linux
• Solaris

Issue

• We attempted to start JBoss, but standalone.sh never completed. It appeared to hang on a GC log file move

Resolution

• Await a fix in a later release
• Manually correct the standane.sh by adding the -f flag to the mv operations:

        # backup prior gc logs
        mv -f "$JBOSS_LOG_DIR/gc.log.0" "$JBOSS_LOG_DIR/backupgc.log.0" >/dev/null 2>&1
        mv -f "$JBOSS_LOG_DIR/gc.log.1" "$JBOSS_LOG_DIR/backupgc.log.1" >/dev/null 2>&1
        mv -f "$JBOSS_LOG_DIR/gc.log.2" "$JBOSS_LOG_DIR/backupgc.log.2" >/dev/null 2>&1
        mv -f "$JBOSS_LOG_DIR/gc.log.3" "$JBOSS_LOG_DIR/backupgc.log.3" >/dev/null 2>&1
        mv -f "$JBOSS_LOG_DIR/gc.log.4" "$JBOSS_LOG_DIR/backupgc.log.4" >/dev/null 2>&1
        mv -f "$JBOSS_LOG_DIR"/gc.log.*.current "$JBOSS_LOG_DIR/backupgc.log.current" >/dev/null 2>&1

Root Cause

• This content is not included.BZ-1426647
  • If proper write permissions to the GC log are not available, the mv operations requires a prompt, delaying start up.
• Content from issues.jboss.org is not included.JBEAP-9460
• Content from issues.jboss.org is not included.WFCORE-2514

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.