[
https://issues.apache.org/jira/browse/AMQ-7131?focusedWorklogId=666449&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-666449
]
ASF GitHub Bot logged work on AMQ-7131:
---------------------------------------
Author: ASF GitHub Bot
Created on: 18/Oct/21 18:03
Start Date: 18/Oct/21 18:03
Worklog Time Spent: 10m
Work Description: DrMattFaulkner commented on pull request #477:
URL: https://github.com/apache/activemq/pull/477#issuecomment-946026723
Apologies for digging up an old thread, but i'm a little confused as to how
the connection pooling works within the ActiveMQ pool. If the connection pool
borrowObject timesout we will be stuck in the while loop until there is a free
connect to borrow from the pool no?
i.e.,
`connection = connectionsPool.borrowObject(key);`
Throws a _Timeout waiting for idle object_ then we will never exit
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 666449)
Time Spent: 2h 10m (was: 2h)
> ActiveMQ JMS pool has no borrow timeout causing starvation
> ----------------------------------------------------------
>
> Key: AMQ-7131
> URL: https://issues.apache.org/jira/browse/AMQ-7131
> Project: ActiveMQ
> Issue Type: Bug
> Components: Pool
> Affects Versions: 5.15.8
> Reporter: Benjamin Graf
> Assignee: Benjamin Graf
> Priority: Major
> Fix For: 5.16.0, 5.15.12
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> A maxPoolSize of 1 can cause starvation during createConnection if the only
> connection gets evicted concurrently since borrow method of pool has no
> timeout waiting forever.
> Maybe introduce a new variable connectionTimeout with default 30000ms.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
