| Author |
Message
|
| RaviKrG |
 Posted: Sun Feb 08, 2009 7:38 am Post subject: Sender Channel Running but listener on Remote is not running |
 |
|
Master
Joined: 07 Sep 2008
Posts: 240
|
Hi , I have two QM on solaris (single machine) as below
QM1 ---- > QM2
QM1 : sender channel is QM1.QM2
QM2 : listener port is 1450 (manually created as DEF Listener)
QM2 : receiver channel is QM1.QM2
Scenario ONE:
Now I started the channel QM1.QM2 on QM1 but found it in retrying state and then checked the log and found as
02/08/09 20:10:59 - Process(10553.1) User(mqm) Program(runmqchl_nd)
AMQ9520: Channel not defined remotely.
EXPLANATION:
There is no definition of channel 'QM1.QM2' at the remote location.
ACTION:
Add an appropriate definition to the remote hosts list of defined channels and
retry the operation.
Finanly I checked the RCVR and found it was defined and then checked the status of port 1450 using ps -ef then found that lis was running but when I checked the Lis with command "DIS LSSTATUS(lis_name)" i was not able to see the status then I tried to stop the lis but could not so I KILLED the lis process and started the lis and finally started the channel QM1.QM2 successfully also the RCVR channel was running fine.
Scenario 2:
But now when I manually stopped the lis as STOP LISTENER(lis_name) successfully, checked the lis status and also through ps -ef it was not running which is fine BUT I FOUND THE SENDER CHANNEL on QM1 and RCVR CHANNEL running on QM2.
Doubts:
1) why in scenario 1 it said for "no definition of channel"
2) was it good to kill the lis process in scenario one and start the channels.
3) in scenario 2 why the channel are running should then not change the status as listener is not running.
Please suggest on this . Thanks |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sun Feb 08, 2009 9:11 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
In future posts, please include all your object definitions - like DISPLAY CHL(QM1.QM2), DISPLAY LISTENER(listenername), etc.. This will help us help you.
I'd guess that your sender channel definition does not specify what port to send to at the receiver end. WMQ defaults to port 1414.
Your reciever channel status would not exist until the channel becomes active. This happens when the listener receives inbound data and sends it to the receiver channel.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| RaviKrG |
| Posted: Sun Feb 08, 2009 9:29 am Post subject: |
|
|
Master
Joined: 07 Sep 2008
Posts: 240
|
sender channel is QM1.QM2 is connected to 1450 port on QM2. Also my channel has been defined with the port 1450 in conncetion.
Does this help :
Sender channel on QM1:
----------------
dis channel(QM1.QM2)
2 : dis channel(QM1.QM2)
AMQ8414: Display Channel details.
CHANNEL(QM1.Qm2) CHLTYPE(SDR)
ALTDATE(2009-01-30) ALTTIME(14.09.59)
BATCHHB(0) BATCHINT(0)
BATCHSZ(50) COMPHDR(NONE)
COMPMSG(NONE) CONNAME(174.20.5.245(1450))
-----
-----
Receiver Channel QM2:
-------------------
dis channel(QM1.QM2)
2 : dis channel(QM1.QM2)
AMQ8414: Display Channel details.
CHANNEL(QM1.QM2) CHLTYPE(RCVR)
ALTDATE(2009-01-30) ALTTIME(14.19.43)
BATCHSZ(50) COMPHDR(NONE)
COMPMSG(NONE) DESCR( )
------
------
Listener on QM2:
--------------
dis listener(LSN)
4 : dis listener(LSN)
AMQ8630: Display listener information details.
LISTENER(LSN) CONTROL(MANUAL)
TRPTYPE(TCP) PORT(1450)
IPADDR( ) BACKLOG(0)
DESCR( ) ALTDATE(2009-01-30)
ALTTIME(14.19. 08 )
bruce2359 this is right that "reciever channel status would not exist until the channel becomes active." but for "This happens when the listener receives inbound data and sends it to the receiver channel." I would say that there no data no passing not even of 0 kb.
It was just that we defined all the properties and all was fine before 15 days but today when we checked we found the that channel QM1.QM2 on QM1 was stopped so started and then we encountered scenario 1 and then I took the action as have defined in my previous post and then I faced the scenario 2. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Feb 08, 2009 9:42 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Your listener is defined with control(manual).
You might want to change that to control(qmgr). In that case it gets started when the qmgr starts and gets stopped when the qmgr stops.
Also make sure that no other processes have been added to the box that might use the 1450 port. As a precaution you might want to add it to the services table as
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Feb 08, 2009 9:44 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
Did you perform a PING CHANNELQM1.QM2) to test all your definitions?
Did you start your listener? CONTROL(MANUAL) requires that you manually start the listener.
And, yes, an active channel will have an entry in the channel status table. I would expect that you would get 'channel not found' for an inactive receiver channel.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Sun Feb 08, 2009 1:09 pm Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
| RaviKrG wrote: |
Sender channel on QM1:
----------------
dis channel(QM1.QM2)
2 : dis channel(QM1.QM2)
AMQ8414: Display Channel details.
CHANNEL(QM1.Qm2) CHLTYPE(SDR)
ALTDATE(2009-01-30) ALTTIME(14.09.59)
BATCHHB(0) BATCHINT(0)
BATCHSZ(50) COMPHDR(NONE)
COMPMSG(NONE) CONNAME(174.20.5.245(1450))
-----
-----
Receiver Channel QM2:
-------------------
dis channel(QM1.QM2)
2 : dis channel(QM1.QM2)
AMQ8414: Display Channel details.
CHANNEL(QM1.QM2) CHLTYPE(RCVR)
ALTDATE(2009-01-30) ALTTIME(14.19.43)
BATCHSZ(50) COMPHDR(NONE)
COMPMSG(NONE) DESCR( )
------
------
|
You have a typo in your sender channel definition. You have a lower case "m" in the channel name. The sender and receiver names must be an exact match, even in case. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Feb 08, 2009 1:10 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
Good eye.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| RaviKrG |
| Posted: Mon Feb 09, 2009 3:28 am Post subject: |
|
|
Master
Joined: 07 Sep 2008
Posts: 240
|
Thanks fjb_saper I think this will be good idea
SAFraser : sorry about the channel name that was just a printing mistake
In simple words I faced the scenario of
when the lis was running on rcvr QM then the sender channel was not running on sender QM and when the lis was not running on the rcvr QM then the sender channel on sender QM was running also the rcvr channel on rcvr QM was running. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Feb 09, 2009 3:58 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| RaviKrG wrote: |
In simple words I faced the scenario of
when the lis was running on rcvr QM then the sender channel was not running on sender QM and when the lis was not running on the rcvr QM then the sender channel on sender QM was running also the rcvr channel on rcvr QM was running. |
In general this is not possible. There may have been *two* listeners configured for the same port - that conflicted with each other. When you had one "stopped", then the other could run just fine. |
|
| Back to top |
|
|
| RaviKrG |
| Posted: Mon Feb 09, 2009 4:06 am Post subject: |
|
|
Master
Joined: 07 Sep 2008
Posts: 240
|
mqjeff ya thats right I was surprised to see this behaviour of MQ but I think the problem was somewhere and this issue stands closed now.
Thanks all for their help |
|
| Back to top |
|
|
|
|
