Jetty Server總是使用Handler返回404

Question

我正在研究一個項目，我正在嘗試創建一個服務器，監聽端口8082上的本地主機地址（我已經預留了8081與另一台服務器）

 public class Class2HTTPServer {
    public static void main(String[] args) {
        Class1 object1= new Class1 (300);// parameter I need for other stuff
        Class2 object2= new Class2 (300,object1,5); // parameters for other unrelated stuff
        int listen_on_port = 8082;
        Class2HTTPMessageHandler handler = new Class2HTTPMessageHandler (
            object2);
        String server_port_string = System.getProperty(SystemConstants.PROPERTY_KEY_SERVER_PORT);
        if(server_port_string != null) {
            try {
                listen_on_port = Integer.parseInt(server_port_string);
                listen_on_portfs = Integer.parseInt(server_port_string);
            } catch(NumberFormatException ex) {
                System.err.println(ex);
            }
        }
        ComponentHTTPServerUtility.createServer(listen_on_port, handler);

    }
}

這是ComponentHTTPServerUtility類：

import java.net.InetAddress;
import java.net.InetSocketAddress;
import java.net.UnknownHostException;
import org.eclipse.jetty.server.Server;
import org.eclipse.jetty.server.handler.AbstractHandler;

public class ComponentHTTPServerUtility {
    /**
     * Creates a server on the port and blocks the calling thread
     * @param port
     * @param handler
     * @return 
     */
    public static boolean createServer(int port, AbstractHandler handler) {
        Server server = new Server(port);
        if (handler != null) {
            server.setHandler(handler);
        }

        try {
            server.start();
            server.join();
        } catch (Exception ex) {
            ex.printStackTrace();
        }
        return true;
    }

    /**
     * Creates a server on the InetAddress and blocks the calling thread
     * @param ipAddress
     * @param port
     * @param handler
     * @return 
     */
    public static boolean createServer(String ipAddress, int port,
            AbstractHandler handler) {
        InetAddress inetIpAddress;
        InetSocketAddress address;
        Server server;

        if (ipAddress == null)
            return false;

        try {
            inetIpAddress = InetAddress.getByName(ipAddress);
            address = new InetSocketAddress(inetIpAddress, port);
        } catch (UnknownHostException ex) {
            ex.printStackTrace();
            return false;
        }

        server = new Server(address);
        if (handler != null) {
            server.setHandler(handler);
        }

        try {
            server.start();
            server.join();
        } catch (Exception ex) {
            ex.printStackTrace();
        }
        return true;
    }
}

當我運行服務器時，我在控制台中收到以下消息：

2015-01-19 13:13:49.451:INFO:oejs.Server:jetty-8.1.13.v20130916
2015-01-19 13:13:49.501:INFO:oejs.AbstractConnector:Started SelectChannelConnector@0.0.0.0:8082

但是，如果我使用我的瀏覽器： http：// localhost：8082 /

我得到錯誤404.但是，如果我對其他服務器（端口8081）執行相同操作，我會得到一個空白頁面，表明服務器正在運行。

對不起，但我不能進一步具體。 任何想法或建議將受到高度贊賞。 我被困在這幾個小時。

謝謝

編輯：

這些是我在插入行后獲得的兩個服務器的結果：

通信System.err.println（server.dump（））;

工作一：

2015-01-19 15:37:05.600:INFO:oejs.Server:jetty-8.1.13.v20130916
2015-01-19 15:37:05.651:INFO:oejs.AbstractConnector:Started SelectChannelConnector@0.0.0.0:8081
org.eclipse.jetty.server.Server@2090b38d - STARTED
 +- com.project.server.Class1HTTPMessageHandler@35f3198f - STARTED
 |
 +- qtp831407528{8<=6<=8/254,0} - STARTED
 |   +- 10 qtp831407528-10 TIMED_WAITING @ sun.misc.Unsafe.park(Native Method) IDLE
 |   +- 11 qtp831407528-11 TIMED_WAITING @ sun.misc.Unsafe.park(Native Method) IDLE
 |   +- 12 qtp831407528-12 TIMED_WAITING @ sun.misc.Unsafe.park(Native Method) IDLE
 |   +- 13 qtp831407528-13 TIMED_WAITING @ sun.misc.Unsafe.park(Native Method) IDLE
 |   +- 14 qtp831407528-14 Acceptor0 SelectChannelConnector@0.0.0.0:8081 RUNNABLE @ sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
 |   +- 15 qtp831407528-15 Selector0 RUNNABLE @ sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
 |   +- 16 qtp831407528-16 TIMED_WAITING @ sun.misc.Unsafe.park(Native Method) IDLE
 |   +- 17 qtp831407528-17 TIMED_WAITING @ sun.misc.Unsafe.park(Native Method) IDLE
 |
 +- SelectChannelConnector@0.0.0.0:8081 - STARTED
     +- PooledBuffers [0/1024@6144,0/1024@16384,0/1024@-]/PooledBuffers [0/1024@6144,0/1024@32768,0/1024@-] - STARTED
     +- org.eclipse.jetty.server.nio.SelectChannelConnector$ConnectorSelectorManager@42557280 - STARTED
     |   +- org.eclipse.jetty.io.nio.SelectorManager$SelectSet@77d05385 keys=0 selected=0 id=0
     |       +- org.eclipse.jetty.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:569)
     |       +- sun.nio.ch.WindowsSelectorImpl@4611dca9 keys=0
     +- sun.nio.ch.ServerSocketChannelImpl[/0:0:0:0:0:0:0:0:8081]
     +- qtp831407528{8<=6<=8/254,0} - STARTED

這些來自非工作的：

2015-01-19 15:37:23.231:INFO:oejs.Server:jetty-8.1.13.v20130916
2015-01-19 15:37:23.280:INFO:oejs.AbstractConnector:Started SelectChannelConnector@0.0.0.0:8082
org.eclipse.jetty.server.Server@183c97db - STARTED
 +- com.project.server.Class2HTTPMessageHandler@33767f84     - STARTED
 |
 +- qtp597321988{8<=6<=8/254,0} - STARTED
 |   +- 10 qtp597321988-10 Selector0 RUNNABLE @ sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
 |   +- 11 qtp597321988-11 TIMED_WAITING @ sun.misc.Unsafe.park(Native Method) IDLE
 |   +- 12 qtp597321988-12 TIMED_WAITING @ sun.misc.Unsafe.park(Native Method) IDLE
 |   +- 13 qtp597321988-13 TIMED_WAITING @ sun.misc.Unsafe.park(Native Method) IDLE
 |   +- 14 qtp597321988-14 Acceptor0 SelectChannelConnector@0.0.0.0:8082 RUNNABLE @ sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
 |   +- 15 qtp597321988-15 TIMED_WAITING @ sun.misc.Unsafe.park(Native Method) IDLE
 |   +- 16 qtp597321988-16 TIMED_WAITING @ sun.misc.Unsafe.park(Native Method) IDLE
 |   +- 17 qtp597321988-17 TIMED_WAITING @ sun.misc.Unsafe.park(Native Method) IDLE
 |
 +- SelectChannelConnector@0.0.0.0:8082 - STARTED
     +- PooledBuffers [0/1024@6144,0/1024@16384,0/1024@-]/PooledBuffers [0/1024@6144,0/1024@32768,0/1024@-] - STARTED
     +- org.eclipse.jetty.server.nio.SelectChannelConnector$ConnectorSelectorManager@7f39425c - STARTED
     |   +- org.eclipse.jetty.io.nio.SelectorManager$SelectSet@833e745 keys=0 selected=0 id=0
     |       +- org.eclipse.jetty.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:569)
     |       +- sun.nio.ch.WindowsSelectorImpl@32787e9f keys=0
     +- sun.nio.ch.ServerSocketChannelImpl[/0:0:0:0:0:0:0:0:8082]
     +- qtp597321988{8<=6<=8/254,0} - STARTED

基本的處理程序聲明：

public class Class2HTTPMessageHandler extends AbstractHandler{
     private Class2 object= null;

    public Class2HTTPMessageHandler(Class2 obj){
        object= obj;
    }
    @SuppressWarnings("unchecked")
    public void handle(String target, Request baseRequest,
            HttpServletRequest request, HttpServletResponse response)
            throws IOException, ServletException {
        MessageTag messageTag;

        String  requestURI;
        Response fieldResponse = null;
        response.setContentType("text/html;charset=utf-8");
        response.setStatus(HttpServletResponse.SC_OK);
        requestURI = request.getRequestURI();
        if (!ComponentUtility.isEmpty(requestURI)
                && requestURI.toLowerCase().startsWith("/stock")) {
            messageTag = ComponentUtility.convertURItoMessageTag(requestURI
                .substring(6)); // the request is from store
            // manager, more
            // sophisticated security
            // features could be added
            // here
        } else {
                messageTag = ComponentUtility.convertURItoMessageTag(requestURI);
        }
        // the RequestURI before the switch
        if (messageTag == null) {
                System.out.println("Unknown message tag");
        } else {
            switch (messageTag) {
                // handling of various messages
            }
        }
    }
}

我試圖向服務器發送一個消息標記，這是我得到的異常：

 2015-01-19 18:16:43.739:WARN:oejs.AbstractHttpConnection:/MESSAGETAG
 java.lang.NullPointerException
     at com.project.business.Class2.functionFoo(Class2.java:98)
    at com.project.server.Class2HTTPMessageHandler.handle(Class2HTTPMessageHandler.java:69)
     at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
     at org.eclipse.jetty.server.Server.handle(Server.java:370)
     at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
     at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960)
     at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021)
     at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865)
     at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)
     at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
     at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668)
     at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
     at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
     at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
     at java.lang.Thread.run(Thread.java:745)

Answer 1

使用處理程序時，您必須在處理程序實際處理請求時告知服務器。

不要忘記調用baseRequest.setHandled(true);

如果沒有這個調用，處理程序就會完成，然后移動到下一個處理程序，在你的情況下，它將是返回404的默認處理程序。

此外，使用Handler時，請使用Handler為您提供的參數。 target參數將具有提供的路徑，如在原始請求中看到的那樣。

request.getRequestURI()行為依賴於各種ServletContext信息，因此不太可能是您在不使用ServletContext時所期望的結果。

注意：如果你實際上想要一個ServletContext和普通的servlet行為，可以使用ServletContextHandler和真正的servlet，也可以在嵌入模式下使用。 請參閱ManyServletContexts示例。

但是，處理這種情況更容易。 創建ContextHandlerCollection並通過ContextHandler將您的每個Handler設置為該集合。 請參閱ManyContexts示例 。

例：

ContextHandlerCollection contexts = new ContextHandlerCollection();
server.setHandler(contexts);

ContextHandler stock = new ContextHandler("/stock");
stock.setHandler(new Class2HTTPMessageHandler());
contexts.add(stock);

有了這個，你可以跳過對Requested URI的整個檢查，讓Jetty處理它。

應該注意，即使Jetty使用Handler的target參數來執行此上下文邏輯。