Killing a session

Hi,

I'm trying to kill an inactive session.

I execute show_sessions so i obtain all sessions related information.

So i now have "session" (the object ID of the session begun by user_name)...

If i kill an active session, the CS deactivate it. But what should i do if i want to delete or kill Inactive sessions????

Now if i try to kill an inactive sessions an Exception occurs saying that this session id does not exist in repository.

Here is my code

public boolean matarSesion (String identificadorSesion, String repositorio)

{

try

{

sesion = manager.getSession(repositorio);

IDfId id = new DfId(identificadorSesion);

sesion.killSession(id, DfSessionKillImmediacyLevel.UNSAFE, "La sesión "+ identificadorSesion + " ha sido desconectada de forma manual");

return true;

}

catch (DfServiceException e1)

{

e1.printStackTrace();

}

catch (DfException e2)

{

e2.printStackTrace();

}

finally

{

manager.release(sesion);

}

return false;

}

Find more posts tagged with

Comments

aflowers001

Why do you need to kill the inactive sessions? Is it causing issues?

sivarry

Hi,

Yes it is not possible to kill/remove an inactive session probably some handles are still in use. This is the definition of Inactive sessions from CS Fundamentals guide

Inactive repository sessions are sessions in which the server connection has timed out but
the client has not specifically disconnected from the server. If the client sends a request
to the server, Content Server re-authenticates the user and, if the user is authenticated,
the inactive session automatically reestablishes its server connection and becomes active.
If a session is started with single-use login ticket and that session times out, the session
cannot be automatically restarted by default because the login ticket cannot be re-used.
To avoid this problem, an application can use resetPassword, an IDfSession method.
This method allows an application to provide either the user’s actual password or
another login ticket for the user. After the user connects with the initial login ticket,
the application can either:
• Generate a second ticket with a long validity period and then use resetPassword
to replace the single-use ticket
• Execute resetPassword to replace the single-use ticket with the user’s actual password
Performing either option will ensure that the user is reconnected automatically if his
or her session times out.

Hope this helps

-Siva

Axel_Gil

Thanks,

I'm seeing a lot of inactive sessions in the repository, more than active sessions. I'm not sure if they are consuming resources or what they are doing. After an indeterminate number of hours, an inactive session dissapears, it can be 1 or 2 hours or 6 or 7!! I don't know why, but i don't like it.

I'm totally sure that if i logging again using the user which has an inactive session, it use or create an active session, no reactivate an inactive one.

sivarry

Hi,

I too have the same question on the time it takes to remove the inactive session I could see inactive sessions older than 10 days in our system.

My understanding is that the underlying DB and filesystem connections will not be kept open for such long time rather only the client information is persisted for a while to reconnect if required

-Siva