What Are the Potential Problems When End-Users Access OOTB InfoCente Webapp Using Browsers With Cookies Persistence Disabled? (Doc ID 2090629.1)

Last updated on DECEMBER 22, 2015

Applies to:

Oracle Knowledge - Version 8.2 and later
Information in this document applies to any platform.

Symptoms

 When end-users access OOTB InfoCente webapp (or iConnect infocenter) using browsers with cookies persistence disabled, there are many potential problems like below:

1) For OOTB infocenter webapp, the user submits content rating will not work.

2) The iConnect infocenter portlet/tab will not work properly.

3) The Analytics event tracking will not work properly and hence the resulted Analytics report statistics are wrong/misleading.

4) The worse scenario (see note below for detail technical explanation) is that if large enough of end-users (hundreds in short period of time say in minutes) accessing the OOTB InfoCente webapp (or iConnect infocenter) using browsers with cookies persistence disabled, it may crash/bring down the WLS (or Tomcat) server hosting the target infocenter webapp due to resource exhaustion.

Note: With InfoCenter webapp deployed on WLS(Tomcat) server, we can only have so many users sessions per instance, which is driven mostly by number of concurrent open sessions. So, if end-users have cookies persistence disabled in their browsers, each click that user makes creates a new InfoCenter session in WLS(Tomcat) server, storing all of their user information over and over again. As a result, 'orphaned' auto-generated sessions (from each end-users clicks) will be left-behind at the WLS(Tomcat) server waiting for the session idle timeout (default to be 30min?) to expired before the resources can be reclaimed/reused.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms