The connections are pooled and reused. A new one is created only when
needed, and only when all the previously created connections are in use for
simultaneously running queries. When a new one is created, you'll see
something like this in the log:
[QueryLogger] () Opening connection: jdbc:oracle:oci8..atabasename
Login: accountname
Password: *******
It would be quite unlikely that more than a small fraction of the user
sessions will be running queries at the same time, unless your application
is doing something unusual like running queries continuously in the
background. We've been running an internal application with a load of about
20 users for over a year, and we've never needed more than 2 connections.
----- Original Message -----
From: <tnaki..ofthome.net>
To: <cayenne-use..bjectstyle.org>
Sent: Tuesday, April 05, 2005 1:57 PM
Subject: Re: cannot obtain connection
> Andrus Adamchik wrote:
>
> >Hi Tomislav,
> >
> >Looks like your application load requires more than one connection in the
> >pool ... or maybe you just have long running queries, so timeouts can
> >occur even on light loads.
> >
> >Just change the maximum number of connections for the DataNode to a
higher
> >value in this dialog:
> >
> >http://objectstyle.org/cayenne/images/modelerguide/datanode.jpg
> >
> Thanks, Andrus. Still, do you think a much bigger default might be in
order?
> What would happen if I set max=256? Would I have 256 connection objects
> or would they be created on demand, when all other connection objects in
> a connection pool are in use? Questions, questions, questions, I know. :)
>
> Regards,
> Tomislav
This archive was generated by hypermail 2.0.0 : Tue Apr 05 2005 - 14:40:11 EDT
