Cog VM doesn't start to listen on socket
Locked
Cog VM doesn't start to listen on socket
 
|
Hi Eliot,
I noticed that on the Cog VM the Kom Seaside server does not automatically start to listen, even if there is a process waiting at the semaphore of the socket. Singaling that semaphore from the process browser fixes the problem and the Cog image is fully working until the next time it is opened. The exact same image opened with an old VM does not show the problem and immediately starts to listen by itself. Did anybody else notice the same problem? Anybody found a solution? Lukas -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
Hi Lukas,
I'm using Pharo 1.1 + Cog (04/10/2010) + Seaside 3 and haven't that problem. I started Kom (WAKom startOn: 9090) once and when I open my image it start automatically all times.
Facundo ps: I'm using Windows 7.
On Tue, Oct 26, 2010 at 9:04 AM, Lukas Renggli <[hidden email]> wrote: Hi Eliot, _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Fwd: Cog VM doesn't start to listen on socket
|
|
In reply to this post by Lukas Renggli
---------- Forwarded message ---------- From: Eliot Miranda <[hidden email]> Date: Tue, Oct 26, 2010 at 10:23 AM Subject: Re: Cog VM doesn't start to listen on socket To: Lukas Renggli <[hidden email]> Hi Lukas,
obviously we use sockets intensively in Teleplace and we see no problems that are to do with Cog. But Cog does throw up timing issues in your code because it has very different performance to the base VM (Smalltalk code is faster, most primitives have the same speed, allocation is slightly faster, etc). So my gut feeling is that what you're seeing is a timing related issue (race condition?) that is revealed when on Cog and hidden when on the normal VM.
HTH (yeah, right... ed.) Eliot
On Tue, Oct 26, 2010 at 5:04 AM, Lukas Renggli <[hidden email]> wrote: Hi Eliot, _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: Fwd: Cog VM doesn't start to listen on socket
|
|
Thank you Eliot for the answer. I will have to investigate and see if
this is a Seaside specific issue or related to Kom. Lukas 2010/10/26 Eliot Miranda <[hidden email]>: > > > ---------- Forwarded message ---------- > From: Eliot Miranda <[hidden email]> > Date: Tue, Oct 26, 2010 at 10:23 AM > Subject: Re: Cog VM doesn't start to listen on socket > To: Lukas Renggli <[hidden email]> > > > Hi Lukas, > obviously we use sockets intensively in Teleplace and we see no problems > that are to do with Cog. But Cog does throw up timing issues in your code > because it has very different performance to the base VM (Smalltalk code is > faster, most primitives have the same speed, allocation is slightly faster, > etc). So my gut feeling is that what you're seeing is a timing related > issue (race condition?) that is revealed when on Cog and hidden when on the > normal VM. > HTH (yeah, right... ed.) > Eliot > > On Tue, Oct 26, 2010 at 5:04 AM, Lukas Renggli <[hidden email]> wrote: >> >> Hi Eliot, >> >> I noticed that on the Cog VM the Kom Seaside server does not >> automatically start to listen, even if there is a process waiting at >> the semaphore of the socket. Singaling that semaphore from the process >> browser fixes the problem and the Cog image is fully working until the >> next time it is opened. >> >> The exact same image opened with an old VM does not show the problem >> and immediately starts to listen by itself. >> >> Did anybody else notice the same problem? Anybody found a solution? >> >> Lukas >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch > > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: Fwd: Cog VM doesn't start to listen on socket
|
|
Ok, I think I solved the issue. Restarting the server on startup seems
to solve the problem on all my machines. Thanks again for the hints! Lukas On 26 October 2010 20:41, Lukas Renggli <[hidden email]> wrote: > Thank you Eliot for the answer. I will have to investigate and see if > this is a Seaside specific issue or related to Kom. > > Lukas > > 2010/10/26 Eliot Miranda <[hidden email]>: >> >> >> ---------- Forwarded message ---------- >> From: Eliot Miranda <[hidden email]> >> Date: Tue, Oct 26, 2010 at 10:23 AM >> Subject: Re: Cog VM doesn't start to listen on socket >> To: Lukas Renggli <[hidden email]> >> >> >> Hi Lukas, >> obviously we use sockets intensively in Teleplace and we see no problems >> that are to do with Cog. But Cog does throw up timing issues in your code >> because it has very different performance to the base VM (Smalltalk code is >> faster, most primitives have the same speed, allocation is slightly faster, >> etc). So my gut feeling is that what you're seeing is a timing related >> issue (race condition?) that is revealed when on Cog and hidden when on the >> normal VM. >> HTH (yeah, right... ed.) >> Eliot >> >> On Tue, Oct 26, 2010 at 5:04 AM, Lukas Renggli <[hidden email]> wrote: >>> >>> Hi Eliot, >>> >>> I noticed that on the Cog VM the Kom Seaside server does not >>> automatically start to listen, even if there is a process waiting at >>> the semaphore of the socket. Singaling that semaphore from the process >>> browser fixes the problem and the Cog image is fully working until the >>> next time it is opened. >>> >>> The exact same image opened with an old VM does not show the problem >>> and immediately starts to listen by itself. >>> >>> Did anybody else notice the same problem? Anybody found a solution? >>> >>> Lukas >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: Fwd: Cog VM doesn't start to listen on socket
|
|
So, you always have to pass a script that restarts the server? This sounds like a workaround, right?
Cheers, Doru On 26 Oct 2010, at 21:48, Lukas Renggli wrote: > Ok, I think I solved the issue. Restarting the server on startup seems > to solve the problem on all my machines. > > Thanks again for the hints! > > Lukas > > On 26 October 2010 20:41, Lukas Renggli <[hidden email]> wrote: >> Thank you Eliot for the answer. I will have to investigate and see if >> this is a Seaside specific issue or related to Kom. >> >> Lukas >> >> 2010/10/26 Eliot Miranda <[hidden email]>: >>> >>> >>> ---------- Forwarded message ---------- >>> From: Eliot Miranda <[hidden email]> >>> Date: Tue, Oct 26, 2010 at 10:23 AM >>> Subject: Re: Cog VM doesn't start to listen on socket >>> To: Lukas Renggli <[hidden email]> >>> >>> >>> Hi Lukas, >>> obviously we use sockets intensively in Teleplace and we see no problems >>> that are to do with Cog. But Cog does throw up timing issues in your code >>> because it has very different performance to the base VM (Smalltalk code is >>> faster, most primitives have the same speed, allocation is slightly faster, >>> etc). So my gut feeling is that what you're seeing is a timing related >>> issue (race condition?) that is revealed when on Cog and hidden when on the >>> normal VM. >>> HTH (yeah, right... ed.) >>> Eliot >>> >>> On Tue, Oct 26, 2010 at 5:04 AM, Lukas Renggli <[hidden email]> wrote: >>>> >>>> Hi Eliot, >>>> >>>> I noticed that on the Cog VM the Kom Seaside server does not >>>> automatically start to listen, even if there is a process waiting at >>>> the semaphore of the socket. Singaling that semaphore from the process >>>> browser fixes the problem and the Cog image is fully working until the >>>> next time it is opened. >>>> >>>> The exact same image opened with an old VM does not show the problem >>>> and immediately starts to listen by itself. >>>> >>>> Did anybody else notice the same problem? Anybody found a solution? >>>> >>>> Lukas >>>> >>>> -- >>>> Lukas Renggli >>>> www.lukas-renggli.ch >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [hidden email] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Sometimes the best solution is not the best solution." _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: Fwd: Cog VM doesn't start to listen on socket
|
|
No, I fixed it in Kom.
Lukas On 26 October 2010 22:12, Tudor Girba <[hidden email]> wrote: > So, you always have to pass a script that restarts the server? This sounds like a workaround, right? > > Cheers, > Doru > > > On 26 Oct 2010, at 21:48, Lukas Renggli wrote: > >> Ok, I think I solved the issue. Restarting the server on startup seems >> to solve the problem on all my machines. >> >> Thanks again for the hints! >> >> Lukas >> >> On 26 October 2010 20:41, Lukas Renggli <[hidden email]> wrote: >>> Thank you Eliot for the answer. I will have to investigate and see if >>> this is a Seaside specific issue or related to Kom. >>> >>> Lukas >>> >>> 2010/10/26 Eliot Miranda <[hidden email]>: >>>> >>>> >>>> ---------- Forwarded message ---------- >>>> From: Eliot Miranda <[hidden email]> >>>> Date: Tue, Oct 26, 2010 at 10:23 AM >>>> Subject: Re: Cog VM doesn't start to listen on socket >>>> To: Lukas Renggli <[hidden email]> >>>> >>>> >>>> Hi Lukas, >>>> obviously we use sockets intensively in Teleplace and we see no problems >>>> that are to do with Cog. But Cog does throw up timing issues in your code >>>> because it has very different performance to the base VM (Smalltalk code is >>>> faster, most primitives have the same speed, allocation is slightly faster, >>>> etc). So my gut feeling is that what you're seeing is a timing related >>>> issue (race condition?) that is revealed when on Cog and hidden when on the >>>> normal VM. >>>> HTH (yeah, right... ed.) >>>> Eliot >>>> >>>> On Tue, Oct 26, 2010 at 5:04 AM, Lukas Renggli <[hidden email]> wrote: >>>>> >>>>> Hi Eliot, >>>>> >>>>> I noticed that on the Cog VM the Kom Seaside server does not >>>>> automatically start to listen, even if there is a process waiting at >>>>> the semaphore of the socket. Singaling that semaphore from the process >>>>> browser fixes the problem and the Cog image is fully working until the >>>>> next time it is opened. >>>>> >>>>> The exact same image opened with an old VM does not show the problem >>>>> and immediately starts to listen by itself. >>>>> >>>>> Did anybody else notice the same problem? Anybody found a solution? >>>>> >>>>> Lukas >>>>> >>>>> -- >>>>> Lukas Renggli >>>>> www.lukas-renggli.ch >>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> [hidden email] >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "Sometimes the best solution is not the best solution." > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: Fwd: Cog VM doesn't start to listen on socket
|
|
Ahh, I see :)
Doru On 26 Oct 2010, at 22:14, Lukas Renggli wrote: > No, I fixed it in Kom. > > Lukas > > On 26 October 2010 22:12, Tudor Girba <[hidden email]> wrote: >> So, you always have to pass a script that restarts the server? This sounds like a workaround, right? >> >> Cheers, >> Doru >> >> >> On 26 Oct 2010, at 21:48, Lukas Renggli wrote: >> >>> Ok, I think I solved the issue. Restarting the server on startup seems >>> to solve the problem on all my machines. >>> >>> Thanks again for the hints! >>> >>> Lukas >>> >>> On 26 October 2010 20:41, Lukas Renggli <[hidden email]> wrote: >>>> Thank you Eliot for the answer. I will have to investigate and see if >>>> this is a Seaside specific issue or related to Kom. >>>> >>>> Lukas >>>> >>>> 2010/10/26 Eliot Miranda <[hidden email]>: >>>>> >>>>> >>>>> ---------- Forwarded message ---------- >>>>> From: Eliot Miranda <[hidden email]> >>>>> Date: Tue, Oct 26, 2010 at 10:23 AM >>>>> Subject: Re: Cog VM doesn't start to listen on socket >>>>> To: Lukas Renggli <[hidden email]> >>>>> >>>>> >>>>> Hi Lukas, >>>>> obviously we use sockets intensively in Teleplace and we see no problems >>>>> that are to do with Cog. But Cog does throw up timing issues in your code >>>>> because it has very different performance to the base VM (Smalltalk code is >>>>> faster, most primitives have the same speed, allocation is slightly faster, >>>>> etc). So my gut feeling is that what you're seeing is a timing related >>>>> issue (race condition?) that is revealed when on Cog and hidden when on the >>>>> normal VM. >>>>> HTH (yeah, right... ed.) >>>>> Eliot >>>>> >>>>> On Tue, Oct 26, 2010 at 5:04 AM, Lukas Renggli <[hidden email]> wrote: >>>>>> >>>>>> Hi Eliot, >>>>>> >>>>>> I noticed that on the Cog VM the Kom Seaside server does not >>>>>> automatically start to listen, even if there is a process waiting at >>>>>> the semaphore of the socket. Singaling that semaphore from the process >>>>>> browser fixes the problem and the Cog image is fully working until the >>>>>> next time it is opened. >>>>>> >>>>>> The exact same image opened with an old VM does not show the problem >>>>>> and immediately starts to listen by itself. >>>>>> >>>>>> Did anybody else notice the same problem? Anybody found a solution? >>>>>> >>>>>> Lukas >>>>>> >>>>>> -- >>>>>> Lukas Renggli >>>>>> www.lukas-renggli.ch >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> [hidden email] >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>>> >>>> >>>> -- >>>> Lukas Renggli >>>> www.lukas-renggli.ch >>>> >>> >>> >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [hidden email] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> www.tudorgirba.com >> >> "Sometimes the best solution is not the best solution." >> >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding." _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
«
Return to Pharo Smalltalk Developers
|
1 view|%1 views
| Free forum by Nabble | Edit this page |