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 Installation/Configuration Support » Message sent to several MDBs

Post new topic  Reply to topic
 Message sent to several MDBs « View previous topic :: View next topic » 
Author Message
CRyback
PostPosted: Sun Nov 19, 2006 1:48 am    Post subject: Message sent to several MDBs Reply with quote

Newbie

Joined: 19 Nov 2006
Posts: 5

Hello,

I am administrating a quit simple J2EE environment, where we have some MDBs in WebSphere 5.0.x and as a msg broker we have WebSphere MQ on a separate LPAR.
I bumped into a problem, where it seems that MQ Broker is sending(or the queue) twice a same message to MDBs.
Can anyone confirm are there any parameters related to queues, queue manager that would prohibit this?

Thanks for any help.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Sun Nov 19, 2006 6:04 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

There are several different ways this could be happening.

All of them require that some application has been written to cause this. Neither MQ nor Message Broker will do this "automatically" without a reason.

For example, pub/sub is explicitly designed to put the same message on more than one queue. But it will only do it if applications register subscriptions for those different queues.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
CRyback
PostPosted: Sun Nov 19, 2006 10:35 pm    Post subject: Reply with quote

Newbie

Joined: 19 Nov 2006
Posts: 5

Hi,

But this is not a pub/sub queue. And I have verified that the application works in another similar environment. That makes it harder to fix, since I can't replicate the problem
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Mon Nov 20, 2006 2:20 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

The problem is in your code, somewhere.

It's either in the flow or in the MDB.

But it's not clear to me from what you've posted, what the real problem is.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Nov 20, 2006 3:35 am    Post subject: Reply with quote

Grand High Poobah

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

I imagine that if you get the message multiple times in your MDB it's because you were not able to process it correctly the first time and threw an EJBException...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
CRyback
PostPosted: Mon Nov 20, 2006 10:30 pm    Post subject: Reply with quote

Newbie

Joined: 19 Nov 2006
Posts: 5

fjb_saper wrote:
I imagine that if you get the message multiple times in your MDB it's because you were not able to process it correctly the first time and threw an EJBException...


Hmm there is no EJBException, and in case an error would happen, it should rollback the transaction making the message available in the queue?
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 » IBM MQ Installation/Configuration Support » Message sent to several MDBs
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.