The ReleaseCas request is sent to the wrong queue so the CAS pool is soon exhausted and the CM hangs. If the reply queue is local (tcp connected) all is well.
This has been fixed in the latest code which uses temporary queues (and so will be incompatible with the 2.2.2 build)
|Status||Open [ 1 ]||Closed [ 6 ]|
|Resolution||Won't Fix [ 2 ]|
|Fix Version/s||2.3AS [ 12313219 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|41d 2h 27m||1||Marshall Schor||09/Dec/08 21:18|