[jira] Created: (AMQ-1043) transaction commit does not fail even though parts of transactions raised exception
transaction commit does not fail even though parts of transactions raised exception --- Key: AMQ-1043 URL: https://issues.apache.org/activemq/browse/AMQ-1043 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.0.1 Environment: windows, 4.0.1, transacted session, perssistent queues Reporter: Massive Boisson quoting Hiram I think we need to enhance our broker so that it keeps track of any errors that occurred that were part of a transaction and to force that transaction to fail on the commit. This problem is demonstrated in a related JIRA issue: https://issues.apache.org/activemq/browse/AMQ-1022 -- 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
[ 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] 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] Created: (AMQ-751) Extend ExceptionListener mechanism by creating a custom AMQ exception which would provide more detail about the exception
Extend ExceptionListener mechanism by creating a custom AMQ exception which would provide more detail about the exception - Key: AMQ-751 URL: https://issues.apache.org/activemq/browse/AMQ-751 Project: ActiveMQ Type: Improvement Components: JMS client, Broker Reporter: Massive Boisson To quote James: I wonder if we could add a neater non-JMS extension to ActiveMQ to make it easier to be notified asynchronously of which Message objects could not be sent? I guess we could just use the ExceptionListener and use a custom type of Exception which contained the Message object? I think this would greatly increase the usefulness of async sends. -- 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
