Bug 1002221

Summary:	Server startup/install fails with no indication to user
Product:	[JBoss] JBoss Operations Network	Reporter:	Larry O'Leary <loleary>
Component:	Usability	Assignee:	Jay Shaughnessy <jshaughn>
Status:	CLOSED DUPLICATE	QA Contact:	Mike Foley <mfoley>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	JON 3.2	CC:	hrupp
Target Milestone:	ER02
Target Release:	JON 3.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-19 17:46:50 UTC	Type:	Bug
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:	1006862

Description Larry O'Leary 2013-08-28 16:15:41 UTC

Description of problem:
After extracting the server installation archive the following command can be issue but the server is unavailable:

./rhq-server.sh start

Version-Release number of selected component (if applicable):
3.2.0.ALPHA_QA-58

How reproducible:
Always

Steps to Reproduce:
1. Extract jon-server-3.2.0.ALPHA_QA.zip.
2. Execute jon-server-*/bin/rhq-server start.

Actual results:
Server startup shows success and log indicates server is running but unable to reach JON server.

Expected results:
JON server should be available when going to http://host:7080

Additional info:
Although this may be related to the new installation procedures, the old procedure should continue to work or be removed completely to ensure the user understands the startup process has changed.

Comment 1 Heiko W. Rupp 2013-09-12 08:55:56 UTC

This is related to Bug 1000065 and probably duplicates it. Let's keep it open anyway.

Comment 2 Jay Shaughnessy 2013-09-19 17:46:50 UTC

This is definitely a duplicate.

*** This bug has been marked as a duplicate of bug 1006347 ***