Unresponsive page issue

dev google-group-archive
1

We seem to have some sort of recurring issue with our production machine
where occasionally a cfm template will simply stop responding. No timeout
error, just no response. Once the issue occurs once, I can try the page in
different browsers, logged in as different users, requests from different
locations, and it always displays the same problem. The weird thing is
that if i edit that cfm page and change it in any way such as adding a
non-breaking space somewhere, it starts working again. If i change it back
it reverts to being broken. If i restart the server it fixes it as well.
This same issue has happened several times before with different cfm
templates. Always with the same issue, where adding a non-breaking space
fixes it.

We’re running Lucee 4.5 on a Windows Server with IIS & Tomcat 8 without
ModCFML. Any ideas on where to look to correct this? Do i need to
explicitly turn caching off within tomcat? Right now I’m using pretty
close to default Lucee settings.

<?xml version='1.0' encoding='utf-8'?> 
        <Server port="8005" shutdown="SHUTDOWN">
          <Listener className="org.apache.catalina.startup.VersionLoggerListener" />
          <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />
          <Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
          <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
          <Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" />
          <Service name="Catalina">
            <Connector port="8888" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" />
            <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />
            <Engine name="Catalina" defaultHost="127.0.0.1">
                <Host name="127.0.0.1" autoDeploy="false" unpackWARs="false" appBase="webapps">
                    <Context docBase="C:\inetpub\wwwroot\application\" path=""/>
                    <Alias>*.domain.com</Alias>
                </Host>
            </Engine>
          </Service>
        </Server>
2

eventually the server did respond with the error below. Seems strange that
adding a non breaking space fixes it though:

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

3

Jace… we had a similar generic communication error this because of javas
jacobcom object. Take a look at c:/windows for some win error dump (.mdmp)
files and take a look at the refering error log files in the same folder.
You might find somerhing there.Am 24.06.2016 18:39 schrieb “Jace Coleman” <@Jace_Coleman>:

eventually the server did respond with the error below. Seems strange
that adding a non breaking space fixes it though:

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

–
Win a ticket to dev.objective from Lucee via Twitter, see
http://bit.ly/1UbTMWj for details, good luck and see you there…

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+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/32479a39-80b3-478c-a699-7fdc1d5d9fb2%40googlegroups.com
https://groups.google.com/d/msgid/lucee/32479a39-80b3-478c-a699-7fdc1d5d9fb2%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

4

Jace,
you may be running into a situation where all your allocated threads have
been used for connections.
Here is a slight modification on the AJP definition in server.xml that
increases the number of threads as well as sets a timeout on idle ones
(since you seem to have a timeout on http already):

Also, if you are not on the latest version of the connector I would
recommend you look into upgrading it if possible:
http://tomcatiis.riaforge.org/blog/index.cfm/2015/6/16/Upgrading-Railo-or-Lucee-Connector-Version

Best,
Bilal>