You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rupert Smith (JIRA)" <qp...@incubator.apache.org> on 2007/06/15 11:35:26 UTC

[jira] Created: (QPID-517) Broker doesn't return NO_CONSUMERS code for an immediate message, when the consumer is disconnected.

Broker doesn't return NO_CONSUMERS code for an immediate message, when the consumer is disconnected.
----------------------------------------------------------------------------------------------------

                 Key: QPID-517
                 URL: https://issues.apache.org/jira/browse/QPID-517
             Project: Qpid
          Issue Type: Bug
          Components: Java Broker
    Affects Versions: M2
         Environment: Java broker M2.
            Reporter: Rupert Smith
            Assignee: Rupert Smith


The broker fails to return this error code when an immediate message is sent but there is no consumer. This should cause a JMSException on the client, which wraps an AMQNoConsumersException, to be thrown to the calling client.

This was working previously but some broker changes have cancelled this behaviour.

Fix and write a test to expose this desired functionality.

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


[jira] Closed: (QPID-517) Broker doesn't return NO_CONSUMERS code for an immediate message, when the consumer is disconnected.

Posted by "Rupert Smith (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rupert Smith closed QPID-517.
-----------------------------

    Resolution: Fixed

> Broker doesn't return NO_CONSUMERS code for an immediate message, when the consumer is disconnected.
> ----------------------------------------------------------------------------------------------------
>
>                 Key: QPID-517
>                 URL: https://issues.apache.org/jira/browse/QPID-517
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M2
>         Environment: Java broker M2.
>            Reporter: Rupert Smith
>            Assignee: Rupert Smith
>
> The broker fails to return this error code when an immediate message is sent but there is no consumer. This should cause a JMSException on the client, which wraps an AMQNoConsumersException, to be thrown to the calling client.
> This was working previously but some broker changes have cancelled this behaviour.
> Fix and write a test to expose this desired functionality.

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


[jira] Commented: (QPID-517) Broker doesn't return NO_CONSUMERS code for an immediate message, when the consumer is disconnected.

Posted by "Rupert Smith (JIRA)" <qp...@incubator.apache.org>.
    [ https://issues.apache.org/jira/browse/QPID-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530953 ] 

Rupert Smith commented on QPID-517:
-----------------------------------

ImmediateMessageTest tests for this, and fix has been applied.

> Broker doesn't return NO_CONSUMERS code for an immediate message, when the consumer is disconnected.
> ----------------------------------------------------------------------------------------------------
>
>                 Key: QPID-517
>                 URL: https://issues.apache.org/jira/browse/QPID-517
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M2
>         Environment: Java broker M2.
>            Reporter: Rupert Smith
>            Assignee: Rupert Smith
>
> The broker fails to return this error code when an immediate message is sent but there is no consumer. This should cause a JMSException on the client, which wraps an AMQNoConsumersException, to be thrown to the calling client.
> This was working previously but some broker changes have cancelled this behaviour.
> Fix and write a test to expose this desired functionality.

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