| Author |
Message
|
| sabu21s |
 Posted: Tue Aug 10, 2004 8:05 am Post subject: Problem having 2 Qmanagers |
 |
|
Apprentice
Joined: 01 Oct 2003
Posts: 27
Location: Atlanta
|
I have Mqseries v5.1(I know this is out dated  ) running on a Unix box, and I wanted to create 2 Q managers. So by default one takes port 1414 and for the second Qmanager I specified port 1823. I followed the instruction from an article, which said to do the following.
Add a line in the /etc/services file:
MQSeries 1414/tcp
where 1414, the default, is the port number required. Alternatively, you might want to use a different port, for example, port number 1822 in which case add the line:
MQSeries 1822/tcp
Add a line (case sensitive) in the inetd.conf file to call the program amqcrsta:
MQSeries stream tcp nowait mqm /mqmtop/bin/amqcrsta amqcrsta [-m QM1]
But when I try to connect to the QM from an windows box it cannot reach the 2nd QM. However, has no problem with the first? Please help.
Thanks
Sabu21s |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Aug 10, 2004 8:13 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Sabu try this
/etc/services:
| Code: |
MQSeries 1414/tcp
MQSeries2 1415/tcp
|
Now in /etc/inetd.conf
| Code: |
MQSeries stream tcp nowait mqm /mqmtop/bin/amqcrsta amqcrsta [-m QM1]
MQSeries2 stream tcp nowait mqm /mqmtop/bin/amqcrsta amqcrsta [-m QM2] |
Now you should be able to reach both queue managers.
The second one will have its listener at port 1415 but you can change this to any other free port. |
|
| Back to top |
|
|
| sabu21s |
| Posted: Tue Aug 10, 2004 8:51 am Post subject: Tried but no luck |
|
|
Apprentice
Joined: 01 Oct 2003
Posts: 27
Location: Atlanta
|
I tried to run this command to 1415 and got this message:
./runmqlsr -t tcp -m UXQA01.QUEUE.MANAGER -p 1415
04L1816, 5765-B75 (C) Copyright IBM Corp. 1994, 1999. ALL RIGHTS RESERVED.
08/10/04 12:03:36 PM AMQ9218: The TCP/IP listener program could not bind to port number 1415.
I did the same as you mentioned and I tried to reconnect and I get this error message on my Win2k box(Event Viewer)
Event Type: Error
Event Source: MQSeries
Event Category: None
Event ID: 9520
Date: 8/10/2004
Time: 11:28:43 AM
User: N/A
Computer: NTQA01
Description:
Channel not defined remotely.
There is no definition of channel 'NTQA01.UXQA01' at the remote location.
Add an appropriate definition to the remote hosts list of defined channels and retry the operation.
Is there anything else I can try. How can I see if both the listeners are running?
Thanks for your time
Sabu
Last edited by sabu21s on Tue Aug 10, 2004 9:04 am; edited 1 time in total |
|
| Back to top |
|
|
| EddieA |
| Posted: Tue Aug 10, 2004 8:57 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
That message is indicating that you did indeed make a connection, through the listener, to a QM. But, there is no channel defined that is called "'NTQA01.UXQA01".
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| sabu21s |
| Posted: Tue Aug 10, 2004 9:10 am Post subject: I checked but... |
|
|
Apprentice
Joined: 01 Oct 2003
Posts: 27
Location: Atlanta
|
I did a display and it shows I have a Channel defined.
display chstatus(NTQA01.UXQA01)
AMQ8417: Display Channel Status details.
CHANNEL(NTQA01.UXQA01) XMITQ( )
CONNAME( ) CURRENT
CHLTYPE(RCVR) STATUS(STOPPED)
Note: I had to stop the channel to see the result
Then I tried to start the listener and I got this error:
I tried to run this command to 1415 and got this message:
./runmqlsr -t tcp -m UXQA01.QUEUE.MANAGER -p 1415
04L1816, 5765-B75 (C) Copyright IBM Corp. 1994, 1999. ALL RIGHTS RESERVED.
08/10/04 12:03:36 PM AMQ9218: The TCP/IP listener program could not bind to port number 1415. |
|
| Back to top |
|
|
| PGoodhart |
| Posted: Tue Aug 10, 2004 10:54 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
Your latest issue is kind of the classic error you get when you have another program already bound to a port. Is the listener running on port 1415 already when you tried to start it? Or do you have another program using port 1415? (sometimes people start a listener as a service rather then a program and then they can't figure out why the listener won't start from the command line...)
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Aug 10, 2004 12:26 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
display chstatus(NTQA01.UXQA01)
AMQ8417: Display Channel Status details.
CHANNEL(NTQA01.UXQA01) XMITQ( )
CONNAME( ) CURRENT
CHLTYPE(RCVR) STATUS(STOPPED)
|
Somebody manually stopped the channel
You should start it. |
|
| Back to top |
|
|
| bbburson |
| Posted: Tue Aug 10, 2004 12:38 pm Post subject: Look very closely at /etc/services and /etc/inet.d |
|
|
Partisan
Joined: 06 Jan 2004
Posts: 378
Location: Nowhere near a queue manager
|
runmqlsr cannot bind to port 1415 because something else is already listening on that port (probably your inetd service).
Look in /etc/services for "1415/tcp" to find the NAME of the service for that port.
Look in /etc/inetd.conf for that NAME to find what command is being run when something connects to that port (should be amqcrsta -m <QMGR>).
If the 1415 service has the same NAME as the 1414 service, then you've got two listeners for one queue manager and none for the second queue manager. That could explain the "channel not defined" error because a connection to QM1 will not find the channels defined in QM2. |
|
| Back to top |
|
|
| EddieA |
| Posted: Tue Aug 10, 2004 4:41 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
You should NOT use runmqlsr IF you have defined the listener to run as an inetd service. It's one OR the other.
Show us the lines from the /etc/services and /etc/inetd.conf files for MQSeries. And also the channel definition from the 'sending' side (Windows) and the channel definition on the 'receiving' side.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| njacob |
| Posted: Wed Aug 11, 2004 7:08 am Post subject: Inetd.conf and Services |
|
|
Newbie
Joined: 11 Aug 2004
Posts: 5
|
Entries from /etc/inetd.conf
MQSeries stream tcp nowait mqm /opt/mqm/bin/amqcrsta amqcrsta -m UXDV01.QUEUE.MANAGER
MQSeries2 stream tcp nowait mqm /opt/mqm/bin/amqcrsta amqcrsta -m UXQA01.QUEUE.MANAGER
Entries from /etc/services
MQSeries 1414/tcp # MQSeries Channel
MQSeries2 1824/tcp # MQSeries Channel
NOTE: I changed the port # from 1415 to 1824. |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Aug 11, 2004 10:54 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| And also the channel definition from the 'sending' side (Windows) and the channel definition on the 'receiving' side. |
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Aug 12, 2004 5:56 am Post subject: Adding a second QMGR |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
There are a number of this you can do to sort this out. One that has not ben mentioned is if you change the /etc/services & /etc/inetd.conf files you may need to restart the inetd daemon to pick up the new config (unless you reboot)
Then, /var/adm/messages (or /var/log/messages dependingupon your unix type) should show a record of any incoming IP connection attempts that get matched to an MQ Service.
for example
Aug 12 14:43:28 NUMPTY inetd[491]: [ID 317013 daemon.notice] MQseries2[21338] from 170.150.54.39 60641
That shows that IP 170.150.54.39 tried to connect to WMQ Queue Manager identified in /etc/services & /etc/inetd.conf by MQseries2
Then you can go to the /errors directory (In the above /var/mqm/qmgrs/NUMPTYQMGR/errors) and look for entries like
08/12/04 12:07:06
AMQ9002: Channel program started.
EXPLANATION:
Channel program 'T1.MICKEY.NUMPTYQMGR' started.
ACTION:
None.
That means that the channel connection has started.
If you are not sure if the Channel connection is working you can try using telnet to conect to the port. That is a check I use to see if the /etc/services etc is working correctly.
$ telnet 127.0.0.1 1415
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
^C^C
Connection closed by foreign host.
$
$ telnet 127.0.0.1 1413
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
$
The first example shows a telnet to a port that is listening. The second to one that is not.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
