Details
-
Bug
-
Resolution: Fixed
-
Medium
-
5.0
-
None
-
5
-
Description
We are not setting maxIdle in the server.xml for the standalone environment - this means the connection pool defaults to 8 maximum idle connections, and it nearly always results in closed connections being removed from the pool. Experimentation has confirmed that setting it to -1 gives better pooling performance.
Attachments
Issue Links
- derived from
-
JRASERVER-27866 Default connection pool size is inconsistent.
- Closed
- details
-
JRASERVER-27736 Decouple JdbcDatasource from ConnectionPoolInfo's internal data
- Closed
-
JRASERVER-27739 Add the new fields to the Configurator's datamodel (Settings, SettingsLoader)
- Closed
-
JRASERVER-27764 Add the new fields to the DatabaseConfigHandler and SystemTenantProvider
- Closed
-
JRASERVER-27737 Add new fields to ConnectionPoolInfo and DatabaseConfigHandler's persistence of it.
- Closed
-
JRASERVER-27740 Add new fields to the console rendering of the configurator
- Closed
-
JRASERVER-27741 Add new fields to the swing rendering of the configurator
- Closed
-
JRASERVER-27784 Refactor console and swing impls of configurator to share state implementations
- Closed
- is incorporated by
-
JRASERVER-27880 Analyse JIRA performances and Identify bottlenecks
- Closed
- is related to
-
JRADEV-10747 Loading...
- mentioned in
-
Wiki Page Loading...