I just noticed that the 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. It always reads a message at the end of the loop, without first checking to see if maxMessages has already been reached. I have attached a patchfile here that corrects the issue. http://www.nabble.com/file/p19662481/patchfile.txt patchfile.txt --Mike -- View this message in context: http://www.nabble.com/MessageServlet-reads-too-many-messages---Fixed-%28patch-included%29-tp19662481p19662481.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
