cayenne-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Gentry <mgen...@masslight.net>
Subject Re: Connection Pool
Date Fri, 16 Apr 2010 12:57:53 GMT
Hi Joe,

I've deployed a long-running (up 24x7) internal application before
that had a max of 2 DB connections using the built-in Cayenne
connection pooling mechanism and never had any issues with running out
of connections.  The only reason I even used 2 was I had long-running
(several minutes) queries in a background thread that might block the
interactive portion and make the user wait during those periods, so I
basically allocated one to the background thread and one to the user
threads.

I don't know of a way to report open connections off the top of my
head, but I could look into that if needed.

mrg


On Thu, Apr 15, 2010 at 8:57 AM, Joe Baldwin <jfbaldwin@earthlink.net> wrote:
> Hi Michael,
>
> min = 1
> max = 10 (we changed this to 20 but then got the same error)
>
> To my knowledge there are no long running transactions.  Most are product list fetches
which should take less than a second each.  There is some content editing right now, so there
are about 50-100 updates per day, (which again should take no more than 1 sec per transaction)
>
> I have been searching through my code, but can't find anything that seems out of the
ordinary.
>
> Is there an object available to me that will report open connections?
>
> Thanks,
> Joe
>
>
> On Apr 15, 2010, at 8:18 AM, Michael Gentry wrote:
>
>> The connections are stored and reused.  What is your min/max setting?
>> Do you have any long-running transactions?
>>
>>
>> On Wed, Apr 14, 2010 at 11:34 PM, Joe Baldwin <jfbaldwin@earthlink.net> wrote:
>>> Why would the DataContext be running out of connections in a web app with only
a small amount of traffic?
>>>
>>> (I thought that a group of connections were stored (base on the modeler specification),
and then reused for each transaction.)
>>>
>>> Joe
>>>
>>>
>
>

Mime
View raw message