I recommend to update to the last commit I did...

Otherwise, if you were using different instances of Login for each session you should have several SelmaConnectionPool alive :) (rather than 1)

On Sat, Jul 6, 2013 at 5:54 PM, Facundo Vozzi <facundov79@gmail.com> wrote:

Thanks Esteban.

Now, I changed GlorpOpenDBXPoolingDriver for GlorpOpenDBXDriver and all is working properly. I'll try to fix the problem because I think that will be a problem the number of postgres.exe process running on the server this way.

On Sat, Jul 6, 2013 at 5:36 PM, Esteban Lorenzano <estebanlm@gmail.com> wrote:

On Jul 6, 2013, at 7:15 PM, Facundo Vozzi <facundov79@gmail.com> wrote:

Hi,

I migrated my small app from Pharo 1.3 to Pharo 2.0. I'm using DBXTalk and GlorpDBX.

It's working perfectly on my notebook (Windows 7 64 bits and postgreSql 9.1) but on my server (Windows 2003 32 bits server and postgreSql 9.0) I'm getting this error at OpenDBXWin32 level with 3 simultaneus connections:�'FATAL: �lo siento, ya tenemos demasiados clientes'.

It's strange (for me) because the version on Pharo 1.3 works properly in both machines but the version on Pharo 2.0 works perfect on my notebook and works properly for the first two connections on the server.

I think that could be a problem with the OpenDBX library with the server and the implementation of FFI on Pharo 2.0 but I can't figure out it.

Any suggestions?

Thanks in advance,

Facundo

p.s.: where is hosted the DBXTalk project now? I can't find it on�http://dbxtalk.smallworks.com.ar/�anymore

sorry, I'm changing servers and the DNS is not well refreshed yet...�

however, you can find it here:�

http://dbxtalk.smallworks.eu

<Error on the third connection attempt.txt>

--
Mariano
http://marianopeck.wordpress.com