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 » Output from MQGET node is not read by next compute node

Post new topic  Reply to topic
 Output from MQGET node is not read by next compute node « View previous topic :: View next topic » 
Author Message
Siddu
PostPosted: Mon Dec 03, 2012 1:33 am    Post subject: Output from MQGET node is not read by next compute node Reply with quote

Apprentice

Joined: 22 Aug 2012
Posts: 44

Hi All,

I've a flow which looks like this:
Input - > MQGET -> Compute Node -> Output

I'm able to read a message from Queue using MQGET node and I can see the control being passed to 'Out' from MQGET. However, the control is not entering into compute node.
The node properties under "Result" are:
Output Data Location: OutputRoot.XMLNSC.LastRunTime
Result Data Location: ResultRoot.XMLNSC.PPGEvent.LastSuccessfullRun

Can anyone please guide me on whaere I'm wrong??

Your help is greatly appreciated...
_________________
"Be honest. It is one of the few things that you can control in your life."
Back to top
View user's profile Send private message
McueMart
PostPosted: Mon Dec 03, 2012 2:29 am    Post subject: Reply with quote

Chevalier

Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere

Have you tried debugging your flow? If so, what error are you getting?
Back to top
View user's profile Send private message
Siddu
PostPosted: Mon Dec 03, 2012 3:34 am    Post subject: Reply with quote

Apprentice

Joined: 22 Aug 2012
Posts: 44

McueMart wrote:
Have you tried debugging your flow? If so, what error are you getting?

It's not showing any errors at all.
Once the file has been read from Queue I can see the control being passed to 'Out' terminal, but it's not entering into compute node
_________________
"Be honest. It is one of the few things that you can control in your life."
Back to top
View user's profile Send private message
McueMart
PostPosted: Mon Dec 03, 2012 3:48 am    Post subject: Reply with quote

Chevalier

Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere

What version of Broker? How do you know you are not entering the compute module?

Try placing a trace node after your MQGET node and tracing ${Root} and check that the whole message tree looks like you would expect.
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Mon Dec 03, 2012 5:56 am    Post subject: Re: Output from MQGET node is not read by next compute node Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Siddu wrote:
I've a flow which looks like this:
Input - > MQGET -> Compute Node -> Output
Can anyone please guide me on whaere I'm wrong??


You have no trace nodes in your flow.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
bdrummond
PostPosted: Tue Dec 04, 2012 3:29 am    Post subject: Reply with quote

Disciple

Joined: 06 May 2004
Posts: 164

We have the same issue and are using v 8.0.0.1.
Subflow is receiving the message and the first compute node completes successfully and passes the message to it's 'out' terminal. Then nothing happens.

We have placed a trace node after the compute node but nothing is written to the trace, so it looks like the message never gets there.

If we propagate to a Label node and not a terminal, the Label node accepts the message, passes it to it's own 'out' terminal and then nothing happens.

It appears that the SubFlow is not recognising the connections between nodes.
Very strange.

If anyone has any ideas on what the issue could be, it would be greatly appreciated.
Back to top
View user's profile Send private message
Siddu
PostPosted: Tue Dec 04, 2012 3:31 am    Post subject: Reply with quote

Apprentice

Joined: 22 Aug 2012
Posts: 44

McueMart wrote:
What version of Broker? How do you know you are not entering the compute module?

Try placing a trace node after your MQGET node and tracing ${Root} and check that the whole message tree looks like you would expect.


Hi McMart,
I resolved this issue.
Actually i was trying to access two different DSNs in a single compute node and it was hanging. Now, I included one more seperate compute node and the issue is resolved.

Thanks a lot for your response
_________________
"Be honest. It is one of the few things that you can control in your life."
Back to top
View user's profile Send private message
bdrummond
PostPosted: Tue Dec 04, 2012 3:45 am    Post subject: Reply with quote

Disciple

Joined: 06 May 2004
Posts: 164

Now that your issue is resolved, I will post my question in a new thread.
Back to top
View user's profile Send private message
Siddu
PostPosted: Tue Dec 04, 2012 4:14 am    Post subject: Reply with quote

Apprentice

Joined: 22 Aug 2012
Posts: 44

bdrummond wrote:
Now that your issue is resolved, I will post my question in a new thread.

Hehe
_________________
"Be honest. It is one of the few things that you can control in your life."
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 » Output from MQGET node is not read by next compute node
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.