Catalina.out is growing and growing

I have shutdown loggin altogether but catalina.out doesn’t seem to care. It
keeps on growing and growing with the following message and I have no clue
where to look. Can someone point me in the right direction??

This is the only message in catalina.out that grows to several GB’s untill
the server grinds to a halt.

java.lang.StackTraceElement{java.net.SocketInputStream.socketRead0(Native
Method)
,java.net.SocketInputStream.read(SocketInputStream.java:152)
,java.net.SocketInputStream.read(SocketInputStream.java:122)
,com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1782)
,com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:4881)
,com.microsoft.sqlserver.jdbc.TDSReader.nextPacket(IOBuffer.java:4791)
,com.microsoft.sqlserver.jdbc.TDSReader.ensurePayload(IOBuffer.java:4767)
,com.microsoft.sqlserver.jdbc.TDSReader.peekTokenType(IOBuffer.java:4961)
,com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:50)
,com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1510)
,com.microsoft.sqlserver.jdbc.SQLServerStatement.processResults(SQLServerStatement.java:1157)
,com.microsoft.sqlserver.jdbc.SQLServerStatement.processBatch(SQLServerStatement.java:1145)
,com.microsoft.sqlserver.jdbc.SQLServerStatement.processExecuteResults(SQLServerStatement.java:1137)
,com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.processResponse(SQLServerPreparedStatement.java:357)
,com.microsoft.sqlserver.jdbc.TDSCommand.close(IOBuffer.java:5781)
,com.microsoft.sqlserver.jdbc.SQLServerStatement.discardLastExecutionResults(SQLServerStatement.java:94)
,com.microsoft.sqlserver.jdbc.SQLServerStatement.closeInternal(SQLServerStatement.java:584)
,com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.closeInternal(SQLServerPreparedStatement.java:170)
,com.microsoft.sqlserver.jdbc.SQLServerStatement.close(SQLServerStatement.java:596)
,lucee.runtime.db.driver.StatementProxy.close(StatementProxy.java:189)
,lucee.commons.db.DBUtil.closeEL(DBUtil.java:88)
,lucee.runtime.type.QueryImpl.(QueryImpl.java:282)
,lucee.runtime.type.QueryImpl.(QueryImpl.java:204)
,lucee.runtime.type.scope.storage.db.Ansi92.clean(Ansi92.java:186)
,lucee.runtime.type.scope.storage.clean.DatasourceStorageScopeCleaner.clean(DatasourceStorageScopeCleaner.java:72)
,lucee.runtime.type.scope.storage.clean.DatasourceStorageScopeCleaner._clean(DatasourceStorageScopeCleaner.java:56)
,lucee.runtime.type.scope.storage.clean.StorageScopeCleanerSupport.clean(StorageScopeCleanerSupport.java:59)
,lucee.runtime.type.scope.storage.StorageScopeEngine.clean(StorageScopeEngine.java:44)
,lucee.runtime.type.scope.ScopeContext.clearUnused(ScopeContext.java:727)
,lucee.runtime.engine.Controler.control(Controler.java:263)
,lucee.runtime.engine.Controler.control(Controler.java:214)
,lucee.runtime.engine.Controler.access$000(Controler.java:59)
,lucee.runtime.engine.Controler$ControlerThread.run(Controler.java:110)
}

The catalina.out file does not rotate which is a little “feature” of Tomcat
I’ve run into before. Their response is basically, “Well, you shouldn’t be
logging so much stuff to it in the first place.” which is, at best…
unhelpful. There are some workarounds listed here:
https://wiki.apache.org/tomcat/FAQ/Logging#Q10

To your actual question though, that stack trace doesn’t appear to be an
exception-- just a stack. Are you sure there’s no other lines in there
that indicate when or where this text is getting output? If I was to
guess, I’d say you have long-running requests which are hitting your Lucee
timeout, and you’re using Java 8 which can cause a boat load of logging
when Lucee tries to start killing the threads by first using a method that
only works on Java 7. See if there are any references to “thread death” in
there.

Also, a very very important piece of info: What version of Lucee are you
running?

Thanks!

~BradOn Thursday, June 30, 2016 at 2:12:46 AM UTC-5, Tjarko Rikkerink wrote:

I have shutdown loggin altogether but catalina.out doesn’t seem to care.
It keeps on growing and growing with the following message and I have no
clue where to look. Can someone point me in the right direction??

This is the only message in catalina.out that grows to several GB’s untill
the server grinds to a halt.

java.lang.StackTraceElement{java.net.SocketInputStream.socketRead0(Native
Method)
,java.net.SocketInputStream.read(SocketInputStream.java:152)
,java.net.SocketInputStream.read(SocketInputStream.java:122)
,com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1782)
,com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:4881)
,com.microsoft.sqlserver.jdbc.TDSReader.nextPacket(IOBuffer.java:4791)
,com.microsoft.sqlserver.jdbc.TDSReader.ensurePayload(IOBuffer.java:4767)
,com.microsoft.sqlserver.jdbc.TDSReader.peekTokenType(IOBuffer.java:4961)
,com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:50)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1510)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.processResults(SQLServerStatement.java:1157)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.processBatch(SQLServerStatement.java:1145)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.processExecuteResults(SQLServerStatement.java:1137)

,com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.processResponse(SQLServerPreparedStatement.java:357)
,com.microsoft.sqlserver.jdbc.TDSCommand.close(IOBuffer.java:5781)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.discardLastExecutionResults(SQLServerStatement.java:94)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.closeInternal(SQLServerStatement.java:584)

,com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.closeInternal(SQLServerPreparedStatement.java:170)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.close(SQLServerStatement.java:596)
,lucee.runtime.db.driver.StatementProxy.close(StatementProxy.java:189)
,lucee.commons.db.DBUtil.closeEL(DBUtil.java:88)
,lucee.runtime.type.QueryImpl.(QueryImpl.java:282)
,lucee.runtime.type.QueryImpl.(QueryImpl.java:204)
,lucee.runtime.type.scope.storage.db.Ansi92.clean(Ansi92.java:186)

,lucee.runtime.type.scope.storage.clean.DatasourceStorageScopeCleaner.clean(DatasourceStorageScopeCleaner.java:72)

,lucee.runtime.type.scope.storage.clean.DatasourceStorageScopeCleaner._clean(DatasourceStorageScopeCleaner.java:56)

,lucee.runtime.type.scope.storage.clean.StorageScopeCleanerSupport.clean(StorageScopeCleanerSupport.java:59)

,lucee.runtime.type.scope.storage.StorageScopeEngine.clean(StorageScopeEngine.java:44)
,lucee.runtime.type.scope.ScopeContext.clearUnused(ScopeContext.java:727)
,lucee.runtime.engine.Controler.control(Controler.java:263)
,lucee.runtime.engine.Controler.control(Controler.java:214)
,lucee.runtime.engine.Controler.access$000(Controler.java:59)
,lucee.runtime.engine.Controler$ControlerThread.run(Controler.java:110)
}

Implementing log rotation with Log4j and Lucee is really easy:

https://kb.viviotech.net/knowledge-base/hosting/lucee/implementing-log-rotation-with-log4j/--
Kind regards,
Jordan Michaels
Vivio Technologies

----- Original Message -----
From: “Brad Wood” <@Brad_Wood>
To: “Lucee” lucee@googlegroups.com
Sent: Thursday, June 30, 2016 7:37:31 AM
Subject: [Lucee] Re: Catalina.out is growing and growing

The catalina.out file does not rotate which is a little “feature” of Tomcat
I’ve run into before. Their response is basically, “Well, you shouldn’t be
logging so much stuff to it in the first place.” which is, at best…
unhelpful. There are some workarounds listed here:
https://wiki.apache.org/tomcat/FAQ/Logging#Q10

To your actual question though, that stack trace doesn’t appear to be an
exception-- just a stack. Are you sure there’s no other lines in there
that indicate when or where this text is getting output? If I was to
guess, I’d say you have long-running requests which are hitting your Lucee
timeout, and you’re using Java 8 which can cause a boat load of logging
when Lucee tries to start killing the threads by first using a method that
only works on Java 7. See if there are any references to “thread death” in
there.

Also, a very very important piece of info: What version of Lucee are you
running?

Thanks!

~Brad

On Thursday, June 30, 2016 at 2:12:46 AM UTC-5, Tjarko Rikkerink wrote:

I have shutdown loggin altogether but catalina.out doesn’t seem to care.
It keeps on growing and growing with the following message and I have no
clue where to look. Can someone point me in the right direction??

This is the only message in catalina.out that grows to several GB’s untill
the server grinds to a halt.

java.lang.StackTraceElement{java.net.SocketInputStream.socketRead0(Native
Method)
,java.net.SocketInputStream.read(SocketInputStream.java:152)
,java.net.SocketInputStream.read(SocketInputStream.java:122)
,com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1782)
,com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:4881)
,com.microsoft.sqlserver.jdbc.TDSReader.nextPacket(IOBuffer.java:4791)
,com.microsoft.sqlserver.jdbc.TDSReader.ensurePayload(IOBuffer.java:4767)
,com.microsoft.sqlserver.jdbc.TDSReader.peekTokenType(IOBuffer.java:4961)
,com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:50)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1510)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.processResults(SQLServerStatement.java:1157)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.processBatch(SQLServerStatement.java:1145)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.processExecuteResults(SQLServerStatement.java:1137)

,com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.processResponse(SQLServerPreparedStatement.java:357)
,com.microsoft.sqlserver.jdbc.TDSCommand.close(IOBuffer.java:5781)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.discardLastExecutionResults(SQLServerStatement.java:94)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.closeInternal(SQLServerStatement.java:584)

,com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.closeInternal(SQLServerPreparedStatement.java:170)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.close(SQLServerStatement.java:596)
,lucee.runtime.db.driver.StatementProxy.close(StatementProxy.java:189)
,lucee.commons.db.DBUtil.closeEL(DBUtil.java:88)
,lucee.runtime.type.QueryImpl.(QueryImpl.java:282)
,lucee.runtime.type.QueryImpl.(QueryImpl.java:204)
,lucee.runtime.type.scope.storage.db.Ansi92.clean(Ansi92.java:186)

,lucee.runtime.type.scope.storage.clean.DatasourceStorageScopeCleaner.clean(DatasourceStorageScopeCleaner.java:72)

,lucee.runtime.type.scope.storage.clean.DatasourceStorageScopeCleaner._clean(DatasourceStorageScopeCleaner.java:56)

,lucee.runtime.type.scope.storage.clean.StorageScopeCleanerSupport.clean(StorageScopeCleanerSupport.java:59)

,lucee.runtime.type.scope.storage.StorageScopeEngine.clean(StorageScopeEngine.java:44)
,lucee.runtime.type.scope.ScopeContext.clearUnused(ScopeContext.java:727)
,lucee.runtime.engine.Controler.control(Controler.java:263)
,lucee.runtime.engine.Controler.control(Controler.java:214)
,lucee.runtime.engine.Controler.access$000(Controler.java:59)
,lucee.runtime.engine.Controler$ControlerThread.run(Controler.java:110)
}


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/01181324-df79-4da9-b282-0f7b6017366b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

The logging properties only apply to logging that uses Lucee’s logging
facilities. Any Java or CF code that writes straight to the system out
(console) will still be written to the catalina.out file. For instance,
e.printStackTrace() would write there as it bypasses any Lucee loggers.

Thanks!

~Brad

Developer Advocate
*Ortus Solutions, Corp *

E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.comOn Fri, Jul 1, 2016 at 1:53 AM, Tjarko Rikkerink < @Tjarko_Rikkerink> wrote:

Thanks! I Already have logrotate running but the thing is that I have set
my logging to OFF but the catalina.out file is still written… how can
that be when I have set the loggin handler to OFF :slight_smile:

Op vrijdag 1 juli 2016 04:27:29 UTC+2 schreef Jordan Michaels:

Implementing log rotation with Log4j and Lucee is really easy:

https://kb.viviotech.net/knowledge-base/hosting/lucee/implementing-log-rotation-with-log4j/


Kind regards,
Jordan Michaels
Vivio Technologies

----- Original Message -----
From: “Brad Wood” bdw...@gmail.com
To: “Lucee” lu...@googlegroups.com
Sent: Thursday, June 30, 2016 7:37:31 AM
Subject: [Lucee] Re: Catalina.out is growing and growing

The catalina.out file does not rotate which is a little “feature” of
Tomcat
I’ve run into before. Their response is basically, “Well, you shouldn’t
be
logging so much stuff to it in the first place.” which is, at best…
unhelpful. There are some workarounds listed here:
https://wiki.apache.org/tomcat/FAQ/Logging#Q10

To your actual question though, that stack trace doesn’t appear to be an
exception-- just a stack. Are you sure there’s no other lines in there
that indicate when or where this text is getting output? If I was to
guess, I’d say you have long-running requests which are hitting your
Lucee
timeout, and you’re using Java 8 which can cause a boat load of logging
when Lucee tries to start killing the threads by first using a method
that
only works on Java 7. See if there are any references to “thread death”
in
there.

Also, a very very important piece of info: What version of Lucee are you
running?

Thanks!

~Brad

On Thursday, June 30, 2016 at 2:12:46 AM UTC-5, Tjarko Rikkerink wrote:

I have shutdown loggin altogether but catalina.out doesn’t seem to
care.
It keeps on growing and growing with the following message and I have
no
clue where to look. Can someone point me in the right direction??

This is the only message in catalina.out that grows to several GB’s
untill
the server grinds to a halt.

java.lang.StackTraceElement{java.net.SocketInputStream.socketRead0(Native

Method)
,java.net.SocketInputStream.read(SocketInputStream.java:152)
,java.net.SocketInputStream.read(SocketInputStream.java:122)
,com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1782)
,com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:4881)
,com.microsoft.sqlserver.jdbc.TDSReader.nextPacket(IOBuffer.java:4791)

,com.microsoft.sqlserver.jdbc.TDSReader.ensurePayload(IOBuffer.java:4767)

,com.microsoft.sqlserver.jdbc.TDSReader.peekTokenType(IOBuffer.java:4961)

,com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:50)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1510)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.processResults(SQLServerStatement.java:1157)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.processBatch(SQLServerStatement.java:1145)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.processExecuteResults(SQLServerStatement.java:1137)

,com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.processResponse(SQLServerPreparedStatement.java:357)

,com.microsoft.sqlserver.jdbc.TDSCommand.close(IOBuffer.java:5781)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.discardLastExecutionResults(SQLServerStatement.java:94)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.closeInternal(SQLServerStatement.java:584)

,com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.closeInternal(SQLServerPreparedStatement.java:170)

,com.microsoft.sqlserver.jdbc.SQLServerStatement.close(SQLServerStatement.java:596)

,lucee.runtime.db.driver.StatementProxy.close(StatementProxy.java:189)
,lucee.commons.db.DBUtil.closeEL(DBUtil.java:88)
,lucee.runtime.type.QueryImpl.(QueryImpl.java:282)
,lucee.runtime.type.QueryImpl.(QueryImpl.java:204)
,lucee.runtime.type.scope.storage.db.Ansi92.clean(Ansi92.java:186)

,lucee.runtime.type.scope.storage.clean.DatasourceStorageScopeCleaner.clean(DatasourceStorageScopeCleaner.java:72)

,lucee.runtime.type.scope.storage.clean.DatasourceStorageScopeCleaner._clean(DatasourceStorageScopeCleaner.java:56)

,lucee.runtime.type.scope.storage.clean.StorageScopeCleanerSupport.clean(StorageScopeCleanerSupport.java:59)

,lucee.runtime.type.scope.storage.StorageScopeEngine.clean(StorageScopeEngine.java:44)

,lucee.runtime.type.scope.ScopeContext.clearUnused(ScopeContext.java:727)

,lucee.runtime.engine.Controler.control(Controler.java:263)
,lucee.runtime.engine.Controler.control(Controler.java:214)
,lucee.runtime.engine.Controler.access$000(Controler.java:59)
,lucee.runtime.engine.Controler$ControlerThread.run(Controler.java:110)
}


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+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/01181324-df79-4da9-b282-0f7b6017366b%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


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 a topic in the
Google Groups “Lucee” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/lucee/v33DTB9SY5A/unsubscribe.
To unsubscribe from this group and all its topics, 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/c21fae7e-ab65-4037-9ab5-82802091607b%40googlegroups.com
https://groups.google.com/d/msgid/lucee/c21fae7e-ab65-4037-9ab5-82802091607b%40googlegroups.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.