Are you hitting a Stateful Session Bean or a Stateless one? According
to the EBJ spec, it is illegal to hit a transactional Stateful one from
two threads simultaneously that have the same bean handle.
David
--
Beau Cronin escribió::
I have a Swing app which is essentially single-threaded,
Beau Cronin wrote:
I have a Swing app which is essentially single-threaded, accessing the
server in the usual way through a session facade. I'd like to do some
background loading of certain data for performance reasons, but when I
try to do this by using a separate thread (and separate
These deadlocks are most likely on your entity beans (the second one is
fishy looking, but I really can't say much without seeing more (all) of
the stack trace.). By default, JBoss only keeps one instance per bean
identity, so each transaction from your client will block on the entity.
Give
