sending messages one way

[ataylor]

When we send a message that is non durable but in a transaction we send it one way rather than blocking. If the sending of this message fails, say due to a security exception or other problem, the client is not notified. The session is then committed and the client thinks that the messages have been delivered.

Do we need to always send blocking (and take the hit) or should we fail on session.commit(). This would mean holding exceptions on the server until this happens! any thoughts?

[timfox]

Yeah, this is why the security tests are failing.

I think what we need to do is throw the security exception on commit (we can flag the tx as "tofail" as sends arrive and just check the flag on commit.

Sending blocking for each send would be too slow.

[ataylor]

ok sounds good, I'll get that done.