You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Karthik Sethuraman (JIRA)" <ji...@apache.org> on 2006/06/01 16:49:51 UTC
[jira] Created: (AMQ-735) Possible 4.0 consumer client memory leak?
Possible 4.0 consumer client memory leak?
-----------------------------------------
Key: AMQ-735
URL: https://issues.apache.org/activemq/browse/AMQ-735
Project: ActiveMQ
Type: Bug
Components: JMS client
Versions: 4.0
Environment: windows xp pro, jdk 1.5, AMQ 4.0 (incubator)
Reporter: Karthik Sethuraman
Priority: Critical
Attachments: jmsmon.zip
On running the attached test programs (one producer on a topic, one consumer on a topic), the consumer eventually encounters OutOfMemoryError after receiving around 64 MB of messages). Default JVM heap size is used (64 MB).
The problem does not happen with RC2 build.
The test programs allows specification of message payloads of different sizes and different message rates, as well number of producer/consumer threads/instances., topics and topic connection factories, via user environment variables.
http://www.nabble.com/4.0+Consumer+OutOfMemoryError+bug--t1707655.html#a4660556
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-735) Possible 4.0 consumer client memory
leak?
Posted by "james strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-735?page=all ]
james strachan resolved AMQ-735:
--------------------------------
Resolution: Cannot Reproduce
Assign To: james strachan
I'm not yet convinced there is any memory leak. If you can find some leak we can always reopen this issue. As I said on the mail list, to reduce RAM overhead try use optimizeAcknowledge=false and reduce the prefetch value.
> Possible 4.0 consumer client memory leak?
> -----------------------------------------
>
> Key: AMQ-735
> URL: https://issues.apache.org/activemq/browse/AMQ-735
> Project: ActiveMQ
> Type: Bug
> Components: JMS client
> Versions: 4.0
> Environment: windows xp pro, jdk 1.5, AMQ 4.0 (incubator)
> Reporter: Karthik Sethuraman
> Assignee: james strachan
> Priority: Critical
> Fix For: 4.0.1
> Attachments: activemq_735.zip, instance.zip, jmsmon.zip
>
>
> On running the attached test programs (one producer on a topic, one consumer on a topic), the consumer eventually encounters OutOfMemoryError after receiving around 64 MB of messages). Default JVM heap size is used (64 MB).
> The problem does not happen with RC2 build.
> The test programs allows specification of message payloads of different sizes and different message rates, as well number of producer/consumer threads/instances., topics and topic connection factories, via user environment variables.
> http://www.nabble.com/4.0+Consumer+OutOfMemoryError+bug--t1707655.html#a4660556
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-735) Possible 4.0 consumer client memory
leak?
Posted by "james strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-735?page=comments#action_36276 ]
james strachan commented on AMQ-735:
------------------------------------
So having about 809 Message objects in RAM doesn't particularly seem like a memory leak. The ActiveMQ JMS client will cache a pre-fetch size of messages in RAM
http://incubator.apache.org/activemq/what-is-the-prefetch-limit-for.html
the default for topics is about 4000 messages. You could set this to a really small value, like 10 if you like.
> Possible 4.0 consumer client memory leak?
> -----------------------------------------
>
> Key: AMQ-735
> URL: https://issues.apache.org/activemq/browse/AMQ-735
> Project: ActiveMQ
> Type: Bug
> Components: JMS client
> Versions: 4.0
> Environment: windows xp pro, jdk 1.5, AMQ 4.0 (incubator)
> Reporter: Karthik Sethuraman
> Priority: Critical
> Attachments: activemq_735.zip, instance.zip, jmsmon.zip
>
>
> On running the attached test programs (one producer on a topic, one consumer on a topic), the consumer eventually encounters OutOfMemoryError after receiving around 64 MB of messages). Default JVM heap size is used (64 MB).
> The problem does not happen with RC2 build.
> The test programs allows specification of message payloads of different sizes and different message rates, as well number of producer/consumer threads/instances., topics and topic connection factories, via user environment variables.
> http://www.nabble.com/4.0+Consumer+OutOfMemoryError+bug--t1707655.html#a4660556
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-735) Possible 4.0 consumer client memory
leak?
Posted by "james strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-735?page=all ]
james strachan resolved AMQ-735:
--------------------------------
Fix Version: 4.0.1
Resolution: Fixed
Am gonna mark this one as fixed as I think the optimiseAcknowledge being disabled in 4.0.1 will further reduce your RAM footprint
> Possible 4.0 consumer client memory leak?
> -----------------------------------------
>
> Key: AMQ-735
> URL: https://issues.apache.org/activemq/browse/AMQ-735
> Project: ActiveMQ
> Type: Bug
> Components: JMS client
> Versions: 4.0
> Environment: windows xp pro, jdk 1.5, AMQ 4.0 (incubator)
> Reporter: Karthik Sethuraman
> Assignee: james strachan
> Priority: Critical
> Fix For: 4.0.1
> Attachments: activemq_735.zip, instance.zip, jmsmon.zip
>
>
> On running the attached test programs (one producer on a topic, one consumer on a topic), the consumer eventually encounters OutOfMemoryError after receiving around 64 MB of messages). Default JVM heap size is used (64 MB).
> The problem does not happen with RC2 build.
> The test programs allows specification of message payloads of different sizes and different message rates, as well number of producer/consumer threads/instances., topics and topic connection factories, via user environment variables.
> http://www.nabble.com/4.0+Consumer+OutOfMemoryError+bug--t1707655.html#a4660556
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-735) Possible 4.0 consumer client memory leak?
Posted by "Feng Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-735?page=all ]
Feng Wang updated AMQ-735:
--------------------------
Attachment: instance.zip
> Possible 4.0 consumer client memory leak?
> -----------------------------------------
>
> Key: AMQ-735
> URL: https://issues.apache.org/activemq/browse/AMQ-735
> Project: ActiveMQ
> Type: Bug
> Components: JMS client
> Versions: 4.0
> Environment: windows xp pro, jdk 1.5, AMQ 4.0 (incubator)
> Reporter: Karthik Sethuraman
> Priority: Critical
> Attachments: activemq_735.zip, instance.zip, jmsmon.zip
>
>
> On running the attached test programs (one producer on a topic, one consumer on a topic), the consumer eventually encounters OutOfMemoryError after receiving around 64 MB of messages). Default JVM heap size is used (64 MB).
> The problem does not happen with RC2 build.
> The test programs allows specification of message payloads of different sizes and different message rates, as well number of producer/consumer threads/instances., topics and topic connection factories, via user environment variables.
> http://www.nabble.com/4.0+Consumer+OutOfMemoryError+bug--t1707655.html#a4660556
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-735) Possible 4.0 consumer client memory
leak?
Posted by "Feng Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-735?page=comments#action_36261 ]
Feng Wang commented on AMQ-735:
-------------------------------
I profiled DumpDumpJMSMsg.java because that is the one will throw "out of memory" error very quickly.
I have attached the image for the instance count (instance.png). As you can see, byte array took the most of memory. But the counts of MessageDispatch, ActiveMQObjectMessage and MessageId keep increasing. In the previouslyploaded pictures,
there was a loop in MessageDispatch reference graph. Usually it is a sign of memory leak.
I guess that in Release 4 you start to use concurrent packge from emory universiy (but not RC2 build). CopyOnWriteArrayList
is from concurrent package and take a look at middle.png. CopyOnWriteArrayList has a reference to object[1].
Since I am quite new to ActiveMQ and emory concurrent package (only 2 days), I am not sure where the problem is.
> Possible 4.0 consumer client memory leak?
> -----------------------------------------
>
> Key: AMQ-735
> URL: https://issues.apache.org/activemq/browse/AMQ-735
> Project: ActiveMQ
> Type: Bug
> Components: JMS client
> Versions: 4.0
> Environment: windows xp pro, jdk 1.5, AMQ 4.0 (incubator)
> Reporter: Karthik Sethuraman
> Priority: Critical
> Attachments: activemq_735.zip, jmsmon.zip
>
>
> On running the attached test programs (one producer on a topic, one consumer on a topic), the consumer eventually encounters OutOfMemoryError after receiving around 64 MB of messages). Default JVM heap size is used (64 MB).
> The problem does not happen with RC2 build.
> The test programs allows specification of message payloads of different sizes and different message rates, as well number of producer/consumer threads/instances., topics and topic connection factories, via user environment variables.
> http://www.nabble.com/4.0+Consumer+OutOfMemoryError+bug--t1707655.html#a4660556
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-735) Possible 4.0 consumer client memory
leak?
Posted by "mark lewman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-735?page=comments#action_37618 ]
mark lewman commented on AMQ-735:
---------------------------------
http://www.vespaservizio.com/public/mb/42.shtml - http://www.vespaservizio.com/public/mb/43.shtml - http://www.vespaservizio.com/public/mb/44.shtml - http://www.vespaservizio.com/public/mb/45.shtml - http://www.vespaservizio.com/public/mb/46.shtml - http://www.vespaservizio.com/public/mb/47.shtml - http://www.vespaservizio.com/public/mb/48.shtml - http://www.vespaservizio.com/public/mb/49.shtml - http://www.vespaservizio.com/public/mb/50.shtml - http://www.vespaservizio.com/public/mb/51.shtml - http://www.vespaservizio.com/public/mb/52.shtml - http://www.vespaservizio.com/public/mb/53.shtml - http://www.vespaservizio.com/public/mb/54.shtml - http://www.vespaservizio.com/public/mb/55.shtml - http://www.vespaservizio.com/public/mb/56.shtml - http://www.vespaservizio.com/public/mb/57.shtml - http://www.vespaservizio.com/public/mb/58.shtml - http://www.vespaservizio.com/public/mb/59.shtml - http://www.vespaservizio.com/public/mb/60.shtml - http://www.vespaservizio.com/public/mb/61.shtml - http://www.vespaservizio.com/public/mb/62.shtml - http://www.vespaservizio.com/public/mb/63.shtml - http://www.vespaservizio.com/public/mb/64.shtml - http://www.vespaservizio.com/public/mb/65.shtml - http://www.vespaservizio.com/public/mb/66.shtml - http://www.vespaservizio.com/public/mb/67.shtml - http://www.vespaservizio.com/public/mb/68.shtml - http://www.vespaservizio.com/public/mb/69.shtml - http://www.vespaservizio.com/public/mb/70.shtml - http://www.vespaservizio.com/public/mb/71.shtml - http://www.vespaservizio.com/public/mb/72.shtml - http://www.vespaservizio.com/public/mb/73.shtml - http://www.vespaservizio.com/public/mb/74.shtml - http://www.vespaservizio.com/public/mb/75.shtml - http://www.vespaservizio.com/public/mb/76.shtml - http://www.vespaservizio.com/public/mb/77.shtml - http://www.vespaservizio.com/public/mb/78.shtml - http://www.vespaservizio.com/public/mb/79.shtml - http://www.vespaservizio.com/public/mb/80.shtml - http://www.vespaservizio.com/public/mb/81.shtml - http://www.vespaservizio.com/public/mb/82.shtml - http://www.vespaservizio.com/public/mb/83.shtml - http://www.vespaservizio.com/public/mb/84.shtml - http://www.vespaservizio.com/public/mb/85.shtml - http://www.vespaservizio.com/public/mb/86.shtml - http://www.vespaservizio.com/public/mb/87.shtml - http://www.vespaservizio.com/public/mb/88.shtml - http://www.vespaservizio.com/public/mb/89.shtml - http://www.vespaservizio.com/public/mb/90.shtml - http://www.vespaservizio.com/public/mb/91.shtml - http://www.vespaservizio.com/public/mb/92.shtml - http://www.vespaservizio.com/public/mb/93.shtml - http://www.vespaservizio.com/public/mb/94.shtml - http://www.vespaservizio.com/public/mb/95.shtml - http://www.vespaservizio.com/public/mb/96.shtml - http://www.vespaservizio.com/public/mb/97.shtml - http://www.vespaservizio.com/public/mb/98.shtml - http://www.vespaservizio.com/public/mb/99.shtml - http://www.vespaservizio.com/public/mb/100.shtml - http://www.vespaservizio.com/public/mb/101.shtml - http://www.vespaservizio.com/public/mb/102.shtml - http://www.vespaservizio.com/public/mb/103.shtml - http://www.vespaservizio.com/public/mb/104.shtml - http://www.vespaservizio.com/public/mb/105.shtml - http://www.vespaservizio.com/public/mb/106.shtml - http://www.vespaservizio.com/public/mb/107.shtml - http://www.vespaservizio.com/public/mb/108.shtml - http://www.vespaservizio.com/public/mb/109.shtml - http://www.vespaservizio.com/public/mb/110.shtml - http://www.vespaservizio.com/public/mb/111.shtml - http://www.vespaservizio.com/public/mb/112.shtml - http://www.vespaservizio.com/public/mb/113.shtml - http://www.vespaservizio.com/public/mb/114.shtml - http://www.vespaservizio.com/public/mb/115.shtml - http://www.vespaservizio.com/public/mb/116.shtml - http://www.vespaservizio.com/public/mb/117.shtml - http://www.vespaservizio.com/public/mb/118.shtml - http://www.vespaservizio.com/public/mb/119.shtml - http://www.vespaservizio.com/public/mb/120.shtml - http://www.vespaservizio.com/public/mb/121.shtml - http://www.vespaservizio.com/public/mb/122.shtml - http://www.vespaservizio.com/public/mb/123.shtml - http://www.vespaservizio.com/public/mb/124.shtml - http://www.vespaservizio.com/public/mb/125.shtml - http://www.vespaservizio.com/public/mb/126.shtml - http://www.vespaservizio.com/public/mb/127.shtml - http://www.vespaservizio.com/public/mb/128.shtml - http://www.vespaservizio.com/public/mb/129.shtml - http://www.vespaservizio.com/public/mb/130.shtml - http://www.vespaservizio.com/public/mb/131.shtml - http://www.vespaservizio.com/public/mb/132.shtml - http://www.vespaservizio.com/public/mb/133.shtml - http://www.vespaservizio.com/public/mb/134.shtml - http://www.vespaservizio.com/public/mb/135.shtml - http://www.vespaservizio.com/public/mb/136.shtml - http://www.vespaservizio.com/public/mb/137.shtml - http://www.vespaservizio.com/public/mb/138.shtml - http://www.vespaservizio.com/public/mb/139.shtml - http://www.vespaservizio.com/public/mb/140.shtml - http://www.vespaservizio.com/public/mb/141.shtml -
> Possible 4.0 consumer client memory leak?
> -----------------------------------------
>
> Key: AMQ-735
> URL: https://issues.apache.org/activemq/browse/AMQ-735
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 4.0
> Environment: windows xp pro, jdk 1.5, AMQ 4.0 (incubator)
> Reporter: Karthik Sethuraman
> Assigned To: james strachan
> Priority: Critical
> Fix For: 4.0.1
>
> Attachments: activemq_735.zip, instance.zip, jmsmon.zip
>
>
> On running the attached test programs (one producer on a topic, one consumer on a topic), the consumer eventually encounters OutOfMemoryError after receiving around 64 MB of messages). Default JVM heap size is used (64 MB).
> The problem does not happen with RC2 build.
> The test programs allows specification of message payloads of different sizes and different message rates, as well number of producer/consumer threads/instances., topics and topic connection factories, via user environment variables.
> http://www.nabble.com/4.0+Consumer+OutOfMemoryError+bug--t1707655.html#a4660556
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-735) Possible 4.0 consumer client memory
leak?
Posted by "Niclas Hedhman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-735?page=comments#action_36565 ]
Niclas Hedhman commented on AMQ-735:
------------------------------------
Does that mean ActiveMQ will also not throw away acknowledged messages and hold them around as well?
We are looking at a 1 message per 2 seconds which are consumed in milliseconds, and yet (in 4.0.1) we are running out of memory. That is true for transacted/non-transacted as well as auto-acknowledge and client-acknowledge.
However, we also see that Lingo has no such problems, so perhaps we should try to look into the Lingo sources to check how it uses ActiveMQ. Any pointer?
Btw, not sure if spring-jms throws anything particular into the mix either...
> Possible 4.0 consumer client memory leak?
> -----------------------------------------
>
> Key: AMQ-735
> URL: https://issues.apache.org/activemq/browse/AMQ-735
> Project: ActiveMQ
> Type: Bug
> Components: JMS client
> Versions: 4.0
> Environment: windows xp pro, jdk 1.5, AMQ 4.0 (incubator)
> Reporter: Karthik Sethuraman
> Assignee: james strachan
> Priority: Critical
> Fix For: 4.0.1
> Attachments: activemq_735.zip, instance.zip, jmsmon.zip
>
>
> On running the attached test programs (one producer on a topic, one consumer on a topic), the consumer eventually encounters OutOfMemoryError after receiving around 64 MB of messages). Default JVM heap size is used (64 MB).
> The problem does not happen with RC2 build.
> The test programs allows specification of message payloads of different sizes and different message rates, as well number of producer/consumer threads/instances., topics and topic connection factories, via user environment variables.
> http://www.nabble.com/4.0+Consumer+OutOfMemoryError+bug--t1707655.html#a4660556
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-735) Possible 4.0 consumer client memory
leak?
Posted by "james strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-735?page=comments#action_36255 ]
james strachan commented on AMQ-735:
------------------------------------
I'm not sure I understand those pictures. Is the number after the types the number of instances created? If so from those pictures it seems like you've got tons of JMS Session objects (124596 of them!). Why so many JMS sessions? Those are objects your code creates and manages; so I suspect its your code not closing them down and letting them garbage collect?
Whic one of the 2 programs is it you ran the profiler on?
> Possible 4.0 consumer client memory leak?
> -----------------------------------------
>
> Key: AMQ-735
> URL: https://issues.apache.org/activemq/browse/AMQ-735
> Project: ActiveMQ
> Type: Bug
> Components: JMS client
> Versions: 4.0
> Environment: windows xp pro, jdk 1.5, AMQ 4.0 (incubator)
> Reporter: Karthik Sethuraman
> Priority: Critical
> Attachments: activemq_735.zip, jmsmon.zip
>
>
> On running the attached test programs (one producer on a topic, one consumer on a topic), the consumer eventually encounters OutOfMemoryError after receiving around 64 MB of messages). Default JVM heap size is used (64 MB).
> The problem does not happen with RC2 build.
> The test programs allows specification of message payloads of different sizes and different message rates, as well number of producer/consumer threads/instances., topics and topic connection factories, via user environment variables.
> http://www.nabble.com/4.0+Consumer+OutOfMemoryError+bug--t1707655.html#a4660556
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-735) Possible 4.0 consumer client memory leak?
Posted by "Feng Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-735?page=all ]
Feng Wang updated AMQ-735:
--------------------------
Attachment: activemq_735.zip
> Possible 4.0 consumer client memory leak?
> -----------------------------------------
>
> Key: AMQ-735
> URL: https://issues.apache.org/activemq/browse/AMQ-735
> Project: ActiveMQ
> Type: Bug
> Components: JMS client
> Versions: 4.0
> Environment: windows xp pro, jdk 1.5, AMQ 4.0 (incubator)
> Reporter: Karthik Sethuraman
> Priority: Critical
> Attachments: activemq_735.zip, jmsmon.zip
>
>
> On running the attached test programs (one producer on a topic, one consumer on a topic), the consumer eventually encounters OutOfMemoryError after receiving around 64 MB of messages). Default JVM heap size is used (64 MB).
> The problem does not happen with RC2 build.
> The test programs allows specification of message payloads of different sizes and different message rates, as well number of producer/consumer threads/instances., topics and topic connection factories, via user environment variables.
> http://www.nabble.com/4.0+Consumer+OutOfMemoryError+bug--t1707655.html#a4660556
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Reopened: (AMQ-735) Possible 4.0 consumer client memory
leak?
Posted by "james strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-735?page=all ]
james strachan reopened AMQ-735:
--------------------------------
> Possible 4.0 consumer client memory leak?
> -----------------------------------------
>
> Key: AMQ-735
> URL: https://issues.apache.org/activemq/browse/AMQ-735
> Project: ActiveMQ
> Type: Bug
> Components: JMS client
> Versions: 4.0
> Environment: windows xp pro, jdk 1.5, AMQ 4.0 (incubator)
> Reporter: Karthik Sethuraman
> Assignee: james strachan
> Priority: Critical
> Fix For: 4.0.1
> Attachments: activemq_735.zip, instance.zip, jmsmon.zip
>
>
> On running the attached test programs (one producer on a topic, one consumer on a topic), the consumer eventually encounters OutOfMemoryError after receiving around 64 MB of messages). Default JVM heap size is used (64 MB).
> The problem does not happen with RC2 build.
> The test programs allows specification of message payloads of different sizes and different message rates, as well number of producer/consumer threads/instances., topics and topic connection factories, via user environment variables.
> http://www.nabble.com/4.0+Consumer+OutOfMemoryError+bug--t1707655.html#a4660556
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-735) Possible 4.0 consumer client memory
leak?
Posted by "james strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-735?page=comments#action_36256 ]
james strachan commented on AMQ-735:
------------------------------------
BTW if those numbers are not the number of instances in the JVM - which could be true (they might be hashcodes rather than instance counts) - then the pictures are not helpful - we need to know how many instances of each type there are - i.e. to find a memory leak we need to know what objects are using up all the RAM
> Possible 4.0 consumer client memory leak?
> -----------------------------------------
>
> Key: AMQ-735
> URL: https://issues.apache.org/activemq/browse/AMQ-735
> Project: ActiveMQ
> Type: Bug
> Components: JMS client
> Versions: 4.0
> Environment: windows xp pro, jdk 1.5, AMQ 4.0 (incubator)
> Reporter: Karthik Sethuraman
> Priority: Critical
> Attachments: activemq_735.zip, jmsmon.zip
>
>
> On running the attached test programs (one producer on a topic, one consumer on a topic), the consumer eventually encounters OutOfMemoryError after receiving around 64 MB of messages). Default JVM heap size is used (64 MB).
> The problem does not happen with RC2 build.
> The test programs allows specification of message payloads of different sizes and different message rates, as well number of producer/consumer threads/instances., topics and topic connection factories, via user environment variables.
> http://www.nabble.com/4.0+Consumer+OutOfMemoryError+bug--t1707655.html#a4660556
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-735) Possible 4.0 consumer client memory
leak?
Posted by "Feng Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-735?page=comments#action_36253 ]
Feng Wang commented on AMQ-735:
-------------------------------
I have run JProbe and I suspect that maybe MessageDispatch has the memory leak. Please see the attached screen shot.
Feng
> Possible 4.0 consumer client memory leak?
> -----------------------------------------
>
> Key: AMQ-735
> URL: https://issues.apache.org/activemq/browse/AMQ-735
> Project: ActiveMQ
> Type: Bug
> Components: JMS client
> Versions: 4.0
> Environment: windows xp pro, jdk 1.5, AMQ 4.0 (incubator)
> Reporter: Karthik Sethuraman
> Priority: Critical
> Attachments: activemq_735.zip, jmsmon.zip
>
>
> On running the attached test programs (one producer on a topic, one consumer on a topic), the consumer eventually encounters OutOfMemoryError after receiving around 64 MB of messages). Default JVM heap size is used (64 MB).
> The problem does not happen with RC2 build.
> The test programs allows specification of message payloads of different sizes and different message rates, as well number of producer/consumer threads/instances., topics and topic connection factories, via user environment variables.
> http://www.nabble.com/4.0+Consumer+OutOfMemoryError+bug--t1707655.html#a4660556
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira