If you change the attributes of the connectionManager element while a server is running, the updates to different attributes are applied at different times and in different ways.
You configure a connection pool by specifying the attributes of the connectionManager element in the server.xml configuration file. If you change these attributes for a running server, the updates are applied at different times and in different ways, depending on which attribute is changed. The following table describes, for each attribute of the connectionManager element, how a configuration change is applied at run time.
Attribute name | How the configuration update is applied |
---|---|
agedTimeout | The update is effective immediately. |
connectionTimeout | The update is effective immediately. |
maxIdleTime | The update is effective immediately. |
maxNumberOfMCsAllowableInThread | The update is effective immediately. |
maxPoolSize | The update is effective immediately. |
minPoolSize | The update is effective immediately. |
numConnectionsPerThreadLocal | The update is effective immediately. |
reapTime | The update is effective immediately. |
purgePolicy | The update is effective immediately. |
Because updates to the connection manager are effective immediately, errors might occur if you make changes with active connections; including the potential risks for the connections to be ended prematurely.