| Author |
Message
|
| tanishka |
 Posted: Fri Dec 26, 2008 9:25 am Post subject: AMQ9218 error |
 |
|
Centurion
Joined: 24 Nov 2008
Posts: 144
|
I am getting following error when i defined lstr and started listener on linux MQ v6.0
12/26/2008 10:02:04 AM - Process(9570.1) User(mqm) Program(runmqlsr)
AMQ9218: The TCP/IP listener program could not bind to port number 1414.
EXPLANATION:
An attempt to bind the TCP/IP socket to the listener port was unsuccessful.
ACTION:
The failure could be due to another program using the same port number. The
return code from the 'bind' call for port 1414 was 98. Record these values and
tell the systems administrator.
----- amqclita.c : 700 --------------------------------------------------------
12/26/2008 10:02:04 AM - Process(1338.1) User(mqm) Program(amqzmgr0)
AMQ5027: The Listener 'LSTR1' has ended. ProcessId(9570).
EXPLANATION:
The Listener process has ended.
ACTION:
None.
below is output from 'netstat' command
netstat -an | grep 1414
tcp 0 0 0.0.0.0:1414 0.0.0.0:* LISTEN |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Dec 26, 2008 11:39 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
This is quite clear.
You are trying to bind the listener to the default port 1414. However that port as you showed is already in use. Find a different port for this listener. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| tanishka |
| Posted: Fri Dec 26, 2008 1:28 pm Post subject: |
|
|
Centurion
Joined: 24 Nov 2008
Posts: 144
|
| What is the command to know that listener1414 is already running |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Dec 26, 2008 4:58 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| tanishka wrote: |
| What is the command to know that listener1414 is already running |
| tanishka wrote: |
below is output from 'netstat' command
netstat -an | grep 1414
tcp 0 0 0.0.0.0:1414 0.0.0.0:* LISTEN |
Note it does not mean that there is an MQListener on that port. It just means that the port is already in use.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| exerk |
| Posted: Sat Dec 27, 2008 1:29 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
If there are any other queue managers on the server, check their Listener objects to see what IP Port has been assigned - you are using Listener objects aren't you?.
If this was a migration, check that Listener entries were not set up in inetd.conf and /etc/services, and were not removed pre/post migration.
Alternatively, scripting may be starting a Listener, in which case ps -ef | grep runmqlsr should show if any are running.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Augusto |
| Posted: Mon Dec 29, 2008 11:23 am Post subject: |
|
|
Apprentice
Joined: 08 Dec 2008
Posts: 29
|
I am able to connect QM on linux box from explorer on my system but
output from ps -ef | grep runmqlsr is
mqm 11047 11004 0 21:29 pts/1 00:00:00 grep runmqlsr |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Mon Dec 29, 2008 11:40 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
| Augusto wrote: |
I am able to connect QM on linux box from explorer on my system but
output from ps -ef | grep runmqlsr is
mqm 11047 11004 0 21:29 pts/1 00:00:00 grep runmqlsr |
As exerk has already stated, check /etc/inetd.conf and /etc/services.
Specifically, try:
grep 1414 /etc/services |
|
| Back to top |
|
|
|
|
