database pool problem

[Blake Day <bl...@charter.net>]

I am apparently having a problem where multiple database connection pools
are being created with the same name.  My logs have the following lines:
[Tue Apr 16 19:12:25 EDT 2002] -- INFO -- FROM logger:database: default (in
+ out = total): 0 + 0 = 0
[Tue Apr 16 19:12:38 EDT 2002] -- INFO -- FROM logger:database: default (in
+ out = total): 2 + 0 = 2

I definitely know that there are two separate pools because they have
differing amounts of available connections, and I have the following setting
in TR.props: database.logInterval = 120000.  Could anyone shed some light on
me as to why this might be occuring?

Thanks,
Michael Blake Day
Artistry Studios - e-commerce design, implementation and hosting
email: mday@artistrystudios.net



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Fulcrum as Entrance for Torque

[Daniel Rall <dl...@finemaltcoding.com>]

"Eric Pugh" <ep...@upstate.com> writes:

> Hi all,
>
> I want to use Torque in a non Turbine Servlet.  Looking into Torque, it
> seems to have it's own connection pooling system seperate from the Pool
> Service.  Is that correct, Torque doesn't need anything else to do
> connection pooling?

John can answer definitely here.

> Secondly, if I use Fulcrum to run my other services, then to get to Torque,
> I would want to use the TurbineDatabaseService?  Or should I just use Torque
> directly?  What does the TurbineDatabaseService give me that others don't
> have...?

You should use Torque directly -- the TurbineDatabaseService is
deprecated.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Fulcrum as Entrance for Torque

[John McNally <jm...@collab.net>]

Eric Pugh wrote:
> 
> Hi all,
> 
> I want to use Torque in a non Turbine Servlet.  Looking into Torque, it
> seems to have it's own connection pooling system seperate from the Pool
> Service.  Is that correct, Torque doesn't need anything else to do
> connection pooling?

Torque has its own internal connection pooling.  I plan to replace this
with pluggable connection pools after the 3.0 release.  But currently
nothing else is required or possible.

> 
> Secondly, if I use Fulcrum to run my other services, then to get to Torque,
> I would want to use the TurbineDatabaseService?  Or should I just use Torque
> directly?  What does the TurbineDatabaseService give me that others don't
> have...?

Use torque directly.

john mcnally

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Fulcrum as Entrance for Torque

[Eric Pugh <ep...@upstate.com>]

Hi all,

I want to use Torque in a non Turbine Servlet.  Looking into Torque, it
seems to have it's own connection pooling system seperate from the Pool
Service.  Is that correct, Torque doesn't need anything else to do
connection pooling?

Secondly, if I use Fulcrum to run my other services, then to get to Torque,
I would want to use the TurbineDatabaseService?  Or should I just use Torque
directly?  What does the TurbineDatabaseService give me that others don't
have...?

Eric


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>