嵌入式jetty处理从eclipse运行但未部署的请求

我有一个应用程序嵌入Jetty作为Web服务器来托管RESTful API。我一直在Ubuntu的Eclipse上开发它，当从IDE启动时，一切都很好。但是，当我打包应用程序时，将其部署到服务器上，Jetty不再响应请求。嵌入式jetty处理从eclipse运行但未部署的请求

服务器在我指定的端口上打开一个套接字，并打开INFO日志记录spring-mvc显示我的控制器，它的方法被正确映射。请求成功地打开了一个连接，但是没有数据被发送回来，实际上这个请求从来没有将它传递给我的控制器代码。当我关闭应用程序时，我看到所有已建立的连接都被杀死了。

我已经检查过Eclipse项目的类路径上的所有库在部署时都在类路径上。我还应该检查什么来弄清楚它为什么在Eclipse中工作并在其他地方被破解？

Jetty是版本9，Java版本1.7，Spring 3.2.2。从码头

编辑调试日志记录，当我提出一个要求：

2013-05-06 09:40:30,214 DEBUG [email protected]{HTTP/1.1}{0.0.0.0:8090} [SelectorManager.java submit]-: <Queued change [email protected]f589> 
2013-05-06 09:40:30,215 DEBUG qtp1215430550-29-selector-2 [SelectorManager.java runChange]-: <Running change [email protected]f589> 
2013-05-06 09:40:30,217 DEBUG qtp1215430550-29-selector-2 [AbstractEndPoint.java onOpen]-: <onOpen [email protected]{/127.0.0.1:39895<r-l>/127.0.0.1:8090,o=true,is=false,os=false,[email protected]{false,null},[email protected]{IDLE},it=30000}{null}{io=0,kio=0,kro=0}> 
2013-05-06 09:40:30,220 DEBUG qtp1215430550-29-selector-2 [IdleTimeout.java checkIdleTimeout]-: <[email protected]{/127.0.0.1:39895<r-l>/127.0.0.1:8090,o=true,is=false,os=false,[email protected]{false,null},[email protected]{IDLE},it=30000}{null}{io=0,kio=0,kro=0} idle timeout check, elapsed: 3 ms, remaining: 29997 ms> 
2013-05-06 09:40:30,221 DEBUG qtp1215430550-29-selector-2 [HttpConnection.java <init>]-: <New HTTP Connection [email protected]{IDLE},g=HttpGenerator{s=START},p=HttpParser{s=START,0 of 0}> 
2013-05-06 09:40:30,224 DEBUG qtp1215430550-29-selector-2 [AbstractConnection.java onOpen]-: <onOpen [email protected]{IDLE},g=HttpGenerator{s=START},p=HttpParser{s=START,0 of 0}> 
2013-05-06 09:40:30,227 DEBUG qtp1215430550-29-selector-2 [AbstractConnection.java fillInterested]-: <fillInterested [email protected]{IDLE},g=HttpGenerator{s=START},p=HttpParser{s=START,0 of 0}> 
2013-05-06 09:40:30,229 DEBUG qtp1215430550-29-selector-2 [SelectChannelEndPoint.java updateLocalInterests]-: <Local interests updated 0 -> 1 for [email protected]{/127.0.0.1:39895<r-l>/127.0.0.1:8090,o=true,is=false,os=false,[email protected]{true,[email protected]},[email protected]{IDLE},it=30000}{[email protected]{INTERESTED},g=HttpGenerator{s=START},p=HttpParser{s=START,0 of 0}}{io=1,kio=0,kro=0}> 
2013-05-06 09:40:30,232 DEBUG qtp1215430550-29-selector-2 [SelectorManager.java createEndPoint]-: <Created [email protected]{/127.0.0.1:39895<r-l>/127.0.0.1:8090,o=true,is=false,os=false,[email protected]{true,[email protected]},[email protected]{IDLE},it=30000}{[email protected]{INTERESTED},g=HttpGenerator{s=START},p=HttpParser{s=START,0 of 0}}{io=1,kio=0,kro=0}> 
2013-05-06 09:40:30,233 DEBUG qtp1215430550-29-selector-2 [SelectorManager.java runChange]-: <Running change [email protected]> 
2013-05-06 09:40:30,233 DEBUG qtp1215430550-29-selector-2 [SelectChannelEndPoint.java setKeyInterests]-: <Key interests updated 0 -> 1> 
2013-05-06 09:40:30,234 DEBUG qtp1215430550-29-selector-2 [SelectorManager.java select]-: <Selector loop waiting on select> 
2013-05-06 09:40:30,234 DEBUG qtp1215430550-29-selector-2 [SelectorManager.java select]-: <Selector loop woken up from select, 1/1 selected> 
2013-05-06 09:40:30,234 DEBUG qtp1215430550-29-selector-2 [SelectChannelEndPoint.java setKeyInterests]-: <Key interests updated 1 -> 0> 
2013-05-06 09:40:30,238 DEBUG qtp1215430550-29-selector-2 [SelectChannelEndPoint.java updateLocalInterests]-: <Local interests updated 1 -> 0 for [email protected]{/127.0.0.1:39895<r-l>/127.0.0.1:8090,o=true,is=false,os=false,[email protected]{true,[email protected]},[email protected]{IDLE},it=30000}{[email protected]{INTERESTED},g=HttpGenerator{s=START},p=HttpParser{s=START,0 of 0}}{io=0,kio=0,kro=1}> 
2013-05-06 09:40:30,238 DEBUG qtp1215430550-29-selector-2 [SelectorManager.java runChange]-: <Running change [email protected]> 
2013-05-06 09:40:30,239 DEBUG qtp1215430550-29-selector-2 [QueuedThreadPool.java dispatch]-: <qtp1215430550{STARTED,2<=10<=10,i=0,q=4} dispatched [email protected]> 
2013-05-06 09:40:30,240 DEBUG qtp1215430550-29-selector-2 [SelectorManager.java select]-: <Selector loop waiting on select> 
2013-05-06 09:40:35,88 DEBUG Scheduler-702565976 [IdleTimeout.java checkIdleTimeout]-: <[email protected]{/127.0.0.1:39894<r-l>/127.0.0.1:8090,o=true,is=false,os=false,[email protected]{false,null},[email protected]{IDLE},it=30000}{[email protected]{INTERESTED},g=HttpGenerator{s=START},p=HttpParser{s=START,0 of 0}}{io=0,kio=0,kro=1} idle timeout check, elapsed: 29996 ms, remaining: 4 ms> 
2013-05-06 09:40:35,96 DEBUG Scheduler-702565976 [IdleTimeout.java checkIdleTimeout]-: <[email protected]{/127.0.0.1:39894<r-l>/127.0.0.1:8090,o=true,is=false,os=false,[email protected]{false,null},[email protected]{IDLE},it=30000}{[email protected]{INTERESTED},g=HttpGenerator{s=START},p=HttpParser{s=START,0 of 0}}{io=0,kio=0,kro=1} idle timeout check, elapsed: 30005 ms, remaining: -5 ms> 
2013-05-06 09:40:35,99 DEBUG Scheduler-702565976 [IdleTimeout.java checkIdleTimeout]-: <[email protected]{/127.0.0.1:39894<r-l>/127.0.0.1:8090,o=true,is=false,os=false,[email protected]{false,null},[email protected]{IDLE},it=30000}{[email protected]{INTERESTED},g=HttpGenerator{s=START},p=HttpParser{s=START,0 of 0}}{io=0,kio=0,kro=1} idle timeout expired>

EDIT 2我的Jetty服务器配置都在春豆：

<bean id="JettyServer" class="org.eclipse.jetty.server.Server" init-method="start" destroy-method="stop"> 

<property name="connectors"> 
    <list> 
     <bean id="Connector" class="org.eclipse.jetty.server.nio.SelectChannelConnector"> 
      <property name="port" value="8090"/> 
     </bean> 
    </list> 
</property> 

<property name="handler"> 
    <bean id="handlers" class="org.eclipse.jetty.server.handler.HandlerCollection"> 
     <property name="handlers"> 
      <list> 
       <bean id="servletContextHandler" class="org.eclipse.jetty.servlet.ServletContextHandler"> 
        <property name="contextPath" value="/"/> 
        <property name="servletHandler"> 
         <bean class="org.eclipse.jetty.servlet.ServletHandler"> 

          <property name="servlets"> 
           <list> 
            <bean class="org.eclipse.jetty.servlet.ServletHolder"> 
             <property name="name" value="DefaultServlet"/> 
             <property name="servlet"> 
              <bean class="com.company.project.api.DispatcherServletWrapper"/> 
             </property> 
            </bean> 
           </list> 
          </property> 
          <property name="servletMappings"> 
           <list> 
            <bean class="org.eclipse.jetty.servlet.ServletMapping"> 
             <property name="pathSpecs"> 
              <list><value>/</value></list> 
             </property> 
             <property name="servletName" value="DefaultServlet"/> 
            </bean> 
           </list> 
          </property> 
         </bean> 
        </property> 
       </bean> 
       <bean class="org.eclipse.jetty.server.handler.RequestLogHandler"> 
        <property name="requestLog"> 
         <bean class="org.eclipse.jetty.server.NCSARequestLog"> 
          <constructor-arg value="/opt/company/logs/jetty-yyyy_mm_dd.log"/> 
          <property name="extended" value="false" /> 
         </bean> 
        </property> 
       </bean> 
      </list> 
     </property> 
    </bean> 
</property> 
</bean>

我需要调度的servlet要知道定义这个Jetty服务器的ApplicationContext，所以参考我的DispatcherServletWrapper类看起来像这样：

package com.company.project.api; 

import org.springframework.beans.BeansException; 
import org.springframework.context.ApplicationContext; 
import org.springframework.context.ApplicationContextAware; 
import org.springframework.web.context.WebApplicationContext; 
import org.springframework.web.context.support.GenericWebApplicationContext; 
import org.springframework.web.servlet.DispatcherServlet; 

public class DispatcherServletWrapper extends DispatcherServlet implements ApplicationContextAware { 

    private static final long serialVersionUID = -2281511575328213502L; 
    private ApplicationContext appContext; 

    @Override 
    public void setApplicationContext(ApplicationContext arg0) 
      throws BeansException { 
     this.appContext = arg0; 
    } 

    protected WebApplicationContext createWebApplicationContext(WebApplicationContext arg0) { 
     GenericWebApplicationContext wac = new GenericWebApplicationContext(); 
     wac.setParent(appContext); 
     wac.refresh(); 

     return wac; 
    } 

}

来源

2013-05-06 tdimmig

我已经确定我的开发环境使用与生产服务器完全相同的JRE，并且IDE类路径与exa相匹配在服务器上运行时，请使用类路径。服务器运行CentOS 5.9。我发现Jetty服务器按预期工作，在CentOS 6.4服务器上按预期处理我的请求并返回.... 由于JRE和classpath是相等的，我的应用程序比“java - cp $（classpath变量）com.company.project.Main“还有什么不同，导致它在我的Ubuntu开发环境和6.4服务器，但不是5.9？ – tdimmig 2013-05-07 03:44:49

没有足够的信息去。你没有表明*你如何开始码头。你可以包括一些关于你如何开始码头的代码？比如你如何处理'Server'实例？你是否server.start（）'然后'server.join（）'或者你是否在你的项目中以不同的方式管理服务器线程？ – 2013-05-08 18:41:24

我切换到Jetty 8（它需要一个不同的类为连接器，并没有其他更改，除了库交换），一切正常。我仍然不知道什么样的完美风暴组合会导致它被Jetty 9打破，后者在我提到的其他几个平台上工作过。但是，备份到Jetty 8使其在我的部署平台中工作，所以这就是我所走的方向。如果我知道如何，我会关闭/删除这个问题。感谢您的评论，但我很感激有人表示有兴趣提供帮助。 – tdimmig 2013-05-08 20:03:04

啊，连接器已经与码头9.

与码头9开始改变时，连接器是内置了一个链连接工厂的的，其提供的连接类型检测和回退。

这样做是为了支持替代网络连接类型（如TLS扩展，NPN，SPDY，WebSocket甚至为HTTP/2.0做准备）的现代现实。

这里的一些嵌入的例子：

在码头9

package org.eclipse.jetty.embedded; 

import org.eclipse.jetty.server.Server; 
import org.eclipse.jetty.server.ServerConnector; 

public class OneConnector 
{ 
    public static void main(String[] args) throws Exception 
    { 
     // The Server 
     Server server = new Server(); 

     // HTTP connector 
     ServerConnector http = new ServerConnector(server); 
     http.setHost("localhost"); 
     http.setPort(8080); 
     http.setIdleTimeout(30000); 

     // Set the connector 
     server.addConnector(http); 

     // Set a handler 
     server.setHandler(new HelloHandler()); 

     // Start the server 
     server.start(); 
     server.join(); 
    } 
}

配置一个标准的HTTP连接器配置为SSL + NPN + SPDY/3 + SPDY/2 + HTTPS在码头的连接器链9

package org.eclipse.jetty.embedded; 

import org.eclipse.jetty.server.HttpConfiguration; 
import org.eclipse.jetty.server.HttpConnectionFactory; 
import org.eclipse.jetty.server.SecureRequestCustomizer; 
import org.eclipse.jetty.server.Server; 
import org.eclipse.jetty.server.ServerConnector; 
import org.eclipse.jetty.server.SslConnectionFactory; 
import org.eclipse.jetty.spdy.server.NPNServerConnectionFactory; 
import org.eclipse.jetty.spdy.server.SPDYServerConnectionFactory; 
import org.eclipse.jetty.spdy.server.http.HTTPSPDYServerConnectionFactory; 
import org.eclipse.jetty.spdy.server.http.ReferrerPushStrategy; 
import org.eclipse.jetty.util.ssl.SslContextFactory; 

public class SpdyConnector 
{ 
    public static void main(String[] args) throws Exception 
    { 
     String jetty_home = System.getProperty("jetty.home","../../jetty-distribution/target/distribution"); 
     System.setProperty("jetty.home", jetty_home); 

     // The Server 
     Server server = new Server(); 

     // HTTP Configuration 
     HttpConfiguration http_config = new HttpConfiguration(); 
     http_config.setSecureScheme("https"); 
     http_config.setSecurePort(8443); 

     // HTTP connector 
     ServerConnector http = new ServerConnector(server,new HttpConnectionFactory(http_config));   
     http.setPort(8080); 
     server.addConnector(http); 

     // SSL Context Factory for HTTPS and SPDY 
     SslContextFactory sslContextFactory = new SslContextFactory(); 
     sslContextFactory.setKeyStorePath(jetty_home + "/etc/keystore"); 
     sslContextFactory.setKeyStorePassword("OBF:1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4"); 
     sslContextFactory.setKeyManagerPassword("OBF:1u2u1wml1z7s1z7a1wnl1u2g"); 

     // HTTPS Configuration 
     HttpConfiguration https_config = new HttpConfiguration(http_config); 
     https_config.addCustomizer(new SecureRequestCustomizer()); 

     // SPDY versions 
     HTTPSPDYServerConnectionFactory spdy2 = 
      new HTTPSPDYServerConnectionFactory(2,https_config); 

     HTTPSPDYServerConnectionFactory spdy3 = 
      new HTTPSPDYServerConnectionFactory(3,https_config,new ReferrerPushStrategy()); 

     // NPN Factory 
     SPDYServerConnectionFactory.checkNPNAvailable(); 
     NPNServerConnectionFactory npn = 
      new NPNServerConnectionFactory(spdy3.getProtocol(),spdy2.getProtocol(),http.getDefaultProtocol()); 
     npn.setDefaultProtocol(http.getDefaultProtocol()); 

     // SSL Factory 
     SslConnectionFactory ssl = new SslConnectionFactory(sslContextFactory,npn.getProtocol()); 

     // SPDY Connector 
     ServerConnector spdyConnector = 
      new ServerConnector(server,ssl,npn,spdy3,spdy2,new HttpConnectionFactory(https_config)); 
     spdyConnector.setPort(8443); 
     server.addConnector(spdyConnector); 

     // Set a handler 
     server.setHandler(new HelloHandler()); 

     // Start the server 
     server.start(); 
     server.join(); 
    } 
}

来源

2013-05-08 21:17:34

我用代码示例更新了我的问题，显示了如何启动我的Jetty服务器的XML。我提到连接器差异只是为了说明它是唯一的配置部分，我必须在从9切换回Jetty 8时更改。服务器在我的开发环境和CentOS上按预期工作，版本9 6服务器。它在CentOS 5服务器上不起作用。切换回Jetty 8使其无处不在。我不知道什么完美的软件风暴会导致我的项目的Jetty 9版本失败，但我没有时间弄清楚。 – tdimmig 2013-05-09 13:28:10

我非常感谢您在尝试提供帮助时的努力，但我不相信这只是一个配置问题，因为它在我尝试使用的3个平台中的2个平台上运行。 – tdimmig 2013-05-09 13:29:29

嵌入式jetty处理从eclipse运行但未部署的请求

回答

相关问题