If I change JBoss to use a non-xa connection-factory and remove the xa-transaction tag in the config, and change spring from jtatransactionmanager to JmsTransactionManager, everything works just fine... :-P
So this has nothing todo with camel or anything related to that, I guess. It's time to use that support contract from tibco... ;) Thanks. /Magnus On Feb 7, 2008 8:40 PM, Magnus Heino <[EMAIL PROTECTED]> wrote: > > I added some debug output and made it available here: > > http://www.alvkarlebygk.com/camel > > The queue contains ~300msgs. I start the app, and it starts consuming > them. The msg count in the ems console finally shows 0 msgs. I then stop > Jboss, get some error messages, this looks strange to me: > > [SimpleThreadPool] There are still 30 worker threads active. See javadoc > runInThread(Runnable) for a possible explanation > > > When JBoss has died, the msg count in ems is ~300 once again... > > ? > > /Magnus > > > On Feb 7, 2008 8:01 PM, Magnus Heino <[EMAIL PROTECTED]> wrote: > > > > > > Other examples I find uses routes and policy... but I want > > > @Transactional. > > > > Is this possible? I'm really confused. > > > > > > It should be. The Camel endpoint will typically set the transaction up > > > before invoking your bean; so you don't need to create a dynamic proxy > > > of your bean with a transaction interceptor around it. > > > > > > Uh? If I use tx:annotation-driven and @Transactional spring does create > > a dynamic proxy as a transaction interceptor, right? So what are you saying > > here? > > > > > > > > > > I wonder if your problem is with the JTA transaction manager; which > > > depends on an XA aware ConnectionFactory? Maybe using the JMS > > > > > > Probably. I'll take another look at my config in jboss and ems. > > > > > > > > > > transaction manager might work better; then TibCo doesn't need to do > > > XA stuff? > > > > > > I really want xa. Speed is not an issue, and I want to be able to read a > > jms message, update the db, and most importantly send a few jms messages in > > the same transaction. The first part I guess could be just as good using > > idempotent consumer, but what about the sending part? If the db commits, one > > could say that I need to create xml messages for every hibernate mapped > > entity in the db that has been updated. One xml message per jms message, and > > all or none should be sent. Maybe it's just my jms knowledge thats lacking? > > > > Thanks, > > > > /Magnus > > > > > > > > > -- > > /Magnus Heino -- /Magnus Heino
