What controls the number of database connections made between the Identity
Manager product and how would one go about "limiting" them?
ANSWER:
By default, the number of concurrent JDBC connections is unlimited. The Identity
Manager repository will request as many connections as it needs to serve each
concurrent repository request.
Database connections can be controlled by these means:
- Identity Manager (not limited by default)
- Application server datasource configuration (If you are using a datasource).
- Database itself.
To limit the number of connections in the Identity Manager product, you could
set the maxConcurrentConnections property in the RepositoryConfiguration object.
Setting this value to a positive integer limits the number of concurrent
connections. The Repository will never exceed a configured limit N. Instead,
every thread N+1 will block *prior* to obtaining JDBC connection until one of
the previously outstanding connections is closed.
By default, this property is set to 0, which means "do not limit" the number of
connections.
Note that when a resource adapter makes connections to the same back-end database
instance that the repository uses, these adapter connections are not affected by
RepositoryConfiguration settings.
No comments:
Post a Comment