[Pharo-project] Please help!! Error: There is no free space in this set!'
I know this is a alraedy known issue: http://code.google.com/p/pharo/issues/detail?id=1628 I am trying to make SqueakDBX work in 1.1 and it doesn't work because of this. Each DBXConnection is registered in the WeakRegistry just to close the database connection in case they don't do it explicitly. This this, I have a: addObjectToGarbageCollect: anObject WeakRegistry default add: anObject. And in DBXConnetion >> connect, I call that method. Do you know how to solve the problem? I read the issue but I am uncertain what should I do nor if it is fixed. I think this bug is really important. Thanks Mariano
El jue, 05-08-2010 a las 21:35 +0200, Mariano Martinez Peck escribió:
I know this is a alraedy known issue: http://code.google.com/p/pharo/issues/detail?id=1628 I am trying to make SqueakDBX work in 1.1 and it doesn't work because of this. Each DBXConnection is registered in the WeakRegistry just to close the database connection in case they don't do it explicitly.
This this, I have a:
addObjectToGarbageCollect: anObject
WeakRegistry default add: anObject.
And in DBXConnetion >> connect, I call that method.
Do you know how to solve the problem? I read the issue but I am uncertain what should I do nor if it is fixed. I think this bug is really important.
Not a solution sorry, but a suggestion (or maybe this is already implemented, I haven't used SqueakDBX). :) Maybe it would be useful to add a pool for the connections so they aren't so many at the same time. Also, the database admin will be grateful. Cheers
Thanks
Mariano _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Miguel Cobá http://miguel.leugim.com.mx
So....any helpers? http://code.google.com/p/pharo/issues/detail?id=2551 http://code.google.com/p/pharo/issues/detail?id=1628 I would like to help, but I am 100% newbie in this. Please consider me as tester. Cheers mariano 2010/8/5 Miguel Enrique Cobá MartÃnez <miguel.coba@gmail.com>
El jue, 05-08-2010 a las 21:35 +0200, Mariano Martinez Peck escribió:
I know this is a alraedy known issue: http://code.google.com/p/pharo/issues/detail?id=1628 I am trying to make SqueakDBX work in 1.1 and it doesn't work because of this. Each DBXConnection is registered in the WeakRegistry just to close the database connection in case they don't do it explicitly.
This this, I have a:
addObjectToGarbageCollect: anObject
WeakRegistry default add: anObject.
And in DBXConnetion >> connect, I call that method.
Do you know how to solve the problem? I read the issue but I am uncertain what should I do nor if it is fixed. I think this bug is really important.
Not a solution sorry, but a suggestion (or maybe this is already implemented, I haven't used SqueakDBX). :)
Maybe it would be useful to add a pool for the connections so they aren't so many at the same time. Also, the database admin will be grateful.
Cheers
Thanks
Mariano _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Yes we need help on this one. Stef On Sep 1, 2010, at 4:41 PM, Mariano Martinez Peck wrote:
So....any helpers?
http://code.google.com/p/pharo/issues/detail?id=2551 http://code.google.com/p/pharo/issues/detail?id=1628
I would like to help, but I am 100% newbie in this. Please consider me as tester.
Cheers
mariano
2010/8/5 Miguel Enrique Cobá MartÃnez <miguel.coba@gmail.com> El jue, 05-08-2010 a las 21:35 +0200, Mariano Martinez Peck escribió:
I know this is a alraedy known issue: http://code.google.com/p/pharo/issues/detail?id=1628 I am trying to make SqueakDBX work in 1.1 and it doesn't work because of this. Each DBXConnection is registered in the WeakRegistry just to close the database connection in case they don't do it explicitly.
This this, I have a:
addObjectToGarbageCollect: anObject
WeakRegistry default add: anObject.
And in DBXConnetion >> connect, I call that method.
Do you know how to solve the problem? I read the issue but I am uncertain what should I do nor if it is fixed. I think this bug is really important.
Not a solution sorry, but a suggestion (or maybe this is already implemented, I haven't used SqueakDBX). :)
Maybe it would be useful to add a pool for the connections so they aren't so many at the same time. Also, the database admin will be grateful.
Cheers
Thanks
Mariano _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
The error no free space in set should be fixed in 1.1. Except abysmal performance, what problem do you have exactly? Cheers, Henry On 01.09.2010 16:41, Mariano Martinez Peck wrote:
So....any helpers?
http://code.google.com/p/pharo/issues/detail?id=2551 <http://code.google.com/p/pharo/issues/detail?id=2551> http://code.google.com/p/pharo/issues/detail?id=1628 <http://code.google.com/p/pharo/issues/detail?id=1628>
I would like to help, but I am 100% newbie in this. Please consider me as tester.
Cheers
mariano
2010/8/5 Miguel Enrique Cobá MartÃnez <miguel.coba@gmail.com <mailto:miguel.coba@gmail.com>>
El jue, 05-08-2010 a las 21:35 +0200, Mariano Martinez Peck escribió: > I know this is a alraedy known issue: > http://code.google.com/p/pharo/issues/detail?id=1628 > I am trying to make SqueakDBX work in 1.1 and it doesn't work because > of this. Each DBXConnection is registered in the WeakRegistry just to > close the database connection in case they don't do it explicitly. > > This this, I have a: > > addObjectToGarbageCollect: anObject > > WeakRegistry default add: anObject. > > > And in DBXConnetion >> connect, I call that method. > > Do you know how to solve the problem? I read the issue but I am > uncertain what should I do nor if it is fixed. I think this bug is > really important.
Not a solution sorry, but a suggestion (or maybe this is already implemented, I haven't used SqueakDBX). :)
Maybe it would be useful to add a pool for the connections so they aren't so many at the same time. Also, the database admin will be grateful.
Cheers
> > Thanks > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr <mailto:Pharo-project@lists.gforge.inria.fr> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr <mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
2010/9/1 Henrik Sperre Johansen <henrik.s.johansen@veloxit.no>
The error no free space in set should be fixed in 1.1. Except abysmal performance, what problem do you have exactly?
I am not talking about performance. I am talking that it just raise that error. What I do particulary in SqueakDBX (it is optional thus) is that when a Connection is created, it is added to WeakRegistry default so that I can implement #finalize and this method releases the database connection if it was not already done. This is for possible bugs or developers where they don't cal correctly yhe#disconnect method. Of course, if you use the pool you won't have this problem (depending how many connections you define in the pool as max). Anyway, while running tests, I create a lot of connections, thus, I get the error "There is no free space in this set!'" when the code tries to add the connection to the WeakRegistry. Thanks Henry. mariano
Cheers, Henry
On 01.09.2010 16:41, Mariano Martinez Peck wrote:
So....any helpers?
http://code.google.com/p/pharo/issues/detail?id=2551 http://code.google.com/p/pharo/issues/detail?id=1628
I would like to help, but I am 100% newbie in this. Please consider me as tester.
Cheers
mariano
2010/8/5 Miguel Enrique Cobá MartÃnez <miguel.coba@gmail.com>
El jue, 05-08-2010 a las 21:35 +0200, Mariano Martinez Peck escribió:
I know this is a alraedy known issue: http://code.google.com/p/pharo/issues/detail?id=1628 I am trying to make SqueakDBX work in 1.1 and it doesn't work because of this. Each DBXConnection is registered in the WeakRegistry just to close the database connection in case they don't do it explicitly.
This this, I have a:
addObjectToGarbageCollect: anObject
WeakRegistry default add: anObject.
And in DBXConnetion >> connect, I call that method.
Do you know how to solve the problem? I read the issue but I am uncertain what should I do nor if it is fixed. I think this bug is really important.
Not a solution sorry, but a suggestion (or maybe this is already implemented, I haven't used SqueakDBX). :)
Maybe it would be useful to add a pool for the connections so they aren't so many at the same time. Also, the database admin will be grateful.
Cheers
Thanks
Mariano _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing listPharo-project@lists.gforge.inria.frhttp://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
I couldn't reproduce your original error :S. I tested the code in the comments of the issue in an updated 1.2 Core image on windows... I did a 'do it' and a 'debug it' and nothing special happened... Check the comment 3 in this issue http://code.google.com/p/pharo/issues/detail?id=1628 , looking at the code and the comments below that one, I think that's the fix implemented :). 2010/9/1 Mariano Martinez Peck <marianopeck@gmail.com>
2010/9/1 Henrik Sperre Johansen <henrik.s.johansen@veloxit.no>
The error no free space in set should be fixed in 1.1.
Except abysmal performance, what problem do you have exactly?
I am not talking about performance. I am talking that it just raise that error.
What I do particulary in SqueakDBX (it is optional thus) is that when a Connection is created, it is added to WeakRegistry default so that I can implement #finalize and this method releases the database connection if it was not already done.
This is for possible bugs or developers where they don't cal correctly yhe#disconnect method. Of course, if you use the pool you won't have this problem (depending how many connections you define in the pool as max). Anyway, while running tests, I create a lot of connections, thus, I get the error "There is no free space in this set!'" when the code tries to add the connection to the WeakRegistry.
Thanks Henry.
mariano
Cheers, Henry
On 01.09.2010 16:41, Mariano Martinez Peck wrote:
So....any helpers?
http://code.google.com/p/pharo/issues/detail?id=2551 http://code.google.com/p/pharo/issues/detail?id=1628
I would like to help, but I am 100% newbie in this. Please consider me as tester.
Cheers
mariano
2010/8/5 Miguel Enrique Cobá MartÃnez <miguel.coba@gmail.com>
El jue, 05-08-2010 a las 21:35 +0200, Mariano Martinez Peck escribió:
I know this is a alraedy known issue: http://code.google.com/p/pharo/issues/detail?id=1628 I am trying to make SqueakDBX work in 1.1 and it doesn't work because of this. Each DBXConnection is registered in the WeakRegistry just to close the database connection in case they don't do it explicitly.
This this, I have a:
addObjectToGarbageCollect: anObject
WeakRegistry default add: anObject.
And in DBXConnetion >> connect, I call that method.
Do you know how to solve the problem? I read the issue but I am uncertain what should I do nor if it is fixed. I think this bug is really important.
Not a solution sorry, but a suggestion (or maybe this is already implemented, I haven't used SqueakDBX). :)
Maybe it would be useful to add a pool for the connections so they aren't so many at the same time. Also, the database admin will be grateful.
Cheers
Thanks
Mariano _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing listPharo-project@lists.gforge.inria.frhttp://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
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
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
participants (6)
-
Guillermo Polito -
Henrik Sperre Johansen -
Mariano Martinez Peck -
Miguel Enrique Cobá MartÃnez -
Panu Suominen -
Stéphane Ducasse