Lucee IIS10 - Tomcat 8.5 BonCodeAJP 连接器 - 通用连接器通信错误

问题描述 投票:0回答:2

我安装了 Windows 2016 64 位服务器,运行 Lucee 5.3.1.102、Tomcat/8.5.35 和 BonCodeAJP 连接器。

总体来说一切运行顺利,网站平均每天有 60 万到 100 万用户。在极少数情况下,我们会收到以下错误:

Generic Connector Communication Error:

Please check and adjust your setup:

Ensure that Tomcat is running on given host and port.

If this is a timeout error consider adjusting IIS timeout by changing
executionTimeout attribute in web.config (see manual).

当浏览器显示错误时,重新显示网站实际页面的唯一方法是清除所有网站数据。如果您仅刷新,它会再次显示错误,尽管网站现在运行没有错误(错误显示一次,但无论重新加载多少次,错误页面仍然显示在浏览器上,因此用户认为该网站已关闭,直到他尝试使用隐身窗口或尝试使用其他浏览器)。

那么有没有办法更改错误页面,使其自动重定向或使内容过期,以便浏览器可以再次看到该网站? 另外,您知道为什么会出现此错误,即使它出现的情况如此罕见?

提前感谢您的帮助 这是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="8888" 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" keepAliveTimeout="-1" connectionTimeout="121000" packetSize="65530" 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="127.0.0.1">

     <!--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="127.0.0.1"  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" />

   <!-- visit modcfml.org for details on mod_cfml configuration options -->
   <Valve className="mod_cfml.core"
       loggingEnabled="false"
       maxContexts="200"
       timeBetweenContexts="2000"
       scanClassPaths="false"
       sharedKey="8cb4bca1476f6af2ef9e5f548bfdf7c58015ba1fad1adc9818863b8ea2b8af50"
       />
     </Host>

     <!--
       Add additional VIRTUALHOSTS by copying the following example config:
       REPLACE:
       [ENTER DOMAIN NAME] with a domain, IE: "mysite.com"
       [ENTER SYSTEM PATH] with your web site's base directory. IE: /home/user/public_html/ or C:\websites\www.mysite.com\ etc...
   [ENTER DOMAIN ALIAS] with any domain that also points to this same site/directory. You can repeat this tag as often as needed. 
       Don't forget to remove comments!
     -->
     <!--
   EXAMPLE HOST ENTRY:
       <Host name="lucee.org" appBase="webapps">
            <Context path="" docBase="/var/sites/lucee.org" />
        <Alias>www.lucee.org</Alias>
        <Alias>my.lucee.org</Alias>
       </Host>
   
   HOST ENTRY TEMPLATE:
       <Host name="[ENTER DOMAIN NAME]" appBase="webapps">
            <Context path="" docBase="[ENTER SYSTEM PATH]" />
        <Alias>[ENTER DOMAIN ALIAS]</Alias>
       </Host>
     -->

     <!-- ADD NEW HOSTS HERE -->
    <Host name="xxxx.xx" appBase="webapps">
            <Context path="" docBase="C:\xxxxxx" />
           <Alias>xxx.xx</Alias>
       <Alias>www.xxxxx.xx</Alias>
       <Alias>xxxx.xxxxxx.xx</Alias>
       </Host>
   </Engine>
 </Service>
</Server>
tomcat communication connector lucee
2个回答
0
投票

听起来您可能达到了某种连接限制。尝试为现有连接添加超时(以便清除无效连接),如果您有足够的内存,请尝试添加更多连接。您需要修改 BonCode 连接器(它使用 .NET)和 Tomcat 的 AJP 连接器设置中的设置。有关如何执行此操作的文档以及有用的调试部分可以在此处找到: http://www.boncode.net/boncode-connector


0
投票

检查server.xml中设置的超时时间是否小于IIS中设置的超时时间。

参考:https://www.boncode.net/connector/webdocs/Tomcat_Connector.htm

要更快地释放未使用/卡住的连接,您应该建立空闲超时。这些必须在 Tomcat 和 IIS 端进行设置,并且它们具有不同的形状。您应该确保将 Tomcat 空闲超时设置为 61000 到 121000 之间的值作为一个好的开始。该值应始终大于应用程序池空闲超时。如果没有,您将遇到“无法将数据写入传输连接:已建立的连接被主机中的软件中止”。错误。例如,以下定义将Tomcat空闲时的超时设置为2分1秒。另外,设置 keepAliveTimeout 也很重要,这样 Tomcat 在客户端仍处于活动状态时不会关闭连接。

<!-- Define an AJP 1.3 Connector on port 8009 -->
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" maxThreads="1000" connectionTimeout="121000" keepAliveTimeout="-1" packetSize="65536" />

您应该将 IIS 超时设置为小于 Tomcat 中的连接超时。下面展示通过操作IIS管理器高级设置进行2分钟设置

© www.soinside.com 2019 - 2024. All rights reserved.