[Pharo-project] Kom not starting in Pharo-web image
bschwab at anest.ufl.edu
Fri Jul 31 17:00:12 CEST 2009
It appears to be a known problem. I reported it here, and (too lazy to check on who<g>) somebody pointed to some similar traffic on the Seaside list. There I saw things like "none of us noticed because we are all using the new conrol panel." See for example, the "MNU after clean install..." thread from 22-24 Jul. They also mention problems I do not recognize, but seems related.
From: pharo-project-bounces at lists.gforge.inria.fr [mailto:pharo-project-bounces at lists.gforge.inria.fr] On Behalf Of Adrian Lienhard
Sent: Friday, July 31, 2009 6:42 AM
To: Pharo Development
Subject: [Pharo-project] Kom not starting in Pharo-web image
In the latest Pharo-web image on startup HttpService complains that
'a service is already running on port 8080' (stack trace attached).
Damien said he loaded the latest versions of Seaside/Kom from SqueakSource.
If I do "WAKomEncoded startOn: 8080" and restart the image, it works.
Is this a known problem and if not, what would be the right place to report it? On the Seaside bug tracker?
More information about the Pharo-project