well about logs it should jus tbe configured but will not prevent tx to be handled ;)
@Async is great and you can handle after return part usnig AsyncResult. *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/3/23 Howard W. Smith, Jr. <[email protected]> > I have experienced the same in my tomee logs that almos is reporting here, > since I am using 'simple MDB' approach via Tomee/ActiveMQ. Actually, I am > quite please and all of that 'stuff' in the log files is not much of a > concern to me. > > @Asynchronous doesn't meet my requirements, or maybe I just did not know > how to handle @Asynchronous after it completes the tasks. It seems to end > up in some piece of my code, and some old piece of code seems to want to be > executed after @Asynchronous returns. > > With that said, TomEE/ActiveMQ meets my requirements, but Romain, can you > please explain your response below to almos's question? Do you have an > example on how to use, so the log line will not be filled up with all those > lines related to ActiveMQ, Geronimo, etc...? > > "@TransactionAttribute or @TransactionManagement are here for that" > > > > On Sat, Mar 23, 2013 at 4:21 PM, Romain Manni-Bucau > <[email protected]>wrote: > > > @TransactionAttribute or @TransactionManagement are here for that > > > > depending on the bus type you want using @Asynchronous + a queue can be > > more efficient > > > > *Romain Manni-Bucau* > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > *Blog: **http://rmannibucau.wordpress.com/*< > > http://rmannibucau.wordpress.com/> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > *Github: https://github.com/rmannibucau* > > > > > > > > 2013/3/23 almos <[email protected]> > > > > > Hi, > > > > > > When JMS message goes to the MDB deployed in TomEE there are a lot of > log > > > entries like these: > > > > > > INFO: Removing non-required WorkContextHandler with no context: > > > org.apache.geronimo.connector.work.TransactionContextHandler@19647f24 > > > Mar 23, 2013 2:25:21 PM > org.apache.geronimo.connector.work.WorkerContext > > > run > > > INFO: Removing non-required WorkContextHandler with no context: > > > org.apache.openejb.core.security.SecurityContextHandler@14d72182 > > > Mar 23, 2013 2:25:21 PM > org.apache.geronimo.connector.work.WorkerContext > > > run > > > INFO: Removing non-required WorkContextHandler with no context: > > > org.apache.geronimo.connector.work.HintsContextHandler@37d8e87e > > > Mar 23, 2013 2:25:21 PM > org.apache.geronimo.connector.work.WorkerContext > > > run > > > > > > So there's a lot of things going behind the scenes according to EE > specs. > > > For one of the tasks I need to implement I would like to reduce > overhead > > of > > > MDB processing and somehow switch off transaction support and other > > > handlers/interceptors on MDBs in case of using embedded ActiveMQ with > > vm:// > > > type of transport. > > > Which broker/TomEE configuration options/MDB annotations you may > > recommend > > > to reduce processing overhead as much as possible? > > > Is it even somehow possible or I should just use some lightweight event > > bus > > > alternatives like Akka or whatever else similar? > > > > > > Regards, > > > Alex > > > > > > > > > > > > -- > > > View this message in context: > > > > > > http://openejb.979440.n4.nabble.com/Question-on-MDB-processing-tp4661685.html > > > Sent from the OpenEJB User mailing list archive at Nabble.com. > > > > > >
