Lucee stops serving 3 / 4 times per day - odd error

Hello!

Please could anyone help me - I have this odd error throughout the
lucee-stderr log:

;;lucee.runtime.engine.Controler$ControlerThread.stop0(java.lang.Object);java.lang.NoSuchMethodException:
lucee.runtime.engine.Controler$ControlerThread.stop0(java.lang.Object)
at java.lang.Class.getMethod(Class.java:1786)
at lucee.commons.io.StopThread.run(SystemUtil.java:1085)

I’m not 100% sure the above error is the cause of .cfm pages not being
served but cannot find any other logs near the time of the crash.

Running Lucee 4.5.3.020

Cheers
Luke

Error from application.log:

“ERROR”,“Thread-29”,“01/06/2017”,“10:37:53”,“controler”,"was not able to
stop conroler thread running for
60029ms;java.lang.Throwable;java.lang.Throwable
at java.net.DualStackPlainDatagramSocketImpl.socketReceiveOrPeekData(Native
Method)
at
java.net.DualStackPlainDatagramSocketImpl.receive0(DualStackPlainDatagramSocketImpl.java:120)
at
java.net.AbstractPlainDatagramSocketImpl.receive(AbstractPlainDatagramSocketImpl.java:144)
at java.net.DatagramSocket.receive(DatagramSocket.java:812)
at lucee.runtime.net.ntp.NtpClient.getOffset(NtpClient.java:67)
at
lucee.runtime.config.ConfigImpl.reloadTimeServerOffset(ConfigImpl.java:462)
at lucee.runtime.engine.Controler.control(Controler.java:291)
at lucee.runtime.engine.Controler.control(Controler.java:214)
at lucee.runtime.engine.Controler.access$000(Controler.java:59)
at lucee.runtime.engine.Controler$ControlerThread.run(Controler.java:110)

Running on windows 2012R2, iis 8.5

That message comes from Lucee’s service thread that runs all the time
looking for requests that have exceeded the time limit and tries to kill
them. If you see a lot of those, it means Lucee is trying to kill a lot of
long running requests, but those messages don’t really tell you anything
other than the fact that Lucee has tried to kill something. Grab
FusionReactor, if you don’t already have a license, and configured it to
E-mail you when request times exceed a threshold. That will dump a ton of
into into your inbox including what the running requests are doing and how
long they’ve been there.

Thanks!

~BradOn Friday, January 6, 2017 at 4:56:10 AM UTC-6, luke insley wrote:

Error from application.log:

“ERROR”,“Thread-29”,“01/06/2017”,“10:37:53”,“controler”,"was not able to
stop conroler thread running for
60029ms;java.lang.Throwable;java.lang.Throwable
at
java.net.DualStackPlainDatagramSocketImpl.socketReceiveOrPeekData(Native
Method)
at
java.net.DualStackPlainDatagramSocketImpl.receive0(DualStackPlainDatagramSocketImpl.java:120)
at
java.net.AbstractPlainDatagramSocketImpl.receive(AbstractPlainDatagramSocketImpl.java:144)
at java.net.DatagramSocket.receive(DatagramSocket.java:812)
at lucee.runtime.net.ntp.NtpClient.getOffset(NtpClient.java:67)
at
lucee.runtime.config.ConfigImpl.reloadTimeServerOffset(ConfigImpl.java:462)
at lucee.runtime.engine.Controler.control(Controler.java:291)
at lucee.runtime.engine.Controler.control(Controler.java:214)
at lucee.runtime.engine.Controler.access$000(Controler.java:59)
at lucee.runtime.engine.Controler$ControlerThread.run(Controler.java:110)

Thanks for the hint Brad, I had FR and will set the email thing up.

Same server, and this may or may not be related, I’ve turned logs on
through the boncode connector, and I see this:
Unable to write data to the transport connection: An established
connection was aborted by the software in your host machine.

Google gives me this post, I’ve tried the recommendations on here (change
connector max connections to 0).
https://groups.google.com/forum/#!topic/lucee/rjk71m_tJGE
Making the change loses this error, but then pages don’t load correctly,
they just spin in the browser, only way to resolve that is to reset IIS
which works for a couple hours max.

2017-01-10 11:18:05 New Connection 33 of 1000 to tomcat: [::1]:8009 ID: 500
[T-33]
2017-01-10 11:18:05 1.0.20 ERROR
TCP Client level – Server/Port:localhost/8009
Unable to write data to the transport connection: An established connection
was aborted by the software in your host machine.
2017-01-10 11:18:05 One Connection raised an error
2017-01-10 11:18:18 New Connection 34 of 1000 to tomcat: [::1]:8009 ID: 501
[T-31]
2017-01-10 11:18:28 New Connection 35 of 1000 to tomcat: [::1]:8009 ID: 502
[T-32]
2017-01-10 11:18:28 1.0.20 ERROR
TCP Client level – Server/Port:localhost/8009
Unable to write data to the transport connection: An established connection
was aborted by the software in your host machine.
2017-01-10 11:18:28 One Connection raised an error
2017-01-10 11:18:31 New Connection 36 of 1000 to tomcat: [::1]:8009 ID: 503
[T-33]
2017-01-10 11:18:31 1.0.20 ERROR
TCP Client level – Server/Port:localhost/8009
Unable to write data to the transport connection: An established connection
was aborted by the software in your host machine.
2017-01-10 11:18:31 One Connection raised an error
2017-01-10 11:18:35 New Connection 37 of 1000 to tomcat: [::1]:8009 ID: 504
[T-32]

Any help or pointers is appreciated!

Kind regards
LukeOn Saturday, January 7, 2017 at 5:11:28 PM UTC, Brad Wood wrote:

That message comes from Lucee’s service thread that runs all the time
looking for requests that have exceeded the time limit and tries to kill
them. If you see a lot of those, it means Lucee is trying to kill a lot of
long running requests, but those messages don’t really tell you anything
other than the fact that Lucee has tried to kill something. Grab
FusionReactor, if you don’t already have a license, and configured it to
E-mail you when request times exceed a threshold. That will dump a ton of
into into your inbox including what the running requests are doing and how
long they’ve been there.

Thanks!

~Brad

On Friday, January 6, 2017 at 4:56:10 AM UTC-6, luke insley wrote:

Error from application.log:

“ERROR”,“Thread-29”,“01/06/2017”,“10:37:53”,“controler”,"was not able to
stop conroler thread running for
60029ms;java.lang.Throwable;java.lang.Throwable
at
java.net.DualStackPlainDatagramSocketImpl.socketReceiveOrPeekData(Native
Method)
at
java.net.DualStackPlainDatagramSocketImpl.receive0(DualStackPlainDatagramSocketImpl.java:120)
at
java.net.AbstractPlainDatagramSocketImpl.receive(AbstractPlainDatagramSocketImpl.java:144)
at java.net.DatagramSocket.receive(DatagramSocket.java:812)
at lucee.runtime.net.ntp.NtpClient.getOffset(NtpClient.java:67)
at
lucee.runtime.config.ConfigImpl.reloadTimeServerOffset(ConfigImpl.java:462)
at lucee.runtime.engine.Controler.control(Controler.java:291)
at lucee.runtime.engine.Controler.control(Controler.java:214)
at lucee.runtime.engine.Controler.access$000(Controler.java:59)
at lucee.runtime.engine.Controler$ControlerThread.run(Controler.java:110)

Pretty sure this is resolved now.
The following worked for us, your environment may be different:

Edit server.xml in \lucee\tomcat\conf\server.xml
Change the connector line to include following:

Add these to boncode.settings:
65536
0

I’ve set the max allowable packet size, you may get away with smaller.
debug (2) logs now look like this:
2017-01-11 00:02:41 New Connection 23 of 0 to tomcat: [::1]:8009 ID: 5058
[T-35]
2017-01-11 00:02:49 New Connection 24 of 0 to tomcat: [::1]:8009 ID: 5059
[T-44]
2017-01-11 00:03:03 New Connection 25 of 0 to tomcat: [::1]:8009 ID: 5060
[T-44]
2017-01-11 00:03:20 New Connection 26 of 0 to tomcat: [::1]:8009 ID: 5061
[T-20]
2017-01-11 00:03:49 New Connection 27 of 0 to tomcat: [::1]:8009 ID: 5062
[T-31]
2017-01-11 00:04:01 New Connection 28 of 0 to tomcat: [::1]:8009 ID: 5063
[T-44]
2017-01-11 00:04:04 New Connection 29 of 0 to tomcat: [::1]:8009 ID: 5064
[T-44]