[ QUOTE ]
I am currently running a JAS server on OAS 10.1.2.0.2
however i find that the CPU utilisation going to 100% with the java.exe using 98-100%.There are around 6 java.exe which got created.
can somebody tell me how to rectify this problem. THe heap memory is utilized only 20.4 %. Also this happens even with few users( 4-5) logged in.
Freddy,
[/ QUOTE ]
We are having this same issue (WS2k3, OAS 10.1.2.0.2) and we're still in development, so there are very few users using the system. It will run fune from anywhere between 3 days to a week but the CPU will eventually jump to 100% on java.exe - the one associated with JasOC4J's default_island. Looking at the MANY threads (guessing about 100) associated with this particular process, just 2 were using the bulk of the CPU. Beyond this, I'm not sure what to look at exactly or what would cause this problem, so if anyone could suggest something to look at or try, I'm very interested.
The commandline for the java.exe that's going bad is:
"E:\OAS\jdk\bin\java.exe" "-server" "-Xrs" "-Djava.security.policy=E:\OAS\j2ee\JasOC4J\config\java2.policy" "-Djava.awt.headless=true" "-Xms1024m" "-Xmx1024m" "-Doracle.ons.oraclehome=E:\OAS" "-Doracle.home=E:\OAS" "-Doracle.ons.oracleconfighome=E:\OAS" "-Doracle.ons.clustername=C_123.123.123.123.910040.113681438d4.-8000" "-Doracle.ons.instancename=OASDV.cosrvap62.rtc.ts.local" "-Dopmn.compatible=904" "-Doracle.ons.indexid=JasOC4J.default_island.1" "-Doracle.ons.uid=1375993944" "-Doracle.oc4j.instancename=JasOC4J" "-Doracle.oc4j.islandname=default_island" "-DOPMN=true" "-jar" "oc4j.jar" "-config" "E:\OAS\j2ee\JasOC4J\config\server.xml" "-properties" "-properties" "-ports" "ajp:12501,rmi:12401,jms:12601"
You will notice that the contractor that is responsible for installing the system upped the heap to 1024 from the default 512, this was to try and fix the issue. It did not.
I also agree that rebooting nightly is unacceptable. We're a 24/7 shop.
EDIT: Well it just went to 100% only 11 hours after it was last restarted.
One thing I noticed is that the latest JDBC driver wasn't installed per p.20 of the HTML Web Server Installation Guide. Do you think that would have anything to do with it? I'll be installing it tonight and will report back either way.