XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • TBD EAP 5
    • EAP 5.0.1
    • System
    • None
    • Linux

    • Hide

      1. Start an EAP instance with the following environment properties set
      LAUNCH_JBOSS_IN_BACKGROUND
      JBOSS_PIDFILE
      2. Stop the instance and the JBOSS_PIDFILE is still in place.

      Show
      1. Start an EAP instance with the following environment properties set LAUNCH_JBOSS_IN_BACKGROUND JBOSS_PIDFILE 2. Stop the instance and the JBOSS_PIDFILE is still in place.
    • Compatibility/Configuration
    • Not Required

      Using the latest run.sh, the pid file is not deleted after the process is stopped. Could additional checks be made to ensure the file is removed.
      For instance, the last three lines could be added to ensure the files are removed.

      if [ "$JBOSS_STATUS" -ne 10 ]; then

      1. Wait for a complete shudown
      wait $JBOSS_PID 2>/dev/null
      fi
      if [ "x$JBOSS_PIDFILE" != "x" ]; then
      grep "$JBOSS_PID" $JBOSS_PIDFILE && rm $JBOSS_PIDFILE
      fi

      This is linked to the fix in https://jira.jboss.org/browse/JBPAPP-3797
      It was fixed in https://issues.jboss.org/browse/JBPAPP-4494 but not committed to the EAP 5.x branch

              jgreene@redhat.com Jason Greene
              rhn-support-lakagwu Lami Akagwu
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: