search

mauriciorodrigues / memcached-session-manager

Automatically exported from code.google.com/p/memcached-session-manager
0 stars 0 forks source link

Dbcp connection leaks when msm is enabled #198

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.We use dbcp connection pooling. MaxCon = 100. Max http sessions per node = 
1k. Tomcat worker threads = 500. There are 5 tomcat nodes
2.With msm enabled, under load all 500 worker threads keep waiting for dbcp 
connection. This crashes tomcat and makes it unresponsive.
3.When we disable msm, tomcat responds pretty well and doesn't exhaust.

What is the expected output? What do you see instead?

Need to understand if there are any known issues with msm, dbcp and Spring Txs. 

What version of the product are you using? On what operating system?
1.7 msm version

Please provide any additional information below.

Let me know what details you need.

Thanks for this lovely project

Original issue reported on code.google.com by Sid.24.1...@gmail.com on 28 Feb 2014 at 6:00

GoogleCodeExporter commented 8 years ago 
Can you please provide a sample app that allows me to reproduce the issue?

Original comment by martin.grotzke on 28 Feb 2014 at 6:12

GoogleCodeExporter commented 8 years ago 
Hi Martin,

This is reproducible only in production. We are trying to recreate this 
situation in qa.  Our average session size is 400kb and we use Java 
serialization.

Is there any performance benchmark done for msm using Java serialization?

Original comment by Sid.24.1...@gmail.com on 1 Mar 2014 at 7:46

GoogleCodeExporter commented 8 years ago 
Not sure if this is what you're asking for: 
https://code.google.com/p/memcached-session-manager/wiki/SerializationStrategyBe
nchmark

An avg session size of 400k sounds fairly large, perhaps you're serializing 
unexpected stuff? Although in this case you should experience problems in 
simple failover tests in any environment and not only in production.

Original comment by martin.grotzke on 1 Mar 2014 at 12:09

GoogleCodeExporter commented 8 years ago 
Is there anything I can do to help, or shall we close this issue?

Original comment by martin.grotzke on 27 Mar 2014 at 8:14

GoogleCodeExporter commented 8 years ago 
Martin, please close the case. It was a coding issue at our end.

Thanks again for prompt support.

Original comment by Sid.24.1...@gmail.com on 27 Mar 2014 at 9:54

GoogleCodeExporter commented 8 years ago 
Ok

Original comment by martin.grotzke on 27 Mar 2014 at 10:52