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 » IBM MQ Java / JMS » WebSphere MQ 7: Automatism needed for "bad" messag

Post new topic  Reply to topic
 WebSphere MQ 7: Automatism needed for "bad" messag « View previous topic :: View next topic » 
Author Message
cemeinz
PostPosted: Tue Sep 01, 2009 1:40 pm    Post subject: WebSphere MQ 7: Automatism needed for "bad" messag Reply with quote

Newbie

Joined: 01 Sep 2009
Posts: 6

Hello!

I read some post, queried the forum database, but I found no matching topic.

Here we go, this is my question.

We are using IBM WebSphere MQ 7 (on Windows) as a JMS provider. But one thing made us some headaches today. We read a message from the queue and validate it against a schema. Sometimes the files from the queue does not match with this schema. Our application then does a rollback, the message still resist in the queue. Is there any automatism to put those messages into an other queue, for example an error queue? Because this is the behaviour that we knew from WebSphere MQ if it is configured using good old MQ messages.

What will be a good solution? What should be a best-practice JMS architecture in this case?

Thanks in advance!

Cemeinz
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Sep 01, 2009 2:25 pm    Post subject: Re: WebSphere MQ 7: Automatism needed for "bad" me Reply with quote

Grand High Poobah

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

cemeinz wrote:
What will be a good solution? What should be a best-practice JMS architecture in this case?


Add code to your application to check the backout count of the message against the backout threshold of the input queue, and put it into the backout queue of the input queue if that count exceeds the threshold.

Alternatively don't make any changes to your code and run it under an app server, which provides this functionality automatically.

I'm interested to know what you searched for; this has been discussed a number of times and I'm concerned it didn't come up in your results.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Sep 01, 2009 8:08 pm    Post subject: Reply with quote

Grand High Poobah

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

Make sure the BOTHRESH and BOQUEUE are set on your process input queue.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » WebSphere MQ 7: Automatism needed for "bad" messag
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.