Re: M5 startup without changing configs causes 'port-in-use' trouble

[Kevan Miller]

I haven't seen any discussion on this. Where do things stand? Personally, I don't see how we can keep an installer with this behavior available for download. Users have a very reasonable expectation to launch, accept default settings, and have a running server. Is changing the default Tomcat ports an option? Or making Tomcat/Jetty mutually exclusive unless explicitly specified?

--kevan

On 10/5/05, Stefan Schmidt <[EMAIL PROTECTED]> wrote:

Hi,

I installed the new M5 with the installer (all options selected) and
started the server without any changes to the configs. This (of course -
silly me) caused heaps of 'port already in use' exceptions for 8080 and
8443. Running G on either Tomcat or Jetty configs (or both with seperate
ports) works fine though.

My problem with this that new users might not be aware of this and think
that the distrobution ships broken. Is there any chance to change M5 to
either different port settings for Tomcat/Jetty or have only one running
by default?

Regards,
Stefan Schmidt