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 » Aggregator Node Timeout

Post new topic  Reply to topic
 Aggregator Node Timeout « View previous topic :: View next topic » 
Author Message
Gopal
PostPosted: Wed Jan 22, 2003 10:06 pm    Post subject: Aggregator Node Timeout Reply with quote

Novice

Joined: 22 Jan 2003
Posts: 19
Location: Bangalore

I'm using Aggregator Node and setting the time out in control node to 30 secs. When I deploy the Message Flows both request and response I see that after every 30 secs aggregator reply times out even without any message being put in the request queues. Is this how the Aggregator Node behaves or there is some way to control this? I want my message flow to start after a message is first put in the request fanout queue.
Back to top
View user's profile Send private message
lillo
PostPosted: Wed Jan 22, 2003 11:22 pm    Post subject: Reply with quote

Master

Joined: 11 Sep 2001
Posts: 224

That is not the way is supposed to work. I´ve been using the aggregator nodes for a long time and I never got that problem.

Make sure you don´t have any input queue associated with any output node in other message flows.

Cheers,
_________________
Lillo
IBM Certified Specialist - WebSphere MQ
Back to top
View user's profile Send private message
Gopal
PostPosted: Thu Jan 23, 2003 1:07 am    Post subject: Re: Aggregator Node Timeout Reply with quote

Novice

Joined: 22 Jan 2003
Posts: 19
Location: Bangalore

[quote="Gopal"] I didnt understand Lilio when u said that make sure u dont have any input queue associated with any output modes in other message flows. In fact the queues that I'm using for my message flow are being used only in this message flow. These queues are not being used by anyone.
Following is my message flow
Request Flow Q1
QIN--AggrContrl--Q2
CtrlQ

ResponseFlow
CtrlQ-|
RepQ--AggrReply-out----------QOUT
-timeout--processing-TimeOutQ

I have set Timeout in aggrcontrol as 30 secs. When I Deploy these 2 in my execution grp for every 30 secs I see AggrReply timing out without even any message being put in QIN.
Try this same code. Put some sample XML data and you should be able to reproduce the problem.
Back to top
View user's profile Send private message
lillo
PostPosted: Thu Jan 23, 2003 2:47 am    Post subject: Reply with quote

Master

Joined: 11 Sep 2001
Posts: 224


    Can you give me the details for the queues (Q1, QIN, Q2, CtrlQ, RepQ, QOUT and TimeOutQ) ?
    What are you doing with the request messages?
    Where is your Aggregate Request node?

_________________
Lillo
IBM Certified Specialist - WebSphere MQ
Back to top
View user's profile Send private message
Gopal
PostPosted: Thu Jan 23, 2003 4:08 am    Post subject: Reply with quote

Novice

Joined: 22 Jan 2003
Posts: 19
Location: Bangalore

Request Flow
Q1---aggrReqQ1
QIN--AggrContrl--Q2---aggrReqQ2
CtrlQ

For Q1 and Q2 reply queue is sent RepQ.

ResponseFlow
CtrlQ-|
RepQ--AggrReply-out----------QOUT
-timeout--processing-TimeOutQ.

I have followed the same procedure as given WMQI Documentation Chapter 6 Aggregator Nodes.

Request Messages I'm sending to different host system queues which will reply back in RepQ. I aggregate this reply and put in QOUT and on time out put in TimeOutQ.

Q1, Q2 - Request Queues
CtrlQ - Control Queue
RepQ - Reply Queue which gets the responses from the Q1, Q2.
TimeOutQ - is timeout queue for aggrReply timeout terminal
QOUT - is output queue for aggrReply out terminal

What is surprising here is the after a specific time interval set in the aggrCtrl node aggrReply starts timing out periodically after specified time in aggrCtrl node. I wanted to make sure that this behaviour is actual behaviour of AggrNode. Or it is something strange and can be controlled?
Back to top
View user's profile Send private message
lillo
PostPosted: Thu Jan 23, 2003 4:24 am    Post subject: Reply with quote

Master

Joined: 11 Sep 2001
Posts: 224

I´m sure that this is not the correct way to work for the aggregator nodes.

You could also take a look to the redbook "Developing solutions in WebSphere MQ Integrator" where you could find a chapter covering the aggregator nodes.

Cheers,
_________________
Lillo
IBM Certified Specialist - WebSphere MQ
Back to top
View user's profile Send private message
Gopal
PostPosted: Fri Jan 24, 2003 12:35 am    Post subject: Reply with quote

Novice

Joined: 22 Jan 2003
Posts: 19
Location: Bangalore

I have found the solution to this. Basically the problem was the previously deployed message flow used to run and that was causing the problem.
Anyway thanks for your suggestions and making me to find out the solution.
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 » Aggregator Node Timeout
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.