1, WebLogic memory overflow
Recently visited a sudden increase portal traffic, always out of memory, frequent downtime, no parameters to adjust a lot of work, accidentally discovered Weblogic domain is constantly increasing, the culprit turned out to be the diagnostic file Weblogic, Weblogic is also the cause of memory the main reason. When the Weblogic startup when loading the diagnosis on each Server document, taking up most of the memory allocation, the larger the file the user has visited result of the greater, after he was removed to restart the service, surprisingly only eight Server took 6 minutes, only 7-8 minutes to deploy the project also has been running smoothly, no memory overflow.
The document addresses:
/bea/user_projects/domains/(domain_name)/servers/(Server_name)/data/store/diagnostics/*.DAT
(Note: AdminServer 1M under file about the diagnosis of normal)
However, the file will continue to generate increases, our domain is not configured set of documents related to start diagnosis, Bea sale can not explain, but you can start by trying to increase the parameter (-Dcom.bea.wlw.netui.disableInstrumentation = true
) To control the growth of the diagnostic file in the / bea / user_projects / domains / (domain_name) / bin / startWebLogic.sh in:
if ["$ (WLS_REDIRECT_LOG)" = ""]; then
echo "Starting WLS with line:"
echo "$ (JAVA_HOME) / bin / java $ (JAVA_VM) $ (MEM_ARGS) $ (JAVA_OPTIONS)-Dcom.bea.wlw.netui.disableInstrumentation = true-Dweblogic.Name = $ (SERVER_NAME)-Djava.security.policy = $ (WL_HOME) / server / lib / weblogic.policy $ (PROXY_SETTINGS) $ (SERVER_CLASS) "
$ (JAVA_HOME) / bin / java $ (JAVA_VM) $ (MEM_ARGS) $ (JAVA_OPTIONS)-Dcom.bea.wlw.netui.disableInstrumentation = true-Dweblogic.Name = $ (SERVER_NAME)-Djava.security.policy = $ ( WL_HOME) / server / lib / weblogic.policy $ (PROXY_SETTINGS) $ (SERVER_CLASS)
else
echo "Redirecting output from WLS window to $ (WLS_REDIRECT_LOG)"
$ (JAVA_HOME) / bin / java $ (JAVA_VM) $ (MEM_ARGS) $ (JAVA_OPTIONS)-Dcom.bea.wlw.netui.disableInstrumentation = true-Dweblogic.Name = $ (SERVER_NAME)-Djava.security.policy = $ ( WL_HOME) / server / lib / weblogic.policy $ (PROXY_SETTINGS) $ (SERVER_CLASS)> "$ (WLS_REDIRECT_LOG)" 2> & 1
This parameter controls netui diagnostic file generation.
At the same time, you can / bea / user_projects / domains / (domain_name) / bin / setDomainEnv.sh set the print parameters of GC log analysis:
MEM_ARGS = "-Xms2048m-Xmx2048m-verbosegclog: gc.log"
Export MEM_ARGS
The parameters in the / bea / user_projects / domains / (domain_name) / next output gc.lgo
2, Portal Domain adjustment
Domain directory / bin / setDomainEnv, the following parameters:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3, Weblogic configuration commonly used parameters
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||
|
|
| |||
|
|
|
|
| |
|
|
|
|
|
Weblogic.xml the parameters:
Cluster deployment parameters (single cluster environment are available):
<wls:session-descriptor>
<wls:persistent-store-type> replicated_if_clustered </ wls: persistent-store-type>
<wls:sharing-enabled> true </ wls: sharing-enabled>
</ Wls: session-descriptor>
Automatically compile the detection time
<wls:jsp-descriptor>
<wls:page-check-seconds> 60 </ wls: page-check-seconds>
</ Wls: jsp-descriptor>
<wls:container-descriptor>
<wls:servlet-reload-check-secs> 60 </ wls: servlet-reload-check-secs>
</ Wls: container-descriptor>
Third, cluster projects and solutions to deploy error
Cluster project to deploy, there would appear inconsistent version, resulting in the deployment of failure or very slow deployment, deployment error message:
Failure occured in the execution of deployment request with ID '116857440499 'for task '2'.
Error is: 'weblogic.management.DeploymentException: J2EE: one hundred sixty thousand one hundred and forty-nine Error while processing library references.
Unresolved application library references, defined in weblogic-application.xml:
Extension-Name: beehive-controls-1.0, Specification-Version: 1, Implementation-Version: 1.0, exact-match: false,
Extension-Name: weblogic-controls-1.0, Specification-Version: 1, Implementation-Version: 1.0, exact-match: false,
Extension-Name: wls-commonslogging-bridge, Specification-Version: 1, Implementation-Version: 1.0, exact-match: false. '
weblogic.management.DeploymentException: J2EE: one hundred and sixty thousand one hundred forty-nine Error while processing library references.
Unresolved application library references, defined in weblogic-application.xml:
Extension-Name: beehive-controls-1.0, Specification-Version: 1, Implementation-Version: 1.0, exact-match: false,
Extension-Name: weblogic-controls-1.0, Specification-Version: 1, Implementation-Version: 1.0, exact-match: false,
Extension-Name: wls-commonslogging-bridge, Specification-Version: 1, Implementation-Version: 1.0, exact-match: false.
......
Solution:
Weblogic all the libraries will not only fat but also simultaneously released in less than a Cluster to the AdminServer, the change in all libraries of the Target, shown in Figure
评论