Performance Issues are Observed In WebLogic Portal Due to Unnecessary CMS Repository Re-Connects
(Doc ID 1102113.1)
Last updated on JULY 13, 2020
Applies to:Oracle WebLogic Server - Version 10.0 to 10.3
Oracle WebLogic Portal - Version 10.0.0 to 10.3.1.0.3
Information in this document applies to any platform.
WebLogic Portal frequently reconnects to the content repository, slowing the overall performance. This can be verified using thread dumps which may show a high number of reconnects to the content repository with the following stack trace:
at com/bea/content/federated/internal/delegate/RepositoryManagerDelegate.connect(RepositoryManagerDelegate.java:1106(Compiled Code))
at com/bea/content/federated/internal/delegate/RepositoryHelper.getSessionWithConnectImpl(RepositoryHelper.java:532(Compiled Code))
This can also be confirmed by enabling debug for the class 'com.bea.content.federated.internal.delegate.RepositoryManagerDelegate: on' and observing the debug output which may show reconnects happening for anonymous and authenticated user(s) as follows:
com.bea.content.federated.internal.delegate.RepositoryManagerDelegate@2e7b3f8: (re)initializing all repo sessions for username: <anonymous>
com.bea.content.federated.internal.delegate.RepositoryManagerDelegate@27f0d27: (re)initializing all repo sessions for username: weblogic
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