activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3994) DefaultDatabaseLocker will leak pooled connections on link failure
Date Mon, 10 Sep 2012 17:02:07 GMT

     [ https://issues.apache.org/jira/browse/AMQ-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved AMQ-3994.
------------------------------

    Resolution: Fixed

Thanks for the patch.
                
> DefaultDatabaseLocker will leak pooled connections on link failure
> ------------------------------------------------------------------
>
>                 Key: AMQ-3994
>                 URL: https://issues.apache.org/jira/browse/AMQ-3994
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 5.6.0
>            Reporter: Philip Bridger
>            Assignee: Claus Ibsen
>             Fix For: 5.7.0
>
>         Attachments: DefaultDatabaseLocker.java.patch
>
>
> When the broker has lost the connection to the database through external issues -- link
or database goes down, the process broker will stop().
> When it is shutting down, it calls on each component (service) to stop().
> The DefaultDatabaseLocker when stopping will test the connection to see if it is open
or not before calling close() on the connection. Given that the connection was closed due
to a link failure, the connection is never returned to the pool, hence the leak.
> In this same file there is a comment in start() which warns about being careful about
connection leaks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message