DFS and SessionManager with multiple Content Servers

Hi!!

Our organization has 14 Content Servers.

We have developed a services layer over DFS. We have a problem because when a session is stabilized it always use only four of those 14CS. And specially one of them. We have a very heavy problem because after a time, sessions in database grow enormously and finally the CS crash.

We recover the repository from:

ContextFactory contextFactory = ContextFactory.getInstance();

serviceContext = contextFactory.getContext();

RepositoryIdentity repoIdentity = (RepositoryIdentity) serviceContext.getIdentity(0);

repository = repoIdentity.getRepositoryName();

....

session = sessionManager.getSession( repository );

...

sessionManager.release(session);

dfc.properties file:

dfc.session.max_count = 10000

dfc.session.pool.enable=true

dfc.session.pool.expiration_interval = 5

dfc.session.pool.mode = level1

dfc.docbroker.search_order=random

dfc.docbroker.host[0]=GDCS1 ----> 4 CS (those the session is always created) has maximum proximity

dfc.docbroker.port[0]=4492

dfc.docbroker.host[1]=GDCS1

dfc.docbroker.port[1]=4494

dfc.docbroker.host[2]=GDCS1

dfc.docbroker.port[2]=4489

dfc.docbroker.host[3]=GDCS2

dfc.docbroker.port[3]=4492

dfc.docbroker.host[4]=GDCS2

dfc.docbroker.port[4]=4489

Why session are not destroyed when
"sessionManager.release(session);"
is executed?

Find more posts tagged with

Comments

aflowers001

sessionManager.release(session) does not destroy session as they are 'owned' by the session manager in a pool such that they can be quickly returned to callers. If it destroyed sessions there would be no benefit to using it over the standard session get/release.

As to the usage of only 4 CS what version of DFC/DFS/Content Server do you have. There was a bug, in 6.5 SP1 and others if I recall right, in the way that the session manager got session that meant it would go to the first broker only and would not honour the random search order. There is a hot fix and patch in later versions I believe.

Would I be right in assuming thet vehind each broker there is a [smaller] number of server instances? Do the servers on which session are being created all project to a single docbroker?

Axel

Interesting... We are using 6.5 SP1 environment.

All 7 docbrokers are pointing to 14 CS, but depending the docbroker Content Servers have different proximity.

Most of the requests are redirected to one DFS server which has the random docbroker selection, and has the first docbroker index pointing to the 14 CS, but only four of them have proximity 1 in this docbroker.

These 4 CS are those that are experimenting problems with sessions. We don't have and incredible number of users, more or less 900, and more or less 100 concurrents. But these 4 CS generate a large number of sessions that are not released and finally this behavior crashes these servers.

aflowers001

Might be worth raising a support call and asking about hot fixes/patches or other advice, or just having a look over the release notes for later service packs and versions.