[
https://issues.apache.org/jira/browse/AMQ-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739808#comment-16739808
]
Timothy Bish commented on AMQ-7131:
-----------------------------------
Blocking and throwing an error seems like the wrong thing to do, if the
connection timed out it should be replaced by a new one. Perhaps not blocking
and handling the NoSuchElementException to replenish the pool entry would be a
better idea.
Do you have a test for this?
> 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: activemq-pool
> Affects Versions: 5.15.8
> Reporter: Benjamin Graf
> Assignee: Benjamin Graf
> Priority: Major
>
> 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
(v7.6.3#76005)
