[
https://issues.apache.org/jira/browse/QPID-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-6607:
-----------------------------
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.
was:
If the runtime evaluation of a JMS selector throws an exception (for instance x
%y > 0 where x and y are properties of non numeric types), 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.
> Messages causing a runtime selector error may halt the broker
> --------------------------------------------------------------
>
> Key: QPID-6607
> URL: https://issues.apache.org/jira/browse/QPID-6607
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.18, 0.22, 0.30, 0.32
> Reporter: Keith Wall
> Fix For: 6.0 [Java]
>
>
> 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.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
