Given your figures, I agree with your conclusion that it seems there is a memory leak in SEDA flow :( Could you raise a JIRA and attach the configuration you used so that we can reproduce the problem ?
On 10/4/06, Michal <[EMAIL PROTECTED]> wrote:
Hi, I was sending lots of messages to activemq queue via servicemix using sendSync method - there were no cunsumers connected to the queue. After some time I run out of memory. Here are the details: a) servicemix 3.0 M2, activemq (in seperate process), sedaflow - out of memory b) servicemix 3.0 M2, activemq (in seperate process), stflow - out of memory c) servicemix 3.0, activemq (in seperate process), sedaflow - out of memory d) servicemix 3.0, activemq (in seperate process), stflow - NO PROBLEM e) servicemix 3.0, activemq (embedded broker, persistent=true, memorymanagerlimit), sedaflow - out of memory f) servicemix 3.0, activemq (embedded broker, persistent=true, memorymanagerlimit), stflow - NO PROBLEM Conclusion: - there is a memory leak in M2 - indeed, I have seen som bugfix in 3.0 release so I used new version - sedaflow eats up memory - memory leak? Is there really a memory leak in SedaFlow? Or maybe I need to configure it properly? Is StFlow recommended for production? Please advise. Michal -- View this message in context: http://www.nabble.com/SedaFlow---OutOfMemoryError-tf2382645.html#a6640548 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet
