Re: JNDI datasource question

[Andre Van Klaveren]

The initialSize parameter is specific to DBCP.  I believe the
interface in Tomcat only has fields that are common among pooling
implementations (Commons Pool).  You'll have to manually edit the pool
configuration.

An idle connection is one that is in the pool that is not currently
being used by the application.



On 3/8/06, John Cherouvim <[EMAIL PROTECTED]> wrote:
> Thanks for your detailed explanation.
>
> In tomcat 5.0.28 I cannot find initialSize parameter. Is it something
> that was added later?
> And by idle connection, do we mean the connection that was closed in a
> finally block (returned to the pool)?
>
> John
>
>
> Tim Lucia wrote:
>
> >The number of connections is affected by three parameters:
> >
> >initialSize="10"
> >maxIdle="20"
> >maxActive="50"
> >also:
> >maxWait="5000"
> >
> >initialSize="10" says make 10 connections at startup.  SHOW PROCESSLIST will
> >reveal 10 processes in this case.
> >
> >maxIdle="20" says close any idle connections in excess of 20.  SHOW
> >PROCESSLIST will reveal 20 or fewer idle processes in this case.
> >
> >maxActive="50" says to cut off incoming connections at 50.  Any connection
> >attempt beyond 50 will wait for maxWait="5000" (5 seconds) for a free
> >connection before giving up.
> >
> >Tim
> >
> >
> >-Original Message-
> >From: John Cherouvim [mailto:[EMAIL PROTECTED]
> >Sent: Wednesday, March 08, 2006 7:17 AM
> >To: users@tomcat.apache.org
> >Subject: JNDI datasource question
> >
> >Hello
> >
> >I have a JNDI Datasource pooling 10 connections on a database of my
> >mysql server. Why does it use only one process on the mysql server? I
> >have set max active to 10 connections and I am accessing the application
> >from different IPs at the same time. I then perform a SHOW PROCESSLIST
> >on mysql and I only see one process related to the datasource. On the
> >other hand, applications which access the database directly or using
> >programmatic connection polling use many processes as expected.
> >
> >Could someone explain me if this is the case and why does it happen?
> >
> >Thanks
> >
> >-
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >-
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Virtually,
Andre Van Klaveren
Architect III, SCP
Global Public Sector
Unisys Corporation

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat Datasource , can we define them in war file (whithout accessing to Admin console)?

[Andre Van Klaveren]

Like Bruce said, you can define a DataSource as part of your
application's context.  It's the same format as the context definition
in server.xml except it's deployed with your application as an XML
file (context.xml) inside the META-INF directory of the WAR.

Here's a link to explain how to do it:
http://tomcat.apache.org/tomcat-5.0-doc/jndi-datasource-examples-howto.html

They don't go into using context.xml but the same instructions can be
applied to using the context.xml.



On 12/26/05, Legolas Woodland <[EMAIL PROTECTED]> wrote:
> Hi
> Thank you for reading my post.
> Is it possible to make a data-source without admin console ?
> I mean by defining the data-source in web.xml or in Context.xml (i think
> i read somewhere that we could put context.xml into meta-inf folder and
> it will act like Context definition in admin console).
>
> is it mandatory that Tomcat shared library folder contain my database
> jdbc driver to have data-source ?
> I mean can we bundle , our JDBC driver inside war file and define the
> data-source in war file too ?
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Virtually,
Andre Van Klaveren
Architect III, SCP
Global Public Sector
Unisys Corporation

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]