Yes,� to fix it you haev to evaluate:
DBXPlatform
disableAutomaticConnectionReleaseOnGC

this will not store the connections in the weakregistry
so you have to be sure to properly disconnect the connections

On Tue, Sep 7, 2010 at 10:25 AM, Panu Suominen <panu.j.m.suominen@gmail.com> wrote:
In 1.1 running all test with GlorpDBX and Seaside will raise this exception.
However I have not been able to reproduce the error reliably. Like it
says in the error reports is seems that updating the tally value is somehow
broken.

--
Panu

_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project