The warning has not been removed in HornetQ 2.4. I'm not familiar with any bugs related to the detection of concurrent session usage (although that's not to say there aren't any).
At this point I would say if you are getting this message then you are using your sessions concurrently. Have you investigated this possibility?
We did that to warn users when they are using the session wrongly.
If you find an use case where you are using it correctly, then we may need to tweak the warning check and we would need a testcase. Otherwise you have an issue on your code.
I believe there was a case where the warning check was being too aggressive which was fixed... I don't remember now.
But if you are still using the session wrongly you would get the warning. But the bug identifying the correct pattern wrongly was fixed. (I don't remember what was the case now.. maybe MessageListeners?)
How about if I'm only using HornetQ embedded, for inter thread processing? Would the WARN apply for that case? Or is it only for remote HornetQ interaction (due to socket writes, etc).
both really. The session is supposed to reflect a single Thread...
you can reuse it between multiple threads.. as long as you won't use concurrently.