You want help debugging a memory leak in a version that was released 6 years ago (today, coincidentally)? Maybe someone will take pity on you and help you out, but I'd be surprised. Upgrade to a modern version if you want the best chance of getting someone to help you. On Oct 13, 2015 8:39 AM, "chinsong2" <[email protected]> wrote:
> Hi, > > I am struggling with memory leak. > > Target WAS is IBM Websphere base 7.0.0.27, have deployed EAR that use > Active > MQ 5.3.0. > > I found, when i send message by ActiveMQ, It create 'Logger', Jdk14Logger. > > IBM 'WsLogManager' create it, but it's not garbaged. Let's see stack log. > > My Question is .. > - It is IBM WAS Problem or ActiveMQ 5.3.0? > - What can i do with that problem. > - Why ActiveMQ 5.3.0 have not org.apache.commons.logging.impl.Log4JLogger > > Please, help. > > > ---------------------------------------------------------------------------------------------------------------------- > Element Type : java.lang.ref.WeakReference > at java.util.ArrayList.add(ArrayList.java:163) > at java.util.logging.Logger.addChild(Logger.java:663) > at java.util.logging.Logger.internalSetParent(Logger.java:638) > at java.util.logging.LogManager.addToFamilyTree(LogManager.java:352) > at java.util.logging.LogManager.addLogger(LogManager.java:324) > at com.ibm.ws.bootstrap.WsLogManager.getLogger(WsLogManager.java:220) > at java.util.logging.Logger.getLoggerWithRes(Logger.java:350) > at java.util.logging.Logger.getLogger(Logger.java:376) > at > org.apache.commons.logging.impl.Jdk14Logger.getLogger(Jdk14Logger.java:180) > at org.apache.commons.logging.impl.Jdk14Logger. < init > > (Jdk14Logger.java:60) > at sun.reflect.GeneratedConstructorAccessor10.newInstance(Unknown Source) > at > > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39) > at java.lang.reflect.Constructor.newInstance(Constructor.java:527) > at > > org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:605) > at > > org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:333) > at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:664) > at > > org.apache.activemq.transport.TransportLoggerFactory.createLog(TransportLoggerFactory.java:184) > at > > org.apache.activemq.transport.TransportLoggerFactory.createTransportLogger(TransportLoggerFactory.java:139) > at > > org.apache.activemq.transport.tcp.TcpTransportFactory.compositeConfigure(TcpTransportFactory.java:92) > at > > org.apache.activemq.transport.TransportFactory.configure(TransportFactory.java:246) > at > > org.apache.activemq.transport.TransportFactory.doConnect(TransportFactory.java:142) > at > > org.apache.activemq.transport.TransportFactory.doConnect(TransportFactory.java:51) > at > > org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:80) > at > > org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:240) > at > > org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:255) > at > > org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:227) > at > > org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:175) > > > --------------------------------------------------------------------------------------------------------------------- > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-5-3-0-memory-leak-with-IBM-Websphere-7-0-tp4702887.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
