| Author |
Message
|
| suneel |
 Posted: Mon Jan 10, 2011 5:11 am Post subject: Cluster queue is not visble at sender side |
 |
|
Voyager
Joined: 06 Nov 2009
Posts: 89
|
Hi,
When i am posting message on cluster queue i am getting 2085. But as per design queue should be there and this cluseter queue is visible at receiver side. PFB data from logs
AMQ7316: Failed to put message to statistics queue. Reason(2)
EXPLANATION:
The attempt to put a messsage containing statistics data to the queue
SYSTEM.ADMIN.STATISTICS.QUEUE failed with reason code 2. The
message data has been discarded.
This error message will be written only once for attempts to put a message to
the queue as part of the same operation which fail for the same reason.
ACTION:
Ensure that the queue SYSTEM.ADMIN.STATISTICS.QUEUE is
available and operational. |
|
| Back to top |
|
 |
| fatherjack |
| Posted: Mon Jan 10, 2011 5:29 am Post subject: |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
Is your cluster set up and working correctly?
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 10, 2011 5:34 am Post subject: Re: Cluster queue is not visble at sender side |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| suneel wrote: |
| When i am posting message on cluster queue i am getting 2085. But as per design queue should be there and this cluseter queue is visible at receiver side. |
Why are you posting to a SYSTEM object?
Why is a SYSTEM object clustered?
It's quite likely the queue is visible at the receiver side, i.e. where it's hosted. Is it visible to the cluster at either the sender or the receiver side? Is it visible to the FR?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| suneel |
| Posted: Mon Jan 10, 2011 5:37 am Post subject: |
|
|
Voyager
Joined: 06 Nov 2009
Posts: 89
|
| Thanks issue resolved now... |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 10, 2011 5:46 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| suneel wrote: |
| Thanks issue resolved now... |
Care to post the resolution for the benefit of future readers who might find themselves in this rather odd position?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| suneel |
| Posted: Mon Jan 10, 2011 5:47 am Post subject: |
|
|
Voyager
Joined: 06 Nov 2009
Posts: 89
|
| i have done cluster refresh on full repos and it worked |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 10, 2011 5:48 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| suneel wrote: |
| i have done cluster refresh on full repos and it worked |
And why did that help? Why was that needed?
And why are you posting to a SYSTEM object?
And why have you placed it in a cluster?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| John89011 |
| Posted: Wed Jan 12, 2011 10:43 pm Post subject: |
|
|
Voyager
Joined: 15 Apr 2009
Posts: 94
|
If you're not on 7.0.1.3+ you might want to consider upgrading, refresh might just be a temporary workaround..
APAR Identifier ...... IZ70135 Last Changed ........ 10/02/24
UNACKNOWLEDGED CLUSTER SUBSCRIPTIONS COULD LEAD TO A RETURN CODE
OF 2085 MQRC_UNKNOWN_OBJECT_NAME
Symptom ...... IN INCOROUT Status ........... CLOSED PER
Severity ................... 3 Date Closed ......... 10/02/24
Component .......... 5724H7222 Duplicate of ........
Reported Release ......... 700 Fixed Release ............ 999
Component Name WMQ HP V7 Special Notice
Current Target Date ..10/05/14 Flags
SCP ...................
Platform ............
Status Detail: Not Available
PE PTF List:
PTF List:
Release 700 : PTF not available yet
Parent APAR:
Child APAR list: PM08471
ERROR DESCRIPTION:
A timing window exists when putting to a cluster queue resulting
in a 2085 MQRC_UNKNOWN_OBJECT_NAME.
LOCAL FIX:
No local fix
PROBLEM SUMMARY:
****************************************************************
USERS AFFECTED:
Users of WebSphere MQ queue manager clusters.
Platforms affected:
All Distributed (iSeries, all Unix and Windows)
****************************************************************
PROBLEM SUMMARY:
The problem was caused by an incorrect check on the elapsed
subscription acknowledgment time.
PROBLEM CONCLUSION:
The problem has been resolved by removing the timing window.
---------------------------------------------------------------
The fix is targeted for delivery in the following PTFs:
v7.0
Platform Fix Pack 7.0.1.3
-------- --------------------
Windows tbc_p700_0_1_3
AIX tbc_p700_0_1_3
HP-UX (PA-RISC) tbc_p700_0_1_3
HP-UX (Itanium) tbc_p700_0_1_3
Solaris (SPARC) tbc_p700_0_1_3
Solaris (x86-64) tbc_p700_0_1_3
iSeries tbc_p700_0_1_3
Linux (x86) tbc_p700_0_1_3
Linux (x86-64) tbc_p700_0_1_3
Linux (zSeries) tbc_p700_0_1_3
Linux (Power) tbc_p700_0_1_3 |
|
| Back to top |
|
|
|
|
