Qpid JMS client library incorrectly throws a RuntimeException

Solution Unverified - Updated -

Issue

  • In case of an unexpected condition, such as the underlying disk being full, a Java qpid client sending transacted messages and writing to a queue with flow-to-disk policy set up may fail with a SessionException

  • While the failure is expected, the exception is incorrect, since the JMS specification section 7.2 requires that the client throw only exceptions that are derived from JMSException

  • Detailed steps to reproduce are documented in the Diagnostic Steps section

Environment

  • Red Hat Enterprise MRG Messaging 2.0
  • qpid-0.10

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.