1. Overview of GlassFish Server Administration
Default Settings and Locations
Instructions for Administering GlassFish Server
4. Administering the Virtual Machine for the Java Platform
6. Administering Web Applications
7. Administering the Logging Service
8. Administering the Monitoring Service
9. Writing and Running JavaScript Clients to Monitor GlassFish Server
10. Administering Life Cycle Modules
11. Extending and Updating GlassFish Server
Part II Resources and Services Administration
12. Administering Database Connectivity
13. Administering EIS Connectivity
14. Administering Internet Connectivity
15. Administering the Object Request Broker (ORB)
16. Administering the JavaMail Service
17. Administering the Java Message Service (JMS)
18. Administering the Java Naming and Directory Interface (JNDI) Service
19. Administering Transactions
You can specify the minimum and maximum number of threads that are reserved for requests from applications. The thread pool is dynamically adjusted between these two values.
The following topics are addressed here:
Use the create-threadpool subcommand in remote mode to create a thread pool.
The minimum thread pool size that is specified signals the server to allocate at least that many threads in reserve for application requests. That number is increased up to the maximum thread pool size that is specified. Increasing the number of threads available to a process allows the process to respond to more application requests simultaneously.
If one resource adapter or application occupies all the GlassFish Server threads, thread starvation might occur. You can avoid this by dividing the GlassFish Server threads into different thread pools.
Remote subcommands require a running server.
Information about options for the subcommand is included in this help page.
See To Restart a Domain.
Note - Restart is not necessary for thread pools used by the web container.
Example 5-1 Creating a Thread Pool
This example creates threadpool-l.
asadmin> create-threadpool --maxthreadpoolsize 100 --minthreadpoolsize 20 --idletimeout 2 --workqueues 100 threadpool-1 Command create-threadpool executed successfully
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help create-threadpool at the command line.
Use the list-threadpools subcommand in remote mode to list the existing thread pools.
Remote subcommands require a running server.
Example 5-2 Listing Thread Pools
This example lists the existing thread pools.
asadmin> list-threadpools threadpool-1 Command list-threadpools executed successfully
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help list-threadpools at the command line.
Use the set subcommand to update the values for a specified thread pool.
The thread pool is identified by its dotted name.
See To Restart a Domain.
Note - Restart is not necessary for thread pools used by the web container.
Example 5-3 Updating a Thread Pool
This example sets the max-thread-pool-size from its previous value to 8.
asadmin> set server.thread-pools.thread-pool.http-thread-pool.max-thread-pool-size=8 Command set executed successfully
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help set at the command line.
Use the delete-threadpool subcommand in remote mode to delete an existing thread pool. Deleting a thread pool will fail if that pool is referenced by a network listener.
Remote subcommands require a running server.
See To Restart a Domain.
Note - Restart is not necessary for thread pools used by the web container.
Example 5-4 Deleting a Thread Pool
This example deletes threadpool-1.
asadmin> delete-threadpool threadpool-1 Command delete-threadpool executed successfully
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help delete-threadpool at the command line.