ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » QM is trying to connect to a QM that isn't in cluster

Post new topic  Reply to topic
 QM is trying to connect to a QM that isn't in cluster « View previous topic :: View next topic » 
Author Message
Boomn4x4
PostPosted: Wed Apr 18, 2012 5:10 am    Post subject: QM is trying to connect to a QM that isn't in cluster Reply with quote

Disciple

Joined: 28 Nov 2011
Posts: 172

I have 3 systems currently setup; Development, QA, and Production.

I installed and configured a QMGR into the QA cluster, and today, I see in the error logs that it is trying to connect to a queue manager that is a member of the Development configuration. How is this possible? The logs are showing Channel Not found, there is no channel definition. However, it shouldn't find it as they aren't in the same cluster... the QA system I configured shouldn't even know that queue manager exists.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Wed Apr 18, 2012 5:26 am    Post subject: Re: QM is trying to connect to a QM that isn't in cluster Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

Boomn4x4 wrote:
How is this possible? The logs are showing Channel Not found, there is no channel definition.

So, you are saying that there are absolutely no channels defined in the new qmgr? Not even one CLUSSDR channel? CLUSRCVR? And yet, you see errors in the logs that indicate that a channel is not found?

What is 'not found' the channel name? Post the error here.
_________________
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
View user's profile Send private message
Vitor
PostPosted: Wed Apr 18, 2012 5:39 am    Post subject: Re: QM is trying to connect to a QM that isn't in cluster Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Boomn4x4 wrote:
I see in the error logs that it is trying to connect to a queue manager that is a member of the Development configuration.


What role does this queue emanager play in the Development cluster? Full Repository or partial repository? Likewise the queue manager in QA? FR or PR?

Boomn4x4 wrote:
How is this possible?


I see 2 possibilities:

- you have overlapping Dev & QA clusters
- an application in QA thinks it's still in Dev, is addressing messages to the Dev queue manager & the cluster's trying to fulfill the request

There are undoubtably other possibilities, and I'm not entirely certain either of those fully explain what you've described.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Apr 18, 2012 5:42 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

I figure that the qmgr was repurposed and switched environment (dev to QA).
When the qmgr switched environment, it was not done properly and you have probably messages on the SCTQ that are targeted for the DEV cluster.

In order to get a clean bill of health there, you need to remove the messages for the dev cluster, then make sure there is no reference to the dev cluster any more on the qmgr, and on the FRs.

Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Boomn4x4
PostPosted: Wed Apr 18, 2012 6:13 am    Post subject: Reply with quote

Disciple

Joined: 28 Nov 2011
Posts: 172

In Dev, there are two FRs, DEV_HUB1 and DEV_HUB2, they are members of the cluster DEV_CLUSTER. There are several PRs in that cluster, one in particular is the issue, DEV_POS9972_QM

In QA, there are two FR QA_HUB1 and QA_HUB2, they are members of the cluster QA_CLUSTER. There are several PRs in that cluster as well.

I have checked two PRs in QA and they are both throwing similar errors referencing the same IP address (but different channel names)

From QA system 1:
Code:
----- amqrcoba.c : 1344 -------------------------------------------------------
04/18/2012 05:20:13 AM - Process(17016.115) User(mqm) Program(amqrmppa)
                    Host(pos8702)
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'TO.DEV_POS9972_QM' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TO.DEV_POS9972_QM' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 565 --------------------------------------------------------
04/18/2012 05:20:14 AM - Process(17016.116) User(mqm) Program(amqrmppa)
                    Host(pos8702)
AMQ9780: Channel to remote machine '10.240.3.184' is ending due to an error.

EXPLANATION:
Channel 'TO.DEV_POS9972_QM' between this machine and the remote machine
'10.240.3.184' encountered an error and will now end. In some cases the channel
name cannot be determined and so is shown as '????'.

This message will be accompanied by other messages which explain the cause of
the error.
ACTION:
Tell the systems administrator, who should attempt to identify the cause of the
channel failure using problem determination techniques.  For example, look for
FFST files, and examine the error logs on the local and remote systems where
there may be messages explaining the cause of failure.  More information may be
obtained by repeating the operation with tracing enabled.
----- amqrcoba.c : 1307 -------------------------------------------------------
04/18/2012 05:20:14 AM - Process(17016.116) User(mqm) Program(amqrmppa)
                    Host(pos8702)
AMQ9519: Channel 'TO.DEV_POS9972_QM' not found.

EXPLANATION:
The requested operation failed because the program could not find a definition
of channel 'TO.DEV_POS9972_QM'.
ACTION:
Check that the name is specified correctly and the channel definition is
available.
----- amqrcoba.c : 1344 -------------------------------------------------------
04/18/2012 05:20:14 AM - Process(17016.116) User(mqm) Program(amqrmppa)
                    Host(pos8702)
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'TO.DEV_POS9972_QM' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TO.DEV_POS9972_QM' in the
error files to determine the cause of the failure.


From QA system 2:
Code:
---- amqrmrsa.c : 565 --------------------------------------------------------
04/18/2012 10:00:37 AM - Process(21105.33) User(mqm) Program(amqrmppa)
                    Host(pos1035)
AMQ9780: Channel to remote machine '10.240.3.184' is ending due to an error.

EXPLANATION:
Channel 'TO.DEV_POS9958_QM' between this machine and the remote machine
'10.240.3.184' encountered an error and will now end. In some cases the channel
name cannot be determined and so is shown as '????'.

This message will be accompanied by other messages which explain the cause of
the error.
ACTION:
Tell the systems administrator, who should attempt to identify the cause of the
channel failure using problem determination techniques.  For example, look for
FFST files, and examine the error logs on the local and remote systems where
there may be messages explaining the cause of failure.  More information may be
obtained by repeating the operation with tracing enabled.
----- amqrcoba.c : 1307 -------------------------------------------------------
04/18/2012 10:00:37 AM - Process(21105.33) User(mqm) Program(amqrmppa)
                    Host(pos1035)
AMQ9519: Channel 'TO.DEV_POS9958_QM' not found.

EXPLANATION:
The requested operation failed because the program could not find a definition
of channel 'TO.DEV_POS9958_QM'.
ACTION:
Check that the name is specified correctly and the channel definition is
available.
----- amqrcoba.c : 1344 -------------------------------------------------------
04/18/2012 10:00:37 AM - Process(21105.33) User(mqm) Program(amqrmppa)
                    Host(pos1035)
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'TO.DEV_POS9958_QM' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TO.DEV_POS9958_QM' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 565 --------------------------------------------------------
04/18/2012 10:00:37 AM - Process(21105.34) User(mqm) Program(amqrmppa)
                    Host(pos1035)
AMQ9780: Channel to remote machine '10.240.3.184' is ending due to an error.

EXPLANATION:
Channel 'TO.DEV_POS9958_QM' between this machine and the remote machine
'10.240.3.184' encountered an error and will now end. In some cases the channel
name cannot be determined and so is shown as '????'.

This message will be accompanied by other messages which explain the cause of
the error.
ACTION:
Tell the systems administrator, who should attempt to identify the cause of the
channel failure using problem determination techniques.  For example, look for
FFST files, and examine the error logs on the local and remote systems where
there may be messages explaining the cause of failure.  More information may be
obtained by repeating the operation with tracing enabled.
----- amqrcoba.c : 1307 -------------------------------------------------------
04/18/2012 10:00:37 AM - Process(21105.34) User(mqm) Program(amqrmppa)
                    Host(pos1035)
AMQ9519: Channel 'TO.DEV_POS9958_QM' not found.

EXPLANATION:
The requested operation failed because the program could not find a definition
of channel 'TO.DEV_POS9958_QM'.
ACTION:
Check that the name is specified correctly and the channel definition is
available.
----- amqrcoba.c : 1344 -------------------------------------------------------
04/18/2012 10:00:37 AM - Process(21105.34) User(mqm) Program(amqrmppa)
                    Host(pos1035)
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'TO.DEV_POS9958_QM' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TO.DEV_POS9958_QM' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 565 --------------------------------------------------------
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Apr 18, 2012 6:17 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Which queue manager in QA was the one you configured?

Do any QA queue managers have stuck messages in the SCTQ?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » QM is trying to connect to a QM that isn't in cluster
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.