STUCK Threads In IBR Servers After Configuring SSL Idc.provider.KeepaliveSocketOutgoingProvider In Webcenter Content
(Doc ID 2432970.1)
Last updated on DECEMBER 19, 2024
Applies to:
Oracle WebCenter Content - Version 11.1.1.9.0 and laterInformation in this document applies to any platform.
Goal
The following is configured - Webcenter Content SSL Outgoing provider and IBR SSL Incoming provider, as follows:
IBR SSL Incoming Provider:
ProviderClass=idc.provider.ssl.SSLSocketIncomingProvider
ProviderConnection=idc.provider.KeepaliveSocketIncomingConnection
Webcenter Content SSL Outgoing provider:
ProviderClass=idc.provider.KeepaliveSocketOutgoingProvider
ProviderRequest=idc.provider.KeepaliveServerRequest
Connectivity, and IBR Conversions via the SSL provider connection works properly, and was successfully restored, however, STUCK threads started to be observed on the IBR provider incoming side.
The error observed in the IBR_server1-diagnostic.log file:
[2018-05-11T17:41:58.386+00:00] [IBR_server1] [ERROR] [UCM-CS-000001] [oracle.ucm.idcibr] [tid: [STUCK].ExecuteThread: '4' for queue:
'weblogic.kernel.Default (self-tuning)'] [userId: <WLS Kernel>] [ecid:849c5e4ac5fed174:-604f472f:163502019e1:-8000-000000000000001d,0] [APP: Oracle Universal Content Management - Inbound Refinery] general exception[[intradoc.common.ServiceException:
at intradoc.server.ServiceRequestImplementor.buildServiceException(ServiceRequestImplementor.java:2294)
Solution
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
Goal |
Solution |
References |