From my experience, what I assume is happening is that the connection pool
is lazily initialized (just configuring a connection pool doesn't create
connections). If you create a pool in the admin console, and click on
"flush" you'll get this error. If you create this pool (and a connection
resource), deploy an application that uses this resource (lets say
JPA initialization on deployment for example), you'll be able to flush the
pool...because there is one.
Again, this is based on my observations, I have never dug into the code to
verify this.
S
On Sun, Aug 26, 2012 at 10:56 AM, <forums_at_java.net> wrote:
> Hello everyone, I downloaded the last version of Glassfish server 3.1.2.2
> and
> made all configurations to deploy my app, but when I was configuring the
> Connection Pool ( for Oracle Database ) and test Ping, works fine, but I
> can't say the same for Flush in this Connection Pool. Always I receive the
> message " Flush Connection Pool did not happen as pool - MyPool is not
> initialized" What it really means ? what i did wrong to not initialize this
> Pool ? I have to configure one Conector Connection Pools for this resource
> ?
> What I have to do to work with Pooling in Glassfish server ? I already
> research this in internet but could not find anything who might solve this.
> Thanks. Best Regards. Anderson Cruz.
>
> --
>
> [Message sent by forum member 'anderson.cruz']
>
> View Post: http://forums.java.net/node/**889565<http://forums.java.net/node/889565>
>
>
>