[
https://issues.apache.org/jira/browse/APLO-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clajder updated APLO-387:
-------------------------
Description:
For the next MQTT pub-sub config:
pub: topic/<topic_id>
sub: topic/#
the subscriber receives topic name as "topic/#" instead of right one which is
'topic/<topic_id>'.
This defect leads to other high severity issues as sub is not able to determine
actual message source.
Worth to note that this issue constantly reproducible on tcp connector through
eclipse Paho client and it looks like it does not happen with websocket config
(javascript).
Just in case there is linked bug on another JIRA:
https://jira.spring.io/browse/INT-3828
was:
For the next MQTT pub-sub config:
pub: topic/<topic_id>
sub: topic/#
the subscriber receives topic name as "topic/#" instead of right one which is
'topic/<topic_id>'.
This defect leads to other high severity issues as sub is not able to determine
actual message source.
Worth to note that this issue constantly reproducible on tcp connector through
eclipse Paho client and it looks like it does not happen with websocket config.
Just in case there is linked bug on another JIRA:
https://jira.spring.io/browse/INT-3828
> MQTT Client (Paho, tcp connector) does not receive original topic name in
> case of wildcard subscription (topic/#)
> -----------------------------------------------------------------------------------------------------------------
>
> Key: APLO-387
> URL: https://issues.apache.org/jira/browse/APLO-387
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Affects Versions: 1.7
> Reporter: clajder
>
> For the next MQTT pub-sub config:
> pub: topic/<topic_id>
> sub: topic/#
> the subscriber receives topic name as "topic/#" instead of right one which is
> 'topic/<topic_id>'.
> This defect leads to other high severity issues as sub is not able to
> determine actual message source.
> Worth to note that this issue constantly reproducible on tcp connector
> through eclipse Paho client and it looks like it does not happen with
> websocket config (javascript).
> Just in case there is linked bug on another JIRA:
> https://jira.spring.io/browse/INT-3828
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
