| Tomcat encounters out of memory errors |
| Categories: Audium Call Services 3.4.x and 3.5 |
| Article ID: | 45 |
| Last updated: | January 12, 2007 |
| User Opinions |
|
No users have voted.
|
|
Thank you for rating this answer.
|
SUMMARY
While applications are active on Audium Call Services on top of a Tomcat server, the Tomcat server eventually reports an out of memory error.
SYMPTOMS
The Tomcat server reports an out of memory error.
RESOLUTION
There are two common situations that may result in this error:
1) Some custom code is acquiring memory without releasing it. Your code should be checked for memory leaks to avoid this situation.
or
2) The Audium application is not correctly terminating the calls and releasing the sessions. This can be tested through a load test of your Audium Call Services server. Check for this situation throughout the load test, for example when you know there should be 30 active calls to the system, run the status script from within Call Service's admin folder. If it shows more than 30 active calls, then some sessions were not properly released. This will eventually cause memory to fill up as incoming calls get queued because they cannot access the system (each queued call requires memory).
There are additional reasons why Tomcat may report this error, please refer to this page on the Tomcat website for detailed information.
|
| Visitor Comments |
|
No visitor comments posted. Post a comment
|
| Attachments |
|
No attachments were found.
|
Search the Knowledgebase
Jump to ID
Browse by Category
Print this page
Post a comment