db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernt M. Johnsen" <Bernt.John...@Sun.COM>
Subject Re: Restricting number of connections from a single user
Date Tue, 13 Nov 2007 14:04:13 GMT
Well, not quite what you asked for, since this is for the server as a
whole, not per "user". 

>>>>>>>>>>>> Bernt M. Johnsen wrote (2007-11-13 14:58:41):
> Hi,
> 
> >>>>>>>>>>>> Jørgen Løland wrote (2007-11-13 14:35:27):
> > 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.
> 
> You may set tha maximum numbers of threads. This will restrict the
> number of *running* connections. When you exceed this number,
> subsequent connections will wait in a queue until a thread is
> available. 
> 
> 
> > 
> > -- 
> > Jørgen Løland



Mime
View raw message