Could following weblogic settings in the conf file cause this issue?
# Default timeout values.
# Do not change these without understanding their purpose.
wrapper.cpu.timeout=120
wrapper.ping.timeout=0
wrapper.startup.timeout=0
wrapper.shutdown.timeout=0
wrapper.restart.delay=5
We changed these settings to prevent the Wrapper is going to stop/startup the appserver automatically.
What about the following settings I'm currently testing on one of our testboxes? Any experience with ?
wrapper.java.additional.22=-XXtlasize64k
wrapper.java.additional.23=-XXlargeobjectlimit8k
and
wrapper.java.additional.4=-Xgc
arallel
# Java Additional Parameters
wrapper.java.additional.1=-jrockit
wrapper.java.additional.2=-Xms2048m
wrapper.java.additional.3=-Xmx2048m
wrapper.java.additional.4=-Xgc
arallel
wrapper.java.additional.5=-Xverbose:memory
wrapper.java.additional.6=-Xnoclassgc
wrapper.java.additional.7=-Dglog.home=%GLOG_HOME%/glog/config
wrapper.java.additional.8=-Duser.home=%GLOG_HOME%/glog/config
wrapper.java.additional.9=-Djava.io.tmpdir=%GLOG_HOME%/temp
wrapper.java.additional.10=-Djava.awt.headless=true
wrapper.java.additional.11=-Djava.security.auth.login.config=%GLOG_HOME%/glog/config/gc3_jaas.config
wrapper.java.additional.12=-Dweblogic.Name=gc3-fikylx25
wrapper.java.additional.13=-Dbea.home=/opt/otm/bea
wrapper.java.additional.14=-Dweblogic.home=%WL_HOME%/server
wrapper.java.additional.15=-Dweblogic.management.username=system
wrapper.java.additional.16=-Dweblogic.management.password=%WL_PW%
wrapper.java.additional.17=-Dweblogic.ProductionModeEnabled=true
wrapper.java.additional.18=-Dweblogic.management.discover=false
wrapper.java.additional.19=-Djava.security.policy=%WL_HOME%/server/lib/weblogic.policy
wrapper.java.additional.20=-Xss256k
wrapper.java.additional.21=-Xmanagement
wrapper.java.additional.22=-XXtlasize64k
wrapper.java.additional.23=-XXlargeobjectlimit8k
Regards,
Kristof