You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Eugene Rodos (JIRA)" <ji...@apache.org> on 2010/03/15 22:51:45 UTC

[jira] Created: (AMQ-2653) Messages lost when ServerSessionPool.getServerSession() throws a JMSException

Messages lost when ServerSessionPool.getServerSession() throws a JMSException
-----------------------------------------------------------------------------

                 Key: AMQ-2653
                 URL: https://issues.apache.org/activemq/browse/AMQ-2653
             Project: ActiveMQ
          Issue Type: Bug
    Affects Versions: 5.3.0
            Reporter: Eugene Rodos
         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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (AMQ-2653) Messages lost when ServerSessionPool.getServerSession() throws a JMSException

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated AMQ-2653:
------------------------------

    Fix Version/s: 5.5.0
                       (was: 5.4.1)

> Messages lost when ServerSessionPool.getServerSession() throws a JMSException
> -----------------------------------------------------------------------------
>
>                 Key: AMQ-2653
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2653
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.0
>            Reporter: Eugene Rodos
>             Fix For: 5.5.0
>
>         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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (AMQ-2653) Messages lost when ServerSessionPool.getServerSession() throws a JMSException

Posted by "Eugene Rodos (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eugene Rodos updated AMQ-2653:
------------------------------

    Attachment: GetServerSessionExceptionTest.java

Attaching junit test.

> Messages lost when ServerSessionPool.getServerSession() throws a JMSException
> -----------------------------------------------------------------------------
>
>                 Key: AMQ-2653
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2653
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.0
>            Reporter: Eugene Rodos
>         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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.