Brand new install of Lucee on Window Server having site issues

[Barbara ONeal]

Ok so this morning I did a brand new install of Lucee on one of my servers. using the Windows Installer.  Everything went fine and i am able to get the Lucee Server administrator up.  All was good.

I have several innstances of Lucee / Railo running on this server (this is the first fresh install the other Lucee instance i upgraded from Railo)  I have set specific ports for each instance which i then set in the BonConnector.

I made a few modifications to the server.xml file to match my other Lucee installation specifically these settings.

<Connector port="8904" protocol="AJP/1.3" redirectPort="8443" connectionTimeout="60000" maxConnections="-1" />

I also made some adjustments to the web.xml file as i want my contents in a specific directory on another drive.  these are the same type of settings that i currently have on my other railo and lucee installs.

<servlet id="Lucee">
    <description>CFML Engine</description>
    <servlet-name>CFMLServlet</servlet-name>   
    <servlet-class>lucee.loader.servlet.CFMLServlet</servlet-class>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <!-- to specify the location of the Railo Server config and libraries,   -->
    <!-- uncomment the init-param below.  make sure that the param-value     -->
    <!-- points to a valid folder, and that the process that runs Railo has  -->
    <!-- write permissions to that folder.  leave commented for defaults.    -->

    <init-param>
            <param-name>lucee-web-directory</param-name>
            <param-value>E:\Lucee04-Web-INF/{web-context-label}/</param-value>
            <description>Lucee Web Directory directory</description>
    </init-param>

    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <!-- to specify the location of the Web Contexts' config and libraries,  -->
    <!-- uncomment the init-param below.  make sure that the param-value     -->
    <!-- points to a valid folder, and that the process that runs Railo has  -->
    <!-- write permissions to that folder.  the {web-context-label} can be   -->
    <!-- set in Railo Server Admin homepage.  leave commented for defaults.  -->
    <!--
    <init-param>
      <param-name>railo-web-directory</param-name>
      <param-value>/var/Railo/config/web/{web-context-label}/</param-value>
      <description>Railo Web Directory (for Website-specific configurations, settings, and libraries)</description>
    </init-param>
    !-->
    <load-on-startup>1</load-on-startup>
  </servlet>

After making these changes i then restarted the Lucee instance.  I am still able to get to the lucee server admin and on the home page i see that the context did get created in the e:Lucee0-web-inf directory.  All is good.

I then proceeded to take a site that currently had been running on another lucee instance and changed the bon connector to point to the new ajp port,  stopped the site in iis and restarted it.  When browsing to the site i get this error.

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).

now i have looked through several posts here and googled it as well.  I have checked and rechedked my settings.  I also have logging turned on to level 3 in the bon settings

all i get in the logs is this.

2015-07-17 10:52:21 BonCode AJP Connenctor version 1.0.23

nothing else is logged.

<Settings>
<Server>localhost</Server>
<Port>8904</Port>
<EnableRemoteAdmin>False</EnableRemoteAdmin>
<EnableHeaderDataSupport>True</EnableHeaderDataSupport>
<ForceSecureSession>False</ForceSecureSession>
<AllowEmptyHeaders>True</AllowEmptyHeaders>
<ResolveRemoteAddrFrom>HTTP_X_FORWARDED_FOR</ResolveRemoteAddrFrom>
<SkipIISCustomErrors>True</SkipIISCustomErrors>
<LogLevel>3</LogLevel>
<LogDir>E:\mywebsites\mywebsite\www\BIN\logs</LogDir>
</Settings>

I have verified that it is running ..Net 4 in the app pool like the other sites. 

So what am i missing?  I know it has to be something i am overlooking but for the life of me can figure out what it is.  Any insights would be a great help.

Thank you.

[Bilal]

Barbara,

couple of things to check:

a) what is the webport for the new lucee install and what response do you get when you hit it?

b) are you making the request on the iis server itself? If not can you do so and see whether you get more expanded error informtation?

c) are the catalina out log files showing anything?

HTH,

Bilal

[Barbara ONeal]

a) what is the webport for the new lucee install and what response do you get when you hit it?

http://127.0.0.1:8804/lucee/admin/server.cfm    I get the Main Lucee login page.
C:\lucee04\tomcat\webapps\ROOT\  this is the webroot inside of Lucee for the main app.  

b) are you making the request on the iis server itself?

Yes I have my host file set up to resolve sites locally.  And I am trying to get to the site from inside the server not the outside. 

 

If not can you do so and see whether you get more expanded error information?

It doesn't give any more information even with logging set at a higher level. 

c) are the catalina out log files showing anything?

Here is some of the stuff in the logs.

[mod_cfml] Host Value => dev.mywebsite.org:8804
[mod_cfml] FATAL: Invalid DocRoot: Null or zero-length.
[mod_cfml] Decoded Requst URI => /lb/default.cfm
[mod_cfml] QueryString => null
[mod_cfml] DocRoot Value => null
[mod_cfml] Host Value => dev.wbbrchamber.org:8804
[mod_cfml] FATAL: Invalid DocRoot: Null or zero-length.
[mod_cfml] Decoded Requst URI => /lucee/admin/server.cfm
[mod_cfml] QueryString => null
[mod_cfml] DocRoot Value => null
[mod_cfml] Host Value => 127.0.0.1:8804
[mod_cfml] FATAL: Invalid DocRoot: Null or zero-length.
[mod_cfml] Decoded Requst URI => /lucee/res/css/admin-77aade32be11a0b0.css.cfm
[mod_cfml] QueryString => 1437147435339
[mod_cfml] DocRoot Value => null
[mod_cfml] Host Value => 127.0.0.1:8804
[mod_cfml] FATAL: Invalid DocRoot: Null or zero-length.
[mod_cfml] Decoded Requst URI => /lucee/admin/resources/js/jquery-1.7.2.min.js.cfm
[mod_cfml] QueryString => null
[mod_cfml] DocRoot Value => null
[mod_cfml] Host Value => 127.0.0.1:8804
[mod_cfml] FATAL: Invalid DocRoot: Null or zero-length.
[mod_cfml] Decoded Requst URI => /lucee/admin/resources/js/jquery.blockUI.js.cfm
[mod_cfml] QueryString => null
[mod_cfml] DocRoot Value => null
[mod_cfml] Host Value => 127.0.0.1:8804
[mod_cfml] FATAL: Invalid DocRoot: Null or zero-length.
[mod_cfml] Decoded Requst URI => /lucee/admin/resources/js/admin.js.cfm

[Jordan Michaels]

All of those logs in the catalina.out are for hits directly to the 8804 port, which is tomcat's web server. There's nothing there to indicate requests from the BonCode connector - coming in over 8904 - are actually reaching Tomcat. You might have a connection issue with port 8904. Can you verify Tomcat is up and listening on port 8904, and that it's not firewalled?

Last, and this doesn't directly effect your issue yet, but if you used the most recent installer your Tomcat install of mod_cfml is going to need the shared secret key. You'll want to add the <ModCFMLSecret>[YourRandomSecretKeyHere]</ModCFMLSecret> to your BonCode config and make sure the key matches the secret key config in your Tomcat server.xml.

-Jordan

--
You received this message because you are subscribed to the Google Groups "Lucee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/1dd93890-a503-4399-84fd-938397971b09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Barbara ONeal]

Jordan,  For now these requests are directly on the server.  The firewall or Load balance isn't' even in play yet.  These are just direct hits from inside the server. 
Also i do not see an entry for a secret key inside the server.xml file. 

Below is the contents of my server.xml file

I basially followed the same type of set up as the orginal Railo instance.  I also did a compare of the server.xml files between my current Lucee instance that is up and running and the new one.  other than the ports they are the same. 

HttpPort -webserver    8804
ShutdownPort    8004
AJP_Port       8904


Here is the settings of the bon connector:

<Settings>
<Server>localhost</Server>
<Port>8904</Port>
<EnableRemoteAdmin>False</EnableRemoteAdmin>
<EnableHeaderDataSupport>True</EnableHeaderDataSupport>
<ForceSecureSession>False</ForceSecureSession>
<AllowEmptyHeaders>True</AllowEmptyHeaders>
<ResolveRemoteAddrFrom>HTTP_X_FORWARDED_FOR</ResolveRemoteAddrFrom>

<LogLevel>3</LogLevel>
<LogDir>E:\mywebsite.org\www\BIN\logs</LogDir>
</Settings>

<?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="8004" shutdown="SHUTDOWN">
  <!-- 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="8804" 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 HTTP/1.1 Connector on port 8443
         This connector uses the JSSE configuration, when using APR, the
         connector should be using the OpenSSL style configuration
         described in the APR documentation -->
    <!--
    <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
               maxThreads="150" scheme="https" secure="true"
               clientAuth="false" sslProtocol="TLS" />
    -->

    <!-- Define an AJP 1.3 Connector on port 8009 -->

    <Connector port="8904" protocol="AJP/1.3" redirectPort="8443" connectionTimeout="60000" maxConnections="-1" />

    <!-- 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" resolveHosts="false"/>
   
    <!-- visit modcfml.org for details on mod_cfml configuration options -->
    <Valve className="mod_cfml.core"
             loggingEnabled="true"
             waitForContext="10"
             maxContexts="800"
             timeBetweenContexts="100"
       
        />    
      </Host>

      <Host name="localhost" appBase="webapps">
        <Context path="" docBase="C:\inetpub\wwwroot\" />
      </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/getrailo.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>
      -->


    </Engine>
  </Service>
</Server>

[Bilal]

Barbara,

please make a local version call to the connector if you can.

http://[hostname]/a.cfm?BonCodeConnectorVersion=true

If you get an error there your IIS configuration is problematic. (.net conflict?)

For some reason the header data support information is not being transferred to tomcat. 

To check simply turn off the mod_cfml valve and see whether you get any response; then turn it back on. 

Any difference?

If not, looking into IIS and your setting file is probably your next step.

-Bilal

[Barbara ONeal]

Bilal

 The only error i get is the same one i have been getting:

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).

In IIS I have the site set to:  .net 4.0 integrated

I turned off the mod_cfml and set the sight up in the server.xml file get the same response. 

Which settings file do you want me to look at? 

here is the bon settings. 

<Settings>
<Server>localhost</Server>
<Port>8904</Port>
<EnableRemoteAdmin>False</EnableRemoteAdmin>
<EnableHeaderDataSupport>True</EnableHeaderDataSupport>
<ForceSecureSession>False</ForceSecureSession>
<AllowEmptyHeaders>True</AllowEmptyHeaders>
<ResolveRemoteAddrFrom>HTTP_X_FORWARDED_FOR</ResolveRemoteAddrFrom>
<LogLevel>3</LogLevel>

<LogDir>E:\mywebsite\www\BIN\logs</LogDir>
</Settings>

[Barbara ONeal]

ok so I finally have the site up and running but I had to actually run the bon code connector software. On other sites / other servers all i had to do was drop in the bin folder into the web root and it worked.