This problem can be because the broker is unable to access
some semaphores that it needs.
When the JMSServer is installed, the WEMPS broker creates a number of
semaphores. The semaphores are owned by root, and remain on the system
until either the system is restarted, or the semaphores are deleted by the
user.
The WEMPS broker attempts to access these semaphores as part of the
startup routine. If the semaphores do not exist, it creates them. However,
if the semaphores are created using a different user than the one who is
trying to access them, an error occurs and the broker fails to start.
It is suspected that the reason the WEMPS broker fails to start is because
the shared memory semaphores are created by a different user than the
non-root user that is starting WebSphere Application Server.
If you have not restarted the system since the JMSServer was installed,
the semaphores are owned by root, and not the non-root user. Because the
semaphores already exist, WEMPS attempts to reuse them, but is unable to
because the non-root user does not have permission to access them.
|