Announcement Announcement Module
No announcement yet.
Memory leak in SimpleMessageStore?? Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Memory leak in SimpleMessageStore??

    I have a very high volume (400k transactions / day) Socket Server with a complex Integration Flow involving a main synchronous path for the request and an asynchronous path for logging, stats and monitoring.

    In both of these path, I'm using a total of 3 aggregators with SimpleMessageStore (therefore volatile memory). As a precaution, to prevent memory leak I also have a MessageGroupStoreReaper per MessageStore to empty everything if something would get caught.

    Here is the catch, in class SimpleMessageStore,

    ConcurrentMap<Object, Object> locks never seems to be removed at any point, therefore locks are eternal... and leaking!!

    Shouldn't the lock be remove at the same time as the SimpleMessageGroup?
    Are they required for anything?
    Late arriving message? I'd thing No.

    What do you think?
    Thanks for your guidance ;-)

  • #2
    Yes, please open a JIRA issue here