Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-16317

systemctl status eap7-standalone.service reports incorrect status when the EAP process is started directly via standalone.sh

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Optional
    • Resolution: Rejected
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: RPM
    • Labels:
      None
    • Target Release:
    • Steps to Reproduce:
      Hide
      1. install EAP via yum groupinstall jboss-eap7
      2. start it via systemctl start eap7-standalone.service
      3. check status via systemctl status eap7-standalone.service
      4. stop it via systemctl stop eap7-standalone.service
      5. start it via nohup /usr/bin/sudo -u jboss -g jboss /opt/rh/eap7/root/usr/share/wildfly/bin/standalone.sh -c standalone.xml -b 0.0.0.0 &
      6. check status via systemctl status eap7-standalone.service
      Show
      install EAP via yum groupinstall jboss-eap7 start it via systemctl start eap7-standalone.service check status via systemctl status eap7-standalone.service stop it via systemctl stop eap7-standalone.service start it via nohup /usr/bin/sudo -u jboss -g jboss /opt/rh/eap7/root/usr/share/wildfly/bin/standalone.sh -c standalone.xml -b 0.0.0.0 & check status via systemctl status eap7-standalone.service

      Description

      For EAP installed from RPM via yum groupinstall jboss-eap7 it's still possible to start it directly via standalone.sh which is causing systemctl status eap7-standalone.service reporting incorrect status.

      This was found as a side effect while testing EAP's Start/Stop operation invoked from JON (jboss operation network). By default the JON is using the standalone.sh directly to start up the EAP even when the EAP is installed from RPM, which is working fine but it has this side effect.

      See steps to reproduce:

      • after step 3 the status is correctly reported
      • after step 6 the eap process is actually running but reported status is not correct, saying it's inactive (dead)

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                brian.stansberry Brian Stansberry
                Reporter:
                fbrychta Filip Brychta
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: