Session Pooling

Hi All,

I have enabled level1 pooling in dfc.properties and tested few scenarios to check whether the session is getting resued or not.

My testing goes like this...

First i create the session and release it and then try to create the session again using the same session manager and same user credentials, but i never feel that the session is getting reused.

I have checked the DCTM Session ID property in DA, each time the session is created, the DCTM Session ID is different. By this i came to know that the session is not getting reused.

Below is the piece of code i am using for testing...

for(int i=0;i<10;i++)

{

session=sMgr.getSession("docbasename");

sMgr.release(session);

}

dfc.properties:

dfc.session.pool.enable = true

dfc.session.pool.expiration_interval = 1

dfc.session.pool.mode = level1

dfc.session.max_count = 1000

Please let me know whether my testing is correct and am i checking the correct property, if not please let me know how to test this functionality...it is very urgent..waiting for ur replies..

Thanks,

KeenYen

Find more posts tagged with

Comments

Haroon_A

see if these articles help, these are from previous versions, but I guess the concept is still same:

http://developer-content.emc.com/developer/downloads/ConnectionPoolingOverview.pdf

http://developer-content.emc.com/developer/devcenters/ContentManagement/devsupp/DFC_Session_Management_Whitepaper.pdf

Hi Sakhi,

Thanks for the documentation, i went through the documents and didn't find any help regarding my question.

I need to know how can we test the session pooling and need to differentiate the sessions each time they are created.

I have used session.getSessionID() for each session, but it is always returning s2, is there any other property or field to differentiate the sessions

Thanks,

KeenYen

Haroon_A

I belive it should be normal. According to documentation, if pooling is enabled, the session will remain available for a shortperiod of time and if asked again 'quickly', the same session will be returned (I guess with same session id, in your case s2). IF you want, you can add a 'sleep' in between your getsession and release statements, and increase the sleep interval and see if session id changes.

for(int i=0;i<10;i++)

{

session=sMgr.getSession("docbasename");

sysout("session id" + session.getSessionId());

sleep(2 mins); // try to increase this time interval and see if you get different session id

sMgr.release(session);

}