You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Chris Custine (JIRA)" <ji...@apache.org> on 2009/04/02 05:34:34 UTC

[jira] Created: (SMXCOMP-497) Successful InOnly MEP rolling back messages to JMS queue

Successful InOnly MEP rolling back messages to JMS queue
--------------------------------------------------------

                 Key: SMXCOMP-497
                 URL: https://issues.apache.org/activemq/browse/SMXCOMP-497
             Project: ServiceMix Components
          Issue Type: Improvement
          Components: servicemix-jms
    Affects Versions: servicemix-jms-2009.02
            Reporter: Chris Custine
            Assignee: Chris Custine


The fix I made for SMX4COMP-486 breaks the JMS consumer endpoint.  An InOnly DONE message is processed and causes an exception in processExchange which rolls back the messages to the JMS queue.

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

[jira] Updated: (SMXCOMP-497) Successful InOnly MEP rolling back messages to JMS queue

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

Chris Custine updated SMXCOMP-497:
----------------------------------

    Issue Type: Bug  (was: Improvement)

> Successful InOnly MEP rolling back messages to JMS queue
> --------------------------------------------------------
>
>                 Key: SMXCOMP-497
>                 URL: https://issues.apache.org/activemq/browse/SMXCOMP-497
>             Project: ServiceMix Components
>          Issue Type: Bug
>          Components: servicemix-jms
>    Affects Versions: servicemix-jms-2009.02
>            Reporter: Chris Custine
>            Assignee: Chris Custine
>
> The fix I made for SMX4COMP-486 breaks the JMS consumer endpoint.  An InOnly DONE message is processed and causes an exception in processExchange which rolls back the messages to the JMS queue.

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

[jira] Resolved: (SMXCOMP-497) Successful InOnly MEP rolling back messages to JMS queue

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

Chris Custine resolved SMXCOMP-497.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: servicemix-jms-2009.02

> Successful InOnly MEP rolling back messages to JMS queue
> --------------------------------------------------------
>
>                 Key: SMXCOMP-497
>                 URL: https://issues.apache.org/activemq/browse/SMXCOMP-497
>             Project: ServiceMix Components
>          Issue Type: Bug
>          Components: servicemix-jms
>    Affects Versions: servicemix-jms-2009.02
>            Reporter: Chris Custine
>            Assignee: Chris Custine
>             Fix For: servicemix-jms-2009.02
>
>
> The fix I made for SMX4COMP-486 breaks the JMS consumer endpoint.  An InOnly DONE message is processed and causes an exception in processExchange which rolls back the messages to the JMS queue.

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