• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (2)

1 localhost commented Permalink

This is exactly the opposite of jms 1.1:Due to the authentication and communication setup done when a Connection iscreated, a Connection is a relatively heavyweight JMS object. Most clients willdo all their messaging with a single Connection. Other more advancedapplications may use several Connections. JMS does not architect a reason forusing multiple connections (other than when a client acts as a gatewaybetween two different providers); however, there may be operational reasonsfor doing so.

2 localhost commented Permalink

Does that mean all the effort of JMS session pools is inconsequential now?

Add a Comment Add a Comment