RE: [JBoss-dev] FW: [JBoss-user] Strange Behavior When DataSource goes down.
Sounds like a pretty duh request. Maybe Bill can add this when he is adding the isolation level code. -dain > -Original Message- > From: danch [mailto:[EMAIL PROTECTED]] > Sent: Saturday, June 30, 2001 12:03 PM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] FW: [JBoss-user] Strange Behavior When > DataSource goes down. > > > I tend to agree with Doug on this. Also, I think it's reasonable that > the pools be able to tell the difference between inability to > create a > new object (connection, in this case) and simple pool exhaustion - > there's no reason to block startup of the whole server just > because one > datasource is bad - you could be taking 20 applications down just > because 1 has a database that went down. This like inability > to connect > should also be logged at error level. > > If nobody objects, I'll take this on and add this feature for 3.0. > > -danch. > > Ferguson, Doug wrote: > > > Hi, > > > > This is a thread that I think needs to move to DEV... > > > > Basically I feel that it is a royal pain that jboss hangs > whenever I try to > > startup jboss when a datbase is down and I've set the mbean > to blocking. > > > > I would like to see a timeout feature to where I can setup > the mbean with a > > timeout parameter for the blocking. I would also be nice to > have a default > > timeout. > > > > Other people brought up interesting issues... Please check > the thread. > > > > Thanks, > > d. > > > > -Original Message- > > From: Kaseman, Mark T > > To: '[EMAIL PROTECTED]' > > Sent: 6/29/2001 11:40 AM > > Subject: RE: [JBoss-user] Strange Behavior When DataSource > goes down. > > > > Number 2 is a big issue for me and OS/390 DB2. DB2 has an > idle thread > > time > > out parameter, that causes the datasource to become > unusable once DB2 > > kills > > the inactive connection/thread. I then must reboot JBOSS. > Orion server > > recovers the connection with no problem. > > > > -Original Message- > > From: danch (Dan Christopherson) [mailto:[EMAIL PROTECTED]] > > Sent: Friday, June 29, 2001 12:11 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [JBoss-user] Strange Behavior When DataSource > goes down. > > > > > > In this case, no query has been executed. > > > > What I'd change: > > 1. In the pools, object factory create methods should throw > an exception > > > > when they can't create an object - this way we can tell > pool exhaustion > > from inability to create a pooled resource. > > 2. The pools should have an ability to test connections to > determine if > > they're still good (configurable, of course). This is for > those whose > > database thwacks them on the head after some period of time (and no > > ability to turn that behavior off) > > > > others? > > > > -danch > > > > > > David Jencks wrote: > > > > > >> 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, > >>> > >>> > >
Re: [JBoss-dev] FW: [JBoss-user] Strange Behavior When DataSource goes down.
I tend to agree with Doug on this. Also, I think it's reasonable that the pools be able to tell the difference between inability to create a new object (connection, in this case) and simple pool exhaustion - there's no reason to block startup of the whole server just because one datasource is bad - you could be taking 20 applications down just because 1 has a database that went down. This like inability to connect should also be logged at error level. If nobody objects, I'll take this on and add this feature for 3.0. -danch. Ferguson, Doug wrote: > Hi, > > This is a thread that I think needs to move to DEV... > > Basically I feel that it is a royal pain that jboss hangs whenever I try to > startup jboss when a datbase is down and I've set the mbean to blocking. > > I would like to see a timeout feature to where I can setup the mbean with a > timeout parameter for the blocking. I would also be nice to have a default > timeout. > > Other people brought up interesting issues... Please check the thread. > > Thanks, > d. > > -Original Message- > From: Kaseman, Mark T > To: '[EMAIL PROTECTED]' > Sent: 6/29/2001 11:40 AM > Subject: RE: [JBoss-user] Strange Behavior When DataSource goes down. > > Number 2 is a big issue for me and OS/390 DB2. DB2 has an idle thread > time > out parameter, that causes the datasource to become unusable once DB2 > kills > the inactive connection/thread. I then must reboot JBOSS. Orion server > recovers the connection with no problem. > > -Original Message- > From: danch (Dan Christopherson) [mailto:[EMAIL PROTECTED]] > Sent: Friday, June 29, 2001 12:11 PM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] Strange Behavior When DataSource goes down. > > > In this case, no query has been executed. > > What I'd change: > 1. In the pools, object factory create methods should throw an exception > > when they can't create an object - this way we can tell pool exhaustion > from inability to create a pooled resource. > 2. The pools should have an ability to test connections to determine if > they're still good (configurable, of course). This is for those whose > database thwacks them on the head after some period of time (and no > ability to turn that behavior off) > > others? > > -danch > > > David Jencks wrote: > > >> 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. >>> >> > > > > > ___ > 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 > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] FW: [JBoss-user] Strange Behavior When DataSource goes down.
Hi, This is a thread that I think needs to move to DEV... Basically I feel that it is a royal pain that jboss hangs whenever I try to startup jboss when a datbase is down and I've set the mbean to blocking. I would like to see a timeout feature to where I can setup the mbean with a timeout parameter for the blocking. I would also be nice to have a default timeout. Other people brought up interesting issues... Please check the thread. Thanks, d. -Original Message- From: Kaseman, Mark T To: '[EMAIL PROTECTED]' Sent: 6/29/2001 11:40 AM Subject: RE: [JBoss-user] Strange Behavior When DataSource goes down. Number 2 is a big issue for me and OS/390 DB2. DB2 has an idle thread time out parameter, that causes the datasource to become unusable once DB2 kills the inactive connection/thread. I then must reboot JBOSS. Orion server recovers the connection with no problem. -Original Message- From: danch (Dan Christopherson) [mailto:[EMAIL PROTECTED]] Sent: Friday, June 29, 2001 12:11 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Strange Behavior When DataSource goes down. In this case, no query has been executed. What I'd change: 1. In the pools, object factory create methods should throw an exception when they can't create an object - this way we can tell pool exhaustion from inability to create a pooled resource. 2. The pools should have an ability to test connections to determine if they're still good (configurable, of course). This is for those whose database thwacks them on the head after some period of time (and no ability to turn that behavior off) others? -danch David Jencks wrote: > 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. >> ___ 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 ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
