My Oracle Support Banner

WebCenterContent (WCC) Stopped Responding with CsUserTooManySimultaneousCredentialChecks Error (Doc ID 1539217.1)

Last updated on JUNE 07, 2018

Applies to:

Oracle WebCenter Content - Version and later
Information in this document applies to any platform.


When attempting to use Content Server when using an external API to authenticate, one node of 6 in the cluster fails and the following error occurs.


Error 13/01/2013 0:00 Event generated by user 'monitor' at host 'localhost'. monitor = user name
Unable to determine user credentials for monitor. The content server
has too many outstanding requests against the user storage system in order to
handle this request in a reasonable amount of time. [ Details ]
An error has occurred. The stack trace below shows more information.

intradoc.common.ServiceException: !csUserTooManySimultaneousCredentialChecks,monitor
  at intradoc.server.UserStorage.retrieveUserDatabaseProfileDataEx(
  at intradoc.server.UserStorageUtils.loadUserData(
  at intradoc.server.ServiceSecurityImplementor.loadUserData(
  at intradoc.server.ServiceSecurityImplementor.globalSecurityCheck(
  at intradoc.upload.UploadSecurityImplementor.globalSecurityCheck(
  at intradoc.server.Service.globalSecurityCheck(
  at intradoc.server.ServiceRequestImplementor.doRequest(
  at intradoc.server.ServiceManager.processCommand(
  at intradoc.server.IdcServerThread.processRequest(
  at intradoc.idcwls.IdcServletRequestUtils.doRequest(
  at intradoc.idcwls.IdcServletRequestUtils.processFilterEvent(
  at sun.reflect.GeneratedMethodAccessor199.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(
  at java.lang.reflect.Method.invoke(
  at idcservlet.webdav.WebdavFilter.doFilter(
  at weblogic.servlet.internal.FilterChainImpl.doFilter(
  at weblogic.servlet.internal.FilterChainImpl.doFilter(
  at oracle.dms.servlet.DMSServletFilter.doFilter(
  at weblogic.servlet.internal.WebAppServletContext$
  at weblogic.servlet.internal.WebAppServletContext.execute(

The issue cannot be reproduced easily but seems to occur randomly.

The issue has the following business impact:
Due to this issue, users cannot rely on the node for failover since it must be restarted when this occurs.


To view full details, sign in with your My Oracle Support account.

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

In this Document

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.