1 Reply Latest reply on Apr 14, 2011 7:02 AM by davsclaus

    New release for ServiceMix 3.5 ? With Camel 2.7 and ActiveMQ 5.4.1 or upper

    jcamus

      Hi!

      When a new serviceMix 3 will be released, with new ActiveMQ and Camel (2.7)? Currently I am encountering annoying bugs with ActiveMQ 5.4.0 and Camel 2.4 used by Service mix 3.5.

       

      For example, here is a bug I have often in my JMS queues (this bug is fixed in ActiveMQ 5.4.1) :

       

      ava.lang.NullPointerException

           at org.apache.activemq.ActiveMQSession.start(ActiveMQSession.java:1637)

           at org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:508)

           at org.apache.activemq.pool.ConnectionPool.start(ConnectionPool.java:91)

           at org.apache.activemq.pool.PooledConnection.start(PooledConnection.java:78)

           at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:459)

           at org.apache.servicemix.jms.endpoints.JmsProviderEndpoint.processInOnly(JmsProviderEndpoint.java:562)

           at org.apache.servicemix.jms.endpoints.JmsProviderEndpoint.process(JmsProviderEndpoint.java:519)

           at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:617)

           at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:571)

           at org.apache.servicemix.common.AsyncBaseLifeCycle.onMessageExchange(AsyncBaseLifeCycle.java:525)

           at org.apache.servicemix.common.SyncLifeCycleWrapper.onMessageExchange(SyncLifeCycleWrapper.java:60)

           at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:632)

           at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:185)

           at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:168)

           at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)

           at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

           at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

       

       

       

       

      Regards.