Hi Adrian,
I did open both images with the same VM.�� I am sure this must be the problem then.� As I said in one of the mails, the problem in my case went away when I bounced all the images.
It only happens in the Mac VM then?
Do we need to report this bug somewhere or is it already reported?
Cheers
r
Did you open another image with the same VM? There is a wired behavior of the Mac VM that makes the second image listen on the same ports as the already running image. This may (or may not) be related.
See http://lists.squeakfoundation.org/pipermail/vm-dev/2009-June/002726.html
Adrian
On Oct 11, 2009, at 17:18 , Ramiro Diaz Trepat wrote:
Robert, can you see your port still listening with this command ?
sudo lsof -i -P | grep -i listen
On Sun, Oct 11, 2009 at 3:53 PM, Ramiro Diaz Trepat
<ramiro@diaztrepat.name>wrote:
Ah, if Robert still has an image with the issue and if he does not mind
giving it away for autopsy, maybe someone could look at it :)May be John
Macintosh can help us.
On Sun, Oct 11, 2009 at 3:49 PM, Robert Sirois <watchlala@hotmail.com>wrote:
now. <http://clk.atdmt.com/GBL/go/177141664/direct/01/>I'm running the latest mac vm as well. I believe I attempted the same
things to no avail.
RS
Date: Sun, 11 Oct 2009 16:39:37 +0200
Subject: Re: [Seaside] Komanche ?happened
From: renggli@gmail.com
To: seaside@lists.squeakfoundation.org
I use the same configuration with the 4.1.1beta2U VM.
Lukas
2009/10/11 Ramiro Diaz Trepat <ramiro@diaztrepat.name>:
Correlation does not mean causality, I know. �But in my case this
ramiro@diaztrepat.name>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 <
ScriptLoaderwrote:
Hi Lukas,
I am using the latest Pharo, and I have loaded Seaside with
believeloadSeaside30. I am using it on a Mac with Leopard.
I have managed to reuse that port, with random tests and I do not
closingthere 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
when Ithe image and restarting and it did not fix the problem. �Although
are youclosed 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,
wealso running on a mac?
In spite I got the image working again, it is quite worring because
thedon't know the cause when an image stops answering requests (although
weirdimage itself was not hanged at all and kept working fine), and, most
reallyof all, there is no exception or trace of a fault happening. �This is
neverwhat is making me wonder if it is not a low level socket issue that
Seasidegets 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
watchlala@hotmail.com>issue.
On Sun, Oct 11, 2009 at 12:13 PM, Robert Sirois <
two. Iwrote:
I'm using Pharo 1.0.10419, but I'm not sure how to check the other
foundthink 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
atany 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
portsome
point, Komanche stops answering anything at all, althought the
fromkeeps
listening (as listed on a terminal).
No errors are displayed anywere but the port becomes unusable
andthat
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
errorremoving
the adaptor and adding a new one.
I am not even sure that this is a Komanche issue, as I said no
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seasideof
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
up
________________________________
Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. Sign
now.
_______________________________________________
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
------------------------------
Hotmail: Trusted email with Microsoft�s powerful SPAM protection. Sign up
_______________________________________________
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
_______________________________________________
seaside mailing list
seaside@lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside