UCF Session Timeout while accessing webtop via SSL

When we try to access the Webtop via SSL (using RSA or any other) , it always fails in content transfer related action (create document / export / checkout) and gives the below error.

Steps to troubleshoot:

Turn on UCF server and UCF client tracing, and recreate the error? Tracing details are below:



1. UCF Client logs and traces
Please set the following for the above mentioned traces/logs
In ucf.client.config.xml,
       
            true
        .
In ucf.client.logging.properties,
handlers=java.util.logging.FileHandler, java.util.logging.ConsoleHandler
.level=ALL (by default, it is WARNING)

2. UCF Server logs and traces
In ucf.server.config.xml,
     
         true
     

Please reference the log4j.properties example below, which is meant to help us getting the Server and DFC traces

log4j.rootCategory=ALL, stdout, file
log4j.category.MUTE=OFF
log4j.additivity.tracing=false
#log4j.category.tracing=ERROR, FILE_TRACE
log4j.logger.com.documentum=ALL,DFC_TRACE

#------------------- CONSOLE --------------------------
log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1.threshold=ERROR
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%d{ABSOLUTE} %5p [%t] %c - %m%n

#------------------- FILE --------------------------
log4j.appender.F1=org.apache.log4j.RollingFileAppender
log4j.appender.F1.File=C\:/Documentum/logs/log4j.log
log4j.appender.F1.MaxFileSize=10MB
log4j.appender.F1.layout=org.apache.log4j.PatternLayout
log4j.appender.F1.layout.ConversionPattern=%d{ABSOLUTE} %5p [%t] %c - %m%n

#------------------- FILE_TRACE --------------------------
log4j.appender.FILE_TRACE=org.apache.log4j.RollingFileAppender
log4j.appender.FILE_TRACE.File=C\:/Documentum/logs/trace.log
log4j.appender.FILE_TRACE.MaxFileSize=100MB
log4j.appender.FILE_TRACE.layout=org.apache.log4j.PatternLayout
log4j.appender.FILE_TRACE.layout.ConversionPattern=%d{ABSOLUTE} [%t] %m%n

#------------------- DFC_TRACE --------------------------
log4j.appender.DFC_TRACE=org.apache.log4j.RollingFileAppender
log4j.appender.DFC_TRACE.File=C\:\\Documentum\\logs\\dfc.log
log4j.appender.DFC_TRACE.MaxFileSize=100MB
log4j.appender.DFC_TRACE.layout=org.apache.log4j.PatternLayout
log4j.appender.DFC_TRACE.layout.ConversionPattern=%d{ABSOLUTE} [%t] %m%n

log4j.logger.com.documentum.debug=DEBUG
log4j.logger.com.documentum.web=DEBUG
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=[%d{ISO8601}|%-5p|%-22t|%C|%M|%-4L] %m%n
log4j.appender.file=org.apache.log4j.RollingFileAppender
log4j.appender.file.File=C\:/Documentum/logs/wdk.log
log4j.appender.file.MaxFileSize=500KB
log4j.appender.file.MaxBackupIndex=1
log4j.appender.file.layout=org.apache.log4j.PatternLayout
log4j.appender.file.layout.ConversionPattern=[%d{ISO8601}|%-5p|%-22t|%C|%M|%-4L] %m%n

log4j.category.tracing=DEBUG, FILE_TRACE

3. Combined DFC/DMCL  traces
In dfc.properties file, add the following:
dfc.tracing.enable=true
dfc.tracing.verbose=true
dfc.tracing.max_stack_depth=0
dfc.tracing.include_rpcs=true
dfc.tracing.mode=compact
dfc.tracing.include_session_id=true
dfc.tracing.combineDMCL = true

All of these should be taken together for two times, first when the issue is seen and the second when the issue does not occur.
Its imperative for us to get the these logs (1,2 and 3) together in two sets as mentioned in the above line.