Hello,
In my integration I use jms:channel's. For example I have aggregator, which has for both input/output channels jms ones. I can define message-store for aggregator as well. But do I need it ?
I mean, isn't jms:channels are already serve as message stores ?
Or until messageGroup is released (by release-strategy) they are still hold in-memory (then it probably makes sense to use some message-store) ?
Main problem is I always get GC OutOfMemoryError, when aggregator tries to process over 25k of objects (represented by simple class with two string fields). Are there any best practices how to process/store/use of such large amounts of data ?
In my integration I use jms:channel's. For example I have aggregator, which has for both input/output channels jms ones. I can define message-store for aggregator as well. But do I need it ?
I mean, isn't jms:channels are already serve as message stores ?
Or until messageGroup is released (by release-strategy) they are still hold in-memory (then it probably makes sense to use some message-store) ?
Main problem is I always get GC OutOfMemoryError, when aggregator tries to process over 25k of objects (represented by simple class with two string fields). Are there any best practices how to process/store/use of such large amounts of data ?