Enterprise Capture Server Experiences High CPU Usage And Hangs While Recognizing 2-D Data Matrix Bar Codes
(Doc ID 2235904.1)
Last updated on SEPTEMBER 28, 2022
Applies to:
Oracle WebCenter Enterprise Capture - Version 11.1.1.9.0 to 11.1.1.9.0 [Release 11g]Information in this document applies to any platform.
Symptoms
The Capture servers CPU spikes when processing the batches with the Data Matrix bar codes, and over time causes the server to hang. The Capture diagnostic log displays:
[2016-09-28T13:30:40.017-05:00] [wcc_capture1] [NOTIFICATION] [DFW-40101] [oracle.dfw.incident] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: <ECID>] [APP: capture] An incident has been signalled with the incident facts: [problemKey=ADFC-00032 [ADFc] incidentSource=SYSTEM incidentTime=Wed Sep 28 13:30:40 CDT 2016 errorMessage=ADFC-32 executionContextId=79cbd34bdbf854a9:61a02575:157720d36b8:-8000-00000000000009fe]
[2016-09-28T13:30:41.721-05:00] [wcc_capture1] [INCIDENT_ERROR] [DFW-40104] [oracle.dfw.incident] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: <ECID>] [errid: 657] [detailLoc: D:\Oracle\Middleware\user_projects\domains\prod_wcc\servers\wcc_capture1\adr\diag\ofm\prod_wcc\wcc_capture1\incident\incdir_657] [probKey: ADFC-00032 [ADFc]] [APP: capture] incident 657 created with problem key "ADFC-00032 [ADFc]"
[2016-09-28T13:30:42.331-05:00] [wcc_capture1] [NOTIFICATION] [] [oracle.adf.share.dfw.dump.impl.ConfigPropsDumpImpl] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: <ECID>] [APP: capture] Path of configuration propertites dump :D:\Oracle\Middleware\user_projects\domains\prod_wcc\servers\wcc_capture1\adr\diag\ofm\prod_wcc\wcc_capture1\incident\incdir_657/adf_ADFConfigPropertiesDump12_i657.txt
[2016-09-28T13:30:42.331-05:00] [wcc_capture1] [NOTIFICATION] [] [oracle.adf.share.dfw.dump.impl.ConfigPropsDumpImpl] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: <ECID>] [APP: capture] Path of configuration propertites dump :D:\Oracle\Middleware\user_projects\domains\prod_wcc\servers\wcc_capture1\adr\diag\ofm\prod_wcc\wcc_capture1\incident\incdir_657/adf_ADFConfigPropertiesDump12_i657.txt
[2016-09-28T13:30:42.346-05:00] [wcc_capture1] [WARNING] [] [oracle.adfinternal.view.faces.lifecycle.LifecycleImpl] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: <ECID>] [APP: capture] ADF_FACES-60098:Faces lifecycle receives unhandled exceptions in phase RESTORE_VIEW 1[[
javax.faces.application.ViewExpiredException: viewId:/login.jspx - ADF_FACES-30108:The view state of the page has expired because of inactivity. Reload the page.
The instability issues started happening around the same time that they started using a new capture workspace. The major difference in this workspace is that this one pulls data from a Data Matrix bar code to a metadata field. All the other workspaces are using bar codes for document separation. When releasing a batch to the Recognition Processor, the CPU usage for the Capture process increased to around the 20 -30% range and stayed there while it processed the batch. The batches on average have 250-350 pages.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |