A single connection usually represents a single
thread sending/receiving over the network.
This may become a bottle neck?
Holding sessions open isn't really a problem,
except that they use some resources on the server.
On the server, you can use the connection manager
"java:/JmsXA" that pools sessions.
Closing the connection, closes all session which
closes all receivers/subscribers/etc.
I have a multi-threaded application where each thread has its own sessions but they all share one connection. Lots of traffic flows in and out of each thread. Do you advocate maintaining a connection per thread as opposed to threads sharing a connection?
The documentation suggests that it is best to use the RMI IL if one has multiple threads sharing a connection. Is this still the case? If I use a connection per thread, can I then use a different IL? I'm currently using OIL (inappropriately??) but I'd like to move to UIL2.
Is UIL2 still experimental?