Aggregator returning more than one response

[mataratones]

We have been load-testing our ESB implementation and have noticed that the StreamingAggregator occasionally returns more than one aggregated message.  Sometimes it returns a partial aggregation (say, two messages out of three) followed by a full aggregation, and sometimes it returns the full aggregation twice.  For some reason, this doesn't seem to affect the response that goes to the end user, but it is a cause for concern nonetheless.  If nothing else, it makes our request-response logging cockeyed, because one request gets associated with more than one response.  (A single request is split into multiple threads and then recombined by the aggregator before being returned to the requestor.)

I'm having trouble figuring out how this could be happening or what we can do about it.  Are there any known issues related to the aggregator behaving like this?  Are there any anomalies that could cause this kind of misbehaviour?

Derek

[kconner]

It looks like there may be a small window of opportunity for this to happen.  Which release are you using?  Are you building it yourself?

[mataratones]

We're using 4.11, not building it ourselves.  We do inherit from the StreamingAggregator class, but I don't think that should affect it.

[kconner]

Hiya Derek.

I have been doing some investigation into your problem and think I may be on to something.  I should be able to give you an update over the next day or so.

[mataratones]

I believe the fault was ours, and we seem to have it worked out.  Thanks for your help.

[kconner]

Glad you have managed to sort out your problem.  Your original report did prompt me to investigate that code and I have found an issue with the Smooks FileStreamSplitter which could result in one of the aggregated responses being dropped.  I will create the JIRA shortly.

[kconner]

The Jira is JBESB-3926