-
Bug
-
Resolution: Done
-
Major
-
1.3.3.0-fuse
-
None
-
None
This seems to lead to lost messages as per Marat's findings:
"[...] because JmsComponent.requestor wasn't synched it was being overriden so if thread 1 created an instance of Requestor and then thread 2 wrote over JmsComponent.requestor value with its own instance the first requestor became unreferenced and was garbage collected at some point taking down the temp queue along with it, so there was nothing to reply to"