You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Massive Boisson (JIRA)" <ji...@apache.org> on 2006/11/02 14:08:04 UTC

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

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

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

Posted by "Massive Boisson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQ-1022?page=comments#action_37438 ] 
            
Massive Boisson commented on AMQ-1022:
--------------------------------------

This needs clarification: this is a transacted session, and a perssistent queue. 
producer.send does NOT raise an exception
session.commit does NOT raise an excepton. 
Instead an asynchronous exception is raised to ExceptionListener.
Still the same problem.

> 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

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

Posted by "Nathan Mittler (JIRA)" <ji...@apache.org>.
    [ 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

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

Posted by "Nathan Mittler (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQ-1022?page=comments#action_37424 ] 
            
Nathan Mittler commented on AMQ-1022:
-------------------------------------

Ignore my previous comment - this build is for a different issue.

> 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