In addition, the creation of too many threads can result in out of memory errors or thrashing. For example, it can show the time of day and the day of the week in which you usually reach peak thread count. This measure is also useful for determining usage trends. Indicates the number of threads in this pool that are currently processing requests.Ī high value for this measure is indicative of a high load on this applications deployed on the GlassFish application server. Indicates the current number of threads in this pool. Indicates the number of core threads currently in this pool. Measurements made by the test Measurement If there is no response from the server beyond the configured duration, the test will timeout. Specify the duration (in seconds) for which this test should wait for a response from the GlassFish Enterprise server. Specify the package name of this JMX Provider here. This test uses a JMX Provider to access the MBean attributes of the GlassFish Enterprise server and collect metrics. If you have registered the JMX connector in the RMI registry using a different lookup name, then you can change this default value to reflect the same. The JNDIName is a lookup name for connecting to the JMX connector. Confirm the JMX Password you specify by retyping that password in the Confirm Password text box. The user name specified against the auth-realm-name parameter in the code block above can be configured as the JMX User, and the Password of that user can be specified against JMX Password. To know the name of such a user, open the domain.xml file in the \Sun\AppServer\domains\domain1\config directory and look for the code block shown below: However, if you prefer not to expose the credentials of an administrator owing to security considerations, you can use the credentials of any other user with access rights to JMX. You can hence configure the JMX User and JMX Password parameters with the credentials of the administrator. Typically, the GlassFish administrator has the right to use JMX. To enable the eG agent to use JMX therefore, you need to configure the agent with the credentials of a user who is authorized to use JMX. The port number specified against the Port parameter in the code block above refers to the JMX Remote Port.īy default, the JMX connector on the GlassFish Enterprise Server requires authentication. To know the port at which JMX listens, open the domain.xml file in the \Sun\AppServer\domains\domain1\config directory and look for the code block shown below: If JMX listens on a different port in your environment, then specify the same here. Therefore, type 8686 as the JMX Remote Port. The JMX connector listens on port 8686 by default. By default, JMX support is enabled for the JRE used by the GlassFish Enterprise Server. To collect metrics from a GlassFish Enterprise server, the eG agent monitoring that server should be configured to use JMX to connect to the JRE used by the server and pull out the metrics of interest. The port number at which the specified host listens The host for which the test is to be configured. Configurable parameters for the test Parameters Outputs of the test : One set of results for each thread pool configured on the GlassFish Enterprise server being monitored. The GlassFish Thread Pool test provides administrators with the load and thread pool usage insights they require to take these crucial sizing decisions.Īgent deploying the test : An internal/remote agent The thread executes the client's requests and returns results.Īdministrators will have to continuously observe the request load on their applications, periodically check how the thread pool services these requests, and accordingly decide whether/not to resize the thread pool commensurate to the current and anticipated load. When GlassFish Server receives a request, it assigns the request to a free thread from the thread pool. Request threads handle user requests for application components. One thread pool can serve multiple connector modules and enterprise beans. It is possible to assign specific thread pools to connector modules, to network listeners, or to the Object Request Broker (ORB). To help performance, GlassFish Server maintains one or more thread pools. The Virtual Machine for the Java platform (Java Virtual Machine) or JVM machine) can support many threads of execution simultaneously.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |