If you have performance problem while starting up Opmnctl / Application for Oracle Application 10.1.2.0 in clustered, this could be due to the bug in the OC4J.
As higlighted , in the bug fixed for the 10.2.2.2 ,
In a clustered environment the command 'dcmctl updateConfig ..' in one node copies the orion-ejb-jar.xml to other node and as a result unnecessary redeployment of the j2ee application occurs in other node.
To check, goto both server of the clustered and compared the files at $ORACLE_HOME/j2ee/APP/application-deployments/AppName/AppName.jar/orion-ejb-jar.xml
You will also notice in the log files, if you have set the OC4J options -out
09/02/23 20:34:16 Auto-deploying - AppEJB.jar (orion-ejb-jar.xml had been updated since the previous deployment)...
Metalink Doc ID: 398955.1