| Author |
Message
|
| popebb |
 Posted: Mon Apr 02, 2007 4:35 am Post subject: amq9511 reason code 2003 |
 |
|
Apprentice
Joined: 23 Aug 2006
Posts: 34
|
i have a rec channel on windows 2000 server, mq ver 5.3 csd11, that will not stay running. i am getting the error message "amq9511 the attempt to put messages to queue 'local.queue.name' failed with rc 2003"
Any ideas |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Apr 02, 2007 4:42 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Code: |
| 2003 0x000007d3 MQRC_BACKED_OUT |
My 1st guess would be there's no room on the target queue & no dead letter queue (or a full dlq) on the target queue manager.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| popebb |
| Posted: Mon Apr 02, 2007 4:46 am Post subject: |
|
|
Apprentice
Joined: 23 Aug 2006
Posts: 34
|
| the queue is there and the queue depth is 0. i was able to do a local put and it worked fine. when the host puts it does 50 then rolles back and the channel goes to a retry on his side |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 02, 2007 4:49 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
That sounds like a batch of messages being rejected (I think default batch size is 50???).
Check the channel sequence numbers. They might be out of sync.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| popebb |
| Posted: Mon Apr 02, 2007 4:57 am Post subject: |
|
|
Apprentice
Joined: 23 Aug 2006
Posts: 34
|
| tried that, didn't work, looks like we are also getting amq7469 stating that transactions are rolled back to release log space |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 02, 2007 5:06 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| popebb wrote: |
| tried that, didn't work, looks like we are also getting amq7469 stating that transactions are rolled back to release log space |
Ahh... additional information!!! 
Running out of log space is a very good way of getting a 2003 code. You don't say if you're using circular or linear logging, but make sure you have enough defined of either to meet your needs.
If 50 transactions can blow it, I'd also make sure you have enough actual space for the log files.
Use the search function (top right). AMQ7469 and the care of log files has been the topic of previous discussions which you may find of value. Don't forget to verify that any long running transactions issue commits at relevent intervals.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| popebb |
| Posted: Mon Apr 02, 2007 5:38 am Post subject: |
|
|
Apprentice
Joined: 23 Aug 2006
Posts: 34
|
| it is circular, there is 1.62 gig left on this partition, should be enough, i will try to clear some more space |
|
| Back to top |
|
|
| popebb |
| Posted: Mon Apr 02, 2007 5:40 am Post subject: |
|
|
Apprentice
Joined: 23 Aug 2006
Posts: 34
|
| i thought i can not increase log space on the fly, correct |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 02, 2007 5:42 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
If there's enough space, then it's log file you're running out of. The queue manager will only use the amount of log defined when it was created. Once that's gone (possibly because it's not being freed by a long running transaction) you can have as much physical disc as you like & you'll still get log full messages.
Check out some of the topics concerning amq7469 for some solutions and suggestions.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 02, 2007 5:43 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| popebb wrote: |
| i thought i can not increase log space on the fly, correct |
Entirely correct.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| popebb |
| Posted: Mon Apr 02, 2007 5:44 am Post subject: |
|
|
Apprentice
Joined: 23 Aug 2006
Posts: 34
|
| this can only be changed at qmgr creation if i am not mistaken |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 02, 2007 5:49 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| popebb wrote: |
| this can only be changed at qmgr creation if i am not mistaken |
Still with the entirely correct there. 
So review some of the posts for helpful suggestions and methodolgies (some good, some slightly dubious) for getting yourself out of a log full situation.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| popebb |
| Posted: Mon Apr 02, 2007 6:01 am Post subject: |
|
|
Apprentice
Joined: 23 Aug 2006
Posts: 34
|
i have changed the batch interval down to 10 where it was 50 and looks
the channel is staying running |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 02, 2007 6:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| popebb wrote: |
i have changed the batch interval down to 10 where it was 50 and looks
the channel is staying running |
Rather fixing the symptom than the cause but if it works & you can take the performance hit... 
If it was me, I'd find out why the logs are so small / so full & either increase log size or have the offending transaction rewritten. But it's not me, it's you.
Glad you've got your channel fixed.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| popebb |
| Posted: Mon Apr 02, 2007 6:10 am Post subject: |
|
|
Apprentice
Joined: 23 Aug 2006
Posts: 34
|
| this is currently production so i just want to get things flowing again. i am not familiar with the programming side of this, what should i tell the application guys? the messages where showing commited on the MF side, so i don't really know if the app people are not doing the commits looks like a log space prob to me? |
|
| Back to top |
|
|
|
|
