Tomcat正在8080端口运行,但无法使用IP地址远程访问?

4

我在服务器上新安装了apache-tomcat-7.0.62。当我启动tomcat时,它没有错误地启动,但是当我想要使用浏览器访问它时,它显示页面不可用。我使用以下命令检查tomcat是否正常运行:

     netstat -ntlp | grep LISTEN

以下是输出结果:-

tcp 0 0 0.0.0.0:22 0.0.0.0:* 监听中 -
tcp 0 0 127.0.0.1:8005 0.0.0.0:* 监听中 19430/java
tcp 0 0 0.0.0.0:8009 0.0.0.0:* 监听中 19430/java
tcp 0 0 127.0.0.1:3306 0.0.0.0:* 监听中 -
tcp 0 0 0.0.0.0:8080 0.0.0.0:* 监听中 19430/java
tcp6 0 0 :::22 :::* 监听中 -
tcp6 0 0 :::8000 :::* 监听中 -
tcp6 0 0 :::80 :::* 监听中 -

以下是catalina.out的内容。

 Aug 28, 2015 7:56:39 AM               org.apache.catalina.startup.VersionLoggerListener log
INFO: Server version:        Apache Tomcat/7.0.62
Aug 28, 2015 7:56:39 AM    org.apache.catalina.startup.VersionLoggerListener log
INFO: Server built:          May 7 2015 17:14:55 UTC
Aug 28, 2015 7:56:39 AM     org.apache.catalina.startup.VersionLoggerListener log
INFO: Server number:         7.0.62.0
Aug 28, 2015 7:56:39 AM  org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Name:               Linux
  Aug 28, 2015 7:56:39 AM  org.apache.catalina.startup.VersionLoggerListener log
  INFO: OS Version:            3.13.0-48-generic
 Aug 28, 2015 7:56:39 AM      org.apache.catalina.startup.VersionLoggerListener log
 INFO: Architecture:          amd64
   Aug 28, 2015 7:56:39 AM  org.apache.catalina.startup.VersionLoggerListener log
 INFO: Java Home:             /usr/lib/jvm/java-7-openjdk-amd64/jre
 Aug 28, 2015 7:56:39 AM      org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Version:           1.7.0_79-b14
 Aug 28, 2015 7:56:39 AM  org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Vendor:            Oracle Corporation 
Aug 28, 2015 7:56:39 AM  org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_BASE:         /home/ubuntu/apache-tomcat-7.0.62
Aug 28, 2015 7:56:39 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_HOME:         /home/ubuntu/apache-tomcat-7.0.62
Aug 28, 2015 7:56:39 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: - Djava.util.logging.config.file=/home/ubuntu/apache-tomcat- 7.0.62/conf/logging.properties
 Aug 28, 2015 7:56:39 AM  org.apache.catalina.startup.VersionLoggerListener log
 INFO: Command line argument: - Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
Aug 28, 2015 7:56:39 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.net.preferIPv4Stack=true 
 Aug 28, 2015 7:56:39 AM  org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.net.preferIPv4Addresses=true
Aug 28, 2015 7:56:39 AM  org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.endorsed.dirs=/home/ubuntu/apache- tomcat-7.0.62/endorsed
Aug 28, 2015 7:56:39 AM  org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dcatalina.base=/home/ubuntu/apache-     tomcat-7.0.62
Aug 28, 2015 7:56:39 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dcatalina.home=/home/ubuntu/apache- tomcat-7.0.62
 Aug 28, 2015 7:56:39 AM   org.apache.catalina.startup.VersionLoggerListener log
 INFO: Command line argument: -Djava.io.tmpdir=/home/ubuntu/apache-   tomcat-7.0.62/temp
 Aug 28, 2015 7:56:39 AM org.apache.catalina.core.AprLifecycleListener  lifecycleEvent
  INFO: The APR based Apache Tomcat Native library which allows optimal     performance in production environments was not found on the   java.library.path: /usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-  gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-  gnu:/usr/lib/jni:/lib:/usr/lib
 Aug 28, 2015 7:56:39 AM org.apache.coyote.AbstractProtocol init
 INFO: Initializing ProtocolHandler ["http-bio-8080"]
 Aug 28, 2015 7:56:39 AM org.apache.coyote.AbstractProtocol init
 INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
 Aug 28, 2015 7:56:39 AM org.apache.catalina.startup.Catalina load
 INFO: Initialization processed in 1060 ms
 Aug 28, 2015 7:56:39 AM org.apache.catalina.core.StandardService     startInternal
 INFO: Starting service Catalina
  Aug 28, 2015 7:56:39 AM org.apache.catalina.core.StandardEngine   startInternal
 INFO: Starting Servlet Engine: Apache Tomcat/7.0.62
 Aug 28, 2015 7:56:39 AM org.apache.catalina.startup.HostConfig  deployDirectory
INFO: Deploying web application directory /home/ubuntu/apache-tomcat- 7.0.62/webapps/ROOT
Aug 28, 2015 7:56:40 AM org.apache.catalina.startup.HostConfig  deployDirectory
 INFO: Deployment of web application directory /home/ubuntu/apache - tomcat-7.0.62/webapps/ROOT has finished in 805 ms
 Aug 28, 2015 7:56:40 AM org.apache.catalina.startup.HostConfig    deployDirectory
 INFO: Deploying web application directory /home/ubuntu/apache-tomcat- 7.0.62/webapps/examples
 Aug 28, 2015 7:56:40 AM org.apache.catalina.startup.HostConfig  deployDirectory
 INFO: Deployment of web application directory /home/ubuntu/apache-  tomcat-7.0.62/webapps/examples has finished in 611 ms
 Aug 28, 2015 7:56:40 AM org.apache.catalina.startup.HostConfig  deployDirectory
 INFO: Deploying web application directory /home/ubuntu/apache-tomcat-  7.0.62/webapps/host-manager
  Aug 28, 2015 7:56:40 AM org.apache.catalina.startup.HostConfig   deployDirectory
 INFO: Deployment of web application directory /home/ubuntu/apache- tomcat-7.0.62/webapps/host-manager has finished in 204 ms
Aug 28, 2015 7:56:40 AM org.apache.catalina.startup.HostConfig  deployDirectory
INFO: Deploying web application directory /home/ubuntu/apache-tomcat    -7.0.62/webapps/manager
 Aug 28, 2015 7:56:41 AM org.apache.catalina.startup.HostConfig    deployDirectory
 INFO: Deployment of web application directory /home/ubuntu/apache- tomcat-7.0.62/webapps/manager has finished in 107 ms
Aug 28, 2015 7:56:41 AM org.apache.catalina.startup.HostConfig  deployDirectory
INFO: Deploying web application directory /home/ubuntu/apache-tomcat-  7.0.62/webapps/docs
Aug 28, 2015 7:56:41 AM org.apache.catalina.startup.HostConfig   deployDirectory
 INFO: Deployment of web application directory /home/ubuntu/apache-  tomcat-7.0.62/webapps/docs has finished in 115 ms
 Aug 28, 2015 7:56:41 AM org.apache.coyote.AbstractProtocol start
 INFO: Starting ProtocolHandler ["http-bio-8080"]
 Aug 28, 2015 7:56:41 AM org.apache.coyote.AbstractProtocol start
 INFO: Starting ProtocolHandler ["ajp-bio-8009"]
 Aug 28, 2015 7:56:41 AM org.apache.catalina.startup.Catalina start
 INFO: Server startup in 1960 ms

以下是 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" />
  <!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html -->
  <Listener className="org.apache.catalina.core.JasperListener" />
  <!-- 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 HTTP/1.1 Connector on port 8080
    -->
    <Connector port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" 
 useIPVHosts="true" />
    <!-- A "Connector" using the shared thread pool-->
    <!--
    <Connector executor="tomcatThreadPool"
               port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" />
    -->
    <!-- Define a SSL HTTP/1.1 Connector on port 8443
         This connector uses the BIO 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.Http11Protocol"
               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>


 <Host name="mining.knowaptitude.in"  appBase="mining_apps"
            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>


当您尝试访问远程IP时,到底发生了什么?您试图访问哪个上下文路径? - Sercan Ozdemir
1
请展示您的 server.xml 配置文件。 - Fran Montero
1
你的Tomcat只能监听本地主机。请将server.xml更改为你的外部IP地址。 - Jens
1
如 @thienkhoi-tran 所指出的,在您的地址上使用 NAT,您必须进行设置。如果您想从另一台计算机访问它,则还必须禁用防火墙或添加此端口号的异常。 - Christophe
1
还有一件事,请检查您的防火墙。逐步检查外部网络到服务器的连接。祝你好运。 - thienkhoi tran
显示剩余3条评论
3个回答

6
请检查端口8080是否可以从外部访问。端口可能被阻止。检查您的防火墙设置并为http请求打开该端口。

我使用以下命令 nmap 54.149.233.194 进行了检查,但在端口列表中没有找到8080端口。我该怎么做才能解决这个问题?@Azhar - Sushant Srivastava
我正在使用自定义端口,并且该端口可以从外部访问。但是当我调用特定的服务,例如225.125.888.115:628时,我的控制台显示错误。但在本地,我没有收到任何错误。 - Moeez

2
  1. disable firewalld:

    # systemctl stop firewalld
    # systemctl disable firewalld
    
  2. replace localhost with a valid IP that can be exposed externally in server.xml


找了一段时间,最终停止firewalld帮助了!谢谢。 - Aurimas Stands with Ukraine

2

网页内容由stack overflow 提供, 点击上面的
可以查看英文原文,
原文链接