on 05-31-2016 9:57 AM
Hello!
We have a problem with possible memory leak in DestinationContainer. This class is parts of JMS component. I found that this issue is very similar to issue described in SAP note (1919681 - Prevent OutOfMemory error in JMS destination container).
In our case, NW stack is in SP 10 (7.4010.2015***). So I expect that the problem is fixed (SAP note fix it in SP 06).
I attached some pictures from heap analysis:
Huge amount of memory is used in waitingForMessagesConsumers (a member of QueueDestinationManager). This hash map contains more than 2 400 000 hash items. It's this expected state or it's memory leak.
Thanks.
Samuel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.