To add to this hard to reproduce issue, it only happens in production (where if not?) when running within a Docker Swarm where PostgreSQL is inside the Swarm, so there might be something there fiddling with the network, or I don't know really :-/
Regards. Esteban A. Maringolo On Mon, Aug 10, 2020 at 4:15 PM Esteban Maringolo <emaring...@gmail.com> wrote: > > Hi all, Sven ;-) > > I'm having erratic P3 errors in a recent application I wrote using > Pharo, Seaside and Glorp with P3 as driver. > > Each Seaside session has a GlorpSession, which in turn has a > P3Connection in its accessor. I don't know why, but sometimes the > P3Connection socket is closed, and then when trying to read from the > database, it cannot write the query to the P3 socket and exception is > raised, and it isn't handled by the P3DatabaseDriver (automatically > trying to reconnect?). > > I don't know if I'm doing something wrong, I plan to migrate the > GlorpPooledDatabaseAccessor and also use the P3ConnectionPool, but I > want to be sure that the current setup works of if maybe I'm exceeding > some limit or timeout that causes the connection to be closed. > > Regards! > > > Esteban A. Maringolo
