Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

+1 and I like when this is not Pharo the problem :) S. > On 21 Aug 2020, at 08:24, Sven Van Caekenberghe wrote: > > Hi Esteban, > > That is good to hear ! > > Sven > >> On 20 Aug 2020, at 23:36, Esteban Maringolo wrote: >> >> Hi all, >> >> On Thu, Aug 20, 2020 at 3:02 PM Sven Van Caekenbe

Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

Hi Esteban, That is good to hear ! Sven > On 20 Aug 2020, at 23:36, Esteban Maringolo wrote: > > Hi all, > > On Thu, Aug 20, 2020 at 3:02 PM Sven Van Caekenberghe wrote: > I don't know what is going on inside Socket, I just stated my opinion. >>> Maybe there is something to investigate

Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

Hi all, Good news. :-) On Thu, Aug 20, 2020 at 6:36 PM Esteban Maringolo wrote: > > Is it not so that in Docker all network connections in/out/between > > instances are mediated by some management software ? > > I even thought it was nginx. Maybe I am totally wrong here. > > No, it is not that

Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

Hi all, On Thu, Aug 20, 2020 at 3:02 PM Sven Van Caekenberghe wrote: > >> I don't know what is going on inside Socket, I just stated my opinion. > > Maybe there is something to investigate here? > Is it not so that in Docker all network connections in/out/between instances > are mediated by so

Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

HI guys let us know if we have to do something from our side because we want to support business. S. > On 20 Aug 2020, at 20:01, Sven Van Caekenberghe wrote: > > > >> On 20 Aug 2020, at 19:51, Esteban Maringolo > > wrote: >> >> Hi, >> >> I'm replying to the

Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

> On 20 Aug 2020, at 19:51, Esteban Maringolo wrote: > > Hi, > > I'm replying to the list as well... because the last two mails got > replied to our personal addresses. Oh, I did not notice that, that was not my intention. > On Thu, Aug 20, 2020 at 11:55 AM Sven Van Caekenberghe wrote: >>>

Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

Hi, I'm replying to the list as well... because the last two mails got replied to our personal addresses. On Thu, Aug 20, 2020 at 11:55 AM Sven Van Caekenberghe wrote: > > On 20 Aug 2020, at 15:31, Esteban Maringolo wrote: > > > > Hi Sven, > > > > If a socketstream doesn't know the state of the

Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

IIUC a socket stream does not automatically/automagically know that the state of the connection changed, unless/until it tries to use it (read or write to it, wait for data, ...). I would recommend using #isWorking to actually test if a connection is good, if you would need to do that. That doe

Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

I kept looking into this, and still haven't found what might be causing it. However, I was trying to "salvage" that until I find a solution, and run a "healthcheck" to be sure that the GlorpSession has an active connection, and then I found that a P3Client reports as connected even when it's not.

Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

Looking at the Postgres side of the log I find that the connection was reset from the other side (it is Pharo). The reason for that is yet unknown to me. Since I don't do anything (that I'm aware of). golfware_database.1.9sl4bt9j6cv5@gw| 2020-08-10 20:02:35.939 UTC [132] LOG: could not recei

Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

My Seaside session isn't closing the connection, only when unregistered, but this seems to be something else I don't know. I saw there is logging, and I need to set it up in general (including Fuel serialized stacks). Looking in the web apparently there is the need for a keepalive that is not in p

Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

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, 202

Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

Hi Esteban, I have a web app with P3 under Seaside in production and it works fine. But that is without Glorp, nor any connection pooling. You say the connection seems closed, maybe the closing got triggered by your app somehow ? How do you clean up expired sessions ? How do you handle logouts

[Pharo-users] CannotWriteData errors in P3 and Seaside

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 wh