8
More or less, it is possible to configure in the database a session limit per user not a connection pool. For this we can create and configure profiles, thanks to this feature we can control things like:
- Total sessions per user
- CPU consumption per user
- Maximum connection time
Many other possibilities are possible thanks to user profiles. See the following link for more information on the subject: http://docs.oracle.com/cd/E11882_01/server.112/e41084/statements_6010.htm#SQLRF01310
To change a user’s profile see: https://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_4003.htm
Now I’ll explain why I said "sort of". The connection pool is usually configured in your application, for example, if you have a Java application running over a Tomcat the connection pool can be managed by the Java application, or more commonly by Tomcat. Already on the database side you control features like:
- Connection limit per user
- Maximum downtime before adjourn
- Maximum session time etc...
Have you looked at the reference documentation? http://docs.oracle.com/cd/E11882_01/java.112/e12265/manage.htm#BABICIII
– Giuliana Bezerra
@Giulianabezerra, I checked yes, but if you notice, there are only settings to change the default connection pool, I can’t find anything referring to create (A pool for each bank user).
– Harisson Ford A. R.
Ah, I saw here, in fact it’s all on top of a single pool manager. Quite interesting your question, I’ll take a look here to see if I find something.
– Giuliana Bezerra