[QPID-6607] Messages causing a runtime selector error may halt the broker

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.18, 0.22, 0.30, 0.32
• Fix Version/s: qpid-java-6.0
• Component/s: Broker-J
• Assignee: Alex Rudyy
• Reporter: Keith Wall
• Created: 23/Jun/15 17:34
• Updated: 02/Oct/19 19:22
• Resolved: 30/Jun/15 08:15

Description

If the runtime evaluation of a JMS selector throws an exception (for instance x %y > 0) where x and y are message properties but have non numeric values at eval time), this issue can cause the Broker to shutdown.

On current trunk, if the message follows the straight through path, the abrupt termination of the IO thread will cause the Broker's uncaught exception handler to shutdown the Broker. If the message is processed by QueueRunner, the termination of the VH thread does not cause the Broker to shutdown. . This appears to be as a result of QPID-6584 and the removal of RCES.

On older releases, the straight through path guarded uncaught exceptions, but the QR or SFR threads could cause Broker shutdown.