Jetty

Starting jetty from cygwin is not working properly

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 7.0.2, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.2.0, 7.2.2, 8.0.0.M0, 8.0.0.M1
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    Windows XP, cygwin, Java 1.6.023
  • Number of attachments :
    0

Description

Starting jetty from cygwin is not working for all version 7.x and 8.x. Latest version where this was working is 6.1.26.

When you starting from cygwin jetty launched and listen to specified port, but none of servlets are deployed, even test servlets.

xxx@xxx /cygdrive/c/opt/jetty/bin
$ ./jetty-cygwin.sh start
** WARNING: Cannot read '--pre=etc/jetty-logging.xml' specified in '/cygdrive/c/
opt/jetty/etc/jetty.conf'
C:\opt\jetty\start.jar
C:\opt\jetty\etc\jetty-logging.xml C:\opt\jetty\etc\jetty.xml
Starting Jetty: STARTED Jetty Tue Feb 22 17:59:36 FLEST 2011

xxx@xxx /cygdrive/c/opt/jetty/bin
$ 2011-02-22 17:59:36.500:INFO::Redirecting stderr/stdout to C:\opt\jetty\logs\2011_02_22.stderrout.log

accessing localhost:8080 gives:

Error 404 - Not Found.

No context on this server matched or handled this request.
Contexts known to this server are:

log

2011-02-22 17:39:45.156:INFO::jetty-8.0.0.M2
2011-02-22 17:39:45.218:INFO::Started SelectChannelConnector@0.0.0.0:8080

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jan Bartel added a comment -

Joakim,

Can you take a look into this, as ISTR that you were looking at the startup scripts recently? If not, can you assign to who is?

thanks
Jan

Show
Jan Bartel added a comment - Joakim, Can you take a look into this, as ISTR that you were looking at the startup scripts recently? If not, can you assign to who is? thanks Jan
Hide
Permalink
Mark Laffoon added a comment -

We have this problem as well. The only workaround we've found is to write our own jetty.sh script which, instead of setting a bunch of path variables, moves to the root jetty folder and executes from there. So the script does a pushd $JETTY_HOME at some point and the command line looks more like this (lots of -X options omitted for clarity):

/usr/local/java/jre/bin/java.exe -Djetty.home=. -Djetty.logs=./logs -Djava.io.tmpdir=./work -jar ./start.jar

Not a fix, but it might allow some people to move forward.

Show
Mark Laffoon added a comment - We have this problem as well. The only workaround we've found is to write our own jetty.sh script which, instead of setting a bunch of path variables, moves to the root jetty folder and executes from there. So the script does a pushd $JETTY_HOME at some point and the command line looks more like this (lots of -X options omitted for clarity): /usr/local/java/jre/bin/java.exe -Djetty.home=. -Djetty.logs=./logs -Djava.io.tmpdir=./work -jar ./start.jar Not a fix, but it might allow some people to move forward.
Hide
Permalink
Jan Bartel added a comment -

This issue has been moved across to jetty eclipse bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=396572

Show
Jan Bartel added a comment - This issue has been moved across to jetty eclipse bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=396572

People

  • Assignee:
    Joakim Erdfelt
    Reporter:
    Kirill Stokoz
Vote (1)
Watch (3)

Dates

  • Created:
    Updated:
    Resolved: