You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/12/17 14:17:00 UTC

[jira] [Work logged] (AMQ-9820) Closed connections leaked in the connection pool

     [ https://issues.apache.org/jira/browse/AMQ-9820?focusedWorklogId=996695&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-996695 ]

ASF GitHub Bot logged work on AMQ-9820:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 17/Dec/25 14:16
            Start Date: 17/Dec/25 14:16
    Worklog Time Spent: 10m 
      Work Description: jeanouii opened a new pull request, #1564:
URL: https://github.com/apache/activemq/pull/1564

   Possible bug revealed by PooledConnectionSecurityExceptionTest on faster environments (Github Actions nodes for example). 
   
   The PR fixes the test itself leaking connections during the waitFor condition.
   But it also fixes the connection pool itself because when reconnectOnException is used, commons-pool will close the underlying connection in order to reconnect. I've updated the validateObject() to consider the underlying connection state in order to decide if a connection is valid or not.
   
   I'm not quite sure my hypothesis is correct or not and therefore if the fix is relevant.
   
   ```
   [INFO] Running
     org.apache.activemq.jms.pool.PooledConnectionSecurityExceptionTest
     Error:  Tests run: 8, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.173 s <<< FAILURE! 

Issue Time Tracking
-------------------

            Worklog Id:     (was: 996695)
    Remaining Estimate: 0h
            Time Spent: 10m

> Closed connections leaked in the connection pool
> ------------------------------------------------
>
>                 Key: AMQ-9820
>                 URL: https://issues.apache.org/jira/browse/AMQ-9820
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: ConnectionPool
>            Reporter: Jean-Louis Monteiro
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When using reconnectOnException for the PooledConnectionFactory, it seems that closed connections (on exception) remain in the pool due to wrong validation rules



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact