[
https://issues.apache.org/jira/browse/ARTEMIS-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404942#comment-16404942
]
ASF GitHub Bot commented on ARTEMIS-1753:
-----------------------------------------
GitHub user mtaylor opened a pull request:
https://github.com/apache/activemq-artemis/pull/1958
ARTEMIS-1753 Prevent NPE on 1.x Client Topic Sub
When creting a durable topic subscription using the Artemis 1.x JMS
client library. The client sends a QueueQuery to the server to see if
the durable subsciption queue already exists. The broker then performs
some transformation of the queue addresses to suit the 1.x naming
scheme. However, if the queue does not already exist the transform is
attempted on a null string causing NPE. To fix we simply check that the
result return isExists=true.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mtaylor/activemq-artemis ARTEMIS-1753
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1958.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1958
----
----
> When using the 1.5.5 Artemis JMS Client, NPE is thrown when creating a
> durable subscription
> -------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-1753
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1753
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Martyn Taylor
> Priority: Major
>
> When creating a durable topic subcription using the Artemis 1.5.5 client a
> QueueQuery is performed to see if the subscription already exists. There is
> some code that converts the queue names to the old 1.x scheme. However, if
> the subscription does not already exist, the conversion is attempted on a
> null string, causing an NPE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
