On 2/7/20 11:57 AM, akabhishek1 wrote:
Hi Tim,
Thanks a lot for quick reply. Please find attached updated code. I am
intentionally throwing exception after receiving the message. We could face
this issue in production.
We have implemented reliability pattern, message should be acknowledge only
after successful transformation. Bussiness transformation/process could be
fail continously due to unavailability of service.
We are using *connection.createSession(false, 101)* , so only one message
will be acknowledged at a time not prior messages.
Client individual ack mode operates in fundamentally the same manner as
Client Ack mode where failures due to exceptions in the asynchronous
path must be handled by a call to session recover to replay the message
and reprocess it, or close the session if you can't handle reprocessing
of failed messages. You can't just throw an exception in the async
MessageListener onMessage handler and hope for the best here.
The given example is just to replicate Out of Memory error based on
bussiness scenario.
Please suggest, if i can do anything to avoid this error.
Don't throw exceptions from onMessage as the specification labels this a
client programming error.
TestQpidRcvOnly.txt
<http://qpid.2158936.n2.nabble.com/file/t396358/TestQpidRcvOnly.txt>
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Tim Bish
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
