In my opinion, it would be good form for the producer.send() to throw exception
when the exception notification reaches the client (understanding that since
this is async operation, the client may send several messages before the
exception reaches the client).
However, as long as the exception
use alwaysSyncSend has huge impacts on performance, but async sends could not
receive exceptions in the same thread you call producer.send(). Could the
client side receive jms.resourceAllocationException while calling
session.commit() ? Then async sends and receive exception in the same thread
co
Yes, that does work, thanks. :)
However, without alwaysSyncSend=true, commit() is not performed synchronous (or
at least, the call to commit() is completed without errors), so this is still a
strange transactional contract.
Setting alwaysSyncSend=true seems to have had a huge performance impact
No, use alwasySyncSend==true.
Transactions are sent asynchronously as Tim mentioned, however the commit
is always synchronous. You can force all sends within the TX to by sync
with the above property. This would get you the sendFailIfNoSpace exception
on the same thread.
On Thu, Aug 29, 2013 at
>>
>> What's happening is that inside a transaction the normal behavior is to
>> send messages without waiting for a response from the broker (async)
>> which is why the only way the exception gets noticed is by an exception
>> listener. You can however configure this to work by using the opti
>
> What's happening is that inside a transaction the normal behavior is to
> send messages without waiting for a response from the broker (async)
> which is why the only way the exception gets noticed is by an exception
> listener. You can however configure this to work by using the option
>
On 08/29/2013 05:54 AM, jvbrandis wrote:
Good suggestion!! :)
Yes, an ExceptionListener on the Connection does get the exception when
ResourceAllocationException is thrown.
Of course, I could hack my way around it, notifying the client from the
connection when the connection receives the error
Good suggestion!! :)
Yes, an ExceptionListener on the Connection does get the exception when
ResourceAllocationException is thrown.
Of course, I could hack my way around it, notifying the client from the
connection when the connection receives the error, but that seems backwards to
me…. the er
Maybe set an exception listener on the connection and see if you get it
there?
http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnection.html#setExceptionListener(javax.jms.ExceptionListener)
On Wed, Aug 28, 2013 at 12:38 PM, joa...@mnemonic.no wrote:
> Hi all.
>
> I am fa
