Considerations for Schema Publishing and Performance Expectations
(Doc ID 1436645.1)
Last updated on MARCH 31, 2023
Applies to:
Oracle WebCenter Content - Version 10.0 and laterInformation in this document applies to any platform.
Purpose
This bulletin is for anyone experiencing slow or poor performance during peak intervals or during server startup. It serves to explain the Schema Publisher and how to configure it.
Scope
This note also includes (but is not limited to) individuals experiencing this type of thread dump:
Long execution starting at 3/14/12 4:06 PM for 223 (secs)
Long connection active time at 3/14/12 4:06 PM for 227 (secs)
system 03.14 16:06:43.932 FileUtilsLockThread The background thread FileUtilsLockThread is taking too long (18087 millis). The following processes are currently being watched:
----/u01/app/stel/data/schema/publishlock/publish.flck schemamonitor
system 03.14 16:07:01.804 HealthMonitorThread ----Start Health Monitor Trace----
2012-03-14 16:07:28
Full thread dump Java HotSpot(TM) 64-Bit Server VM (1.6.0-b105 interpreted mode):
"IdcServerThread-36" daemon prio=10 tid=0x00000000511db800 nid=0x7608 waiting for monitor entry [0x00000000430dd000..0x00000000430dda90]
java.lang.Thread.State: BLOCKED (on object monitor)
at java.util.Arrays.copyOfRange(Arrays.java:3209)
at java.lang.String.<init>(String.java:216)
at intradoc.common.IdcStringBuilder.toString(IdcStringBuilder.java:1279)
at intradoc.common.LocaleUtils.encodeMessage(LocaleUtils.java:178)
at intradoc.common.LocaleUtils.encodeMessage(LocaleUtils.java:173)
at intradoc.shared.ComponentClassFactory.createClassInstance(ComponentClassFactory.java:137)
at intradoc.server.Service.addHandler(Service.java:289)
at intradoc.server.Service.createHandlers(Service.java:260)
at intradoc.server.ServerInfoService.createHandlersForService(ServerInfoService.java:30)
at intradoc.server.Service.initDelegatedObjects(Service.java:199)
at intradoc.server.ServiceManager.processCommand(ServiceManager.java:358)
at intradoc.server.IdcServerThread.run(IdcServerThread.java:197)
Long connection active time at 3/14/12 4:06 PM for 227 (secs)
system 03.14 16:06:43.932 FileUtilsLockThread The background thread FileUtilsLockThread is taking too long (18087 millis). The following processes are currently being watched:
----/u01/app/stel/data/schema/publishlock/publish.flck schemamonitor
system 03.14 16:07:01.804 HealthMonitorThread ----Start Health Monitor Trace----
2012-03-14 16:07:28
Full thread dump Java HotSpot(TM) 64-Bit Server VM (1.6.0-b105 interpreted mode):
"IdcServerThread-36" daemon prio=10 tid=0x00000000511db800 nid=0x7608 waiting for monitor entry [0x00000000430dd000..0x00000000430dda90]
java.lang.Thread.State: BLOCKED (on object monitor)
at java.util.Arrays.copyOfRange(Arrays.java:3209)
at java.lang.String.<init>(String.java:216)
at intradoc.common.IdcStringBuilder.toString(IdcStringBuilder.java:1279)
at intradoc.common.LocaleUtils.encodeMessage(LocaleUtils.java:178)
at intradoc.common.LocaleUtils.encodeMessage(LocaleUtils.java:173)
at intradoc.shared.ComponentClassFactory.createClassInstance(ComponentClassFactory.java:137)
at intradoc.server.Service.addHandler(Service.java:289)
at intradoc.server.Service.createHandlers(Service.java:260)
at intradoc.server.ServerInfoService.createHandlersForService(ServerInfoService.java:30)
at intradoc.server.Service.initDelegatedObjects(Service.java:199)
at intradoc.server.ServiceManager.processCommand(ServiceManager.java:358)
at intradoc.server.IdcServerThread.run(IdcServerThread.java:197)
Details
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
| Purpose |
| Scope |
| Details |
| References |