[
https://issues.apache.org/jira/browse/AMQ-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16740128#comment-16740128
]
Benjamin Graf commented on AMQ-7131:
------------------------------------
Hi [~tabish121],
actually I only get this tested by manually debugging both threads causing the
"collision" in the small open window. For me the patch with the
connectionTimeout work good. Camel/Spring-jms for example immediately tries to
reconnect after exception. I think most consuming frameworks will act like
that. In this way a connection get created, too. :)
By the way it seems extremely rare to occur, but it does.
Benjamin
> 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)
