Change JBOSS_NAME causes error in EAP startup as service

Solution Verified - Updated -

Issue

After changing JBOSS_NAME the service can't be stopped, the PID of the service does not reflect the new name:

Nov 24 12:38:47 txdot4svtpam01 systemd[1]: Starting SYSV: JBoss EAP startup script...
Nov 24 12:38:47 txdot4svtpam01 runuser[6069]: pam_unix(runuser:session): session opened for user root by (uid=0)
Nov 24 12:38:47 txdot4svtpam01 bbqa2-jboss-eap-rhel.sh[6048]: Starting bbqa2-jboss-eap: /
Nov 24 12:39:45 txdot4svtpam01 bbqa2-jboss-eap-rhel.sh[6048]: [  OK  ]
Nov 24 12:39:45 txdot4svtpam01 systemd[1]: Can't open PID file /var/run/jboss-eap/jboss-eap.pid (yet?) after start:...ectory
Nov 24 12:43:47 txdot4svtpam01 systemd[1]: bbqa2-jboss-eap-rhel.service start operation timed out. Terminating.
Nov 24 12:43:47 txdot4svtpam01 systemd[1]: Failed to start SYSV: JBoss EAP startup script.
Nov 24 12:43:47 txdot4svtpam01 systemd[1]: Unit bbqa2-jboss-eap-rhel.service entered failed state.
Nov 24 12:43:47 txdot4svtpam01 systemd[1]: bbqa2-jboss-eap-rhel.service failed.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content