![logtail aries logtail aries](https://i.pinimg.com/originals/f4/f5/7f/f4f57f8ea6748b84b9160dc764f9516f.jpg)
Instead, this blog post will attempt to deep dive a bit into the fabric:mq-create command. Introducing Fabric in this post would mean to simply repeat the documentation of the Fabric web site, so I'll spare that. If you don't know what Fabric is, have a look at the project web site. You will need to rebuild and redeploy the Camel route.įuse Fabric is a very powerful open source integration platform (iPaaS) developed by Red Hat (former FuseSource).
![logtail aries logtail aries](https://i.pinimg.com/originals/a5/2b/76/a52b761d87af9ac445995d94c4e0b4dd.png)
In this case I suggest to change the maven-bundle-plugin configuration and explicitly require activemq-pool to be of version 5.8.0 or higher, using e.g. It may be that instead it now pulls in from activemq-spring. If you still see the exception, run a packages:imports and verify if it pulls in activemq-pool from the new jar file. This should rewire your Camel bundle to use the new activemq-pool jar. $Bundle-SymbolicName=-pool&Bundle-Version=5.8.0& \Įxport-Package= version=5.8.0' Osgi:install 'wrap:mvn:/activemq-pool/5.8.0 \ As the 5.8.0 version of activemq-pool is not an OSGi bundle, we need to wrap it accordingly.osgi:list -l -t 0 | grep activemq-pool.
#LOGTAIL ARIES UPGRADE#
If you are running on Fuse ESB Enterprise 7.x and you cannot upgrade to JBoss Fuse 6.0, then a possible solution is to replace the activemq-pool/5.7.0 bundle with version 5.8.0. If so, upgrade to ActiveMQ 5.8.0 on the client. So anyone running into this problem, check if you're using ActiveMQ 5.7.0 on the client side. Version 5.8.0 of activemq-pool has this bug fixed already. This problem is caused by a bug in activemq-pool of version 5.7.0 (and most likely earlier versions). : Cannot rollback() inside an XASessionĪt .rollback(ActiveMQXASession.java:76)Īt .PooledSession.close(PooledSession.java:120)Īt .JmsResourceHolder.closeAll(JmsResourceHolder.java:193)Īt .ConnectionFactoryUtils$JmsResourceSynchronization.releaseResource(ConnectionFactoryUtils.java:412)Īt .ConnectionFactoryUtils$JmsResourceSynchronization.releaseResource(ConnectionFactoryUtils.java:1)Īt .ResourceHolderSynchronization.beforeCompletion(ResourceHolderSynchronization.java:72)Īt .iggerBeforeCompletion(TransactionSynchronizationUtils.java:106)Īt .iggerBeforeCompletion(AbstractPlatformTransactionManager.java:940)Īt .AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:738)Īt .mit(AbstractPlatformTransactionManager.java:723)Īt .mit(GeronimoPlatformTransactionManager.java:76)Īt (Unknown Source)Īt (DelegatingMethodAccessorImpl.java:25)Īt .invoke(Method.java:597)Īt .impl.ProxyHandler$1.invoke(ProxyHandler.java:54)Īt .(ProxyHandler.java:119)Īt .$mit(Unknown Source)Īt .AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:257)Īt .DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058)Īt .DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050)Īt .DefaultMessageListenerContainer$n(DefaultMessageListenerContainer.java:947)Īt $nTask(ThreadPoolExecutor.java:895)Īt $n(ThreadPoolExecutor.java:918)Īt (Thread.java:695) When Camel tries to commit the XA transaction it raises the following warning:ġ4:58:37,063 | WARN | Consumer | PooledSession | 122 -pool - 5.7.0.fuse-71-047 |Ĭaught exception trying rollback() when putting session back into the pool, will invalidate. Deploying this demo to Fuse ESB Enterprise 7.1 will immediately reproduce the problem. Most of the time the use case is a Camel route deployed into Karaf consuming messages using XA transaction from an ActiveMQ broker (using Aries as the TX manager).Ī possible example route can be found in the Camel-WMQ-AMQ-XA-TX demo on my fuse-demos github repoository. The following problem has come up repeatedly among ActiveMQ/Camel/Karaf users so I want to capture it here in this post.