Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <E8F8A1FE7C1DD94D9015256F9624E0468CF46403@sm-ex-01-vm.guidewire.com>
References: <fce81908e6c44eed8febd58241cafeaf@KIM01.tis.local>
	<E8F8A1FE7C1DD94D9015256F9624E0468CF46403@sm-ex-01-vm.guidewire.com>
Date: Wed, 3 Dec 2014 11:47:05 -0700
Message-ID: 
 <CAAjH2Utn2KL_nzQRCy=0MPXmTQVfLwLidir_5S9w6O6Z7MELmQ@mail.gmail.com>
Subject: Re: Tomcat JDBC connection pool: Using initSql together with
 validatorClassName
From: Filip Hanik <filip@hanik.com>
To: Tomcat Users List <users@tomcat.apache.org>
Cc: Iris Hupkens <I.Hupkens@topdesk.com>
Content-Type: multipart/alternative; boundary=047d7b5d86a5239b56050954458a

--047d7b5d86a5239b56050954458a
Content-Type: text/plain; charset=UTF-8

You should be able to run init SQL commands yourself in your custom
validator

https://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/tomcat/jdbc/pool/Validator.html


On Wed, Dec 3, 2014 at 11:42 AM, Wes Clark <wclark@guidewire.com> wrote:

> These actions seems to incorrectly conflated in the code.  I'd also like
> to do the same thing, so if you get it working, keep me posted.
>
> -----Original Message-----
> From: Iris Hupkens [mailto:I.Hupkens@topdesk.com]
> Sent: Wednesday, December 03, 2014 5:14 AM
> To: 'users@tomcat.apache.org'
> Subject: Tomcat JDBC connection pool: Using initSql together with
> validatorClassName
>
> Hello,
>
> I am using the Tomcat JDBC connection pool (version 7.0.55) as a
> stand-alone library. The connection pool is configured with a custom
> validator class in order to use the JDBC4 isValid method for connection
> validation.  I would also like to use initSql to perform some preparation
> on all connections created in the pool (such as setting sorting to case
> insensitive under Oracle). However, it appears that initSql does not work
> in combination with a validator class.
>
> Looking at the source, the code that executes the initSql statement is
> skipped if a validator class is configured. The documentation for initSql
> states that it is executed in place of the validation query when
> connections are initialized, but the method which does the validation first
> checks if there is a validator class that should be used instead, and then
> returns immediately.
>
> I was wondering: is this a bug, or is it intentionally not possible? If
> it's intentional, is there perhaps a different way to configure the Tomcat
> connection pool to use both a custom validator class and execute initial
> SQL statements when first creating a connection?
>
> Kind regards,
> Iris Hupkens
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

--047d7b5d86a5239b56050954458a--