adoacorectl - ERROR : Timed out( 100000 ): Interrupted Exception:

Please look at all 3 possible solution provided below:

Errors:

****************************************************
Executing service control script:
/app/oracle/product/applts2/inst/apps/ebsts2_ebsapuat/admin/scripts/adoacorectl.sh start
script returned:
****************************************************
ERROR : Timed out( 100000 ): Interrupted Exception

You are running adoacorectl.sh version 120.13

Starting OPMN managed OACORE OC4J instance  ...

****************************************************

From the log files:

12/06/06 07:58:08 WARNING: ApplicationLogManager is not installed, may result in loader leaks. Set -Djava.util.logging.manager=oracle.classloader.util.ApplicationLogManager
12/06/06 07:58:09 WARNING: Unable to access loaded classes.
12/06/06 07:58:11 WARNING: GC: Unable to access pending References.
12/06/06 07:58:11 WARNING: GC: Unable to access pending Reference lock.

Solution 1:

delete all .lock files from the below directory subtrees:

$INST_TOP/ora/10.1.3/j2ee/forms/persistence/forms_default_group_1/
$INST_TOP/ora/10.1.3/j2ee/oacore/persistence/oacore_default_group_1/
$INST_TOP/ora/10.1.3/j2ee/oafm/persistence/oafm_default_group_1/

Shutdown oacore, and remove all .lock files in the directory subtree of :

find $INST_TOP/ora/10.1.3/j2ee/forms/persistence/forms_default_group_1/ -name *.lock
find $INST_TOP/ora/10.1.3/j2ee/oacore/persistence/oacore_default_group_1/  -name *.lock
find $INST_TOP/ora/10.1.3/j2ee/oafm/persistence/oafm_default_group_1/ -name *.lock

Restart using adstrtal.sh

Solution 2:

If not resolved, follow the below timeout workaround from Oracle:

The timeout value is defined in the $ORA_CONFIG_HOME/10.1.3/opmn/conf/opmn.xml file   There are three entries to be concerned about, one for each of the managed OC4J containers (oacore, forms and oafm).  The entry is shown below the appropriate "process-type id=" section and looks like shown below by default:-

Modifying the timeout value from "600" to "1800" may resolve the timeout error . You can only set it for entry “process-type id="oacore"” 
or all entries giving timeout errors

Before:

ebsapuat(applts2):/app/oracle/product/applts2> grep 'start timeout' $ORA_CONFIG_HOME/10.1.3/opmn/conf/opmn.xml
              
              
              
              
              
              
              
              
               
              
              
ebsapuat(applts2):/app/oracle/product/applts2>
After:
ebsapuat(applts2):/app/oracle/product/applts2> grep 'start timeout' $ORA_CONFIG_HOME/10.1.3/opmn/conf/opmn.xml
              
              
              
              
              
              
              
              
               
              
              
ebsapuat(applts2):/app/oracle/product/applts2>

Solution 3:

Decrease the number of oacore processes started in the $CONTEXT_FILE to see if this is not maybe resource related, or as a result of the server running out of resources
You might need to look at the O/S parameters should it start with a reduced number of processes.

With this set, I got the “TIMEOUT” errors:

ebsapuat(applts2):/app/oracle/product/applts2/inst/apps/ebsts2_ebsapuat/appl/admin> grep nprocs $CONTEXT_FILE
         1
         3
         5
         1
         0
ebsapuat(applts2):/app/oracle/product/applts2/inst/apps/ebsts2_ebsapuat/appl/admin>

But after changing it to ths below, adoacorectl.sh started without any errors:

ebsapuat(applts2):/app/oracle/product/applts2/inst/apps/ebsts2_ebsapuat/appl/admin> grep nprocs $CONTEXT_FILE
         1
         1
         1
         1
         0
ebsapuat(applts2):/app/oracle/product/applts2/inst/apps/ebsts2_ebsapuat/appl/admin>