SessionMgr.release(sess) Vs Session.disconnect()

Selvameena

Which one is the best to use?

Unfortunately we are experiencing session leak while executing our workflow. Below is how we get the session:

IDfSession sessionObj =

null;

// Connect to docbase with given credentials

try { IDfClient client = DfClient.getLocalClient();

DfLoginInfo loginInfo =

new DfLoginInfo();

m_sessionMgr = client.newSessionManager();

loginInfo.setUser(strDocUser);

loginInfo.setPassword(strPasswd);

m_sessionMgr.setIdentity(strDocbase, loginInfo);

sess =

m_sessionMgr.getSession(m_docbase

);

I find they use session.disconnect() everywhere. But I guess as we use newSessionManager(), there should be someway to nullify the session manager and SessionMgr.release(session) does that.This is the code written 3 years back. I see the code release() were commented everywhere and disconnect() was used instead. But no documentation, so cant say why disconnect() was preferred.Are there are any side effects using release() ?Please advice...I find they use session.disconnect() everywhere. But I guess as we use newSessionManager(), there should be someway to nullify the session manager and SessionMgr.release(session) does that.This is the code written 3 years back. I see the code release() were commented everywhere and disconnect() was used instead. But no documentation, so cant say why disconnect() was preferred.Are there are any side effects using release() ?Please advice...I find they use session.disconnect() everywhere. But I guess as we use newSessionManager(), there should be someway to nullify the session manager and SessionMgr.release(session) does that.This is the code written 3 years back. I see the code release() were commented everywhere and disconnect() was used instead. But no documentation, so cant say why disconnect() was preferred.Are there are any side effects using release() ?Please advice...

System details:

Dctm 6.5 SP1

Jboss 4.2

Jdk 1.5

Find more posts tagged with

Comments

msroth

I'm not sure this is exactly the right answer, but check this thread: https://community.emc.com/message/143517.

BartThierens

The difference between the two is that IDfSession.disconnect() will disconnect it from the repository, so you can't use that session anymore to make calls to the repository. However, it does not release the session to the session pool managed by Documentum so it won't be available for re-use.

You also have to be the creator of the session to be able to disconnect it.

IDfSessionManager.release(IDfSession) will release the session back to the session pool making it available for new connections. However, the session may still be connected to the repository.

So you should, when you create a session, release it at the end, and not disconnect it.

Javadoc info:

void disconnect()
                throws DfException

Disconnects the DFC session.

After a session is disconnected, all subsequent calls made using that session cause the exception IDfException.DM_DFCSESS_E_DISCONNECTED to be thrown.

You cannot use this method to disconnect an adopted session.

void release(IDfSession session)

Puts the DFC session object back into the session pool. You should call this method as soon as you are finished with objects in that session.

Haroon_A

Sessions that can be obtained via session manager are managed session, and you should use it, if you enabled session pooling (At the content server level). And at the end you need to 'release' it back to the pool using sessionamanger.release(session), statement in your finally block.

on the other hand, if you get a session, not by session manager, that that's an unmanaged session, and you need to 'disconnect' it, using session.disconnect().

A session, which is obtained via session manager, shouldn't be disconnected, using session.disconnect() (I believe, it won't even allow you, but not sure 100%), it has to be 'release'd back to the pool.

So, if you are using session manager to get your session, then I'd suggest, you change your code to use sessionmanager.release(), as opposed to disconnect().