-
Bug
-
Resolution: Done
-
Major
-
7.3.1.CR2
This customer is seeing some notable growth in the EJB3 SimpleCache expirationFutures map:
Class Name | Objects | Shallow Heap | Retained Heap ---------------------------------------------------------------------------------------------------------------- org.jboss.ejb.client.UUIDSessionID | 5,114,221 | 122,741,304 | >= 490,965,224 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask| 5,064,957 | 364,676,904 | >= 364,692,736 ---------------------------------------------------------------------------------------------------------------- Class Name | Ref. Objects | Shallow Heap | Ref. Shallow Heap | Retained Heap ---------------------------------------------------------------------------------------------------------------------------------------------------------------- cache org.jboss.as.ejb3.cache.simple.SimpleCache @ 0x66eb52818 | 1,494,985 | 40 | 35,879,640 | 307,386,360 '- expirationFutures java.util.concurrent.ConcurrentHashMap @ 0x66eb52840 | 1,494,985 | 64 | 35,879,640 | 307,386,040 '- table java.util.concurrent.ConcurrentHashMap$Node[2097152] @ 0x70ac00000 | 1,494,985 | 8,388,624 | 35,879,640 | 307,385,976 |- [1672250] java.util.concurrent.ConcurrentHashMap$TreeBin @ 0x6cbf7c700 | 8 | 48 | 192 | 1,776 | |- first java.util.concurrent.ConcurrentHashMap$TreeNode @ 0x6cbf7c580 | 5 | 48 | 120 | 216 | | |- parent java.util.concurrent.ConcurrentHashMap$TreeNode @ 0x6cbf7c610 | 4 | 48 | 96 | 216 | | | |- right, next java.util.concurrent.ConcurrentHashMap$TreeNode @ 0x6cbf7c640 | 3 | 48 | 72 | 216 | | | | |- right, next java.util.concurrent.ConcurrentHashMap$TreeNode @ 0x6cbf7c670| 1 | 48 | 24 | 216 | | | | | '- key org.jboss.ejb.client.UUIDSessionID @ 0x6a8da9bd0 | 1 | 24 | 24 | 96 ----------------------------------------------------------------------------------------------------------------------------------------------------------------
5064627 of those tasks are in a cancelled state and are not in the ScheduledThreadPoolExecutor's work queue. And there a just a few hundred in the cache entries map compared to the millions of expirationFutures entries.
Any thoughts how they could end up with such high cancelled expirationFutures while there's so few entries? Are we somehow missing some expiratinoFutures removals?
- is cloned by
-
-
- Verified
-