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 » BACKOUTCOUNT greater than BOTHRESH

Post new topic  Reply to topic
 BACKOUTCOUNT greater than BOTHRESH « View previous topic :: View next topic » 
Author Message
roshan.171188
PostPosted: Sat Mar 09, 2013 8:38 pm    Post subject: BACKOUTCOUNT greater than BOTHRESH Reply with quote

Apprentice

Joined: 07 Jun 2012
Posts: 35

Hello all,

i am not sure what else to check but i have a message lying on a queue where application is unable to pick up the message because of a CCSID issue.
from the message,
Back out Count = more than 1k
BOTHRESH of the queue = 10
BOQUEUE is null for the queue.

Now in this case, the message should go to the default dead queue which is defined on the qmgr object, but thats not happning here in this case.
Can anyone tell me if this can be something because the Queue Manager conversion is not supported for this CCSID??
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sat Mar 09, 2013 10:54 pm    Post subject: Reply with quote

Poobah

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

Why should the message go to the dead letter queue? Is this a message broker app?
_________________
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
roshan.171188
PostPosted: Sat Mar 09, 2013 11:08 pm    Post subject: Reply with quote

Apprentice

Joined: 07 Jun 2012
Posts: 35

If no BOQUEUE is mentioned on the application queue properties, after the backout threshold is reached, should the messages not go to the default dead queue?
Back to top
View user's profile Send private message
exerk
PostPosted: Sun Mar 10, 2013 3:38 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

roshan.171188 wrote:
If no BOQUEUE is mentioned on the application queue properties, after the backout threshold is reached, should the messages not go to the default dead queue?

Why should it? What makes you think it should? I suggest you read the Info Centre more closely.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
Vitor
PostPosted: Sun Mar 10, 2013 4:41 am    Post subject: Reply with quote

Grand High Poobah

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

roshan.171188 wrote:
If no BOQUEUE is mentioned on the application queue properties, after the backout threshold is reached, should the messages not go to the default dead queue?


Unless something like WAS or WAS is running your application, the message won't even go to the backout queue unless the application takes action.

But as others have pointed out, what leads you to believe in your set up a queue with no backout queue defined will start backing out to the dead letter queue? What do you think should be making this happen? Have you checked that the whatever you think is doing this is working?

And if you think the queue manager does this, it's your understanding that's not working.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sun Mar 10, 2013 5:23 am    Post subject: Reply with quote

Poobah

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

Backout count is simply a count of the number of times your application issued the MQBACK (or equivalent) API call for this message.

Backout threshold is simply a number that your application developers specify as the threshold (maximum number) for backouts for this queue.

Backout requeue queue name is simply a the name of the queue that your application should move the message to when backout threshold is reached.

It is an application responsibility to take action to backout a message, or to move it to the backout queue. The queue manager does NOT do this for your application.

This is well-documented in the WMQ Application Programming Reference manual, the WMQ Application Programming Guide manual, and the equivalent documentation on the InfoCenter.
_________________
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
rekarm01
PostPosted: Sun Mar 10, 2013 11:46 am    Post subject: Re: BACKOUTCOUNT greater than BOTHRESH Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 1415

bruce2359 wrote:
This is well-documented in the WMQ Application Programming Reference manual, the WMQ Application Programming Guide manual, and the equivalent documentation on the InfoCenter.

For example, regarding the BOQNAME and BOTHRESH, the APR states:

Quote:
Apart from allowing its value to be queried, the queue manager takes no action based on the value of this attribute.
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 » BACKOUTCOUNT greater than BOTHRESH
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.