activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-1955) MessageServlet reads too many messages
Date Thu, 09 Oct 2008 13:19:52 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dejan Bosanac resolved AMQ-1955.
--------------------------------

         Assignee: Dejan Bosanac
    Fix Version/s: 5.3.0
       Resolution: Fixed

Patch applied in SVN revision 703161. Thanks

> MessageServlet reads too many messages
> --------------------------------------
>
>                 Key: AMQ-1955
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1955
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.0.0, 5.1.0, 5.2.0, 5.3.0
>         Environment: Any
>            Reporter: Mike Richmond
>            Assignee: Dejan Bosanac
>             Fix For: 5.3.0
>
>         Attachments: MessageServlet.java.patch
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> MessageServlet inside activemq-web will pull maxMessages+1 messages off of the queue
but only write a response containing maxMessages. 
>  
> After some debugging, I figured out that the problem is with the while loop that reads
messages inside the doMessages method (and doMessagesWithoutContinuation).  It always reads
a message at the end of the loop, without first checking to see if maxMessages has already
been reached. 
> Attached is a patch that corrects this issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message