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 » mqget message is not coming to "no messsage" Term

Post new topic  Reply to topic
 mqget message is not coming to "no messsage" Term « View previous topic :: View next topic » 
Author Message
brk123
PostPosted: Thu Nov 03, 2011 7:15 pm    Post subject: mqget message is not coming to "no messsage" Term Reply with quote

Novice

Joined: 24 Oct 2011
Posts: 11

mqget node:
message is not coming to "no messsage" Terminal when there is already a dfferent message in the queue.I am getting the message by correlation id

Appreciate your help.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Nov 03, 2011 7:17 pm    Post subject: Re: mqget message is not coming to "no messsage" Reply with quote

Grand High Poobah

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

brk123 wrote:
mqget node:
message is not coming to "no messsage" Terminal when there is already a dfferent message in the queue.I am getting the message by correlation id

Appreciate your help.

Be more verbal and distinctive, not enough information to go on...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
brk123
PostPosted: Thu Nov 03, 2011 7:29 pm    Post subject: Reply with quote

Novice

Joined: 24 Oct 2011
Posts: 11

Hi fjb_saper

flow1
httpinput->compute1->mqout1(queue1.in)->mqget((queue2.out) -> compute2-> httpreply

flow2
mqinput(queue1.in)->compute3->mqout2(queue2.out)


If mqget((queue2.out) doesnt get a message in 4 second It should navigate to "No Message " terminal.

Here I have already a failed message in "queue2.out". I am processing a new message . since the new message is not proceesed in 4 second it should go to "No Message " terminal. since already a message is there its never going to No message terminal.

Please help
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Nov 03, 2011 7:34 pm    Post subject: Reply with quote

Grand High Poobah

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

How did you configure the MQGet for the location of the CorrelId?
Did you check that the expected correlId is in the location specified by the MQGet node?
Did you check that the message being picked up has the right correlation Id ?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
brk123
PostPosted: Thu Nov 03, 2011 8:09 pm    Post subject: Reply with quote

Novice

Joined: 24 Oct 2011
Posts: 11

Quote:

flow1
httpinput->compute1->mqout1(queue1.in)->mqget((queue2.out) -> compute2-> httpreply

flow2
mqinput(queue1.in)->compute3->mqout2(queue2.out)


Quote:
How did you configure the MQGet for the location of the CorrelId?

mqout1 -New correlatetion Id selected
mqget-get by correlation id selected
use complete input mqmd selected.

Can you let me know if I need any other setting to match correlatetion Id
Back to top
View user's profile Send private message
smdavies99
PostPosted: Thu Nov 03, 2011 10:47 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

How are you matching the CorrelId's been the two flows?
What is the timeout on the MQGET Node?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Nov 04, 2011 6:27 am    Post subject: Reply with quote

Grand High Poobah

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

Between the MQout and the MQGet you need a compute node to populate correctly the MQMD with the correlId generated on the MQOutput from the LocalEnvironment...

Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
brk123
PostPosted: Fri Nov 04, 2011 10:18 am    Post subject: Reply with quote

Novice

Joined: 24 Oct 2011
Posts: 11

I have added a compute node and set correld
Quote:
SET OutputRoot.MQMD.CorrelId = InputLocalEnvironment.WrittenDestination.MQ.DestinationData.CorrelId;


i found that correlid is differnt for incoming message (LocalEnvironment.WrittenDestination.MQ.DestinationData.CorrelId) and message in the queue.

but still message is not coming to mqget "no messsage" Terminal when there is already a dfferent message in the queue(queue2.out).

i set mqget timeout is 20 millisecond.inorder to make sure that flow shhould always come to the no message( for testing purpose.)
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Nov 04, 2011 11:41 am    Post subject: Reply with quote

Grand High Poobah

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

what did you wire your "No Message" terminal to?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
brk123
PostPosted: Fri Nov 04, 2011 12:30 pm    Post subject: Reply with quote

Novice

Joined: 24 Oct 2011
Posts: 11

mqget --> No message --> 'No msg ' compute node
mqget -->Out--> output terminal.

Thanks for your help.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Nov 04, 2011 1:02 pm    Post subject: Reply with quote

Grand High Poobah

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

You might want to work it as a PMR
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
brk123
PostPosted: Fri Nov 04, 2011 1:51 pm    Post subject: Reply with quote

Novice

Joined: 24 Oct 2011
Posts: 11

Is there any work around please ?
Back to top
View user's profile Send private message
smdavies99
PostPosted: Sat Nov 05, 2011 6:08 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Have you considered that the application you are sending the message to is not handling the preservation of the CorrelId correctly?

Why not build a test flow that models your application. Then you can prove your logic and then point the finger at the other application.

You can test the other application using RFHUTIL. Why don't you do that first. If you raise a PMR then IBM will as you to verify that the remote app is working properly and using the send CorrelID in the reply message.

Think laterally. Think of other ways to prove the operation of the different bits.
This is really SOP for anyone involved in Systems Integration. Well, it is for me and I've been doing SI for more than 30 years.
Message broker is a key application in SI. It is the key component that links a lot of others together. However if these other components send you a load of cow dung instead of 'neeps' then there is no way that Broker can turn said dung into Pig Food.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
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 » WebSphere Message Broker (ACE) Support » mqget message is not coming to "no messsage" Term
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.