Re: [mdr-users] Loosing last transaction results in case of crash

Hi Olivier,
this is normal - as designed. For the performance reasons the 
transactions are cached in memory and committed to disk only when the 
cache threshold is reached. So, a few transaction performed just before 
the crash of the application may be lost but you are guaranteed that the 
transaction will be lost as a whole (not just partially), so the state 
should at any case be consistent.
Martin

Olivier RICHAUD wrote:

>Hi all,
>
>Has anybody already experienced loosing the results of the last
>transaction in case the JVM crashes. I mean, alltough the last
>read/write transaction has been committed, if the JVM crashes or is
>stopped abruptly, changes are lost. For example, although an object has
>correctly been created and the call to endTrand performed, if the JVM
>unexpectedly stops, I would loose that creation.
>
>Regards.
>
>Olivier.
>
>  
>