It will not be restarted. It will be stopped. You must anyway handle
journal failures.
ons 12 okt. 2016 kl. 09:44 skrev Daniel Stoner :
> Beware that if you don't handle serialisation failures as rejection - then
> you can easily get into a state whereby another actor keeps sending a
> message th
Beware that if you don't handle serialisation failures as rejection - then
you can easily get into a state whereby another actor keeps sending a
message that simply will not serialise when persisted. Your only awareness
of this will be the log errors that might occur in your JournalImpl and
you
On Tue, Oct 11, 2016 at 3:55 PM, Ian Grima wrote:
> Thanks for your reply :). If I were not to support rejections, that would
> imply that if a serialization error occurs i would simply fail the entire
> Future correct?
>
yes, right
> Gapless sequence numbers does indeed sound like a worthy co
Thanks for your reply :). If I were not to support rejections, that would
imply that if a serialization error occurs i would simply fail the entire
Future correct? Gapless sequence numbers does indeed sound like a worthy
consideration.
Thanks Again,
Ian Grima
On Tuesday, 11 October 2016 12:21:
On Tue, Oct 11, 2016 at 11:24 AM, Ian Grima wrote:
> I am still looking for an opinion on this matter if anyone could help :)
>
>
>
> On Saturday, 8 October 2016 15:31:32 UTC+2, Ian Grima wrote:
>>
>> Hi,
>>
>> I was reading up on the API of implementing a custom journal plugin in
>> Java. Coul
