You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/04/15 15:03:25 UTC

[jira] [Commented] (AMQ-6218) Message content returns null occasionally from Virtual Topic to the consumer

    [ https://issues.apache.org/jira/browse/AMQ-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242921#comment-15242921 ] 

ASF subversion and git services commented on AMQ-6218:
------------------------------------------------------

Commit 9c929b6870ae4c19cf4f227fa13472b09ebac729 in activemq's branch refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=9c929b6 ]

Revert "https://issues.apache.org/jira/browse/AMQ-6218"

Reverting commit in favor of a better approach

This reverts commit ea09159a4087212964787e7cf68ef30170d115f0.


> Message content returns null occasionally from Virtual Topic to the consumer
> ----------------------------------------------------------------------------
>
>                 Key: AMQ-6218
>                 URL: https://issues.apache.org/jira/browse/AMQ-6218
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.12.2, 5.13.2
>            Reporter: Rohit Sonawat
>            Assignee: Christopher L. Shannon
>             Fix For: 5.14.0, 5.13.3
>
>         Attachments: AMQ6218Test.java, App.java, Full app.log
>
>
> I have 1 Virtual Topic and 40 Consumer to consume the messages sent by the topic. The problem is when I am sending thousands of Messages lets say 10000 via Virtual Topic I have noticed that 2 or 3 consumer are getting null as a text when I do message.getText(), but virtual topic is not sending a null as a text message if it so then all 40 consumer should report same.
> I have also noticed this problem is not happening in AMQ v5.11 or with levelDB in AMQ v5.12.2/5.13.2. It is happening only in when you use kahaDB with AMQ v5.12.2/5.13.2



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)