The problem only occurs when transaction are started in the same thread as
the @Startup bean. We solved it by starting a new thread, from within the
startup bean. This new thread performs all transation related work. Tommy
--
[Message sent by forum member 'T.Bergkvist']
View Post: http://forums.java.net/node/894269