activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Mittler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-1022) when client is not authorized to write to A_QUEUE, producer.send to A_QUEUE does not raise exception
Date Sun, 12 Nov 2006 14:05:02 GMT
    [ https://issues.apache.org/activemq/browse/AMQ-1022?page=comments#action_37423 ] 
            
Nathan Mittler commented on AMQ-1022:
-------------------------------------

Please give this test build a try and let me know how it goes ...

http://people.apache.org/~nmittler/apache-activemq-4.2-incubator-SNAPSHOT.tar.gz


> 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
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message