You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2008/09/08 16:55:57 UTC

[jira] Updated: (AMQ-1022) when client is not authorized to write to A_QUEUE, producer.send to A_QUEUE does not raise exception

     [ https://issues.apache.org/activemq/browse/AMQ-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated AMQ-1022:
----------------------------

    Fix Version/s: 5.3.0
                       (was: 5.2.0)

> when client is not authorized to write to A_QUEUE, producer.send to A_QUEUE does not raise exception
> ----------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-1022
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1022
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 4.0.1
>         Environment: Windows, amq 4.0.1, using security features described on http://incubator.apache.org/activemq/security.html
>            Reporter: Massive Boisson
>             Fix For: 5.3.0
>
>
> Using amq 4.0.1, transacted session, jms.useAsyncSend=false, security features described on http://incubator.apache.org/activemq/security.html and client NOT authorized to write to A_QUEUE, producer.send to that A_QUEUE does NOT raise an exception. Instead an asynchronous exception is raised to ExceptionListener. 
> This way the data from the message is essentially lost, because it is not possible to connect exception to the message that should have cause the exception.

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