Bug 221846

Summary:	jbossas service init.d script fails to stop minimal service, kills the process instead
Product:	[Retired] Red Hat Web Application Stack	Reporter:	Len DiMaggio <ldimaggi>
Component:	jbossas	Assignee:	Deepak Bhole <dbhole>
Status:	CLOSED ERRATA	QA Contact:	Len DiMaggio <ldimaggi>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	v1.1	CC:	gozen
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	RHEA-2007-0084	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-02-19 18:30:00 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Len DiMaggio 2007-01-08 15:09:40 UTC

Description of problem:

Shutting down the jbossas service, if the service is running the "minimal"
service times out. The /etc/init.d/jbossas script eventually performs a kill -9
on the server process. This is apparently expected as since the minimal config
does not deploy JMX, which is needed for proper shutdown over the network.

This is how it appears to the user:

==============================
[root@dl385-02 opt]# service jbossas stop
Stopping jbossas:                                          [  OK  ]
waiting for processes to stop
waiting for processes to stop
waiting for processes to stop
waiting for processes to stop
waiting for processes to stop
waiting for processes to stop
==============================

Version-Release number of selected component (if applicable):
This is a problem for V1.0 and V1.1

How reproducible:
100%

Steps to Reproduce:
1. Configure the jbossas service to run the minimal configuration - start and
stop the service.

Actual results:
See above

Expected results:
Service should stop init.d script having to resort to SIGKILL

Additional info:

Permaine and Deepak found this issue last Friday. Deepak is going to change the
init.d/jbossas script to issue a SIGTERM signal for the minimal server. I'm
logging this bz to make sure that we test for the change.

Comment 1 Benjamin Kahn 2007-01-09 19:13:35 UTC

Fixed for the next respin.

Comment 2 Len DiMaggio 2007-01-11 18:57:53 UTC

In StacksV1-re20070110.0 (jbossas-4.0.5-1.el4s1.4) - the user sees this:

[root@cheddar jbossas]# service jbossas stop
Stopping jbossas:                                          [  OK  ]
waiting for processes to stop
waiting for processes to stop
waiting for processes to stop
waiting for processes to stop
waiting for processes to stop
waiting for processes to stop
Process refused to stop. Trying alternate method...
waiting for processes to stop

This seems acceptable - but, I'll pass it by the Support team just in case.

Comment 3 Len DiMaggio 2007-01-11 18:58:18 UTC

In StacksV1-re20070110.0 (jbossas-4.0.5-1.el4s1.4) - the user sees this:

[root@cheddar jbossas]# service jbossas stop
Stopping jbossas:                                          [  OK  ]
waiting for processes to stop
waiting for processes to stop
waiting for processes to stop
waiting for processes to stop
waiting for processes to stop
waiting for processes to stop
Process refused to stop. Trying alternate method...
waiting for processes to stop

This wording seems acceptable - but, I'll pass it by the Support team just in case.

Comment 5 Red Hat Bugzilla 2007-02-19 18:30:00 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2007-0084.html