DFC Session Leak

To check the session leaks do the following

1) edit your C:\documentum\config\dfc.properties and add the following in it

dfc.resources.diagnostics.enabled=true

2) Open C:\documentum\config\log4j.properties and add the following at the end

#——————————————-DFC Session Leak Entries————————————-
log4j.logger.com.documentum.fc.client.DfSessionLeakChecker=ERROR,SESS_LEAK_DETECT
log4j.appender.SESS_LEAK_DETECT=org.apache.log4j.R ollingFileAppender
log4j.appender.SESS_LEAK_DETECT.File=C:\Documetum\ logs\sessionLeak.log
log4j.appender.SESS_LEAK_DETECT.MaxFileSize=100MB
log4j.appender.SESS_LEAK_DETECT.MaxBackupIndex=5
log4j.appender.SESS_LEAK_DETECT.layout=org.apache. log4j.PatternLayout
log4j.appender.SESS_LEAK_DETECT.layout.ConversionP attern=%d{ABSOLUTE} [%t] %m%n

#————————————

This will provide output to sessionLeak.log from DfSessionLeakChecker

3) Start your application and check the sessionLeak.log to find the sessionleaks

The stack trace in the log file will have entries like
[Resource Housekeeper] [DFC_BOF_SESSION_LEAK] Unreleased session found in finalize “docbase=TESTING_001, refCounter=1, transFlag=false Session com.documentum.fc.client.DfSession@1245dt4“.
com.documentum.fc.client.DfSessionLeakException

meaning there is a session leak