Instance pooling allows component instances to be reused, avoiding the performance overhead of creating new instances for each client session. Each component that runs in EAServer is assigned to an instance pool, which is specified by the com.sybase.jaguar.component.instancePool property.
These instance pools are preconfigured:
Name |
Description |
Maximum number of instances |
|---|---|---|
SystemPool |
The default for components whose com.sybase.jaguar.component.bind.thread property is set to false. |
infinite, denoted by -1 |
BindThread |
The default for components whose com.sybase.jaguar.component.bind.thread property is set to true. |
512 |
You can create new instance pools using EAServer Manager.
By default, the maximum number of instances is set to 512. Sybase
recommends that you do not create an instance pool with the maximum
number of instances set to -1 (infinite).
If you need an instance pool with an unlimited number of instances, use
the preconfigured SystemPool.
com.sybase.jaguar.component.instancePool, com.sybase.jaguar.component.bind.thread
Enables and disables logging of activity for this pool.
Specify true to enable
debugging. The default of false disables
debugging.
Debug information is written to the server log file. You must refresh the pool or restart the server for the change to take effect.
Specifies the maximum number of instances that can be placed in the pool.
A decimal integer. The default is 512.
The name of the instance pool.
Enter the pool name.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
