I am tracing a client/server app in OptimizeIt and noticed that a bunch of allocations to org.apache.log4j.Logger and org.apache.log4j.CategoryKey are not getting collected.
I am using org.jboss.logging.Logger in beans themselves - these allocations seem to be getting cleaned up ok when the server goes from high load to lower load.
But the org.apache.log4J.Loggers are just sticking around - their allocations just continue to go up as the app runs, which I believe will eventually cause an out of memory condition eventually?
I suspect I have done something wrong in the way I am using the logger?
private static final Logger log = Logger.getLogger("class.ext")
The trace of the loggers says they are hanging on to string references from the JbossMQ. Most of the Loggers left around have string references to message queue Client ID's ???