| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Local queue missing. |
« View previous topic :: View next topic » |
| Author |
Message
|
| vinay_s_s |
 Posted: Tue Jan 20, 2009 4:25 am Post subject: Local queue missing. |
 |
|
Apprentice
Joined: 17 Nov 2008
Posts: 39
|
Hi Team,
A local queue is missing in one of our servers. I cannot find it in MQ explorer, as well as command prompt using runmqsc. However, I see that the queue was existing by browsing to the folder \WebSphere MQ\Qmgrs\Qmgrname\Queues folder.
What is the cause for this kind of error. I dont see any error logged in error log file(s).
WebSphere MQ 6.0
Maintenance level : 6.0.2.2
Windows 2003 Enterprise Server.
Please let me know if you need more information.
Regards,
Vinay |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Jan 20, 2009 4:31 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I would theorise the queue object has been damaged by a file error, though I would have expected it still to show up in Explorer (albeit unusable and with a little warning icon)
Typical course of action in this situation is to delete/define the queue in question. It's for this reason many people define queues with script, so the script can be re-run in seconds.
Another solution (often used in production environments) is linear logging and media recovery. Very useful if (against best practice) you keep messages in the queues for extended periods.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vinay_s_s |
| Posted: Tue Jan 20, 2009 4:39 am Post subject: |
|
|
Apprentice
Joined: 17 Nov 2008
Posts: 39
|
But if an application is unable to put the messages on this queue, there should be some kind of error logging. Why error logging is not updating the logs with this error?
Is it that queue file damages are not considered an error?  |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 20, 2009 4:47 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vinay_s_s wrote: |
| But if an application is unable to put the messages on this queue, there should be some kind of error logging. Why error logging is not updating the logs with this error? |
Because if the queue is missing, the putting application will be getting a 2085 error. At this point the queue manager can't tell if the requested queue is missing, or the application is using an invalid queue name. Hence it's not logged as a queue manager error because it's the application that has the problem. All the queue manager processes are fine.
| vinay_s_s wrote: |
| Is it that queue file damages are not considered an error? |
The error log records errors with the queue manager processes. No queue manager process accesses the queues, so the error will go undetected.
I'm also assuming this is a damaged object; as I said, I'd have expected that to still be shown in Explorer. Another, plausable, explaination is the queue was deleted and the queue manager housekeeping has not yet removed the file.
Depends on your security & procedures of course.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jan 20, 2009 6:28 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| But if an application is unable to put the messages on this queue... |
WMQ returns to the application a Reason and Completion codes for EVERY MQI call. It is the responsibility of the application to test for these, and take appropriate action.
| Quote: |
| Is it that queue file damages are not considered an error? |
An appropriate Reason/Completion will be returned to the application in this case. RC2101: MQRC_OBJECT_DAMAGED.
WMQ might also post this: AMQ9587: Program cannot open queue manager object.
More likely reasons the queue doesn't exist is that someone deleted it, OR the application specified an incorrect queue name at MQOPEN.
The WMQ API calls and the Reason and Completion codes that are returned are documented in the WMQ Application Programming Reference and WMQ Application Programming Guide.
This post is similar to your prior post regarding your application not testing Reason and Completion codes.
_________________
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 |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
