[
https://issues.apache.org/jira/browse/AMQ-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-4964.
-----------------------------
Resolution: Won't Fix
@Tim - thanks for peeking at this. Yep, it is a crazy use case and we would
need to cache some stuff in the connection factory which would be like a poor
man's pool to make it more efficient.
Pooling is the answer.
> org.apache.activemq.bugs.ConnectionPerMessageTest is very slow - seems to
> point to lock contention on close
> -----------------------------------------------------------------------------------------------------------
>
> Key: AMQ-4964
> URL: https://issues.apache.org/jira/browse/AMQ-4964
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker, JMS client, Transport
> Affects Versions: 5.9.0
> Reporter: Gary Tully
> Priority: Minor
>
> This needs some investigation to see if there is something we can do to speed
> up this simple test that does not reuse a connection.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
