[jira] [Commented] (AMQ-5338) Run into Memory Leak problem after upgrade from 5.5.1 to 5.10

["Daniel Sabag (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14732292#comment-14732292 ] 

Daniel Sabag commented on AMQ-5338:
-----------------------------------

Hi there,

We also use AMQ 5.10 and we are monitoring our process using JMX. we also experience such OOM and the MAT reports about the same results: 

Problem Suspect 1

One instance of "com.sun.jmx.mbeanserver.Repository" loaded by "<system class loader>" occupies 1,050,891,224 (33.43%) bytes. The instance is referenced by org.apache.activemq.broker.TransportConnection$2 @ 0x7bb1427b8 Async Exception Handler , loaded by "java.net.URLClassLoader @ 0x7000430b8". The memory is accumulated in one instance of "java.util.HashMap$Node[]" loaded by "<system class loader>".



Problem Suspect 2

756,250 instances of "javax.management.ObjectName", loaded by "<system class loader>" occupy 1,365,859,400 (43.45%) bytes. 

Keywords
javax.management.ObjectName


here is our process command line :

/usr/local/panorama/java/bin/java -Xms512m -Xmx3072m -XX:+HeapDumpOnOutOfMemoryError  -Djava.util.logging.config.file=logging.properties -Djava.security.auth.login.config=/usr/local/panorama/activemq/conf/login.config -Djava.rmi.server.hostname=10.x.x.22 -Dcom.sun.management.jmxremote.port=11099 -Dcom.sun.management.jmxremote.password.file=/usr/local/panorama/etc/jmx/activemq_jmx.pass -Dcom.sun.management.jmxremote.access.file=/usr/local/panorama/etc/jmx/activemq_jmx.access -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote -Djava.awt.headless=true -Djava.io.tmpdir=/usr/local/panorama/activemq/tmp -Dactivemq.classpath=/usr/local/panorama/activemq/conf; -Dactivemq.home=/usr/local/panorama/activemq -Dactivemq.base=/usr/local/panorama/activemq -Dactivemq.conf=/usr/local/panorama/activemq/conf -Dactivemq.data=/usr/local/panorama/activemq/data -jar /usr/local/panorama/activemq/bin/activemq.jar start 


we do not specify GC algo, so i guess its the default for :

java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode) 



> Run into Memory Leak problem after upgrade from 5.5.1 to 5.10
> -------------------------------------------------------------
>
>                 Key: AMQ-5338
>                 URL: https://issues.apache.org/jira/browse/AMQ-5338
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.9.0, 5.10.0
>         Environment: Windows 2012 R2,  JDK 1.7.40, CPU I5, Memory 8G
>            Reporter: Edwin Wang
>
> Our production environment has used ActiveMQ 5.5.1 for a long time and it works well. Recently we decided to verify ActiveMQ 5.10 for prepared for upgrade. However, after we upgrade the test environment to 5.10, the MQ is easy ran into out of memory every 7-10 days. 
> In order to compare the two, I use the same environment and same configuration for both 5.5.1 and 5.10.0. Finally, 5.10.0 ran into out of memory while 5.5.1 works well.
> It looks like a bug for 5.10.
> Below is the main part of the configration
> <destinationPolicy>
>             <policyMap>
>               <policyEntries>
>                 <policyEntry topic=">" advisoryForConsumed="false" advisoryForDelivery="false" gcInactiveDestinations="true" inactiveTimoutBeforeGC="600000" producerFlowControl="true" memoryLimit="3mb">
>                   <pendingSubscriberPolicy>
>                     <vmCursor />
>                   </pendingSubscriberPolicy>
>                 </policyEntry>
>                 <policyEntry queue=">" advisoryForConsumed="false" advisoryForDelivery="false" gcInactiveDestinations="true" inactiveTimoutBeforeGC="600000" producerFlowControl="true" memoryLimit="3mb">
>                 </policyEntry>
>               </policyEntries>
>             </policyMap>
>         </destinationPolicy>
> <managementContext>
>             <managementContext createConnector="true"/>
>         </managementContext>
> <plugins>
> 				<simpleAuthenticationPlugin>
> 					<users>
> 						<authenticationUser username="msgmanager" password="Br0c@d3s0ft" groups="admins"/>
> 					</users>
> 				</simpleAuthenticationPlugin>
> 			  <authorizationPlugin>
> 				<map>
> 				  <authorizationMap>
> 					<authorizationEntries>
> 					  <authorizationEntry queue=">" read="admins" write="admins" admin="admins" />
> 					  <authorizationEntry topic=">" read="admins" write="admins" admin="admins" />
> 					</authorizationEntries>
> 				  </authorizationMap>
> 				</map>
> 			  </authorizationPlugin>
> 	    </plugins>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)