[
https://issues.apache.org/jira/browse/ARTEMIS-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15330942#comment-15330942
]
ASF subversion and git services commented on ARTEMIS-568:
---------------------------------------------------------
Commit 5c29cc9a28b8dde1937c29cd8cd06c2d9def70f8 in activemq-artemis's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=5c29cc9 ]
ARTEMIS-568 Catch broken JMS selector expressions
Enforce an EOF on the expression so the selector parser keeps going and
catches the broken selector statement.
> JMS Selector parsing will not fail if a valid selector is followed by invalid
> text
> ----------------------------------------------------------------------------------
>
> Key: ARTEMIS-568
> URL: https://issues.apache.org/jira/browse/ARTEMIS-568
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 1.3.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 1.4.0
>
>
> A JMS Selector which has a valid stem followed by invalid data will not cause
> a failure, and the selector will be parsed an executed as if only the valid
> stem were present.
> For example the selector
> {code}
> a = 1 AMD b = 2
> {code}
> will be treated as if the selector was
> {code}
> a = 1
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
