Not Able to Release Docbase Session in DFC code

Dear All,

I have written a simple DFC docbase session code in my eclipse, as shown below....

public class DocbaseConnection {

public static void main(String[] args) throws Exception {
   IDfSessionManager sMgr = null;
   IDfSession session = null;
        try {

         IDfClientX clientx = new DfClientX();
         IDfClient client = clientx.getLocalClient();
         DfLoginInfo loginInfoObj = new DfLoginInfo();

         loginInfoObj.setUser("test");
         loginInfoObj.setPassword("test");
         sMgr = client.newSessionManager();
         sMgr.setIdentity("docbase", loginInfoObj);
         session=sMgr.newSession("docbase");
         System.out.println("docbase is connected successfully "+session);

        } catch( Throwable e ) {
            // catch exception here- see the code for Exception Handling
        }
        finally {
         System.out.println("docbase is not disconnected "+session);
            sMgr.release(session);
            System.out.println("Still now session is connected "+session); // Here I am able to get the session again and again.
        }

}

}

In the above code I am not able to release the docbase session. Could you please help me , why I am not able to release session.

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

lastnitescurry

You should be using the isConnect method to see if you truely have a session. Using the session after it has been disconnected is nasty code. If you were on my dev team, I would be giving you a kicking


public static void main(String[] args) {
  IDfSessionManager sMgr = null;
  IDfSession session = null;
  try {
    IDfClientX clientx = new DfClientX();
    IDfClient client = clientx.getLocalClient();
    DfLoginInfo loginInfoObj = new DfLoginInfo();
    loginInfoObj.setUser("test");
    loginInfoObj.setPassword("test");
    sMgr = client.newSessionManager();
    sMgr.setIdentity("docbase", loginInfoObj);
    session = sMgr.newSession("docbase");
    if (session != null && session.isConnected()) {
      System.out.println("docbase is connected successfully ");
      System.out.println("Conencted to repository name: " + session.getDocbaseName());
      System.out.println("Conencted to repository ID  : " + session.getDocbaseId());
    }
  } catch (Throwable e) {
    System.err.println("" + e.getLocalizedMessage());
    e.printStackTrace(System.err);
  } finally {
    System.out.println("docbase is not disconnected ");
    sMgr.release(session);
    try {
      if (session != null && session.isConnected()) {
        System.out.println("O BOTHER, still connected to repository");
        System.out.println("Conencted to repository name: " + session.getDocbaseName());
        System.out.println("Conencted to repository ID  : " + session.getDocbaseId());
      }
    } catch (DfException e) {
      System.err.println("" + e.getLocalizedMessage());
      e.printStackTrace(System.err);
    }
  }
}

All comments

labib

Hi,

i think you should use session.disconnect();

Disconnects the DFC session.

as sMgr.release(session);

Puts the DFC session object back into the session pool.

best wishes.

dipusonu1

Hi,

I already tried with session.disconnect();

Then also I am not able to release session....

Thanks,

Sonu

labib

Hi,

once you disconnected from session you will not able any operation using this

session cause the exception IDfException.DM_DFCSESS_E_DISCONNECTED

so the below code you will make sure that session is disconnected

session.disconnect();

if (!session.isConnected())

{

// Successfully disconnected...

}

using release method

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.

also if you want to kill this session you can use

session.killSession(IDfId sessionId,

String immediacyLevel,

String message)

PanfilovAB

Actually, IDfSessionManager.release(IDfSession) calls IDfSession.disconnect(), so lalib's advice is useless.

If you want disconnect sessions immediately you should set dfc.session.pool.enable=false in dfc.properties, but it will cause performance degradation. I think you do not understand what you are trying to achieve.

derekz

You did release the session - but you released it back to session manager. At this point you are done - that's exactly how you should be releasing sessions, no need to call disconnect on it.

Now - session manager, is backed by two separate pools - to help with recycling resources allocated to the sessions. For the firs little while (you shouldn't care for how long actually) that session sticks around Level 1 session pool - at this point if you were to ask for that session again, you'll get it with minimal overhead (full reuse). After some time it goes to Level 2 pool, where it can be recycled by other session managers or users. But these are internals of session pooling within DFC - that may as well be a black box to you.

lastnitescurry


public static void main(String[] args) {
  IDfSessionManager sMgr = null;
  IDfSession session = null;
  try {
    IDfClientX clientx = new DfClientX();
    IDfClient client = clientx.getLocalClient();
    DfLoginInfo loginInfoObj = new DfLoginInfo();
    loginInfoObj.setUser("test");
    loginInfoObj.setPassword("test");
    sMgr = client.newSessionManager();
    sMgr.setIdentity("docbase", loginInfoObj);
    session = sMgr.newSession("docbase");
    if (session != null && session.isConnected()) {
      System.out.println("docbase is connected successfully ");
      System.out.println("Conencted to repository name: " + session.getDocbaseName());
      System.out.println("Conencted to repository ID  : " + session.getDocbaseId());
    }
  } catch (Throwable e) {
    System.err.println("" + e.getLocalizedMessage());
    e.printStackTrace(System.err);
  } finally {
    System.out.println("docbase is not disconnected ");
    sMgr.release(session);
    try {
      if (session != null && session.isConnected()) {
        System.out.println("O BOTHER, still connected to repository");
        System.out.println("Conencted to repository name: " + session.getDocbaseName());
        System.out.println("Conencted to repository ID  : " + session.getDocbaseId());
      }
    } catch (DfException e) {
      System.err.println("" + e.getLocalizedMessage());
      e.printStackTrace(System.err);
    }
  }
}

derekz

Brian - for future, please try to keep these type of comments to your biker's forums where they belong.Op is simply trying to understand why calling "release()" on session doesn't immediately burn it up. No need to flame anyone - folks should feel free to ask any type of questions here and not feel intimidated.

To the op - please disregard Brian's code sample - it is wrong - you don't need to check whether the session is connected or not after you release() it - I've explained already what happens internally with released session, so any type of "double checking" is useless. Just release it and forget about it.

PanfilovAB

Derek,

it's an internet, everybody is able to write what he thinks without any stupid political correctness.

As for me it looks weird that EMC employee does not read documentation, does not consult co-workers and asks question here.