genman,
to answer your question, context is visible to the container, otherwise it
won't be able to roll it back if needed to. no? the 'multiple threads' are
container and the mdb thread itself so there are 2 threads.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewt
Yes you are right that each thread has its own MDB instance and each of them
has their own context, but because the container have the access to the context
too, and roll it back in certain cases , that makes it hard to control it
unless I synchronize it.
For example, the following happened chr
Sorry forgot to mention that I'm using:
- JBoss 3.2.8SP1
- Hibernate 3.0
- JBossMQ Queue, async processing with MDB (onMessage())
Thanks!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966845#3966845
Reply to the post :
http://www.jboss.com/index.html?modul
I have an issue of JBoss terminating (rolling back) the context of the message
driven bean when large amount of MDB instances are actively processing the
message and gives me the following exceptions:
Caused by: org.hibernate.TransactionException: could not register
synchronization with JTA Tra
