|
| If you have problems starting the Queue Manager and Listener Port for WebSphere_Portal or any other WAS Instance...read this note.
a. use the "delelemq" and "createmq" commands in WAS_ROOT/bin path.
b. Then start the WebSphere_Portal instance by using the "startserver" command.
c. Be aware that the ListenerPort will NOT even attempt to start if there is no MDB deployed on that server, and bound to (listening on) that specific Listener Port.
Caution:
WAS Admin console gives misleading info on the actual state of the JMS Listener Port. For server1 instance it may show the state as "green" (started) when it really is not started. For any other instance it will show the state as "red" (stopped) when it i
s actually started. The only sure way to know is to verify that you have a message logged in SystemOut.log file of the respective server which confirms that the Listener Port that you configured has been started.
|
|