I should add that this is only really a problem when deploying MDBs in JBoss AS that are consuming from a *remote* JMS provider (e.g. another JBossAS instance).
For deploying MDBs that consume from a colocated JMS provider (which is the standard deployment scenario) this is not an issue since you would not want load balancing anyway.
There is no seperate connection for (3).
I don't know what you are seeing, but the sessions for delivery must be
under the same connection as the connection consumer.
The use of the DLQ connection (1) is really pretty redundant since it is only
for JMS implementations that don't have DLQs themselves (like JBossMQ).
Evidence is on its way... I am very busy this week, but will get round to it next week :)
Please do. I can't quite understand what you are seeing as the Session created always originates from the original connection.
Is there any progress on this issue ? We are really need clustered factories for MDBs