I see the same thing with Postgresql, because I'm using the simple datasource.
There were other classes I could have used that were intended for
connection pooling - I got the impression they would allow for this kind of
situation.
On 09/06/07, glassfish_at_javadesktop.org <glassfish_at_javadesktop.org> wrote:
> Hi,
>
> I'm trying to kill off connections when I know the database has gone down.
>
> There are instances when a failure happens on one of the databases in one connection pool. When this went down Thursday, then came back up again, the connections were still not working. When I tried to shut down the database to clear everything out, the domain hung. I found the process ID of the JVM running the domain, and did a force kill on that.
>
> Is there a better way than that?
>
> Ben
> [Message sent by forum member 'bthoma' (bthoma)]
>
> http://forums.java.net/jive/thread.jspa?messageID=221334
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
--
Rasputin :: Jack of All Trades - Master of Nuns
http://number9.hellooperator.net/