Glas you got it to work. Note that your change is a fix, not a workaround.
Your previous code was incorrect as it (1) violated the Java EE restriction
that you can only have one session per connection (2) leaked sessions. Java
EE 6 specification section EE 6.7 states "Application components in the web
and EJB containers must not attempt to create more than one active (not
closed) Session object per connection. An attempt to use the Connection
object’s createSession method when an active Session object exists for that
connection should be prohibited by the container. The container should throw
a JMSException if the application component violates this restriction."
--
[Message sent by forum member 'nigeldeakin']
View Post: http://forums.java.net/node/898001