2016-06-23 10 views
7

Problem verbunden zu zerstören: Laufen mein Projekt auf einem tomcat ich folgendes Problem bekommen:Tomcat: Fehler Endpunkt mit protocol

SCHWERWIEGEND: Failed to destroy end point associated with ProtocolHandler ["ajp-nio-8009"] 
java.lang.NullPointerException 
    at org.apache.tomcat.util.net.NioEndpoint.releaseCaches(NioEndpoint.java:316) 
    at org.apache.tomcat.util.net.NioEndpoint.unbind(NioEndpoint.java:492) 
    at org.apache.tomcat.util.net.AbstractEndpoint.destroy(AbstractEndpoint.java:821) 
    at org.apache.coyote.AbstractProtocol.destroy(AbstractProtocol.java:534) 
    at org.apache.catalina.connector.Connector.destroyInternal(Connector.java:1023) 
    at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:297) 
    at org.apache.catalina.core.StandardService.destroyInternal(StandardService.java:589) 
    at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:297) 
    at org.apache.catalina.core.StandardServer.destroyInternal(StandardServer.java:877) 
    at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:297) 
    at org.apache.catalina.startup.Catalina.start(Catalina.java:633) 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 
    at java.lang.reflect.Method.invoke(Unknown Source) 
    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:351) 
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:485) 

Frage: Ist das Problem durch meine web.xml-Datei verursacht ?

web.xml

<?xml version="1.0" encoding="UTF-8"?> 
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.jcp.org/xml/ns/javaee" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd" id="WebApp_ID" version="3.1"> 
    <display-name>SMS Cloud Service</display-name> 


</web-app> 

HomeController.java

@RestController 
    public class HomeController { 

     private final MachineRepository machineRepository; 

     @Autowired 
     HomeController(MachineRepository machineRepository) { 
      this.machineRepository = machineRepository; 
     } 

     @RequestMapping(value = "/maschine/getAll", method = RequestMethod.GET) 
     Iterable<Machine> readMachines(@PathVariable String userId) { 

      return this.machineRepository.findAll(); 
     } 
    } 

Hinweis: Ich betreibe das Projekt auf

Frühling Tool Suite

Versi auf: 3.7.3.RELEASE Build-ID: 201602251025 Plattform: Eclipse-Neon (4,6)

Tomcat server.xml

<?xml version='1.0' encoding='utf-8'?> 
<!-- 
    Licensed to the Apache Software Foundation (ASF) under one or more 
    contributor license agreements. See the NOTICE file distributed with 
    this work for additional information regarding copyright ownership. 
    The ASF licenses this file to You under the Apache License, Version 2.0 
    (the "License"); you may not use this file except in compliance with 
    the License. You may obtain a copy of the License at 

     http://www.apache.org/licenses/LICENSE-2.0 

    Unless required by applicable law or agreed to in writing, software 
    distributed under the License is distributed on an "AS IS" BASIS, 
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 
    See the License for the specific language governing permissions and 
    limitations under the License. 
--> 
<!-- Note: A "Server" is not itself a "Container", so you may not 
    define subcomponents such as "Valves" at this level. 
    Documentation at /docs/config/server.html 
--> 
<Server port="8005" shutdown="SHUTDOWN"> 
    <Listener className="org.apache.catalina.startup.VersionLoggerListener" /> 
    <!-- Security listener. Documentation at /docs/config/listeners.html 
    <Listener className="org.apache.catalina.security.SecurityListener" /> 
    --> 
    <!--APR library loader. Documentation at /docs/apr.html --> 
    <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" /> 
    <!-- Prevent memory leaks due to use of particular java/javax APIs--> 
    <Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener" /> 
    <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" /> 
    <Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" /> 

    <!-- Global JNDI resources 
     Documentation at /docs/jndi-resources-howto.html 
    --> 
    <GlobalNamingResources> 
    <!-- Editable user database that can also be used by 
     UserDatabaseRealm to authenticate users 
    --> 
    <Resource name="UserDatabase" auth="Container" 
       type="org.apache.catalina.UserDatabase" 
       description="User database that can be updated and saved" 
       factory="org.apache.catalina.users.MemoryUserDatabaseFactory" 
       pathname="conf/tomcat-users.xml" /> 
    </GlobalNamingResources> 

    <!-- A "Service" is a collection of one or more "Connectors" that share 
     a single "Container" Note: A "Service" is not itself a "Container", 
     so you may not define subcomponents such as "Valves" at this level. 
     Documentation at /docs/config/service.html 
    --> 
    <Service name="Catalina"> 

    <!--The connectors can use a shared executor, you can define one or more named thread pools--> 
    <!-- 
    <Executor name="tomcatThreadPool" namePrefix="catalina-exec-" 
     maxThreads="150" minSpareThreads="4"/> 
    --> 


    <!-- A "Connector" represents an endpoint by which requests are received 
     and responses are returned. Documentation at : 
     Java HTTP Connector: /docs/config/http.html (blocking & non-blocking) 
     Java AJP Connector: /docs/config/ajp.html 
     APR (HTTP/AJP) Connector: /docs/apr.html 
     Define a non-SSL/TLS HTTP/1.1 Connector on port 8080 
    --> 
    <Connector port="8080" protocol="HTTP/1.1" 
       connectionTimeout="20000" 
       redirectPort="8443" /> 
    <!-- A "Connector" using the shared thread pool--> 
    <!-- 
    <Connector executor="tomcatThreadPool" 
       port="8080" protocol="HTTP/1.1" 
       connectionTimeout="20000" 
       redirectPort="8443" /> 
    --> 
    <!-- Define a SSL/TLS HTTP/1.1 Connector on port 8443 
     This connector uses the NIO implementation that requires the JSSE 
     style configuration. When using the APR/native implementation, the 
     OpenSSL style configuration is required as described in the APR/native 
     documentation --> 
    <!-- 
    <Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol" 
       maxThreads="150" SSLEnabled="true" scheme="https" secure="true" 
       clientAuth="false" sslProtocol="TLS" /> 
    --> 

    <!-- Define an AJP 1.3 Connector on port 8009 --> 
    <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" /> 


    <!-- An Engine represents the entry point (within Catalina) that processes 
     every request. The Engine implementation for Tomcat stand alone 
     analyzes the HTTP headers included with the request, and passes them 
     on to the appropriate Host (virtual host). 
     Documentation at /docs/config/engine.html --> 

    <!-- You should set jvmRoute to support load-balancing via AJP ie : 
    <Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1"> 
    --> 
    <Engine name="Catalina" defaultHost="localhost"> 

     <!--For clustering, please take a look at documentation at: 
      /docs/cluster-howto.html (simple how to) 
      /docs/config/cluster.html (reference documentation) --> 
     <!-- 
     <Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/> 
     --> 

     <!-- Use the LockOutRealm to prevent attempts to guess user passwords 
      via a brute-force attack --> 
     <Realm className="org.apache.catalina.realm.LockOutRealm"> 
     <!-- This Realm uses the UserDatabase configured in the global JNDI 
      resources under the key "UserDatabase". Any edits 
      that are performed against this UserDatabase are immediately 
      available for use by the Realm. --> 
     <Realm className="org.apache.catalina.realm.UserDatabaseRealm" 
       resourceName="UserDatabase"/> 
     </Realm> 

     <Host name="localhost" appBase="webapps" 
      unpackWARs="true" autoDeploy="true"> 

     <!-- SingleSignOn valve, share authentication between web applications 
      Documentation at: /docs/config/valve.html --> 
     <!-- 
     <Valve className="org.apache.catalina.authenticator.SingleSignOn" /> 
     --> 

     <!-- Access log processes all example. 
      Documentation at: /docs/config/valve.html 
      Note: The pattern used is equivalent to using pattern="common" --> 
     <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" 
       prefix="localhost_access_log" suffix=".txt" 
       pattern="%h %l %u %t &quot;%r&quot; %s %b" /> 

     </Host> 
    </Engine> 
    </Service> 
</Server> 
+0

Was ist in Ihrem Tomcat server.xml? Port-Konfigurationen sind darin gemacht. Führen Sie Ihr Projekt in einer IDE-basierten Serverumgebung aus? – aksappy

+0

Für server.xml finden Sie in meinem aktualisierten Beitrag. Ich betreibe meinen Kater in meiner Spring Tool Suite. Version: 3.7.3.RELEASE Build Id: 201602251025 Plattform: Eclipse Neon (4.6) - Ist das die richtige Antwort auf Ihre Frage? – jublikon

+0

Ich habe diesen Fehler beim Ausführen in einer IDE-Umgebung. Die WTP-Umgebung ändert die Tomcat-Umgebung in ihren eigenen Bedingungen und kann nicht immer eine erfolgreiche/elegante Ausführung garantieren. Können Sie Ihre Anwendung auch in einem eigenständigen Tomcat-Server ausführen? – aksappy

Antwort

2

traf ich ein ähnliches Problem, wenn ich ein Maven Web-Projekt nach der Reinigung veröffentlichen es in Eclipse. Nach meiner Erfahrung, um dieses Problem zu sovle, sollten Sie:

  1. Update das Maven Projekt

  2. Config-Build-Pfad -> entfernen unnötige Quellordner

  3. make sure web deployment assembly looks like this, entfernen Sie unnötige Einträge

  4. Konfigurationen ausführen -> Tomcat wählen -> dann Classpath, make sure it looks like it

  5. Endlich, vergessen Sie nicht, ein Projekt zu bauen.

Funktioniert für mich. Ich hoffe es hilft.

-2

Maven Update für das Projekt hat den Trick für mich getan.

0

Um das Verzeichnis zu sehen, in dem das Jar-Paket von Maven heruntergeladen und alle Child-Verzeichnisse gelöscht werden sollen, kehren Sie zurück zu Eclipse und klicken auf update das Maven-Projekt. Das ist meine Erfahrung und ich gelange auf diese Weise.

+1

Wie beantwortet das die Frage von OP? – RealCheeseLord

0

Versuchen Sie, im Protokoll nach früheren Fehlernachrichten zu suchen.

In meinem Fall zum Beispiel gab es einen Fehler in der Servlets-Definition in web.xml.