Affects: Documentation (Ref Guide, User Guide, etc.) Date of First Response: 2009-06-22 03:10:30 project_key: SOA Related to SOA-980 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) 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 is related to SOA-980
added as known issue to 4.2.CP04 Release Notes: Different passwords required for different administration scripts Some of scripts found in ${SOA_ROOT}/bin for starting and stopping the JBoss Enterprise SOA Platform require different user accounts. shutdown.sh shutdown.sh requires that you supply the credentials of a JMX console user as parameters. By default these users are defined in ${SOA_ROOT}/server/${CONFIG}/conf/props/soa-users.properties. jboss_init_redhat.sh, jboss_init_suse.sh, and jboss_init_hpux.sh These initialization scripts each contain a variable which contains the account username of an operating system user account which has permissions to start and stop the JBoss SOA Platform server process. Each of these scripts is slightly different & contains configuration instructions. The default username in each is jboss.
Link: Added: This issue related JBPAPP-3194