configurable timeout.
cheers,
d.
-Original Message-
From: David Jencks [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 06, 2001 10:17 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Strange Behavior When DataSource goes down.
I've never seen this. Not to be snooty, but how do you know this
I've never seen this. Not to be snooty, but how do you know this is a
jboss problem? I don't know why this would make a difference, but are you
using the jca wrappers? Is jboss-auto.jcml safely out of the way or are
you using a version where it is not read? Whats youre NPE?
david jencks
On
At 12:33 AM 7/6/01 -0700, you wrote:
>JCA is a standard introduced in J2EE 1.3. JDBC is not being deprecated,
How's this.
JBoss conects to my datasource on start up. I shut down, add a new
database, restart the computer even. New datasource generates NPE. Shutdown
JBoss, restart, datasource con
t: Thursday, July 05, 2001 11:18 PM
Subject: Re: [JBoss-user] Strange Behavior When DataSource goes down.
> Scott, is JCA a standard extension that vendors must follow in order to
> claim version x.x compliance? I'm wondering how this mechanism will work,
> for example with database
sConnected()
method is preferable (obviously, DBMS vendors must agree to implement that
for it to do any good.)
- Original Message -
From: "Scott M Stark" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 03, 2001 2:44 AM
Subject: Re: [JBoss-user] Strange Be
Guy Rouillier wrote:
> I see one problem here and one issue.
>
> Problem: There is no standard, cross-vendor approach that I'm aware of to
> test to see if a database connection is still alive.
Yep! In the past I've just made a connection pool execute arbitrary
(defined as one of the pool par
calTransactionCommitted(ConnectionEvent event);
>
> public void localTransactionRolledback(ConnectionEvent event);
>
> }
>
> - Original Message -
> From: "Guy Rouillier" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday,
Message -
From: "Guy Rouillier" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 02, 2001 11:10 PM
Subject: Re: [JBoss-user] Strange Behavior When DataSource goes down.
> I see one problem here and one issue.
>
> Problem: There is no standard, cross-ve
t;
To: <[EMAIL PROTECTED]>
Sent: Friday, June 29, 2001 12:10 PM
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
> whe
: 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 s
Ferguson, Doug wrote:
> I believe that in my first email I mentioned that I have db failover
> coded into my bean.. That means I am not screwed if a db goes down
> unless jboss screws up.. Which is what is exactly happening. Not Good.
>
> You mentioned waiting on a long query to execute but this
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 con
]]
Sent: Thursday, June 28, 2001 8:04 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Strange Behavior When DataSource goes down.
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 y
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
y
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
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
forever.
Any ideas?
d.
-Original Message-
From: Allen fogleson [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 27, 2001 8:07 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Strange Behavior When DataSource goes down.
every time i have seen a hang on startup with the DS binding it was bec
One thing you can do is set the 'Blocking' attribute to false for that
pool in jboss.jcml. This will get rid of the hanging problem, but you'll
have to expect calls to DataSource.getConnection to return null in some
cases.
-danch
Ferguson, Doug wrote:
> We are seeing jboss hang when the data
d had this problem.
Al
- Original Message -
From: danch <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 27, 2001 8:11 PM
Subject: Re: [JBoss-user] Strange Behavior When DataSource goes down.
> Ferguson, Doug wrote:
>
> > We are seeing jboss hang wh
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.
There is another problem that connection poo
Ferguson, Doug wrote:
> We are seeing jboss hang when the datasource goes down and we cannot restart
> jboss becuase it hangs on the datasource binding.
>
> This is terrible because we have implemented within our beans but it can't
> work becuase
> jboss is hanging.
Implemented what within your
We are seeing jboss hang when the datasource goes down and we cannot restart
jboss becuase it hangs on the datasource binding.
This is terrible because we have implemented within our beans but it can't
work becuase
jboss is hanging.
Even if the hanging or our problem, we can't restart because jb
22 matches
Mail list logo
