| Author |
Message
|
| Dev80 |
 Posted: Tue Dec 22, 2015 11:35 pm Post subject: Why does Aggregation control behave oddly in Linux. |
 |
|
Novice
Joined: 28 Nov 2013
Posts: 10
|
Hi,
I am facing a typical issue on Linux environment with aggregation nodes. my flow is a asynchronous message flow it receives XML domain message on a MQ input and from there there is a aggregation request node to send the message to three MQ output. after the processing is complete I receive combined response over a WMQ and create a message on XMLNSC domain and send it to requester over MQ. these two flows works perfectly on my windows system. and I get reply every time correctly. however the same flow if deployed on linux environment behaves very oddly. The first request seems to work and I get a combined response. But afterwards any subsequent request the aggregation response node is not able to combine the responses. I notice that the messages are going to SYSTEM.BROKER.AGGR.UNKNOWN . Just for information before performing testing on Linux environment we have set
Edit the profile of the broker userid and include the following code:
export MQSI_AGGR_COMPAT_MODE=
Reload the profile.
Restart the broker.
from the user if that has started the Integration Node. This user profile is not the same profile that has installed IIB10 on the Linux environment. Can you please let me know what I am missing at the moment.. We even tried these tests with MQSI_AGGR_COMPAT_MODE=ON.
Current memory in Linux Dev environment is as below. It is running one single Integration Node and one single execution group default.
free -m
total used free shared buffers cached
Mem: 3833 2586 1246 44 154 683
-/+ buffers/cache: 1748 2084
Swap: 2015 25 1990
We have also observed that in some cases aggregation request node is not able to send requests in parallel. It sends two requests and then gets one reply back then it sends remaining one request finally receives two replies but only able to correlate last reply and in some cases none. I can not enable trace in linux environment as it is restricted for us.
Regards
Soumitra |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Dec 22, 2015 11:42 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
What is the transactionality set to on the MQ Output nodes? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Dev80 |
| Posted: Tue Dec 22, 2015 11:54 pm Post subject: Why does Aggregation control behave oddly in Linux. |
|
|
Novice
Joined: 28 Nov 2013
Posts: 10
|
| fjb_saper wrote: |
| What is the transactionality set to on the MQ Output nodes? |
Hi,
Thanks for swift response from your end. transaction mode of the 3 MQ Output nodes are set to "No" and also persistence as "No". |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Dec 23, 2015 12:19 am Post subject: Re: Why does Aggregation control behave oddly in Linux. |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Dev80 wrote: |
| fjb_saper wrote: |
| What is the transactionality set to on the MQ Output nodes? |
Hi,
Thanks for swift response from your end. transaction mode of the 3 MQ Output nodes are set to "No" and also persistence as "No". |
So how does the behavior change when you set the transaction to yes on the MQ Output nodes?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Dev80 |
| Posted: Wed Dec 23, 2015 12:20 am Post subject: Re: Why does Aggregation control behave oddly in Linux. |
|
|
Novice
Joined: 28 Nov 2013
Posts: 10
|
| Dev80 wrote: |
| fjb_saper wrote: |
| What is the transactionality set to on the MQ Output nodes? |
Hi,
Thanks for swift response from your end. transaction mode of the 3 MQ Output nodes are set to "No" and also persistence as "No". |
Hi,
I just set it as autometic transaction mode. and it started working like windows..
You are just awesome sir you spotted it in first. |
|
| Back to top |
|
|
|
|
