Embedded Java™ Message Service (JMS) Server Startup Fails With Multiple Instances of WebSphere® Application Server Network Deployment V5 on a Single Host
 Technote (troubleshooting)
 
Problem(Abstract)
When running multiple instances of WebSphere Application Server Network Deployment on a single host, the first instance starts up successfully. Successive instances, however, fail during start up of the Embedded JMS Server.

The startServer.log shows:
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3011E: Server launched but failed initialization. Server log files should contain failure information.

The native error log (native_stderr.log) shows this error:
BIP2227E: Severe error (before init): /build/S210G_P/src/CommonServices/Unix/ImbGlobalMutexHelper.cpp 433 semctl
13
20
doInitialisation
 
Cause
The errors are seen because the other three systems are trying to use the same semaphore as the first system and can't access it. This is because the other systems are running as differerent users than the first, and the users have different primary groups.
 
Resolving the problem
The AIX system user definitions were defined as the following:
uid=520(was1) gid=520(was1grp) groups=210(mqm),211(mqbrkrs)
uid=521(was2) gid=521(was2grp) groups=210(mqm),211(mqbrkrs)
uid=522(was3) gid=522(was3grp) groups=210(mqm),211(mqbrkrs)
uid=523(was4) gid=523(was4grp) groups=210(mqm),211(mqbrkrs)

The process execution environment in the Deployment Manager
Administrative Console was changed so all users were defined to the same
group. For every installation instance:
Servers->JMS Server->jmsserver->Process Definition->Process Execution:
UMASK : 002
Run As User : was<number>
Run As Group: mqbrkrs

This leads to the creation of the following semaphore:
T ID KEY MODE OWNER GROUP
s 3932179 0x410028db --ra-ra---- was1 mqbrkrs

Note: the first jmsserver instance to be started creates this semaphore with the corresponding owner, "was1" in this case. Now the right access is granted to all members of the mqbrkrs group, which allows all four jmsservers start successfully.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
Historical Number
91217010618
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Java Message Service (JMS)
Operating system(s): AIX
Software version: 5.0
Software edition:
Reference #: 1143719
IBM Group: Software Group
Modified date: Nov 3, 2003