This content has been marked as final. Show 2 replies
i looked at the aggregator example. it seems that this action
only can aggregate messages where the number of expected messages is known in advance.
The aggregator actions looks like it assumes that one of the routers (ContentBasedRouter or StaticRouter) did the splitting before?
is this assumption correct? is the aggregator also intended to be used without a router?
what happens if the aggregating service is shutdown/crashes after it has received some of the messages? does the aggregator provide any persistence support?
is the aggregator cluster aware?
You'll find the answer to your last question here :
5.5. Aggregator and other stateful actions are not supported in a clustered environment
As mentioned throughout the Programmers Guide, high-availability services within JBossESB are currently only supported if they are stateless. The Aggregator action is a stateful instance, which necessarily means that if it is used within the Action Pipeline/Chain of a service, that service is no longer stateless and therefore cannot be used in a high-availability manner.