Hi Norman, In our application, there are four interfaces (3 ServerBootstrap and 1 BootStrap) within the same JVM. Total 8 instances of HashedWheelTimer (4 + 2 + 1 + 1) gets created during the application start up. However, when running the application with smaller heap, I see the following error message:
LEAK: You are creating too many HashedWheelTimer instances. HashedWheelTimer is a shared resource that must be reused across the JVM,so that only a few instances are created As per the Netty documentation, I should have a single instance of HashedWheelTimer. *Is it single instance per JVM or Single instance per ServerBootStrap/BootStrap?* *Is it OK if we continue with the current implementation (8 instances of HashedWheelTimer) or is it a MUST to reduce it 1* (per JVM or per ServerBootStrap/BootStrap?) *for performance benefit?* Please let me know. Thanks, Arnab -- You received this message because you are subscribed to the Google Groups "Netty discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/netty/CAOG5%2B9n9gJz271s%2B1_90%3D8UjJQVZoJP73DqTWvZQtcBRd4ipDw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
