Release notes - servicemix-jms-2009.02

Bug

  • SMXCOMP-474 - Regression introduced in servicemix-jms default consumer which does not rollback the transactions by default when an exchange with an ERROR status comes back
  • SMXCOMP-486 - InOnly exchange does not rollback jms message on exchange error
  • SMXCOMP-497 - Successful InOnly MEP rolling back messages to JMS queue
  • SMXCOMP-507 - smx-jms in-out provider w/unspecified replyTo queue and Pooled/SingleConnectionFactory leaks one temp replyTo queue per message
  • SMXCOMP-510 - JMS component DefaultConsumerMarshaler removes whitespace from valid XML message
  • SMXCOMP-565 - JMS consumer marshaler rollBackOnError flag is overwritten
  • SMXCOMP-604 - UnsupportedOperationException in JMS Consumer endpoint when using robust-in-only MEP
  • SMXCOMP-607 - Persistence-id of the component can't contain the minus char
  • SMXCOMP-636 - Upgrade components to use Jencks 2.2
  • SMXCOMP-670 - jms:soap-provider doesn't use custom marshaler

Improvement

Test

  • SMXCOMP-524 - Improve test coverage - ServiceMix :: JMS
  • SMXCOMP-647 - Use dynamic ports for tests
  • SMXCOMP-648 - JmsProviderConsumerEndpointTest is failing consistently
  • No labels