Hi Lukas,I am using the latest Pharo, and I have loaded Seaside with ScriptLoader loadSeaside30. I am using it on a Mac with Leopard. I have managed to reuse that port, with random tests and I do not believe there may be causality here, but I will tell you anyway what I did. When this happens, I removed the problematic adaptor from the Seaside Control Panel and created a new one (on the same port), then I tried closing the image and restarting and it did not fix the problem. Although when I closed another non Seaside image I was running and then restarted the problematic image it worked. I wonder now if it is not a mac vm issue or socket issue. Robert, are you also running on a mac? In spite I got the image working again, it is quite worring because we don't know the cause when an image stops answering requests (although the image itself was not hanged at all and kept working fine), and, most weird of all, there is no exception or trace of a fault happening. This is really what is making me wonder if it is not a low level socket issue that never gets to the image for it to throw an exception or anything at all. Cheers r ps: I'm cross posting to Pharo because I believe this is not a Seaside issue. On Sun, Oct 11, 2009 at 12:13 PM, Robert Sirois <watchlala@hotmail.com>wrote:
I'm using Pharo 1.0.10419, but I'm not sure how to check the other two. I think I'm still running 2.9 in the image I checked.
RS
Date: Sun, 11 Oct 2009 12:30:37 +0200 Subject: Re: [Seaside] Komanche ? From: renggli@gmail.com To: seaside@lists.squeakfoundation.org
I've never seen this problem before.
What version of Pharo? Kom? Seaside?
Lukas
2009/10/11 Robert Sirois <watchlala@hotmail.com>:
I've also had this problem for quite a while now and have not found any
way to fix the problem either.
RS
Ramiro Diaz Trepat <ramiro@diaztrepat.name> wrote:
Something really strange happened to me more than once now.In a simple
dev
image (Pharo + Seaside3 + Kom on a Mac) after saving the image at some point, Komanche stops answering anything at all, althought the port keeps listening (as listed on a terminal). No errors are displayed anywere but the port becomes unusable from that point on. If I wish to continue using the same image I have to add another adaptor in the Seaside Control Panel and start again. The "dead" ports never become usable again, not even stopping and removing the adaptor and adding a new one. I am not even sure that this is a Komanche issue, as I said no error of anykind is visible. Has anyone come across this before? _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
------------------------------ Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. Sign up now. <http://clk.atdmt.com/GBL/go/171222985/direct/01/>
_______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Correlation does not mean causality, I know. But in my case this happened right after saving my image, although I had saved it many times before without issues.Cheers On Sun, Oct 11, 2009 at 3:01 PM, Ramiro Diaz Trepat <ramiro@diaztrepat.name>wrote:
Hi Lukas,I am using the latest Pharo, and I have loaded Seaside with ScriptLoader loadSeaside30. I am using it on a Mac with Leopard. I have managed to reuse that port, with random tests and I do not believe there may be causality here, but I will tell you anyway what I did. When this happens, I removed the problematic adaptor from the Seaside Control Panel and created a new one (on the same port), then I tried closing the image and restarting and it did not fix the problem. Although when I closed another non Seaside image I was running and then restarted the problematic image it worked. I wonder now if it is not a mac vm issue or socket issue. Robert, are you also running on a mac? In spite I got the image working again, it is quite worring because we don't know the cause when an image stops answering requests (although the image itself was not hanged at all and kept working fine), and, most weird of all, there is no exception or trace of a fault happening. This is really what is making me wonder if it is not a low level socket issue that never gets to the image for it to throw an exception or anything at all. Cheers
r
ps: I'm cross posting to Pharo because I believe this is not a Seaside issue.
On Sun, Oct 11, 2009 at 12:13 PM, Robert Sirois <watchlala@hotmail.com>wrote:
I'm using Pharo 1.0.10419, but I'm not sure how to check the other two. I think I'm still running 2.9 in the image I checked.
RS
Date: Sun, 11 Oct 2009 12:30:37 +0200 Subject: Re: [Seaside] Komanche ? From: renggli@gmail.com To: seaside@lists.squeakfoundation.org
I've never seen this problem before.
What version of Pharo? Kom? Seaside?
Lukas
2009/10/11 Robert Sirois <watchlala@hotmail.com>:
I've also had this problem for quite a while now and have not found
any way to fix the problem either.
RS
Ramiro Diaz Trepat <ramiro@diaztrepat.name> wrote:
Something really strange happened to me more than once now.In a simple
dev
image (Pharo + Seaside3 + Kom on a Mac) after saving the image at some point, Komanche stops answering anything at all, althought the port keeps listening (as listed on a terminal). No errors are displayed anywere but the port becomes unusable from that point on. If I wish to continue using the same image I have to add another adaptor in the Seaside Control Panel and start again. The "dead" ports never become usable again, not even stopping and removing the adaptor and adding a new one. I am not even sure that this is a Komanche issue, as I said no error of anykind is visible. Has anyone come across this before? _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
------------------------------ Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. Sign up now. <http://clk.atdmt.com/GBL/go/171222985/direct/01/>
_______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
participants (1)
-
Ramiro Diaz Trepat