You are on page 1of 56

Java parameter set for WebLogic start

Garbage collection (GC) is the the JVM release of Java heap memory occupied by the object is no longer used process Java heap (Heap) Refers to the living space of the Java application objects. Heap size determines the GC frequency and time. Heap bigger GC frequency is low and slow. The smaller the heap, GC frequency and high speed. GC and heap size is a set of contradictions. In order to obtain the ideal Heap heap size, you need to make -Verbosegc parameters (Sun jdk:-Xloggc: <file>) to open the detailed output of the GC. Analysis of GC's frequency and time, Results Together the maximum load required memory situations, draw the size of the heap. Usually the case, we recommend the use of available memory (memory) in addition to the operating system and other applications occupy 70-80% for the avoidance Free heap size adjustment due to overhead, the minimum value equal to the maximum value that:-Xms =-Xmx to set the memory heap. In order to prevent memory overflow, Proposed in the production environment heap size of at least 256M (Platform least 512M) 512M ~ 1G performance in the real environment Jia, 2G is not desirable, the memory adjustment may need to adjust the core parameters of the process allows the maximum amount of memory. For sun And hp the jvm permanent domain is too small (default 4M) may also cause memory overflow, should increase the parameter-XX: MaxPermSize = 128m. Build Meeting to set the size of the temporary domain-Xmn the-Xmx 1/4 1/3 SurvivorRatio The 8

Stack memory optimization, modify the configuration file: WL_HOME = C: \ bea \ weblogic81 "% WL_HOME% \ common \ bin \ commEnv.cmd" : On bea bea # If the JDK # JVM Heap (heap memory) minimum size 96M, and the maximum size of 256M set MEM_ARGS =-Xms96m-Xmx256m : Sun # If the sun's JDK

# JVM Heap (heap memory) minimum size 32M, and the maximum size of 200M # Public variable object memory limit: PermSize: Minimum size MaxPermSize: maximum allowable allocation size set MEM_ARGS =-Xms32m-Xmx200m-XX: MaxPermSize = 128m

Monitor stack usage: Download JRockit JDK, the JDK comes with JRockit Mission Control tools, it seems to have no single Sole place to download JRockit Mission Control, JRockit JDK bind download; In C: \ bea \ jrockit81sp5_142_08 \ console directory run: C: \ bea \ jrockit81sp5_142_08 \ bin \ java-Xmanagement-jar ManagementConsole.jar How to monitor weblogic? Modify weblogic startup script the startWebLogic.cmd, startup parameters inside-Xmanagement: % JAVA_HOME% \ bin \ java-Xmanagement% JAVA_VM%% MEM_ARGS%% JAVA_OPTIONS% -Dweblogic.Name =%

SERVER_NAME% -Djava.security.policy = "%

-Dweblogic.ProductionModeEnabled =% PRODUCTION_MODE%

WL_HOME% \ server \ lib \ weblogic.policy "weblogic.Server

Setting performance related configuration parameters 1. The following table lists the parameters affecting server performance.

Name

Parameter

Location

Effect

Cache

max-beans-in-cache

"% JAVA_HOME% \ bin \ java"

weblogic-ejb-jar.xml entity bean cache empty Between the size, if slow Save the space is too small, Some bean stranded In the database, the next You must re-call New loaded from the database startWLS.cmd for high performance

-hotspot -Xmx512m

-Xms512m

/ startWLS.sh

Throughput, the Java heap Most small value and the largest

-classpath% CLASSPATH% -

Parameters in the 2.console console

Value is set to be equal.

Name NativeIOEnable d

SocketReaders

Maximum Open Sockets Stuck Thread MaxTime

Type server

Location mydomain-> Servers-> myserver-> Configu ration-> Tuning-> "Enable Native IO"

indicating the Server using the ground I/O Is provided in the thread of execution Exclusively used Socket Readers percentage of Largest open Socket number Plug threads time.server-> configuration-> tuning Value TRUE. weblogic will Increasing the number of execution threads Stuck Thread Timer Interval Low Memory . ultraOver this time did not return Back to the thread of execution. the Department of System will be considered to be clogged line Journey If weblogic A queue of all All clogging of the thread Then.

GC Threshold Low Memory Granularity Level Low Memory Sample Size Low Memory Time Interval Accept Backlog Amount. Note: The thread of execution Once the number increased. until it reaches the . mesh Before weblogic not go Reduce his increase Some threads later Occurrence of overflow Warning. weblogic Continue to increase the thread of execution The number.

If received in connection connection refused . if Many client connections are Rejected.Far to the ceiling. the garbage back Closing start Available when two detection The memory change more than the one hundred Points than garbage collection Start Taken in a detection Number of injections Detection interval Up in the waiting queue The number of TCP connections Waiting to be processed. The system checks clogged thread The time interval When the available memory is less than the Percentage. while the server The client does not have error display Explanation This value is set too Is low.

Message stating that should improve This value. -> Configuration-> weblogic.. For clothing .Side operation more .. every time increase 25% ThreadCount ExecuteQ ueue console: mydomain-> Servers-> myserver -> Monitoring-> Monitor all Active Queues .Defaul t-> Server initially created Number of execution threads Setting principles: increased machine The maximum concurrent threads Digital processor utilization Maximum.kernel.

QueueLength QueueLengthThr esholdPercent .

ThreadsIncrease ThreadsMaximu m Threads Minimum ThreadPriority The thread should be reduced Thread count. off Compared to client operating Should be increased thread .

when request the number reaches This ratio of the length of the queue Cases when. weblogic Will be issued overflow Flag information If weblogic issue the overflow the flag letter Interest. weblogic will taste Try to increase this number of Thread of execution.Count. in order to solve Deal with conflicts The maximum number of threads of execution Minimum number of threads of execution . enough Over the General Assembly can drop Low system performance Waiting for the queue please Seeking number ideal state Is 0 A percentage of the number. The number of concurrent threads Theoretically equal to the "local A number of the host CPU + Stuck number of threads.

Thread priority Initial Capacity JDBC mydomain-> JDBC Connection Initial database physically connected MaxCapacity Capacity Increment Statement Cache Type Pools-> Configuration-> Connections The few Maximum database physically connected .

LRU Algorithm in a new statement Arrival and will most without Statement is often used to adjust The cache. FIXED count Act as the first-in.The few Each database physical connection Connected to increase the number of prepared statements The cache policy. first-out count Law TestConnections OnReserve .

adjust the development mode with default value products mode TestConnectionsOn Reserve is set to .Statement Cache Size Login Delay And Third.

go through the measured Trial. the even Connection is assigned to the caller Before that. WebLogic will be used depending on the type of environment you specify different mime Recognize the value of the different services. adjust this value Size. The following table lists the default values in the two modes Optimization parameters mydomain> Servers> myserver> Execute . which will be an additional requirement Repeatedly connected with the database Meet The macro statement setting static Cache size by JDBC Even when the connection pool configuration refers Set.false (the default setting). there are conducive Uploader High efficiency of the system Create a database physical connection Then when the delay time You can specify the domain for the development environment or a production environment. If this parameter is set to True (true).

the domain where all services runtime mode: 1.1 Change the run mode 15 connections 25 connections Can be changed according to the following steps to create a domain.kernel. Open with a text editor to change the running host a WebLogic domain runtime mode WL_HOME \ common \ bin \ commEnv.Queue> weblogic.cmd (Windows) or WL_HOME.sh .Default Thread Count Development model 15 threads Product model 25 threads mydomain> JDBC Connection Pools> MyJDBC Connection Pool-> Connections in the Maximum Capacity 3. is \ common \ bin \ the commEnv.

use a text editor to open the domain-name \ StartWebLogic. Restart all the servers. 2. Or inside mydomain-> General Production Mode selected Change the product model and boot. refers in this script.cmd (Windows) or domain-name \ StartWebLogic. For the specified domain change run mode. 3. change the value of the PRODUCTION_MODE Given a value of TRUE. then Kai Automatically when you need to enter a user name and password.2 two modes of different The following table lists the difference between development mode with product the mode several key items: Function name SSL . WL_HOME is the path to install WebLogic.properties (stored username and password) file deleted. 3.sh (UNIX). domain-name domain created directory.(UNIX). If you want the server to run in production mode.

Deploy applications Log File Rotation Execute Queues .

log. .n. you develop applications Running under SSL to protect the environment. the server automatically Rename local log file server-name. the log file will roll Turn once.JDBC Connection Pool Capacity Development model You can use the WebLogic Security service Service provided validation of digital certificates. as long as the log file Reach 500kb. After starting the server. WEBLOGIC instance automatically Ministry The Department and the update is located domain_name / applications Application directory (Domain_name domain name Name). in order to stranded Session. This These certificates. The default execution threads as 15.

You can not use the automatic deployment capabilities Must use the WebLogic console Or WebLogiceblogic The Deployer tools. Product model If you use to verify the digital certificate Books. you will receive a warning message. When the log file reaches 500kb Will roll.The default capacity is 15. .

To verify this. For example.xml own performance package. so you can let the default execution threads very calmly to deal with the application. The default capacity is 25. Set the method of operation of the performance package: By default. if you must use pure Java socket read running on the host. the benchmark that the main performance improvement. the load in the config. you can still configure each server real Appropriate in cases and client socket to read the number of threads. the use of WebLogic "own IO" performance package When you use its own package of performance. to improve the performance of socket communication. Fourth. Performance package optimization platform and multiThread Socket to improve the performance of the server. the local Socket read multithreaded execution queue without Need to borrow the default execute queue thread. check the configuration file . However.Thread of execution of the default 25.

admin. the queue for the management console through Credit. can be selected.Whether the investigation NativeIOEnabled attribute set to "true" (NativeIOEnabled = true). 7. n weblogic. Management Console.HTTP-. click the service you want to configure instance. WebLogic provides two pre-configured queue: n weblogic. it is for management Transportation purposes. if the Enable Native IO check box is not selected. optimize default execute queue thread By default. 4. . a new configuration of WebLogic instance a development model execution queue weblogic. 5 Select the Configuration-> Tuning tab.only only on the management server. nor can configure it. Servers node. Access management console. In addition. expand the left panel to display the domain service. start the management server.kernel. 8.admin.RMI-. you can not configure it. click Apply. you can also verify that the steps are as follows: 1.default It contains 15 threads. V. restart the server. 6.management server and managed server has the queue.

you will need more threads of execution.1 You should change the default number of threads? Adding more threads to the default execute queue does not mean you can handle more work.kernel. so as to increase the value of the properties of the number of threads unnecessary reduce sexual Can. Type is closely related to the value of the property and the application of the number of threads that process work.If you do not configure additional execute queues. the client will spend more time connected. and specify the application to these queues. web applications and RMI object to With default queue weblogic. if your application accesses the database to spend a long time before returning results. Even more threads. Note. and A very short period of time to access the database application return comparison. it will also reduce sexual Can. to achieve optimum performance. If you do not need to use more than 15 threads (default development mode) or 25 threads (product mode by default) Do not change the value of this property. 5. Typically. with less . therefore. For example. comes with the implementation of the package is not in your platform. will need more number of threads. Because threads consume memory. From the latter point of view.default. to complete Customers of a large number of client tasks compared to the application. A high number of execution threads lead to more memory is occupied and the increase in the context of the conversion process. Still limit the ability of the processor. you might need to adjust the default number of threads of execution queue and As a percentage of the thread socket Reading. if your client application compare Small. remote call processing work more so.

If you're with Set additional execute queues and assign applications to specific queues. to monitor the throughput of the queue. you need to get results based on a connection pool. but the work was completed. ) Note: WebLogic management console displays all servers in the execution queue cumulative throughput. The following table lists the adjustment of the threads in a WebLogic domain associated with the number of CPU circumstances. Later introduced. (In some cases Case. . increasing the number of threads will produce enough context conversion program. these cases also assume that WebLogic running at maximum load. when all applications running in the queue at the maximum load Next. In order to get this value.Point the number of threads that may improve performance. Increase the number of threads. so that the throughput of the queue starts to decrease. repeated load test. CPU utilization can reach 100%. and use the default execute queue to meet the request of the thread.2 the need to modify the default number of threads Queue to determine a number of threads in order to perform. 5. Increase the number of threads. If the result should be: The number of threads <number of CPU threads too few. until you reach the best throughput. if: CPU is waiting for work.

The number of threads (large)> CPU excessive number of context conversion process can lead to significant performance degradation.3 steps to modify the default number of threads Management Console to modify the default execute queue thread number as follows: 1. select View Execute Queues. Number of threads (appropriate)> CPU number actually ideal context appropriate number of conversion process and high CPU Utilization. Appropriate to adjust the number of threads and compare performance results. Increase the number of threads. Servers node. if you have four processors. 5. For example. but the CPU is still low use. 3. If the management server is not running. Access Management Console. Name column. Reduce the number of threads. Right-click on the name of the service.The number of threads = number of CPUs theoretically ideal. then just increase has Having come to "jam" the number of threads. they are running at the same time. 4. start first. 2. Display Configuration tab is used to modify the execution queue number. and gridlock thread. just click the default execution queue name. the performance can be enhanced. . will be displayed in the right panel The execution queue table used to modify. When you reduce the number of threads. Note: you can only modify the default execute queue or user-defined execution queue. so you want the thread of execution 4 + number of clogging threads 5. so that it is equal to the number of the CPU. in the pop-up menu. expand the left panel displays the domain service.

JSP.4 assign an application to the execution queue Although you can configure the default execute queue.5 create execution queue An execution queue named set represents a thread of execution.6. Click Apply to save just changes. a thread pointing to one or more Servlet. Restart the server. 5. the optimal number of threads for all WebLogic applications. RMI objects. 8. EJB. 7. so that the entry into force of the new execute queue settings. Fill in the appropriate number of threads. . you can maintain the Permit application the right to occupy a fixed number of threads. but is off The key to the application configuration multiple to execution queues can provide more management control. 5. regardless of WebLogic server much load. Performed by using the multi-queue.

. 3. change the following attributes or accept the default value of the system: The 65536. <Server Name = "examplesServer" ListenPort = "7001" NativeIOEnabled = "true" /> <ExecuteQueue Name = "default" ThreadCount = "15" /> <ExecuteQueue Name = "CriticalAppQueue" ThreadCount = "4" /> . to handle the additional work. Expand the left panel in the Servers node. 5.Execution queue in config. Boot Manager server.. that at the same time sent a request queue length most Large numbers. In the queue configuration tab. 2. select View Execute Queues. </ Server> Another to create a queue via the management console.xml file Described a 4-thread queue named CriticalAppQueue. the configuration steps are as follows: 1. As described in the config. Note . click configure a new execution queue link.536 requests is a big number. access the console.xml file description.. as part of the server element. display the domain you want to configure the service. 65. 4.. Right-click the queue you want to increase service instance. from the pop-up menu. even if the maximum number is reached is also rare. Queue configuration tab. as follows: .

not just queue the length of the problem. WebLogic logs will produce an error message. increased execution queue The number of threads.536 requests indicative of the threads in the queue. in order to deal with some of the latent In the case. should be retained in the 90% or so. this limit is never triggered. Remember. . Normal circumstances. WebLogic will run good status changed to "Warning" And it will not assign additional threads to reduce the amount of load. default queue length limit is 90%. more than 15 threads (default Recognition).because under normal operating conditions. When an overflow occurs. an overflow occurs. Increase the number of threads. the queue length limit percentile Than as an automatic optimization of parameters not necessarily . The actual queue size under the percentage limitations when considered to be normal. and the value of the property according to the number of threads increment (Threads Increase) in order to help reduce the load. you do not have to change the value of this property. The length restrictions percentage (Queue Length Threshold Percent): reach the queue length percentage (1-99) When constitutes produce overflow condition. Overflow occurs above the limit percentage. so there are additional threads can be to deal with some exception request. the real The practice showed that the blockage thread or number of threads in the queue. When you specify 0 (the default).Italy: more than 65.

Restart the server. Do not use both as a percentage of the incremental number of threads and queue length limit since Activity optimization tool. just in the initial parameter identifies the queue name Said. the queue name as wl-dispatch-policy value of the parameter. Such as: <servlet> . to prevent future similar situation.xml initial parameters appear in Servert or JSP. the maximum number of threads to 400. WebLogic in response to frequent overflow.additional threads will be stranded in the implementation of Queue.6 assigned Servlet and JSP to perform queue You can allocate the servlet or JSP to specify the configuration of the execution queue. until the server is restarted. Init-param element in the deployment descriptor file web. creating Built the excessive number of threads. 6. By default. 7. Click Create. Monitor the error log to determine the the overflow causes of so based on the need to re-configure The number of threads. 5. so The context transformation program causes the server to suffer poor performance. to create the queue. To do so usually results will produce more than the normal need also thread assigned execute queue. In order to subWith a queue.

<servlet-name> MainServlet </ servlet-name> <jsp-file> / myapplication / critical.jsp </ jsp-file> <init-param> <param-name> wl-dispatch-policy </ param-name> <param-value> CriticalAppQueue </ param-value> </ Init-param> .

5. However.7 assign EJB and RMI object to the execution queue Order EJB assigned to a specified queue. this setting does not Lost. BEA strongly recommended to make Deployment descriptor elements. such as: java weblogic. Because in this way. RMI object is assigned to a specified queue. you can use the rmic compiler-dispatchPolicy options.</ Servlet> 5.rmic-dispatchPolicy CriticalAppQueue .. you can by using appc the compiler-dispatchPolicy option to set the dispatch strategy. if the EJB recompile during deployment use cases. you can use the dispatch-policy element in weblogic-ejb-jar.xml file.8 assigned to perform queue served Socket read ..

In order to get a better socket performance. The Socket read accounted thread pool percentage (ThreadPoolPercentSocketReader) attributes can be set to read from the socket The maximum percentage of the message thread of execution. 5. 2. you still can configure the appropriate The number of execution threads to improve socket communication performance for each server instance and client machine shoulder socket reader thread Tasks. however. Socket Reader Edit the percentage of Java reader thread.9 socket to read the number of threads operating settings for the server instance 1. Java socket reader thread is based on enforcement Calculated as a percentage of the line number of threads. BEA recommended that you use its own socket read execution tools. it is better than pure Java Implementation tools. Domain Services configuration. and also the need to balance the server handle the actual task execution Thread. The default value is 33. 4. The need to balance the executive Line number of threads to focus on reading the message from the socket. The optimal value of this property is specified in accordance with the needs of the application. Allocation execution threads as socket read server processing speed and the ability to accept customer request. the effective range between 1-99. If. you must read pure Java socket on the host. the domain console. Boot Manager server. 3. Expand the left panel Servers node. 5. Click on the name of the service you want to configure. Select the configuration (Configuration) -> adjust (Tuning) tab. .

10 Socket read client set the number of threads On the client.ThreadPoolSize = value -Dweblogic.11 to optimize the execution queue overflow condition You can configure WEBLOGIC to monitor and ready to respond to a potential overflow. WebLogic that a queue Possible overflow. When this limit is reached. Specified Socket read. you can configure the the socket read number of threads running on the JVM (Java Virtual Machine). 5. Application (Apply) to adjust. then allocate additional threads to handle ultra-negative . Need to define the following parameters by using java command line: -Dweblogic. Once the current queue size to achieve user-defined fast percentage.6. regardless of its occurrence in the default execute queue or The user-defined queue.ThreadPoolPercentSocketReaders = value 5. the server changes it's in good condition "warning".

the server each time the diagnosis a blockage thread. You . this value is the percentage of the queue size. (You can set up section Point Manager (Node Manager) application to automatically shut down and restart the server. 5. These additional threads to restore the queue to the normal operating Size. you can configure the following items: 1.12 to optimize the implementation of the queue monitoring behavior When a thread in the queue to become clogged. entered in a message to the log.admin. excessive The allocation of the number of threads. The maximum number of threads. WebLogic will automatically monitored. the server state into a "crisis".admin. weblogic. In order to automatically monitor and respond to the overflow.Charge of the work. 3. The WebLogic Diagnostic to a blocked thread. the thread largest number used to protect the server in response to the overload. As If a queue. if it is a continuous work within the specified time (no idle).HTTP. so as to restore its size. the server status becomes "warning".RMI or user-defined queue threads Become clogged. added to the queue. the number of threads. depending on the The following situations: n If all threads in the default queue becomes clogged. It can not complete blockage thread The current work or accept new work. in exceptional circumstances. The queue length limit percentages. ) n If weblogic. When the overflow occurs. 2. all threads become clogged server to change the good condition as "warning" or "crisis".

Configure the WebLogic plug the thread monitoring behavior steps: 1. . The default interval is 600 seconds. but you can not change the default behavior. this time WebLogic periodically scan threads to achieve in order to discern whether they are continuously running a thread through a clogging Thread maximum time attribute specifies the length of time. Select the configuration (Configuration) -> adjust (Tuning) tab. WebLogic thread continuously running 600 Seconds after set to clogging. Restart the server. You want a modified to improve clogged line monitoring and the name of the server instance. Gridlock server settings "warning" or "crisis" behavior. 2. Note: Although you can change the the standard WebLogic decision a thread is blocked. Start WebLogic. access the management console. 6. the thread must be continuous operation Line. it is by changing the length of time before clogging the thread was diagnosed and server verification blocking Plug threads frequency. 4. 5. 3. n clogging threads interval (Stuck Thread Timer Interval): Enter the number of seconds.Server threads that can be adjusted to monitor behavior. Application (Apply) set. Modify the following parameters: n clogged the thread maximum time (Stuck Thread Max Time): Enter the number of seconds. the server will diagnose this thread as a blockage. By default.

xml file to accept the cache number (AcceptBacklog) of property is used to set the request WebLogic instance The number of connections refused additional requests to accept a set number of cache. Start WebLogic. 5.13 set HTTP submitted In console in weblgoic the: MyDomain-> Servers-> MyServer-> Protocols-> HTTP has a shut Post Timeout configuration is used to set the time submitted using HTTP. Click on the name of the server instance you want to configure. The default value is 50. AcceptBacklog attribute specifies the number of TCP connection cache in the waiting queue. but the parameters generally use the default values can be Sixth.Timeout time of 5. 2. the fixed queue storing the TCP stack has received but the application has not yet received To the connection request. 3. Expand the left panel Servers node. to optimize the connection cache The elements in the Config. 4. access the console. The console adjustment to accept a the caching number of steps: 1. and the maximum value is determined by the operating system. Acceptance of the need to modify the default the caching number (Accept Backlog): . Select the configuration (Configuration) -> adjust (Tuning) tab.

When a client closes a connection. in order to connect to all customers. . Click Apply (Apply). n If you receive when you access the WebLogic reject the connection (connection refused) "prompt.n during operation. to save the settings. and the server side there is nothing wrong with Erroneous message stating that the value may be too small cache. WebLogic connection pool provides an efficient solution to Solve this problem. Continue to increase to 25% of its value. How to improve the performance of the JDBC connection pool Create a JDBC connection with the DBMS is very slow. If the application requires a database connection and disconnect This created a major cause performance problems. Connection itself is not closed. this prompts until it stops. this The connection is returned to the connection pool for use by other customers. In the connection pool should create connect? Connection pool based on the maximum number and the minimum number of configuration parameters between increase or Reduce connection. When you start WebLogic open a connection pool. So with minimal cost to achieve Connect and disconnect the connection pool. Should be increased to 25% of the value of the default cache. The best performance should be the same as the number of connections and the number of the current client session (Session). if many clients are connected not respond to or denied. 6.

in order to enable the server to start up faster. In this way. default product models The value of the formula is 25. If you adjust the MaxCapacity Value. instead of creating a new database links Connection. If the server can not create the number of connections. 7. During development. all connections will be created. all resources should be done as soon as the request. it should the value of InitialCapacity is set with same value MaxCapacity.Adjustment of 7. must be convinced that InitialCapacity value the same the setting MaxCapacity value.1 JDBC connection pool initial capacity In the connection pool configuration. you can easily set InitialCapacity property value is small. when the load increases. If InitialCapacity less than MaxCapacity value. when the server starts.2 to adjust the maximum capacity of the JDBC connection pool . the connection pool creation will fail. When the server is in the low-load. the in JDBCConnectionPool element InitialCapacity attributes can set the number of connections. Product system. create Physical database connection. the server needs to create additional database even Connection.

In MaxCapacity property JDBCConnectonPool elements set the connection pool contains the largest physical database connection Number. it will connect to force back into the connection pool. Recommended that the number of connections is equal to the number of the current client session (Session). The default maximum capacity equal to the default number of threads: development mode 15. unlimited connection time. Different JDBC drivers and database servers may limit the number of physical connections. set Connection hold time.3 reserved JDBC connection and recycling activities not connected -> JDBC-> Connection Pools-> MyConnection (the name of the connection pool you created) Inactive Connection Timeout -> Configration-> Connections (Advanced Options) of this parameter Number to set the default to 0. connecting more than this The time value. You can set up a time value. the products mode for 25. 7. in the product . Capacity and execute the server-side connection pool The row number of threads that is independent of the user session in progress for more than a thread of execution. set the Java compiler . default is 10s Eight. -> JDBC-> Connection Pools-> MyConnection (the name of the connection pool you created) -> Configration-> Connections (Advanced Options) Connection Reserve Timeout. However.

Start the server. Expand the left panel Servers node. 6.exe 5.1 compiler changed through the console 1. Click Apply. Select the configuration (Configuration) -> conventional (General) edit box compile Java Compiler Is the full path. Such as: c: \ visualcafe31 \ bin \ sj. Such as: BEA_HOME \ jdk141_02 \ jre \ lib \ rt. Restart the server. You can set the java compiler si or jikes instead of javac This can greatly improve performance. Full path by adding (Append) the Classpath box to enter into the JRE rt. 2. 8. show other properties.Compiled JSP Servlet standard Java compiler javac. .jar library. 8. 3. Click on the Advanced Options (Advanced Option) -> Show. Discussed below. 4. Click on the name of the server instance you want to configure.jar 7. access the console. a set of steps and the matters to be considered.

3 compile EJB container classes EJB2.1 container classes to compile use Weblogic.8. EJB javac compiler. If you compile Jar files deployed EJB container You must use weblogic.xml file compiler n use compileCommand parameter to specify the Java compiler.2 the Weblogic.0 and 1. JSP precompiled start WebLogic. By default. In order to get with good Performance. <jsp-descriptor> <jsp-param> <param-name> compileCommand </ param-name> <param-value> javac </ param-value> </ Jsp-param> </ Jsp-descriptor> 8. n use procompile parameter configured WebLogic. specify a different compiler (such as Symantec's sj) using the-compiler flag .appc the function.appc to generate container classes.

add more memory.8.4 compiler in UNIX environment Compile JSP files on a UNIX machine. IX WebLogic cluster to improve performance WebLogic cluster is a group of WebLogic instances together with anti-overload and its own copy of the function to use a Domain for all customer support scalable high availability run. concurrent transactions can be processed in a specific unit of time.Cluster Scalability is a system to increase the ability of one or more components as a system resource. these components enable concurrent Households are supported. n limited file description file. Cluster for the client is a single server.io. 9. if you receive the following error message: failed: java.IOException: Not enough space Try some or all of the following solution: n If you have only 256MB of memory.1 Scalability and high availability . . such as: set rlim_fd_max = 4096 set rlim_fd_cur = 1024 n Start the JVM-native flag to use its own thread. but actually A group of servers to improve reliability and scalability. Typically.

WebLogic dynamic The state increased cluster. adding additional servers to the cluster should provide linear Scalability. simply add a WebLogic instance to your cluster . Scalability extends the capacity of the intermediate layer. and is transparent to application developers 's. it can add more resources to improve performance. more than a single WebLogic server or single computer can handle 's. before you moved to a clustered environment. the other can take over the running. the performance should be considered to ask . If a server stops running. 9. In order to increase the WebLogic Processing load.without changing the application.2 multi-server instances running on multi-CPU machines.Assumed that the application is well-designed. Cluster to improve Two key benefits: scalability and availability. Benchmarks and initial configuration of the test run. The only restriction is that all WebLogic cluster members must use IP multicast communication. Cluster A server can provide the same service. the application isolation in a separate Tested on the server. WebLogic cluster to ensure high availability through redundancy of multiple servers to reduce the customer's request failed. This functions as a client Increased availability. in order to increase the processing capacity. WebLogic cluster to J2EE scalability and high availability. Warning: If you want to solve the neck bottles of applications and environments. which is unmatched by a single server.

installing a faster network interface card (NIC) can To provide performance. multi-processor servers. For CPU-bound applications. Should consider increasing disk speed or single disk. more CPU is in idle Position. such as Sun's Sun Enterprise 10000. remember the product mode. Thoroughly test your application and determine the best server and the CPU ratio is determined as follows: irements if you find Web applications are mainly affected by the network I / O limitations in the number on the CPU before. there should be some idle CPU cycles to perform administrative tasks. re that the Web application is subject to the CUP restrictions.Title On multi-processor machines. rather than by the network Or disk I / O limitations. rather than adding additional CPUs. configured for a WebLogic instance A CUP). you must consider to clustered WebLogic number of instances should be proportional to the number of the CPU. and then increase the CPU specific gravity (eg. large-scale. Because the WebLogic There is no built-in limit of the number of server instances in a cluster. because waiting to read socket. each CPU on the initial performance testing on a WebLogic instance. but BEA ideal found the WebLogic instances with CPU . If the actual network I / O limitations. has as a very large clusters or multiple clusters host of potential. Web application processing needs changing. If the CPU Utilization is the same or close to 100%. consider Test network throughput.

The ratio is 1:2. For example. HTTP. It includes the following information: e longest time. EJB. 11. monitor WebLogic domain Health status and performance tools for monitoring WebLogic domain management console. 10. according to the number of requests waiting in the queue to measure. such as servers. JNDI. weblogic cluster . security. you can observe The WebLogic resource status and statistical information. Through the console. the Server -> Monitoring -> Performance for the current server instance and wait for and shipped The request of the state of the line performance reference. CORBA Connection pools. JTA subsystem. JDBC and JMS.

1 Introduction Managed Server icon .10.

A domain can contain more than one cluster. By Administrator Server is configured to WebLogic Server instances management logic unit. cluster . A domain that contains one or more WebLogic Server instances.xml. non-clustered instance. or a combination of clustered and non-clustered instance. Group Centralized server instance must reside in the same domain. A domain of one or more . Managed Server. 2. (But must be created in another domain Similar connection pool). Similarly.Explanation of terms: 1.split "into multiple domains. if in one domain to create a JDBC connection slow Buffer pool. Domain is the basic administrative unit of the WebLogic Server instance. Management Server is used to deploy to run a variety of applications. this unit is a collection of all resources. these instances can be group Set of instances. can not be used in another domain server instance or cluster. Configured resource or subsystem can not be shared between domains. Central configuration file Pieces called config. For example.

Server management server and management server is a many-to-one. management server and the domain is a one-to-one. management server and deploy applications to the management server. A Domain and only one management server. and managed by management Server unified management 3. the domain consists of a management server and managed server. you must first start the management server. In each domain. on behalf of a running WebLogic application server is the machine Including its IP address and other information. 5 agent . In this way. management server Is not on the deployment of the application (the application should be deployed to the managed server: Managed Server). each cluster in the domain has the same management server 4. there is only one WebLogic Server instance acts as a management server: This server instance configuration. the management server configuration control center for the entire domain. If a domain contains more Clusters. At the start of this The domain managed server. Management Server is used to manage the configuration domain center point. while Is used to unified management. configuration. A domain can have An active management server. A domain may include multiple machines. monitoring.Stage management server in a production environment. Machine. Administrator Server. will be ordered from the management The server configuration information. the managed server startup. Each management server only manage a domain. management and monitoring of domain the Other managed server instances and resources. in general. the machine is a physical concept.

The main the rver. Forwards the request to a different management server up. a 10. The software Web server. Cluster diagram To weblogic as agent to configure the cluster to better improve performance. Generally hard Some powerful.2. you can use the hardware as their agent Agent diagram: . pieces of agent performance and stability better than software agents.g.

Physical diagram: .

Schematic: management server reads the configuration information to manage the service instances in the cluster .

.

PORT) Machine name Machine type Configuration .3 Create Cluster Deployment table (IP.10.

8.168.49:7001 192.8.49:7009 192.Role Machine49 Window XP Machine49 Window XP Machine49 Window XP Machine49 Window XP Machine48 Window XP 192.168.168.168.49:7000 .8.49:7008 192.8.

168.8.192.3.1 create a management server (Manager Server) .48:7001 Administrator Server Managed Server Managed Server Proxy Server Managed Server 10.