I did a "cvs up -d" in cocoon-2.1 on January 28, followed by a
"build clean" and "build".  When I tried to run this with a full
installation of Jetty (4.2.11) it produced "Address already in use"
errors.  It had been working fine for several months before this.

After an upgrade to Jetty 4.2.17 the error remains the same.  This is
really puzzling because using the bundled Jetty with "cocoon servlet"
does not produce any errors, and running the full Jetty without Cocoon
also does not produce errors.

Any clues?
--Tim Larson

Reply via email to