| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Aggregator Plugin |
« View previous topic :: View next topic » |
| Author |
Message
|
| NickB |
 Posted: Mon Jun 04, 2001 1:07 am Post subject: |
 |
|
Centurion
Joined: 20 May 2001
Posts: 107
Location: Zurich Financial Services
|
I've just downloaded the aggregator plug in and I'm having great difficulty trying to deploy a message flow containing the aggregator nodes. The deploy fails saying that the execution group did not respond in a timely manner.
I'm also surprised that the installation instructions do not contain anything about creating a database which I believe is required in order to persist the aggregation control information.
Has anybody got this working on AIX at all? |
|
| Back to top |
|
 |
| kolban |
| Posted: Mon Jun 04, 2001 8:13 am Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
The Aggregator does not need any database access. I have used this node package myself with great success. Suggest that you shut down the broker, control center and config manager and try again from a clean start. I have seen some unspecified problems if, after adding plugin nodes, all the components haven't been recycled.
Neil |
|
| Back to top |
|
|
| cfarkas |
| Posted: Mon Jun 25, 2001 4:20 pm Post subject: |
|
|
Novice
Joined: 24 Jun 2001
Posts: 13
Location: France
|
Has anyone been using this SupportPak (v1.1) with MQSI v2.02 on NT? I've run into a few problems on this version, although the package looks very nicely done.
A/ I get 2623/2604 msgs in the NT event log at broker startup with text "Unable to open queue 'SYSTEM.BROKER.TIMER.QUEUE' on MQSeries queue manager 'QM_Local': completion code 2; reason code 2085". I seem to have been able to get rid of this by manually creating the Q. The doc indicates no more reliance on this queue, but I think there's still a problem.
B/ After Adding the 3 nodes to my workspace, I'm not allowed to Check in these nodes, so they always disappear from my workspace.
|
|
| Back to top |
|
|
| Yongdeuk |
| Posted: Tue Jun 26, 2001 6:54 am Post subject: |
|
|
Newbie
Joined: 25 Jun 2001
Posts: 2
Location: IBM Korea
|
It was successful under Windows NT environment but I encountered the same problem as the NickB's. I am trying to contact IBM Austrailia lab (who announced ia72 aggregator) and will post something if I receive anything from Austrailia.
I think the document in ia72 is not that detailed.. |
|
| Back to top |
|
|
| Mike Brady |
| Posted: Thu Jul 05, 2001 7:28 pm Post subject: |
|
|
Newbie
Joined: 04 Jul 2001
Posts: 8
|
| The aggregator plug-in node has undergone a number of revisions since its initial publication. Most changes involved introducing new function, but there have also been some bug-fixes and general improvements along the way. In the initial offering, timer messages were sent to a special queue SYSTEM.BROKER.TIMER.QUEUE however, it then became apparent that this was not such a good idea when multiple aggregates were deployed on the same broker. More recently, the design was changed so that timer messages are sent to the ReplyQueue specified in the SpAggregateReply configuration. This means that the SYSTEM.BROKER.TIMER.QUEUE is now NOT used. Any references you may see to this queue (in event log, syslog, etc.) indicate that you are still running old code. Yes, I'm aware that there is still a reference to the queue in the code, but its only a #define and is never used. The latest version about to be published will also remove this! |
|
| 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
|
|
|
|
