M,
1. Do you have any recommendations on the c3p0 config parameters?
2. I'm assuming those parameters (${database.pool.minSize}, etc) will go into
cas.properties?
3. The documentation doesn't specify where we need to put this prop:
<prop key="hibernate.dialect">org.hibernate.dialect.MySQLInnoDBDialect</prop>.
It looks like it will replace
<prop key="hibernate.dialect">org.hibernate.dialect.MySQLDialect</prop>
in deployerConfigContext for the jpaProperties. Please confirm that this is
correct.
Thank you very much in advance!
Tobias
----- Original Message -----
From: "Marvin Addison" <marvin.addi...@gmail.com>
To: cas-user@lists.jasig.org
Sent: Monday, October 17, 2011 11:24:24 AM
Subject: Re: [cas-user] JpaTicketRegistery & DB Connection Pooling
> Using CAS 3.4.10 with the JPA Ticket Registry, is it still recommended to add
> c3p0 DB connection pooling (per this article:
> https://wiki.jasig.org/display/CASUM/JpaTicketRegistry)
Use of c3p0 in that document was entirely arbitrary. You should use
the pooling library that you're familiar with. I used c3p0 in that
example because we have extensive experience with it and therefore had
a sound configuration sample at hand. By all means use dbcp if you
want. In any case you should use connection pooling for production
deployments.
> or is DB connection pooling already included in that (3.4.10) release?
Connection pooling is not explicitly included in any CAS release since
it's a deployment concern.
M
--
You are currently subscribed to cas-user@lists.jasig.org as:
tquos...@kennesaw.edu
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
--
You are currently subscribed to cas-user@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
