Well, I kind of agree, however I don't know how to distinguish between the
db crashing and executing a query whose first results are available in 3
hours...and you're willing to wait. I think if the driver can distinguish
and throw an exception, you get to see the exception. Otherwise, what do
you do? Some kind of time awareness such as jini leases would be nice,
however there certainly isn't any support for them in jdbc. Any ideas?
david jencks
On 2001.06.28 15:32:20 -0400 Richard Kasperowski wrote:
> David Jencks wrote:
>
> > Hi,
> > I find it hard to understand what you want.
> >
> > jboss does try out connections from configured datasources on startup,
> and
> > hangs if they can't connect.
> >
> > I don't see how this is a severe problem: if your datasource isn't
> working,
> > neither will your app.
>
>
> When a datasource becomes unavailable after startup, it might be
> desirable for the application to tell the user, "sorry, the database is
> unavailable."? A user might find that more satisfactory than being
> denied service.
>
> --
> Richard Kasperowski (mailto:[EMAIL PROTECTED])
> Tel: 617-576-1552, Fax: 617-576-2441
> http://www.altisimo.com/
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
