java.lang.OutOfMemoryError: unable to create new native thread when loading data using Integration Interface (Doc ID 2047689.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Demantra Real-Time Sales and Operations Planning - Version 12.2.3 and later
Information in this document applies to any platform.

Symptoms

On :  12.2.3 version, LoadData

ACTUAL BEHAVIOR  
---------------
Unable to load Cost data from staging table to Base table .

Cost stuck in staging table, we trying to load cost data from Staging table ''BIIO_ITEM_COST'' to Base table mdp_matrix but it seems that the data are not getting loaded to base table, once we run the workflow the last update in mdp_matrix still the same from that time and we wait three days and the same time, no update.

We bounced the Demantra Server and still the same issue.

No error in collaborator.log or integration.log file.

The weblogic logs shows bellow :
 

ERROR
----------
2015-08-19 12:51:34,905 GST [WFProcess_1] INFO  appserver.integration: Import Data.
2015-08-19 12:51:34,905 GST [WFProcess_1] INFO  appserver.integration: ODPM-20044: Run Start Time: 08-19-2015 12:51:34
2015-08-19 12:51:34,906 GST [WFProcess_1] INFO  appserver.integration: ODPM-20045: Interface Name: Unit Cost
2015-08-19 12:51:34,906 GST [WFProcess_1] INFO  appserver.integration: ODPM-20046: Profile Name: Unit Cost
2015-08-19 12:51:34,906 GST [WFProcess_1] INFO  appserver.integration: ODPM-20052: Owner: sop
2015-08-19 12:51:34,907 GST [WFProcess_1] INFO  appserver.integration: ODPM-20053: Profile From Date: 08-01-2013
2015-08-19 12:51:34,907 GST [WFProcess_1] INFO  appserver.integration: ODPM-20054: Profile Until Date: 08-01-2016
Exception in thread "Update_21" java.lang.OutOfMemoryError: unable to create new native thread
    at java.lang.Thread.start0(Native Method)
    at java.lang.Thread.start(Thread.java:640)
    at java.util.concurrent.ThreadPoolExecutor.addIfUnderCorePoolSize(ThreadPoolExecutor.java:703)
    at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:652)
    at com.demantra.common.queue.QueueManager.executeTask(QueueManager.java:188)
    at com.demantra.applicationServer.nupdate.process.UpdateCombQueueManager.execute(UpdateCombQueueManager.java:95)
    at com.demantra.applicationServer.nupdate.process.UpdateTableTask.execute(UpdateTableTask.java:69)
    at com.demantra.common.queue.QueueTask.run(QueueTask.java:55)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)

<Aug 19, 2015 12:56:26 PM GST> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 192.168.16.61:63,810 during the configured idle timeout of 5 secs>



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Log into Workflow Manager.
2. Run workflow to load Cost data.
3. The load Cost data is not completing.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot load cost data. This issue in UAT Instance and we are in critical time due we will go live very soon.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms