Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 30 Oct 2013 14:23:36 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12625818.1357201126567.5382.1383143016187@arcas>
In-Reply-To: <JIRA.12625818.1357201126567@arcas>
References: <JIRA.12625818.1357201126567@arcas>
Subject: [jira] [Commented] (AMQ-4242) JMS Stream may lost data
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Claus Ibsen commented on AMQ-4242:
----------------------------------

Yeah we are deprecating this functionality.

> JMS Stream may lost data
> ------------------------
>
>                 Key: AMQ-4242
>                 URL: https://issues.apache.org/jira/browse/AMQ-4242
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.x
>            Reporter: SuoNayi
>              Labels: JMSStream
>             Fix For: NEEDS_REVIEWED
>
>         Attachments: AMQ4242Test.java
>
>
> When more than 75 percent prefetch messages are delivered,the standard ack occurs.
> If consumer/recipient fails after that, the rest messages will be one part of the whole.
> New coming up consumer will discard the rest messages because it's expected to read sequential messages from seq 0.
> From the view of the end user, the data transfered by JMS Stream is incomplete 
> and data is lost in this case.


--
This message was sent by Atlassian JIRA
(v6.1#6144)