Bug 534572 (RHQ-1356)

Summary:	Server dies in Solaris when exiting launch terminal session.
Product:	[Other] RHQ Project	Reporter:	Corey Welton <cwelton>
Component:	Core Server	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Sunil Kondkar <skondkar>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.2	Keywords:	SubBug
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
URL:	http://jira.rhq-project.org/browse/RHQ-1356
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	# uname -a ; java -version SunOS rhnsun19.rhnsun.rdu.redhat.com 5.10 Generic i86pc i386 i86pc java version "1.5.0_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08) Java HotSpot(TM) Client VM (build 1.5.0_01-b08, mixed mode, sharing
Last Closed:	2010-08-31 13:13:26 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:
Bug Depends On:
Bug Blocks:	565628

Description Corey Welton 2009-01-13 17:29:00 UTC

Server starts up perfectly fine on Solaris -- it launches and apparently drops user back at prompt. Once users exits out of terminal session, however, the server goes down.

Steps to repro.

1. telnet (!) to Solaris box.
2. install jon server and/or launch `bin/rhq-server.sh start`.  Note that server starts and user is returned to prompt
3. in your web browser, navigate to the $server:7080 URL
4. Log out of session.
5. Reload browser page

Expected results
Server continues to run

Current result:
Server goes down.  `ps` confirms this:
# ps -u root| grep java
#

Comment 1 John Mazzitelli 2009-01-13 18:40:31 UTC

for the record, this does NOT happen on other UNIXs like Linux.

Comment 2 John Mazzitelli 2009-01-13 19:21:18 UTC

I'm not seeing this.

I'm running the latest trunk/HEAD code on a solaris box:

$ uname -a
SunOS <hostname> 5.9 Generic_118558-25 sun4u sparc SUNW,Sun-Fire-V210 Solaris

It started and stopped fine even after logging out and logging back in.

Note however, that I used ssh, not telnet (unsure if it makes a difference). This solaris box doesn't allow telnet access so I can't test that explicitly.

But since this works on my Solaris (albeit via ssh), then it must be something with either the shell or login that is causing this behavior (or it could be something in the HEAD of trunk fixed something).

I think the end result might be that if this happens to people that will have to use "nohup" in their specific command to start the server.

Wait until the next QA cycle to see if this is corrected by the code in trunk).

Comment 3 Red Hat Bugzilla 2009-11-10 20:31:14 UTC

This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1356

Comment 4 wes hayutin 2010-02-16 16:52:08 UTC

Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug

Comment 5 wes hayutin 2010-02-16 16:58:07 UTC

making sure we're not missing any bugs in rhq_triage

Comment 6 Corey Welton 2010-08-18 15:09:41 UTC

Per triage this is moved to ONQA w/ the expectation that it is fixed.  If not,
please reopen, otherwise close

Comment 7 Sunil Kondkar 2010-08-31 13:13:26 UTC

Verified on jon-2.4.0.GA

Used telnet to access the solaris box and followed the repro steps. The server does not go down. It continues to run.