Ok, In case the problem is direct memory Do you think disable netty direct memory would have a serious impact on performance? E.g. -Dio.netty.noPreferDirect=true -Dio.netty.maxDirectMemory=0 -Dio.netty.allocator.type=unpooled
On Thu, Feb 20, 2025 at 10:47 AM Anton Roskvist <ant...@apache.org> wrote: > Hi, > > I think the point would be that if possible, the idea would be to try the > same conditions against a more recent version of the broker. All else being > equal, this would rule out any and all issues that might already have been > addressed in the roughly 3000 commits since 2.14.0. Same could apply to > your JVM. > > If it's still an issue, then at least the scope has been narrowed. > > As an alternative if you are unable to upgrade, "Native memory tracking" > or "Flight recording" can be helpful in tracking these types of issues > down. Refer to the documentation of your JDK on how to enable these (though > be aware that they incur some overhead while running). > > Switching to NIO is possible but it could very well affect your > performance in a negative way... though depending on your options it could > serve as yet another way of narrowing the scope of this issue. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org > For additional commands, e-mail: users-h...@activemq.apache.org > For further information, visit: https://activemq.apache.org/contact > > >
