Weblogic Admin Server and Manager server memory allocation defect optimization

1. Admin Server and Manager server memory allocation defect Description

WebLogic servers typically design one or more domains (domain) for each business system, and each domain service principal must consist of two types of server, admin server and manage server. Both types of servers need to occupy a certain amount of memory resources (manual configuration), Manage server is responsible for running the business, Admin Server is only responsible for managing Manage server, but only when the WebLogic is started and the WebLogic configuration needs to be adjusted. When WebLogic is started, the admin server shutdown does not affect the normal use of the business, so manage server does require large memory support, but the admin server only needs about 500MB of memory to keep it on standby.

The default design for the Admin server and manage server is to obtain a memory configuration by calling the WebLogic installation directory together bea/user_projects/domain/{domain_name}/ The "Mem_args" parameter in the setdomainenv.sh file in the bin directory to get the memory size, causing both the admin server and manage server to acquire the same size of memory.

For example, because the performance of the business requires the configuration of 4GB memory for manage server, that is, the memory size of 4GB is configured in the setdomainenv.sh file.

mem_args= "-xms4096m -xmx4096m

In this way, Manage server does get 4GB of memory, but the Admin server under each domain is also getting 4gb,admin The server wastes 3.5GB of memory, and if a system has more than one domain, or a weblogic of multiple systems deployed on a single server, the total amount of memory wasted is multiplied.

The above situation belongs to the double flaw in the design and configuration of WebLogic.

2. The impact of Admin server and Manager server memory allocation defects

(1), multiple sets of system common server, in order to create a different domain way to differentiate the system, or, a set of systems, different modules to create different domains to isolate the mode of module services, formed a WebLogic server created a number of domains, each domain must have an admin server, The reality that makes multiple admin servers exist on the same server, in large companies, because of the large number of middleware servers, the waste of hardware equipment is amazing.

(2), in the memory configuration itself is not rich in the system, a lot of wasted memory makes the system performance drops sharply, even caused the server to stop responding and down

(3), because the admin server wasted unnecessary memory space, can be multiple sets of System WebLogic co-deployed to the same server can be resolved, have to configure a server equipment, not only the waste of hardware equipment resources, but also increase the operation of human resources, Input of power resources, input of space resources in computer room, input of network equipment resources, etc.

3. Optimization Strategy3.1 Memory Acquisition mode Architecture design optimization adjustment3.1.1 Old schema before optimization (default) 3.1.2 New architecture after optimization 

3.2 Memory Acquisition configuration code adjustment

For each domain, under the bin directory startweblogic.sh file, add the following:

Add the following line in front of the echo "JAVA Memory Arguments:${mem_args}":

if ["${server_name}" = "AdminServer"]; Then Mem_args= "-xms512m-xmx512m-xx:maxpermsize=256m" Fi

Restart the WebLogic and the adjustment is complete.

This article Li Junjie (Network Name: casing), engaged in "system architecture, operating systems, storage devices, databases, middleware, applications" six levels of systematic performance optimization work

Welcome to the System performance Optimization Professional group, to discuss performance optimization technology together. Group number: 258187244

Weblogic Admin Server and Manager server memory allocation defect optimization