Do you really know where it is taking most of the time ...mostly in these kind of scenarios ..it may be trying to build the cache....
One thing which you can definitely try and see if the ore-compile code parameter is on ....it may be pre-compiling all the code and thus taking time...
You can easily see in that in the logs file which will show precompiling the code...or check the weblogic.xml for precompile as true.
Hi - Thanks for your reply.
I have checked through my server directory and can see weblogic.xml file under
while scanning this file, I dont see any attribute which talks about precompile as true.
do I need to add this paramater in this file as<jsp-descriptor>
Did you observe any out of memory or any other exceptions in the logs?
Please refer the document, Long Delay During Startup of SOA Managed Server (Doc ID 1336411.1) and see if it's applicable for you.
Hi Thanks for your response.
I dont see any OOM issue in logs.
I have see this document and implemented same last week but still seeing same issue. Be more specific, I am seeing this issue on our server where I am having SOA/BPM/ADF code running. other weblogic managed server are running fine.
any idea on this. I can also post the complete log file for your reference if needed.
java.runtime.name = Java(TM) SE Runtime Environment
java.runtime.version = 1.6.0_33-b03
java.security.egd = file:/dev/./urandom
It seems, we need to drill down a little more.
You may use tools like JRockit Mission Control or JvisualVM to gather the stats.
Reference: JVM Memory Monitoring, Tuning, Garbage Collection, Out of Memory, and Heap Dump Analysis For SOA Suite Integration 11g (Doc ID 1358719.1).
If the logs file is not that big ...it would be good if you upload it.