You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Ray Barlow <ra...@makeyour-point.com> on 2008/05/21 23:55:46 UTC
Derby update - critical data loss bug fix
Hi,
Just seen an update posted for Derby with the following message:-
IMPORTANT NOTICE:
If you are currently using Derby 10.3.1.4 or Derby 10.3.2.1, it is strongly
recommended that you upgrade to Derby 10.4.1.3 or 10.3.3.0 to avoid
any chance of database corruption due to an issue with multiple threads
accessing a database that is documented in DERBY-3347.
Would be worth someone with framework access updating the SVN version.
Framework is currently on the 10.3 series (10.3.1.4 to be precise) has
anybody tried the 10.4 series? Looks like it should be worth a try.
Cheers,
Ray
Re: Derby update - critical data loss bug fix
Posted by Ray Barlow <ra...@makeyour-point.com>.
Thanks Jacques,
Had just managed to get through a little testing with 10.4 and it seems
fine.
Ray
Jacques Le Roux wrote:
> Done in r659237
>
> Jacques
>
> From: "Jacques Le Roux" <ja...@les7arts.com>
>> Thanks Ray,
>>
>> I'm currently testing 10.4.1.3, will hopefully commit soon
>>
>> It's interesting to note this new feature from
>> http://www.nabble.com/-ANNOUNCE--Apache-Derby-10.4.1.3-released-tt16910783.html
>>
>> * Asynchronous Replication Allows you to maintain an up to date copy
>> of your (master) database on a different host (the slave). In the
>> case of a crash on the master database you can perform failover to
>> the copy (slave database) and continue serving client requests
>> against your database.
>> More at http://db.apache.org/derby/releases/release-10.4.1.3.cgi
>>
>> Jacques
Re: Derby update - critical data loss bug fix
Posted by Jacques Le Roux <ja...@les7arts.com>.
Done in r659237
Jacques
From: "Jacques Le Roux" <ja...@les7arts.com>
> Thanks Ray,
>
> I'm currently testing 10.4.1.3, will hopefully commit soon
>
> It's interesting to note this new feature from http://www.nabble.com/-ANNOUNCE--Apache-Derby-10.4.1.3-released-tt16910783.html
> * Asynchronous Replication
> Allows you to maintain an up to date copy of your (master) database on
> a different host (the slave). In the case of a crash on the master
> database you can perform failover to the copy (slave database) and
> continue serving client requests against your database.
>
> More at http://db.apache.org/derby/releases/release-10.4.1.3.cgi
>
> Jacques
>
> From: "Ray Barlow" <ra...@makeyour-point.com>
>> Hi,
>>
>> Just seen an update posted for Derby with the following message:-
>>
>> IMPORTANT NOTICE:
>> If you are currently using Derby 10.3.1.4 or Derby 10.3.2.1, it is strongly
>> recommended that you upgrade to Derby 10.4.1.3 or 10.3.3.0 to avoid
>> any chance of database corruption due to an issue with multiple threads
>> accessing a database that is documented in DERBY-3347.
>>
>> Would be worth someone with framework access updating the SVN version.
>> Framework is currently on the 10.3 series (10.3.1.4 to be precise) has
>> anybody tried the 10.4 series? Looks like it should be worth a try.
>>
>> Cheers,
>>
>> Ray
>>
>
Re: Derby update - critical data loss bug fix
Posted by Jacques Le Roux <ja...@les7arts.com>.
Thanks Ray,
I'm currently testing 10.4.1.3, will hopefully commit soon
It's interesting to note this new feature from http://www.nabble.com/-ANNOUNCE--Apache-Derby-10.4.1.3-released-tt16910783.html
* Asynchronous Replication
Allows you to maintain an up to date copy of your (master) database on
a different host (the slave). In the case of a crash on the master
database you can perform failover to the copy (slave database) and
continue serving client requests against your database.
More at http://db.apache.org/derby/releases/release-10.4.1.3.cgi
Jacques
From: "Ray Barlow" <ra...@makeyour-point.com>
> Hi,
>
> Just seen an update posted for Derby with the following message:-
>
> IMPORTANT NOTICE:
> If you are currently using Derby 10.3.1.4 or Derby 10.3.2.1, it is strongly
> recommended that you upgrade to Derby 10.4.1.3 or 10.3.3.0 to avoid
> any chance of database corruption due to an issue with multiple threads
> accessing a database that is documented in DERBY-3347.
>
> Would be worth someone with framework access updating the SVN version.
> Framework is currently on the 10.3 series (10.3.1.4 to be precise) has
> anybody tried the 10.4 series? Looks like it should be worth a try.
>
> Cheers,
>
> Ray
>