On 24/01/2020 1:05 pm, Robbie Gemmell wrote:
On Fri, 24 Jan 2020 at 12:48, Gordon Sim <[email protected]> wrote:
On 24/01/2020 11:03 am, akabhishek1 wrote:
Problem/Situation - We are using ServiceBus to receive the message and
acknowledge the message after completing all the process/transformation.
As one of the processor(Mule Batch) needs every object should be
serializable. We can't acknowledge the message before batch execution which
could be reason for Message loss.
As acknowledgement needs JMSMessage which is not serializable, so we are
trying to find out alternative to acknowledge message without using
JMSMessage object.
Acknowledgement is of course tied to a specific active socket. Even if
you *could* serialize and then deserialize it, it would no longer be
associated the socket and so would be of no use for acknowledgement anyway.
Yep, I was glossing over all this since they wont be serializable.
Indeed. The way I view it is that they are not serializable because
there would be no value in their being serializable (just as there would
be no point in serializing a live socket). They are 'active' objects
tied to their current context in the process in which they are created.
(The data they carry of course may be serializable. That is data
detached from the 'active' context though.)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
