[jetty-dev] [jira] (JETTY-1544) The packaged jetty-setuid.xml file uses the id "Server" for its Configure element, causing a ClassCastException

Jan Bartel
commented on JETTY-1544

The packaged jetty-setuid.xml file uses the id "Server" for its Configure element, causing a ClassCastException

Ido,

The problem appears to be that when using "/etc/init.d/jetty start", the command line produced is:

"/usr/lib/jvm/jdk1.7/bin/java -Djetty.home=/opt/jetty -Djava.io.tmpdir=/tmp -jar /opt/jetty/start.jar --pre=etc/jetty-logging.xml --daemon"

This puts etc/jetty-logging.xml first onto the command line, which creates an instance of Server that is org.eclipse.jetty.server.Server. Thus, when etc/jetty-setuid.xml is executed, it cannot cast that to be org.mortbay.jetty.setuid.SetUIDServer.

I think the solution for you is to insert "-pre=etc/jetty-setuid.xml" into /etc/init.d/jetty script before the "-pre=etc/jetty-logging.xml" (and make sure you take etc/jetty-setuid.xml out of your start.ini).

Alternatively, you could remove the "--pre=etc/jetty-logging.xml" from the init.d script, and instead add etc/jetty-logging.xml after etc/jetty-setuid.xml.

I will document this on the wiki.

Note: in previous releases where the id was incorrectly "org.eclipse.jetty.server.Server", the jetty-setuid.xml file would have been incorrectly creating a second Server instance and applying the setuid configuration to it. Thus I believe the jetty server instance created by the etc/jetty-logging.xml file with id Server would have in fact continued to run as root.

Jan

This message is automatically generated by JIRA.

If you think it was sent incorrectly, please contact your JIRA administrators .

For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email