dev@glassfish.java.net

Re: Bug Report for Admin-gui: unexpected behavior in JDBC connection pool configuration

From: Anissa Lam <Anissa.Lam_at_Sun.COM>
Date: Mon, 16 Mar 2009 22:29:49 -0700

Hi Wu,
Thanks for reporting this, I will look into this and get back to you.
You can also file the issue at
https://glassfish.dev.java.net/servlets/ProjectIssues after you logged
in to java.net

thanks
Anissa

Wu Jie wrote:
> Hi Anissa
> Hi GUI Dev Team
>
> I encountered an unexpected behavior when operate "Validation Method"
> of JDBC connection pool in GF V2.1. the following is the phenomenon and
> repreduction.
>
> 1. Create a JDBC connection pool.
> specify "Validation Method" as "table", and an non-exist table for
> "Table Name".
>
> 2. excute "Ping"
> click the button "Ping", and an expected message is output which means
> the specified table is not exist.
>
> 3. change the value of "Validation Method"
> update the value of "Validation Method" of the JDBC connection pool created
> in step 1. set "auto-commit" instead of "table" and save it.
>
> 4. get the value of "Validation Method" back to "table"
> set the value of "Validation Method" form "auto commit" back to "table",
> left
> the "Table Name" as blank and save it.
> #although "table name" can not be left blank when "Validation Method" is
> specified
> #as "table", indirectly set blank for it by step 3 and 4. I think it is
> the unexpected
> #behavior, and regard it as a bug.
>
> 5. click "Ping"
> unexpectedly, ping failure is due to the non-exist table which specified
> in step 1.
> #why the old value of "table name" is used. is it cached by MBean or other?
>
> the simillar phenomenon maybe take place in any other component in GUI.
> (e.g when create a JDBC Resource with invalid char for jndi name.
> sometimes it
> may be successful, in situation the domain.xml will be broken.)
>
> Anissa, could you please give me the solution or suggestion. and
> appreciation in ahead :-) .
>
> Thanks
> -Wu
>
>