It seems the problem regarding the JMSSecurityException has been fixed in 3.2.2 RC1. I have thested our application on that release and could not reproduce the misbehaviour, great job guys!
we're having _the exact same_ problems you described. I am glad to hear that 3.2.2RC1 seemed to improve things, but I am a bit concerned about using a RC version -- this would go directly for production. What has been your experience with it so far?
Also, have you experienced any side-effects with 3.2.1? I will try to explain here what is happenning:
sometimes, our application simply starts generating errors to some specific requests that used to work just fine. When we check JBoss log, the errors seem to start piling up after the errors you report below. A side-effect to this is that http://[host]:8080/jmx-console doesn't show _anything_.
Have you (or anybody else) been through anything similar?