注册 登录  
 加关注
   显示下一条  |  关闭
温馨提示!由于新浪微博认证机制调整,您的新浪微博帐号绑定已过期,请重新绑定!立即重新绑定新浪微博》  |  关闭

love3400wind的blog

like

 
 
 

日志

 
 
 
 

Weblogic configuration of memory and common parameters  

2011-06-20 14:44:52|  分类: IT |  标签: |举报 |字号 订阅

  下载LOFTER 我的照片书  |

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:


Mark


Production mode is set


Explain


DOMAIN_PRODUCTION_MODE


true


This parameter determines whether the Domain is running in a production environment, you can create a Domain, select the running mode, you can manually adjust the parameters


IterativeDevFlag


false


Is automatically compiled


DebugFalg


false


Debugger is enabled


TestConsoleFlag


False


Testing tools to support JMS


LogErrorsToConsoleFlag


False


Whether the error log output to the screen


verboseLogginFlag


False


Debug log is output


PointbaseFlag


False


It automatically starts Pointbase


3, Weblogic configuration commonly used parameters


Serial number


Project


Content


Description


Reference value


Photos


1


Domain>

Environment>

Cluster>

General>


Default Load Algorithm:


Set cluster load balancing strategy


Round-robin: cycling

Weight-based: the weight (do not configure this policy to address the Server configuration to use the weight, see 2)

Random: Random

Round-robin-affinity /

Weight-based-affinity /

Random-affinity of these three parameters for the hardware to do front-end load balancing settings


Figure 1


2


Domain>

Environment>

Servers>

ManagedServer>

Cluster>


Cluster Weight:


Setting the distribution of each Managed Server weight


Default of 100, set the percentage of total 100


Figure 2


3


Domain>

Environment>

Servers>

Server>

Logging>


Stdout Serverity Threshold:


Logging level


Error


Figure 3


Rotation Type:

Minimum File Size


The type of log rolling

Create new log file size


By Size

5000k


Limit number of retained files

Log Files To Retain: [n]


Limit the number of log files retained

To keep the number of log files


Select

10


4


Domain>

Connection Pools>

Configuration>

Connections


Initial Capacity:

Maximum Capacity:


Set the initial capacity

Maximum capacity


Proposed initial capacity and the maximum capacity set to equal values, and to consider the number of concurrent threads to access the database to adjust the parameters


5


Domain>

Connection Pools>

Configuration>

Connections


URL


Cluster Database URL set method


For example: jdbc: oracle: thin: @

(Description =

(Address_list = (address = (host = scdb1_vip)

(Protocol = tcp) (port = 1521))

(Address = (host = scdb2_vip)

(Protocol = tcp) (port = 1521))

(Load_balance = yes)

(Failover = yes))

(Connect_data = (service_name = scdb)))


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

  评论这张
 
阅读(1623)| 评论(0)
推荐 转载

历史上的今天

在LOFTER的更多文章

评论

<#--最新日志,群博日志--> <#--推荐日志--> <#--引用记录--> <#--博主推荐--> <#--随机阅读--> <#--首页推荐--> <#--历史上的今天--> <#--被推荐日志--> <#--上一篇,下一篇--> <#-- 热度 --> <#-- 网易新闻广告 --> <#--右边模块结构--> <#--评论模块结构--> <#--引用模块结构--> <#--博主发起的投票-->
 
 
 
 
 
 
 
 
 
 
 
 
 
 

页脚

网易公司版权所有 ©1997-2017