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
Link: Added: This issue is related to SOA-226
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
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
Affects: Added: [Documentation (Ref Guide, User Guide, etc.)]
Link: Added: This issue depends JBPAPP-1346
Moving this to SOA 4.3.0 CP02, as the related EAP fix will be in EAP 4.3.0 CP04.
Link: Added: This issue related SOA-1376
Link: Added: This issue related JBPAPP-3194