Session is single-threaded. If you don't have many connections and they are relatively long-lived, there's no big problem in having multiple connections from a single process.
Note from the JMS 1.1 standard section 4.3 "Connection" (my bolding): "Due to the authentication and communication setup done when a Connection is created, *a Connection is a relatively heavyweight JMS object. Most clients will do all their messaging with a single Connection.* Other more advanced applications may use several Connections. JMS does not architect a reason for using multiple connections (other than when a client acts as a gateway between two different providers); however, there may be operational reasons for doing so." The "ActiveMQ in Action" book has some notes on tuning for performance in chapter 13, in particular you might be interested in section 13.2 "Optimizing message producers." ----- Michael Hayes B.Sc. (NUI), M.Sc. (DCU), SCSA SCNA -- View this message in context: http://activemq.2283324.n4.nabble.com/Producer-Performance-tp4653244p4653280.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
