[
https://issues.apache.org/jira/browse/AMQ-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266253#comment-17266253
]
Matt Pavlovich commented on AMQ-2653:
-------------------------------------
[~rodos77] this issue is quite dated and most likely resolved in improvements
since 5.3.0. Please update this ticket if this is still an issue when using
ActiveMQ 5.16.1.
NOTE: This JIRA is scheduled to close in 30 days if no update is provided.
> Messages lost when ServerSessionPool.getServerSession() throws a JMSException
> -----------------------------------------------------------------------------
>
> Key: AMQ-2653
> URL: https://issues.apache.org/jira/browse/AMQ-2653
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.3.0
> Reporter: Eugene Rodos
> Priority: Major
> Fix For: NEEDS_REVIEW
>
> Attachments: GetServerSessionExceptionTest.java
>
>
> In ActiveMQConnectionConsumer.dispatch() method, if the call to
> sessionPool.getServerSession() results in an Exception, the message being
> dispatched is never redelivered and is lost forever. In fact, it gets stuck
> in the dispatch queue and can result in no new messages at all being
> delivered to the consumer if the prefetchSize has been reached!
> This JMSException is part of JMS's public API and it seems to me that if it
> is thrown, that should not result in a lost message.
> I'm attaching a junit test that reproduces the problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
