How to get ID of IDfSession?

Hi All,

I want to destroy session. I found killSession method in DFC api. For killSession method we require ID of IDfSession.

I am using IDfSession.getSessionId() method but it is giving me values like s0,s1...etc. So, how to get session id. If there is other method to destroy session, please suggest.

Thanks

Find more posts tagged with

Comments

Haroon_A

Can you describe your requirement a bit? If you need to disconnect a session, then a) if it's a managed session -- in other word the session has been created using IDfSessionManager.getSession() -- then you need to use IDfSessionManager.release(IDfSession) method to release the session. b) if it's un-managed session, then you could use IDfSession.disconnect() method to do so.

PanfilovAB

IDfSession.getSessionConfig().getObjectId()

Anuradha88

Hi,

I used IDfSession.getSessionConfig().getObjectId() this to get session id but it is giving me exception like :

java.lang.IllegalArgumentException: Kill session requires an ID for a session.

at com.documentum.fc.client.impl.session.Session.killSession(Session.java:3605)

at com.documentum.fc.client.impl.session.SessionHandle.killSession(SessionHandle.java:2554)

at com.impact.qtl12.documentum.services.DocumentumHandler.destroySession(DocumentumHandler.java:2507)

at com.impact.qtl12.imports.UI.CSVWizard.CreateCSVFileWizard.performFinish(CreateCSVFileWizard.java:123)

at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:752)

at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:373)

at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)

at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)

at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)

at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)

at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)

at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)

at org.eclipse.jface.window.Window.open(Window.java:801)

at com.impact.qtl12.imports.UI.CSVFile.QTL$4$1.run(QTL.java:518)

at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)

at com.impact.qtl12.imports.UI.CSVFile.QTL$4.widgetSelected(QTL.java:461)

at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)

at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)

at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)

at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)

at com.impact.qtl12.imports.UI.CSVFile.QTL.createShell(QTL.java:577)

at com.impact.qtl12.imports.UI.CSVFile.QTL.launch(QTL.java:587)

at com.impact.qtl12.imports.UI.CSVFile.QTL.main(QTL.java:607)

PanfilovAB

Oops...

getSessionConfig().getId("session_id")

Anuradha88

Thanks a lot.

Anuradha88

Hi,

I am using idfSession.killSession(id, DfSessionKillImmediacyLevel.NICE, ""); this statement for killing session but it is not killing session.

I am creating SWT application and I want to destroy session on the Finish button of wizardpage. Previously I used

DfSessionKillImmediacyLevel.UNSAFE this parameter in killSession method but application was hanging so I used DfSessionKillImmediacyLevel.NICE parameter. Please give me soulution on this.

Thanks

PanfilovAB


Anuradha88 wrote:

Hi,
         I am using idfSession.killSession(id, DfSessionKillImmediacyLevel.NICE, ""); this statement for killing session but it is not killing session.
         I am creating SWT application and I want to destroy session on the Finish button of wizardpage. Previously I used
DfSessionKillImmediacyLevel.UNSAFE this parameter in killSession method but application was hanging so I used  DfSessionKillImmediacyLevel.NICE parameter. Please give me soulution on this.

Thanks

I suppose you are doing something wrong. KILL_SESSION call cause immediate exit of server process/thread, but it barely affects dfc-clients because they transparently reconnects after failure of server process/thread.