|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Please help !!!!! Problem with aggregate |
« View previous topic :: View next topic » |
Author |
Message
|
genestep |
Posted: Mon Jun 03, 2002 9:30 pm Post subject: Please help !!!!! Problem with aggregate |
|
|
Apprentice
Joined: 16 Apr 2002 Posts: 43 Location: France
|
Hi
I use an "aggregate reply" node (WMQI 2.1) to aggregate some reponses. In out flow, if i have an exception, the aggregate never finishes. I always have message in timeout and catch terminals. The problem, i think, comes from the database, because i always have lines in baggregate table. if i delete manually records, the problem is stopped.
At what time the the records are deleted ??
Is it a bug in aggregate node ??
Thanks for your help.
Philippe |
|
Back to top |
|
 |
devans |
Posted: Wed Jun 05, 2002 4:09 am Post subject: |
|
|
Apprentice
Joined: 18 Mar 2002 Posts: 43
|
The database records relating to an aggregation are deleted by the AggregateReply node after sending out the aggregated reply message.
The fan-out and fan-in flows should be executed within a transaction, so that in an error case (i.e. an exception is thrown) the whole unit of work is backed out and the aggregation is left in a consistent state.
I would recommend that you should firstly find out why an exception is being thrown (look in your event log) and correct that. There should be some useful log information to help you Also, make sure that the input nodes and output nodes have the correct transactionality setting (set to 'Yes') |
|
Back to top |
|
 |
genestep |
Posted: Wed Jun 05, 2002 10:01 am Post subject: |
|
|
Apprentice
Joined: 16 Apr 2002 Posts: 43 Location: France
|
Thanks for informations.
But how in the message i can find info about transactional mode ?
In my message flow i define transactional mode but perhaps the problem is with MQ client developement which posts the message. |
|
Back to top |
|
 |
devans |
Posted: Thu Jun 06, 2002 6:49 am Post subject: |
|
|
Apprentice
Joined: 18 Mar 2002 Posts: 43
|
The transactionality of the MQ Client which does the original MQPUT is not relevant. It is only relevant how WMQI does the MQGET, and that is determined by your transactionality settings on the MQInput and MQOutput nodes. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|