New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory (almost) leak issue #28

Open
uguy opened this Issue Apr 26, 2013 · 1 comment

Comments

Projects
None yet
2 participants
@uguy

uguy commented Apr 26, 2013

After upgrading from version 1.0 to 1.4, I saw that my app was going from 100mo heap to more than 1Go ! (and crashing because the limit I set was xmx 1024). The version upgrade was really the only change in my app.

I found out that the AcknowledgeMode.NONE was the root cause of the heap size grow.
I tracked down the issue and found it was introduced in version 1.2.
=>The ack mode was changed from AUTO to NONE.

It sounds like a spring-rabbit or spring-amqp issue but it impact a lot the camel-spring-amqp component. Maybe it would be safer to change the default ack mode to AUTO while the bug is not fixed on spring side.

If you want to reproduce, just checkout the 1.1.0 tag and change the ack mode from AUTO to NONE, then look at the heap size growing in visualvm when sending a million message.

Regards.
The pull request #25 provides a workaround.

@deckerego

This comment has been minimized.

Show comment
Hide comment
@deckerego

deckerego Feb 16, 2014

Member

You are correct - and while pull request #25 was merged in, we should still change AcknowledgeMode.AUTO to be the default. I'm keeping this issue open until we do so.

Member

deckerego commented Feb 16, 2014

You are correct - and while pull request #25 was merged in, we should still change AcknowledgeMode.AUTO to be the default. I'm keeping this issue open until we do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment