|
Problem(Abstract) |
When Embedded Messaging is used in IBM® WebSphere®
Application Server V5.0, the embedded queue manager and broker may fail to
start due to the following error:
MSGS0501E: The JMS Server failed to create a security service listener
socket: java.net.BindException: The socket name is already in use.
The error would appear in the SystemOut.log for the application server or
the jmsserver (if running in a Network Deployment environment). |
|
|
|
Cause |
The problem occurs when the JMSSERVER_SECURITY_PORT is in
use when the embedded queue manager and broker try to start. The default
JMSSERVER_SECURITY_PORT is 5557. You can check to see which port is used
on your system by using the Administrative Console:
- In a WebSphere Application Server Base installation,
expand Servers, select Application Servers, and choose your application
server. Then select Server Components, JMS Servers, and Security Port
Endpoint.
- In a WebSphere Application Server Network Deployment
environment, expand Servers, select JMS Servers, and select your
jmsserver. Then select Security Port Endpoint.
You can use the netstat
-an command to verify that the port is in use. The port may be in
use by another application server or jmsserver or any other software on
your system. |
|
|
Resolving the
problem |
There are two ways to resolve the problem:
- Ensure that no other processes on your system use port
5557.
- Modify the JMSSERVER_SECURITY_PORT in your WebSphere
configuration to use a different port. See above for the instructions on
how to do this using the Administration Console.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|