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 » WebSphere Message Broker (ACE) Support » Message Broker - Java Compute Node - Msg Affinity

Post new topic  Reply to topic
 Message Broker - Java Compute Node - Msg Affinity « View previous topic :: View next topic » 
Author Message
wyatt
PostPosted: Mon May 21, 2007 3:28 pm    Post subject: Message Broker - Java Compute Node - Msg Affinity Reply with quote

Voyager

Joined: 28 Nov 2004
Posts: 76
Hello

What problem(s) would ensue if a Java Compute node was used to connect to the same queue manager and queue that is being serviced by MQInput Node within a message flow. In this case to retrieve a specific message using MQMD message id.

Using a java compute node within the message flow, you could connect to the Queue/Qmgr and get a specific message. Note, the same results cannot be achieved with MQGet Node as MQRC 2019 ensue
http://www.mqseries.net/phpBB2/viewtopic.php?t=33511&highlight=2019

My assumption is that any MQSeries work within the java compute node would operate outside a unit of work and could therefore be lost. Would there be other consequences?

Environment: AIX
Message Broker: V6
MQ V5.3
Message flow: Additional Instances set to 0
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Mon May 21, 2007 3:52 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981
What's wrong with an MQGet node?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
wyatt
PostPosted: Tue May 22, 2007 2:56 am    Post subject: Reply with quote

Voyager

Joined: 28 Nov 2004
Posts: 76
The MQGet Node does not allow you to connect to same queue that is referenced in the input node. The object connection handle is trashed. We opened a PMR with IBM. IBM Support was not interested in fixing this bug ...resolving this problem was not trivial.
Back to top
View user's profile Send private message
andypiper
PostPosted: Tue May 22, 2007 6:48 am    Post subject: Reply with quote

Acolyte

Joined: 29 Oct 2001
Posts: 59
Location: London
Frankly, it scares me that you would want to do a second GET from the same input queue. Why not either send the other message (which you want to retrieve by Msg ID) to another queue and use the MQGet node... or do something entirely different, like maybe use message groups?

It seems like a really bad design to try to go back to the input queue for your flow in order to pick up another message - you won't be able to guarantee order of messages arriving on that queue. There are all kinds of issues with this. It would be a good idea to revisit your design.
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Message Broker - Java Compute Node - Msg Affinity
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.