Issue 5 in sipana: OutOfMemory in SipanaAgent with high traffic and constant server disconnection

[codesite...@google.com]

Status: Accepted
Owner: marcoshack
Labels: Type-Defect Priority-Critical Performance Milestone-v0.4

New issue 5 by marcoshack: OutOfMemory in SipanaAgent with high traffic and
constant server disconnection
http://code.google.com/p/sipana/issues/detail?id=5

SipanaAgent throws OutOfMemory exception after about 11 minutes when
capturing about 10 calls per second as showed in the jconsole screen shots
attached.

During these tests the server was restart a couple times and client
reconnected to it normally but as showed in the JConsole Thread graph a lot
of JMS client threads were hanged up, probably by a wrong use of the JMS
ConnectionFactory.

Attachments:
sipana-agent-jconsole-Memory-10_caps.png 58.6 KB
sipana-agent-jconsole-Overview-10_caps.png 77.7 KB
sipana-agent-jconsole-Threads-10_caps.png 61.3 KB

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Updates:
Labels: -Performance

Comment #1 on issue 5 by marcoshack: OutOfMemory in SipanaAgent with high

traffic and constant server disconnection
http://code.google.com/p/sipana/issues/detail?id=5

Performance label removed because it isn't a performance problem.

[codesite...@google.com]

Comment #2 on issue 5 by marcoshack: OutOfMemory in SipanaAgent with high

traffic and constant server disconnection
http://code.google.com/p/sipana/issues/detail?id=5

Wait Issue #10 completion before start working in this one. Replacing JMS
sender by
the HTTP sender should fix this problem as the JMS code will be descarted.