Bug 778507 (SOA-980)

Summary:	/bin/shutdown.sh and jboss_init_redhat.sh - inconsistencies in required username/password
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Len DiMaggio <ldimaggi>
Component:	Documentation, Tooling, JBossESB, EAP	Assignee:	Jim Ma <ema>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.3 CR1
Target Milestone:	---
Target Release:	FUTURE
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-980
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	4.3 CR1
Last Closed:	2011-06-15 14:37:05 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:

Description Len DiMaggio 2008-10-24 17:51:57 UTC

Affects: Documentation (Ref Guide, User Guide, etc.)
Date of First Response: 2008-10-27 06:23:05
project_key: SOA

The shutdown.sh script fails with the same JMX authentication error that was originally seen in SOA-226

But - there is an easy workaround - this works:   sh ./jboss_init_redhat.sh stop

Comment 1 Len DiMaggio 2008-10-24 17:52:08 UTC

Link: Added: This issue is related to SOA-226

Comment 2 Julian Coleman 2008-10-27 10:23:05 UTC

If run:
  shutdown.sh -S
I see an authentication error:
  Exception in thread "main" java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console

However, after uncommenting the:
  #admin=admin
line in:
  server/production/conf/props/soa-users.properties
to enable access to the JMX console and running:
  shutdown.sh -S -u admin -p admin
the server shuts down cleanly:
  Shutdown message has been posted to the server.
  Server shutdown may take a while - check logfiles for completion
and on the server console:
  Shutdown complete
  Halting VM

Comment 3 Len DiMaggio 2008-10-27 15:38:44 UTC

The problem here is that the jboss_init_redhat.sh script requires the use of an OS username/password, while the shutdown.sh requires the use of a user defined in /server/*/conf/props/soa-user.properties

This difference is due to EAP's updating the jboss_init_redhat.sh script to post a signal to the server, while, shutdown.sh still uses the JMX console.

So - the user must:

1) For the service init script, either edit the script to reference the desired OS user or let it default to "jboss" (assuming that a "jboss" OS user exists and is used to start the service.

2) The samename user can be used to stop the server with the "stop" option

3) For the shutdown script, specify the user on the command line (-u username -p password) and ensure that the user is defined in the server's conf/props/soa-user.properties file

Comment 4 Len DiMaggio 2008-10-27 15:38:44 UTC

Affects: Added: [Documentation (Ref Guide, User Guide, etc.)]

Comment 5 Len DiMaggio 2008-10-27 16:04:29 UTC

Link: Added: This issue depends JBPAPP-1346

Comment 6 Julian Coleman 2009-01-15 10:19:50 UTC

Moving this to SOA 4.3.0 CP02, as the related EAP fix will be in EAP 4.3.0 CP04.

Comment 7 Len DiMaggio 2009-06-18 13:32:57 UTC

Link: Added: This issue related SOA-1376

Comment 8 Henrik Aronsen 2009-12-01 12:26:48 UTC

Link: Added: This issue related JBPAPP-3194