Yarek Tyshchenko wrote
> 4. Start one producer on queue "bigQueue"
> 5. Start one consumer on queue "smallQueue"
> 6. Start one producer sending 4 messages per second to queue "smallQueue"
> 7. Wait until queue memory and cursor usage gets to the water mark
> 8. Observe that "smallQueue" dequeue co
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
h the above property. This would get you the sendFailIfNoSpace exception
> on the same thread.
>
>
> On Thu, Aug 29, 2013 at 5:50 AM, jvbrandis <[hidden email]> wrote:
>
> > >>
> > >> What's happening is that inside a transaction the normal behavi
>>
>> 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
>
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
