this message in context:
http://activemq.2283324.n4.nabble.com/Fwd-Connection-pooling-for-VM-protocol-tp4680442p4680482.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
the broker maintains some per connection state, connectionId and
clientId to enforce the single clientId in use jms requirement, this
can be an area of thread contention on heavily loaded systems that
open/close many connections.
So even for vm connections (where there is no tcp socket) there will
Hi,
Connection pooling is generally recommended as a good thing. However, is
pooling of VM protocol (vm://) based connections
required/advised/nonsensical when communicating between Camel and a broker
in which it is embedded? Please explain.
>From what I have read the VM protocol bypasses the TCP
