1 of 1 people found this helpful
I have identified this as an ignorable warning...
that's usually happening when you are closing Sessions in a non-thread-safe manner.
I would really like to have a way to replicate this.. so I can avoid the message.
Hm. Thats interesting. I will have to look to see if we are doing that in our app. Its possible...
Do you know what specifically its caused by? Multiple calls to close the session? Or a different thread to one sending/receiving a message?