[esb-issues] [JBoss JIRA] Commented: (JBESB-746) Potential memory leak in Aggregator

Tom Fennelly (JIRA) jira-events at lists.jboss.org
Tue Nov 13 05:48:44 EST 2007


    [ http://jira.jboss.com/jira/browse/JBESB-746?page=comments#action_12387223 ] 
            
Tom Fennelly commented on JBESB-746:
------------------------------------

Sorry, forgot to mark this as started - writing tests around this, JBESB-1201 and JBESB-1204

> Potential memory leak in Aggregator
> -----------------------------------
>
>                 Key: JBESB-746
>                 URL: http://jira.jboss.com/jira/browse/JBESB-746
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta
>    Affects Versions: 4.2 Milestone Release 3
>            Reporter: Jiri Pechanec
>         Assigned To: Tom Fennelly
>            Priority: Minor
>             Fix For: 4.2.1 CP1
>
>
> There is minor potential memory leak in Aggregator action.
> 1) The message is in timeout
> 2) The process method is started by receiveing one part of timeout message
> 3) Timeout checker checks the same message
> 4) Regular process creates aggregated message and removes the record in notification HashMap
> 5) Timout checker sends a notfificaion message and creates the record in notification HashMap
> 6) Regular process method receives notification message and ignores it as already timed out
> 7) The record remains in notification map
> Recommended solution
> Add  _notified.remove(uuId) call to the branch that handles ignoring already timed out messages.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the esb-issues mailing list