On Wed, Jul 11, 2018 at 10:41 AM Giacomo Arru - BETA Technologies
wrote:
> I tried to enable debug logging for org.apache.tomcat.websocket but
> without success
>
> here is my logging.properties
>
>
>
> handlers = java.util.logging.ConsoleHandler
>
> .handlers =
Hi,
while analyzing some heap dump for other reasons, I found that our
application is apparently aggregating a considerable amount of memory in
"org.apache.tomcat.jdbc.pool.TrapException", which is never cleaned by GC.
Digging deeper, it seems that the entries of the "statements" linked list
in
Hi,
Thanks for your reply.
The only change that I've made - I've added *address="0.0.0.0"* to all of
my Tomcat Connectors and seems that it solves the issue. At least I can not
reproduce it any more.
Java runs with *-Djava.net.preferIPv4Stack=true*
Here what ifconfig shows inside the container
I tried to enable debug logging for org.apache.tomcat.websocket but without
success
here is my logging.properties
handlers = java.util.logging.ConsoleHandler
.handlers = 1catalina.org.apache.juli.AsyncFileHandler,
java.util.logging.ConsoleHandler
java.util.logging.ConsoleHandler.level
Dear Will,
I agree to Your approach. Said that, I also don't have any experience with the
concrete question, but from my Tomcat and Java experience, I would say that --
from a quick look -- the docs
