Created attachment 339448 [details]
test case

Description of problem:

If you use a session with an application specified name, then on failover to another cluster node try to open a new session with the same name, you get a SessionBusyException. 

Even retrying after a short wait seems not to avoid this.

How reproducible:

100%

Steps to Reproduce:
1. start cluster with more than one node
2. have client that creates a session with a given name (and 0 timeout, which is default) and e.g. waits for a message 
3. kill the node the client is connected to
4. have client failover to other node and create a new session with the same name as that used previously (which should have been destroyed)

The attached case provides such a client. You should be able to run that against  a cluster (with a queue called test-queue created), then kill the node connected to.
  
Actual results:

Get a SessionBusyException as often as you try.

Expected results:

New session created with same name as that used previously, which should now have been destroyed.

Additional info:

If the session declares an exclusive (but not auto-deleted) queue, then it appears that lock on that queue is released as would be expected. However the name of the session is still marked as busy.