Comment #16 on issue 133 by [email protected]: JSR-309 driver leaks
memory
https://code.google.com/p/mediaserver/issues/detail?id=133
In continuation to the above posts,
After several attempts We have done some changes, which fixed the memory
leak issues for our call flows.
All these changes have been made in the jsr-309-driver-3.0.1-SNAPSHOT.jar
only and they are listed below: (and also attached for reference)
1) MediaGroupImpl.java
Called player.release(), recorder.release() and detector.release() from
release method
2) PlayerImpl.java
Nullified fsm object, clearing listeners and playList from release
method
3) RecorderImpl.java
Nullified fsm object, clearing listeners and triggers from release
method
4) ContainerImpl.java
Commented unused list object from the unjoin method
5) SignalDetectorImpl.java
Cleared listeners and triggers from the release method
6) DeleteConnectionResponseHandler.java
Added null check for connection and fsm objects to
processMgcpResponseEvent method
7) NetworkConnectionImpl.java
Nullified fsm object from release method
8) MediaSessionImpl.java
Nullified mixers, groups ,connections and attributes objects from release
method
9) DriverImpl: when the jsr309 api get called, the requestidentifier gets
added in the concurrenthashmap but not removed once the response was
received.
path:[sip-app]---(jsr309-api)------[jsr309.jar]-----[mgcp]----[mgcp..MMS]
==>Removed RequestIdentifier from requestListeners once the handler has
been called inside the processMgcpCommandEvent method.
Key points:
-----------
1.The above fixes may or maynot work for the type of call scenario that you
are running.
2.But keep the references in hand, and tools like jvisualvm for identifying
and fixing the memory leak.
3.Break down the steps into smaller one and try to identify at which step
the memory leak was occuring.
4.Once you fixed, try to run a small trial run and see the performance and
increase the load step by step.
5.While fixing kindly ensure other functionalities are not effected.
6.If you are performing load tests with less number of CPU/RAM, then
sometimes the error response "No response from server during 5000 ms" will
be throwed. To avoid this behaviour, increase the CPU/RAM and allocate more
memory to MSS/JBOSS.
7.Set the log level to ERROR for MSS, MMS, and the sip application
Attachments:
1.txt 575 bytes
2.txt 470 bytes
3.txt 247 bytes
4.txt 497 bytes
5.txt 224 bytes
6.txt 492 bytes
7.txt 674 bytes
8.txt 803 bytes
9.txt 1.5 KB
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "mobicents-all-issues-changes" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
