You can view diagnostic information for troubleshooting purposes in NexJ System Admin Console on the current state of a dynamic resource pool. You can also view diagnostic information in application logs.
The following relevant information displays for the Pool Manager component:
The number of deactivation locks held by the model. The pool manager shuts down after the model releases all the locks.
Indicates whether managed resources are available. Managed resources are available when the pool manager has successful started at least one of the dynamic resource pools that it manages.
Indicates whether the pool is running consumers. The pool is running consumers when the pool manager has started thread pools for the channels configured with "receive" enabled.
Indicates whether the pool manager is started.
The following relevant information displays for Dynamic Pools:
The amount of time in milliseconds within which the pool must return a resource. If the time is exceeded, an exception occurs.
The time in milliseconds after which a resource not in use by the system is deallocated, or removed from memory, by the pool.
The maximum number of resources the pool can allocate.
The number of resources that are "in use" by the resource pool. For example, a resource is in use when the model has requested a resource but has not yet returned it to the pool.
The number of resources that are considered "unused" by the resource pool. For example, an unused resource has been returned to the pool by the model.
Active resources contain the following information:
The amount of time in milliseconds since the model used the resource. For example, for a database connection, the amount of time since the model issued a command to the database using this connection.
The number of active locks held by the model. The model tracking resources as "in use" that it must later return it to the pool. The refCount for an active resource should always be greater than 0.
The allocation stack frame for the resource. This includes the threadName, schemeStack, and systemStack. The threadName is the name of the thread on which the resource was allocated. The schemeStack and systemStack display the model stack trace and JVM stack trace, respectively.
Idle resources contain the following information:
The amount of time in milliseconds since the model returned the resource to the pool.
The number of active locks held by the model. The refCount for an idle resource should always be 0.
The following example show sample diagnostic information that displays in NexJ System Admin Console: