Have to restart Lucee every morning

Hello everyone, i’m extremely new to Lucee, just testing it out to see if
we can use it instead of ACF as its so expensive.

I’ve put together a test server running:

Windows 2012 64bit (current on patches)
8gb ram
IIS 8
Tomcat 7.0.59 (installed during lucee installation)
Lucee 4.5.1 (upgraded to .008 from the dev path now)
MySQL 5.6.22

Every day sometime during the night the lucee server seems to crash and
only responds with the following tomcat error:

Error connecting to Apache Tomcat instance.------------------------------
Please check that a Tomcat server is running at given location and port.
Details:
No connection could be made because the target machine actively refused it
127.0.0.1:8009

You can change this message by changing TomcatConnectErrorURL setting in
setting file.

If i stop and then restart the lucee server using the lucee server icon by
the clock (actually i think this restarts tomcat?) then everything comes
back up fine. for a while.

unfortunately i have absolutely no experience with apache, lucee, railo and
java. i’ve looked at all the logs i can find and there isn’t anything in
there at the time of the crash. I have external monitoring every minute so
i know the time that the server drops out.

the lucee server properties shows under the java tab
initial memory pool 256mb
max memory pool 512mb
thread stack size has no value entered

i am getting some errors at different times not near the time of the actual
crash tho that possibly are contributing, i just don’t know enough yet to
have a clue. this first error looks promising tho, that error happens
immediately after i restart the lucee server and memory usage does
seem very high to me after a while.

  1. org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
    SEVERE: The web application appears to have started a thread named
    [Thread-3] but has failed to stop it. This is very likely to create a
    memory leak.
  2. static resource /lucee/res/css/admin-1ea2d521fff0203b.css.cfm was not
    found @
    C:\inetpub\wwwroot\WEB-INF\lucee\context\res\css\admin-1ea2d521fff0203b.css
  3. org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING:
    [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
    ‘xmlNamespaceAware’ to ‘false’ did not find a matching property.
  4. org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING:
    [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
    ‘xmlValidation’ to ‘false’ did not find a matching property.

Thank so much for any guidance you can give me.

Jeramie

Strange situation. I think we need more information to help. I run Lucee
on Linux and before that Railo. My box might go months without being
rebooted never had Lucee crash. Have you watched the memory use with
VisualVM or some other tool?

Andrew PenhorwoodOn Monday, March 16, 2015 at 11:24:14 AM UTC-4, Jeramie Gatchell wrote:

Hello everyone, i’m extremely new to Lucee, just testing it out to see if
we can use it instead of ACF as its so expensive.

I’ve put together a test server running:

Windows 2012 64bit (current on patches)
8gb ram
IIS 8
Tomcat 7.0.59 (installed during lucee installation)
Lucee 4.5.1 (upgraded to .008 from the dev path now)
MySQL 5.6.22

Every day sometime during the night the lucee server seems to crash and
only responds with the following tomcat error:

Error connecting to Apache Tomcat instance.

Please check that a Tomcat server is running at given location and port.
Details:
No connection could be made because the target machine actively refused it
127.0.0.1:8009

You can change this message by changing TomcatConnectErrorURL setting in
setting file.

If i stop and then restart the lucee server using the lucee server icon by
the clock (actually i think this restarts tomcat?) then everything comes
back up fine. for a while.

unfortunately i have absolutely no experience with apache, lucee, railo
and java. i’ve looked at all the logs i can find and there isn’t anything
in there at the time of the crash. I have external monitoring every minute
so i know the time that the server drops out.

the lucee server properties shows under the java tab
initial memory pool 256mb
max memory pool 512mb
thread stack size has no value entered

i am getting some errors at different times not near the time of the
actual crash tho that possibly are contributing, i just don’t know enough
yet to have a clue. this first error looks promising tho, that error
happens immediately after i restart the lucee server and memory usage does
seem very high to me after a while.

  1. org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
    SEVERE: The web application appears to have started a thread named
    [Thread-3] but has failed to stop it. This is very likely to create a
    memory leak.
  2. static resource /lucee/res/css/admin-1ea2d521fff0203b.css.cfm was
    not found @
    C:\inetpub\wwwroot\WEB-INF\lucee\context\res\css\admin-1ea2d521fff0203b.css
  3. org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING:
    [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
    ‘xmlNamespaceAware’ to ‘false’ did not find a matching property.
  4. org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING:
    [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
    ‘xmlValidation’ to ‘false’ did not find a matching property.

Thank so much for any guidance you can give me.

Jeramie

Hi Andrew,

Thanks for the fast reply!

I installed VisualVM (i don’t know anything about java unfortunately) but
i’m not sure what i’m looking for. i’m watching the heap monitor
currently as it seems to have the most “action” (lol). i’ll attach a
screenshot.

here also are the server.xml file and the BonCodeAJP13.settings files,
i’ve sanitized them i hope… i do have 3 websites running on this server,
but they are freebie ones i host for friends that get 1 or 2 hits a month
if they are lucky…

BonCodeAJP13.settings (249 Bytes)

server.xml (8.42 KB)

i’m so sorry for not replying, i thought the system would email me when
there was a reply to the thread! woops!

i am indeed running jvm 1.8.

i’m going to attach the log files for the 19th. The server crashed at
7:34pm and started responding with the error in the op. at 10:23pm i
stopped and started the lucee server.On Monday, March 16, 2015 at 8:24:14 AM UTC-7, Jeramie Gatchell wrote:

Hello everyone, i’m extremely new to Lucee, just testing it out to see if
we can use it instead of ACF as its so expensive.

I’ve put together a test server running:

Windows 2012 64bit (current on patches)
8gb ram
IIS 8
Tomcat 7.0.59 (installed during lucee installation)
Lucee 4.5.1 (upgraded to .008 from the dev path now)
MySQL 5.6.22

Every day sometime during the night the lucee server seems to crash and
only responds with the following tomcat error:

Error connecting to Apache Tomcat instance.

Please check that a Tomcat server is running at given location and port.
Details:
No connection could be made because the target machine actively refused it
127.0.0.1:8009

You can change this message by changing TomcatConnectErrorURL setting in
setting file.

If i stop and then restart the lucee server using the lucee server icon by
the clock (actually i think this restarts tomcat?) then everything comes
back up fine. for a while.

unfortunately i have absolutely no experience with apache, lucee, railo
and java. i’ve looked at all the logs i can find and there isn’t anything
in there at the time of the crash. I have external monitoring every minute
so i know the time that the server drops out.

the lucee server properties shows under the java tab
initial memory pool 256mb
max memory pool 512mb
thread stack size has no value entered

i am getting some errors at different times not near the time of the
actual crash tho that possibly are contributing, i just don’t know enough
yet to have a clue. this first error looks promising tho, that error
happens immediately after i restart the lucee server and memory usage does
seem very high to me after a while.

  1. org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
    SEVERE: The web application appears to have started a thread named
    [Thread-3] but has failed to stop it. This is very likely to create a
    memory leak.
  2. static resource /lucee/res/css/admin-1ea2d521fff0203b.css.cfm was
    not found @
    C:\inetpub\wwwroot\WEB-INF\lucee\context\res\css\admin-1ea2d521fff0203b.css
  3. org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING:
    [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
    ‘xmlNamespaceAware’ to ‘false’ did not find a matching property.
  4. org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING:
    [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
    ‘xmlValidation’ to ‘false’ did not find a matching property.

Thank so much for any guidance you can give me.

Jeramie

localhost_access_log.2015-03-19.txt (345 Bytes)

commons-daemon.2015-03-19.log (454 Bytes)

localhost.2015-03-19.log (0 Bytes)

localhost.2015-03-19.log (0 Bytes)

catalina.2015-03-19.log (4.66 KB)

lucee-stdout.2015-03-19.log (2.75 KB)

lucee-stderr.2015-03-19.log (6.42 KB)

localhost.2015-03-19.log (0 Bytes)

Hi Jeramie,
After looking screenshot I realize you are not monitoring Lucee instead it
was stats for Visulavm itself. You may need add one JMX entry for Lucee as
well. I had wrote blog in past for setup with ColdFusion but it will be
similar with Lucee as well.
http://www.thecfguy.com/blog/configure-coldfusion-with-visualvm/

Just give try and may be you want to add some more plugin as suggested by
others.

Thanks,
PriteshOn Monday, 16 March 2015 23:13:04 UTC+5:30, Jeramie Gatchell wrote:

Hi Andrew,

Thanks for the fast reply!

I installed VisualVM (i don’t know anything about java unfortunately) but
i’m not sure what i’m looking for. i’m watching the heap monitor
currently as it seems to have the most “action” (lol). i’ll attach a
screenshot.

oh wow, you are correct Pritesh, thank you. I was indeed just monitoring
visualvm itself…

Using your blog i was able to add lucee and see far different numbers (lol,
imagine that!).

So far, the heap size is sitting around 1.75GB and the heap used is at
about 1.1GB and slowly rising. I started a tracer on it and will see what
happens if/when it crashes next. its been up nearly 48 hours so far, thats
the longest its stayed alive for me so far.

This is a windows IIS issue, not a Tomcat / Lucee / Railo / ACF issue.

I have seen this numerous times where the same code on the same physical or
virtual servers requires the Windows boxes to reboot where as the Linux /
NIX boxes are fine.

The memory leak is dependent upon IIS Services, the version of Java you
have running, and possibly the use or lack of use of error correcting
memory.

The easiest thing to do is just run a restart services script or reboot
script during off hours. If you can not do that, as its an always up,
always online site, your choices are to either use an alternative install,
or fire up at least one other server and start load balancing.On Monday, March 16, 2015 at 11:24:14 AM UTC-4, Jeramie Gatchell wrote:

Hello everyone, i’m extremely new to Lucee, just testing it out to see if
we can use it instead of ACF as its so expensive.

I’ve put together a test server running:

Windows 2012 64bit (current on patches)
8gb ram
IIS 8
Tomcat 7.0.59 (installed during lucee installation)
Lucee 4.5.1 (upgraded to .008 from the dev path now)
MySQL 5.6.22

Every day sometime during the night the lucee server seems to crash and
only responds with the following tomcat error:

Error connecting to Apache Tomcat instance.

Please check that a Tomcat server is running at given location and port.
Details:
No connection could be made because the target machine actively refused it
127.0.0.1:8009

You can change this message by changing TomcatConnectErrorURL setting in
setting file.

If i stop and then restart the lucee server using the lucee server icon by
the clock (actually i think this restarts tomcat?) then everything comes
back up fine. for a while.

unfortunately i have absolutely no experience with apache, lucee, railo
and java. i’ve looked at all the logs i can find and there isn’t anything
in there at the time of the crash. I have external monitoring every minute
so i know the time that the server drops out.

the lucee server properties shows under the java tab
initial memory pool 256mb
max memory pool 512mb
thread stack size has no value entered

i am getting some errors at different times not near the time of the
actual crash tho that possibly are contributing, i just don’t know enough
yet to have a clue. this first error looks promising tho, that error
happens immediately after i restart the lucee server and memory usage does
seem very high to me after a while.

  1. org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
    SEVERE: The web application appears to have started a thread named
    [Thread-3] but has failed to stop it. This is very likely to create a
    memory leak.
  2. static resource /lucee/res/css/admin-1ea2d521fff0203b.css.cfm was
    not found @
    C:\inetpub\wwwroot\WEB-INF\lucee\context\res\css\admin-1ea2d521fff0203b.css
  3. org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING:
    [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
    ‘xmlNamespaceAware’ to ‘false’ did not find a matching property.
  4. org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING:
    [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
    ‘xmlValidation’ to ‘false’ did not find a matching property.

Thank so much for any guidance you can give me.

Jeramie

We used to have the same issue with Railo last year. I would have to
restart every day. Since tweaking, Railo never crashes or needs to be
restarted. You can see my post here
(https://groups.google.com/forum/#!topic/railo/FAd4uXOddJY) with
suggestions. Some of our settings have changed since then, attached is
screenshot of what my settings are at now, and they are rock solid. Another
key is to have your maxThreads in your Tomcat server.xml at a high number.
We used to have it at 500, but after a week, the slots would fill up thus
locking up the server making Railo seem unresponsive (when it really
wasn’t) We have since changed it to 1500, and haven’t had an issue since.
YOu can see how many threads you are using in your tomcat web interface.

My setup is

Windows Server 2012 (R1) with 32gb Ram
IIS8 using BonCode
Mod_CFML with TomCat 7

We haven’t upgrade our production box to Lucce yet, but will be doing so
this month.On Monday, March 23, 2015 at 3:47:53 PM UTC-4, Jeramie Gatchell wrote:

oh wow, you are correct Pritesh, thank you. I was indeed just monitoring
visualvm itself…

Using your blog i was able to add lucee and see far different numbers
(lol, imagine that!).

So far, the heap size is sitting around 1.75GB and the heap used is at
about 1.1GB and slowly rising. I started a tracer on it and will see what
happens if/when it crashes next. its been up nearly 48 hours so far, thats
the longest its stayed alive for me so far.

we have ACF virtual machines with 2gb of ram that run great

Did i read that correctly? You’re running a windows box with a total of 2GB
RAM and serving a Lucee environment?

I have posted an example of a memory configuration for Tomcat here:

https://bitbucket.org/lucee/lucee/wiki/Configuring%20Tomcat%20as%20a%20Windows%20service

The configuration runs on some servers with no problems.

If your box has less memory, decrease the settings accordingly.

oh absolutely. using vmware, i’m looking at one right now that is running
windows server 2012 has 2.6gb of ram dedicated to it, using 1.6gb. has IIS,
DNS, MS SQL and ACF and runs perfectly fine. we haven’t had to reset it
since the last set of MS patches that forced a reset.

I have another that is running server 2008 with 1.35GB of ram dedicated to
it, using 977mb that is running acf, iis and dns albeit i believe that one
is an older version of acf.On Thursday, March 26, 2015 at 10:46:59 AM UTC-7, Martin Schaible wrote:

we have ACF virtual machines with 2gb of ram that run great

Did i read that correctly? You’re running a windows box with a total of
2GB RAM and serving a Lucee environment?

I have posted an example of a memory configuration for Tomcat here:

https://bitbucket.org/lucee/lucee/wiki/Configuring%20Tomcat%20as%20a%20Windows%20service

The configuration runs on some servers with no problems.

If your box has less memory, decrease the settings accordingly.

should i be switching over to 8?

I tested tomcat 8 with Railo and Lucee only. Works perfectly. I wouldn’t
update to Tomcat 8 until your problems are solved. Don’t change too many
parameters at once :wink:

I’m really surprised that you CFML server works with less memory compared
to a microwave oven or a phone :slight_smile: But at the end of the day, Tomcat will
need more Memory sooner or later. As Terry said, i would go for
FusionReactor to see what’s going on under the hood.

oh sorry, i just reread your original post, no its not lucee, its adobe
coldfusion.

Also, i’m going through your guide and i see that its for tomcat 8, i’m
running the lucee installed tomcat 7. should i be switching over to 8?On Thursday, March 26, 2015 at 10:46:59 AM UTC-7, Martin Schaible wrote:

we have ACF virtual machines with 2gb of ram that run great

Did i read that correctly? You’re running a windows box with a total of
2GB RAM and serving a Lucee environment?

I have posted an example of a memory configuration for Tomcat here:

https://bitbucket.org/lucee/lucee/wiki/Configuring%20Tomcat%20as%20a%20Windows%20service

The configuration runs on some servers with no problems.

If your box has less memory, decrease the settings accordingly.

does anyone the minimum memory recommended for a lucee install on windows?

we are a tiny development company and don’t have anything with 32gb… we
have ACF virtual machines with 2gb of ram that run great.

there really isn’t anything running on this, a couple extremely simple
websites with very little cfml. really only one app and its about as basic
as they come. they all run plenty fast until they stop. but i’ll give this
a try and see if it sheds any light.

thank you!!On Thursday, March 26, 2015 at 1:04:15 PM UTC-7, Terry Whitney wrote:

I would install a trial copy of Fusion Reactor on your system and see
where your application is slow and where it crashes.

Additional items I would suggest.

Disable UAC and any AV software temporarily.

On Monday, March 16, 2015 at 11:24:14 AM UTC-4, Jeramie Gatchell wrote:

Hello everyone, i’m extremely new to Lucee, just testing it out to see if
we can use it instead of ACF as its so expensive.

I’ve put together a test server running:

Windows 2012 64bit (current on patches)
8gb ram
IIS 8
Tomcat 7.0.59 (installed during lucee installation)
Lucee 4.5.1 (upgraded to .008 from the dev path now)
MySQL 5.6.22

Every day sometime during the night the lucee server seems to crash and
only responds with the following tomcat error:

Error connecting to Apache Tomcat instance.

Please check that a Tomcat server is running at given location and port.
Details:
No connection could be made because the target machine actively refused
it 127.0.0.1:8009

You can change this message by changing TomcatConnectErrorURL setting in
setting file.

If i stop and then restart the lucee server using the lucee server icon
by the clock (actually i think this restarts tomcat?) then everything comes
back up fine. for a while.

unfortunately i have absolutely no experience with apache, lucee, railo
and java. i’ve looked at all the logs i can find and there isn’t anything
in there at the time of the crash. I have external monitoring every minute
so i know the time that the server drops out.

the lucee server properties shows under the java tab
initial memory pool 256mb
max memory pool 512mb
thread stack size has no value entered

i am getting some errors at different times not near the time of the
actual crash tho that possibly are contributing, i just don’t know enough
yet to have a clue. this first error looks promising tho, that error
happens immediately after i restart the lucee server and memory usage does
seem very high to me after a while.

  1. org.apache.catalina.loader.WebappClassLoader
    clearReferencesThreads SEVERE: The web application appears to have
    started a thread named [Thread-3] but has failed to stop it. This is very
    likely to create a memory leak.
  2. static resource /lucee/res/css/admin-1ea2d521fff0203b.css.cfm was
    not found @
    C:\inetpub\wwwroot\WEB-INF\lucee\context\res\css\admin-1ea2d521fff0203b.css
  3. org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING:
    [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
    ‘xmlNamespaceAware’ to ‘false’ did not find a matching property.
  4. org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING:
    [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
    ‘xmlValidation’ to ‘false’ did not find a matching property.

Thank so much for any guidance you can give me.

Jeramie

oh and thank you so much for the memory config for tomcat!!! i’ll check
that out right now!On Thursday, March 26, 2015 at 11:03:17 AM UTC-7, Jeramie Gatchell wrote:

oh absolutely. using vmware, i’m looking at one right now that is running
windows server 2012 has 2.6gb of ram dedicated to it, using 1.6gb. has IIS,
DNS, MS SQL and ACF and runs perfectly fine. we haven’t had to reset it
since the last set of MS patches that forced a reset.

I have another that is running server 2008 with 1.35GB of ram dedicated to
it, using 977mb that is running acf, iis and dns albeit i believe that one
is an older version of acf.

On Thursday, March 26, 2015 at 10:46:59 AM UTC-7, Martin Schaible wrote:

we have ACF virtual machines with 2gb of ram that run great

Did i read that correctly? You’re running a windows box with a total of
2GB RAM and serving a Lucee environment?

I have posted an example of a memory configuration for Tomcat here:

https://bitbucket.org/lucee/lucee/wiki/Configuring%20Tomcat%20as%20a%20Windows%20service

The configuration runs on some servers with no problems.

If your box has less memory, decrease the settings accordingly.

I would install a trial copy of Fusion Reactor on your system and see where
your application is slow and where it crashes.

Additional items I would suggest.

Disable UAC and any AV software temporarily.On Monday, March 16, 2015 at 11:24:14 AM UTC-4, Jeramie Gatchell wrote:

Hello everyone, i’m extremely new to Lucee, just testing it out to see if
we can use it instead of ACF as its so expensive.

I’ve put together a test server running:

Windows 2012 64bit (current on patches)
8gb ram
IIS 8
Tomcat 7.0.59 (installed during lucee installation)
Lucee 4.5.1 (upgraded to .008 from the dev path now)
MySQL 5.6.22

Every day sometime during the night the lucee server seems to crash and
only responds with the following tomcat error:

Error connecting to Apache Tomcat instance.

Please check that a Tomcat server is running at given location and port.
Details:
No connection could be made because the target machine actively refused it
127.0.0.1:8009

You can change this message by changing TomcatConnectErrorURL setting in
setting file.

If i stop and then restart the lucee server using the lucee server icon by
the clock (actually i think this restarts tomcat?) then everything comes
back up fine. for a while.

unfortunately i have absolutely no experience with apache, lucee, railo
and java. i’ve looked at all the logs i can find and there isn’t anything
in there at the time of the crash. I have external monitoring every minute
so i know the time that the server drops out.

the lucee server properties shows under the java tab
initial memory pool 256mb
max memory pool 512mb
thread stack size has no value entered

i am getting some errors at different times not near the time of the
actual crash tho that possibly are contributing, i just don’t know enough
yet to have a clue. this first error looks promising tho, that error
happens immediately after i restart the lucee server and memory usage does
seem very high to me after a while.

  1. org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
    SEVERE: The web application appears to have started a thread named
    [Thread-3] but has failed to stop it. This is very likely to create a
    memory leak.
  2. static resource /lucee/res/css/admin-1ea2d521fff0203b.css.cfm was
    not found @
    C:\inetpub\wwwroot\WEB-INF\lucee\context\res\css\admin-1ea2d521fff0203b.css
  3. org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING:
    [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
    ‘xmlNamespaceAware’ to ‘false’ did not find a matching property.
  4. org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING:
    [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
    ‘xmlValidation’ to ‘false’ did not find a matching property.

Thank so much for any guidance you can give me.

Jeramie

Thanks Jason, i will try this. the previous changes i made with regard to
increasing the max mem pool to 4gb only delayed the crashes. it takes 2 or
3 days to crash now. i’ve moved it back down to 2gb, one because it should
be able to run with that much to be viable for us and second to speed up
the crashing so i know if something worked or not.On Tuesday, March 24, 2015 at 9:05:49 AM UTC-7, Jason Tully wrote:

We used to have the same issue with Railo last year. I would have to
restart every day. Since tweaking, Railo never crashes or needs to be
restarted. You can see my post here (
https://groups.google.com/forum/#!topic/railo/FAd4uXOddJY) with
suggestions. Some of our settings have changed since then, attached is
screenshot of what my settings are at now, and they are rock solid. Another
key is to have your maxThreads in your Tomcat server.xml at a high number.
We used to have it at 500, but after a week, the slots would fill up thus
locking up the server making Railo seem unresponsive (when it really
wasn’t) We have since changed it to 1500, and haven’t had an issue since.
YOu can see how many threads you are using in your tomcat web interface.

My setup is

Windows Server 2012 (R1) with 32gb Ram
IIS8 using BonCode
Mod_CFML with TomCat 7

We haven’t upgrade our production box to Lucce yet, but will be doing so
this month.

On Monday, March 23, 2015 at 3:47:53 PM UTC-4, Jeramie Gatchell wrote:

oh wow, you are correct Pritesh, thank you. I was indeed just monitoring
visualvm itself…

Using your blog i was able to add lucee and see far different numbers
(lol, imagine that!).

So far, the heap size is sitting around 1.75GB and the heap used is at
about 1.1GB and slowly rising. I started a tracer on it and will see what
happens if/when it crashes next. its been up nearly 48 hours so far, thats
the longest its stayed alive for me so far.

Jeremy the error you are seing is from boncode connector. It does not mean lucee is down, only that tomcat does not accept any further connection on Ajp port. Under low load this is normally an issue with timeouts.
please refer back to my earlier response and add a connection timeout for tomcat. This should take care of your issue.

-Bilal