A client/server Derby will soon be used in a university course to teach
students SQL etc.
Previous experience has revealed that students who are not familiar with
Java programming and JDBC/DBs tend to open a new connection for every
Statement. There will be peaks with a few hundred concurrent users. Is
there any way of restricting the number of connections a user can open
in Derby? I want the faulty student applications to get exceptions
rather than ruining the user experience for the "nice" users.
--
Jørgen Løland
- Restricting number of connections from a single user Jørgen Løland
-
