The JBoss issue is two-fold:

When a minerva pool is configured with Blocking = true then
1) When you run your app and you run a query it haults the entire app and
    will waiting for infinity trying to get that connection... there is no
timeout
2) When you cannot restart jBoss because when jBoss setups up the
Datasources, one 
    of the steps is to test the connection. When it does this it get stuck
in a busy
    wait. Again.. there should be a timeout.

I moved this thread the jBoss-Dev after it deadended on JBoss-User and
someone has
volunteered to make updates to allow for a 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 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 2001.07.06 12:50:02 -0400 Richard Bottoms wrote:
> 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 connects. Shutdown JBoss, restart, NPE.
> 
> Hope version 3 makes this bulletproof.
> 
> 
> r.b.
> 
> 
> 
> 
> 
> _______________________________________________
> 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-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to