On Thu, May 17, 2012 at 10:12 AM, Laird Nelson <ljnelson_at_gmail.com> wrote:
> On Wed, May 16, 2012 at 1:59 PM, Jagadish Prasath Ramu <
> jagadish.ramu_at_oracle.com> wrote:
>
>> Yes, the additional properties in the pool are meant for setters of the
>> bean (DataSource) attribute.
>>
>
> OK; thank you. Since I am not seeing the results of such a call in the
> data source, I now need to debug it.
>
> I will start with logging. What logger can I use to see that this setter
> call is being made by the Glassfish connection pool configuration machinery?
>
Hi, Jagadish (and others); we're running into this problem again. This
time, the Informix ConnectionPoolDataSource implementation (bane of my
existence, O for the days when I can get off this database) does not behave
as though it is having its #setIfxIFX_ISOLATION_LEVEL(String) method called
when I specify an additional connection pool property of
"ifxIFX_ISOLATION_LEVEL". My understanding was that specifying a property
like this on the Additional Properties tab of the connection pool setup
screen would turn this into a Java bean setter invocation
(setIfxIFX_ISOLATION_LEVEL(String)), which, in this case, would presumably
invoke that method on the underlying ConnectionPoolDataSource
implementation. As I said, I'm not seeing behavior out of the driver that
would indicate this happened.
To debug further, what logger would I dial up here? There are an awful lot
to choose from.
Thanks,
Best,
Laird
--
http://about.me/lairdnelson