Closing MDM Connections in Portal

From the Java APIs, I am using Destroy session command in portal to close the MDM Connection.

public void destroySession() throws MdmException{

METHOD="destroySession";

if(simpleConnection!=null){

DestroySessionCommand destroySessionCommand=new DestroySessionCommand(simpleConnection);

try {

if(userSession!=null && repositorySession!=null){

destroySessionCommand.setSession(repositorySession);

destroySessionCommand.execute();

destroySessionCommand.setSession(userSession);

destroySessionCommand.execute();

}

} catch (CommandException e) {

throw new MdmException(e.getMessage(),METHOD,CLASS_NAME);

}

userSession=null;

repositorySession=null;

closeConnection();

}

}

But when I check in MDM Console, I am seeing quite a large number of API connections/users logged in from Java API.

Any idea/pointer to the issue.

I have faced the similar issue on SP4/5 and now on 6.

Is there any thing extra that i need to do?

What are the best practices involved here?

What is the best way to close the session and the connection so that the API connection closes properly?

... Wanted to add one thing: When i unload / load the repository, quite a substantial number of such entries remain intact in Console.

Regards,

Nitin

Edited by: Nitin Mahajan on Oct 14, 2008 8:25 PM