To resolve the problem, the queue must be defined on the
Embedded Messaging queue manager.
The name of the queue hosted on the Embedded Messaging queue manager
must have the same administrative name that was given on the WebSphere JMS
Provider Queue Destination configuration.
To determine the name of the queue follow this path in the
Administrative Console:
Resources -> WebSphere JMS Provider -> WebSphere Queue
Destinations -> <queue_destination_name> ->

In this example, the name of the queue which needs to be defined is
"myQueue". This name was taken from the "Name" field.
The next step is to define this queue on the queue manager:
For a stand-alone BASE installation, follow this path:
Servers -> Application Servers -> <server_name> ->
Server Components -> JMS Servers -> Queue names ->
For a federated Network Deployment environment, follow this path:
Servers -> JMS Servers -> jmsserver -> Queue names ->
In the "Queue names" field, add the queue which is to be hosted by this
JMS Server. In this example, "myQueue" was added.
Click OK and then save and synchronize the changes.
Now, the listener port for the Application server should start
successfully. Note, if there are multiple listener ports defined, you must
add the queues for each listener port to the configuration of the JMS
Server.
|