| Author |
Message
|
| mlafleur |
 Posted: Mon Sep 25, 2006 2:11 pm Post subject: BIP4424 |
 |
|
Acolyte
Joined: 19 Feb 2004
Posts: 73
|
We are using version 5 fix pack 8 and recently switched to using queues to store the state for aggregation nodes. We are receiving the following error:
BIP4424E: Unable to retrieve control message in AggregateReply node. Queue='SYSTEM.BROKER.AGGR.TIMEOUT', Reason Code='2026'.
I have looked up mqrc 2026 and it states that,
The MQMD structure is not valid, for one of the following reasons:
* The StrucId field is not MQMD_STRUC_ID.
* The Version field specifies a value that is not valid or not supported.
* The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)
* The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the pointer points to read-only storage.
Anybody have any ideas on what is happening here? |
|
| Back to top |
|
 |
| vk |
| Posted: Mon Sep 25, 2006 2:38 pm Post subject: |
|
|
Partisan
Joined: 20 Sep 2005
Posts: 302
Location: Houston
|
Did you add an MQMD header to the control message before sending it to the aggregation control queue?
Regards,
VK. |
|
| Back to top |
|
|
| mlafleur |
| Posted: Mon Sep 25, 2006 3:06 pm Post subject: |
|
|
Acolyte
Joined: 19 Feb 2004
Posts: 73
|
| Quote: |
To use WebSphere MQ to store state in aggregation nodes, perform the following steps:
1. Migrate an existing broker or create a new broker.
2. Configure the broker environment to use WebSphere MQ for aggregation nodes.
When you have performed these steps, aggregation will function as it did before, but you might notice the following differences:
* Aggregation is much faster.
* Error messages reflect the use of WebSphere MQ instead of a database table.
* No control messages are sent between the request flow and the reply flow. If required, you can force a control message to be sent. It is no longer necessary to connect the AggregationControl node control terminal to the AggregationReply node control terminal.
|
|
|
| Back to top |
|
|
| wschutz |
| Posted: Mon Sep 25, 2006 4:41 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
| We are using version 5 fix pack 8 and recently switched to using queues to store the state for aggregation nodes. |
What, exactly, did you do?
_________________
-wayne |
|
| Back to top |
|
|
| mlafleur |
| Posted: Tue Sep 26, 2006 6:50 am Post subject: |
|
|
Acolyte
Joined: 19 Feb 2004
Posts: 73
|
Set the MQSI_AGGR_MQ environment variable.
The log does now say for each execution group, "BIP4430I: The execution group 'ABC' running on broker 'DEF' has been configured to use MQSeries to store state for the aggregation nodes." |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Sep 26, 2006 8:49 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Doesn't seem to be much that could go wrong .... I suggest opening a PMR.....
_________________
-wayne |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Sep 26, 2006 9:10 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
|
| Back to top |
|
|
| Pegazus |
| Posted: Wed Mar 07, 2007 7:14 am Post subject: BIP4424E |
|
|
Novice
Joined: 10 Aug 2006
Posts: 16
|
Hi All
I am getting the same error. WBI MB 5.1 Fix Pack 8.
BIP4424E: Unable to retrieve control message in AggregateReply node. Queue='SYSTEM.BROKER.AGGR.TIMEOUT', Reason Code='2019'.
Did you get a solution / Did you open a PMR with IBM.
Thanks |
|
| Back to top |
|
|
| dsriksha |
| Posted: Wed Mar 07, 2007 7:24 am Post subject: Re: BIP4424E |
|
|
Voyager
Joined: 27 Feb 2005
Posts: 95
|
| Pegazus wrote: |
Hi All
IBIP4424E: Unable to retrieve control message in AggregateReply node. Queue='SYSTEM.BROKER.AGGR.TIMEOUT', Reason Code='2019'.
Thanks |
You have a different reason code than what Mlafleur had. Hence, try searching on your reason code  |
|
| Back to top |
|
|
|
|
