My opinion is let user to define a time out for each resource in the pool.
Second solution is the try catch of those errors and handle them properly.
That means if the connection is dropped (for any reason) then user can have
the abillity to throw this connection away from pool. I tried once to use
minerva
pools for tcp-socket pooling and that was the issue that concerd me. I
checked
a more recently version of jboss source code and i found that there is also
support
now for this (you can now specify in your code that you dont want any more
this
connection and so it is disposed from pool). 

Stratis Aravias
Informer S.A.

> -----Original Message-----
> From: Rick Horowitz [SMTP:[EMAIL PROTECTED]]
> Sent: ������, 14 ����������� 2000 16:19
> To:   jBoss
> Subject:      Re: [jBoss-User] JDBC Connection reset by peer
> 
> Aaron Mulder wrote:
> > 
> >         First of all, if you're not using Minerva, please do.
> >         Second, Minerva doesn't test connections before it hands them
> out.
> > If we can think of a good way to test a connection, I'd certainly be
> > happy to add that.  I mean, you could create a statement and close it
> > immediately, but there's no way of knowing whether that actually goes
> > through to the database or just creates a new data structure on the
> client
> > side.  You could execute an invalid SQL statement and catch the
> exception,
> > but that seems kind of heavyweight.  There's no "ping" in JDBC!
> >         There currently is a setting for "InvalidateOnError" that you
> can
> > set to true and it will drop a connection from the pool every time
> there's
> > a SQLException on it (you can change this in jboss.jcml).  But that
> still
> > doesn't catch anything util there's a problem.  If you can think of a
> way
> > to validate a connection before it leaves the pool, I'm all ears.
> 
> I'm not 100% sure of the problem you're trying to solve here, but would
> it be possible to use one of the JDBC connections to read the database
> metadata, and from that create a JDBC query that could be executed to,
> for example, just read some data from one of the tables?
> 
> >         Oh, and the timeout varies by DB - Oracle connections don't seem
> > to timeout (or at least, the timeout is months or longer).  You may be
> > able to set this in your DBMS or its JDBC driver, but it may be out of
> > your hands.
> > 
> > Aaron
> > 
> > On Thu, 14 Sep 2000, Bauer_Wolfgang wrote:
> > > Hello,
> > >
> > > we have the following problem using JBoss with Interbase:
> > >
> > > JBoss is running on a Linux machine, Interbase 6 is running on another
> Linux
> > > machine.
> > > Everything works fine for half an hour. After that time we get a
> > >
> > > "connection reset by peer" exception
> > >
> > > when trying to connect to the database.
> > >
> > > 1) Does anybody know whether JDBC connections are assumed to timeout?
> > > If yes, can this timeout be configured somewhere?
> > > Is this a operation system issue or does it depend on the database?
> > >
> > > 2) Given that connections do get lost for some reason (DB server down,
> etc.)
> > > shouldn't
> > > jBoss check that and asure that only valid connections are used for
> data
> > > access?
> > >
> > > Mit freundlichen Gr��en
> > >
> > > Wolfgang Bauer
> > > Softwareentwicklung
> > > ______________________________________________________
> > >
> > > sympat GmbH
> > > Automatisierungstechnik & Informationstechnologie
> > > ______________________________________________________
> > > mailto:[EMAIL PROTECTED]
> > > ______________________________________________________
> > >
> > >
> > >
> > >
> > > --
> > > --------------------------------------------------------------
> > > To subscribe:        [EMAIL PROTECTED]
> > > To unsubscribe:      [EMAIL PROTECTED]
> > > Problems?:           [EMAIL PROTECTED]
> > >
> > 
> > --
> > --------------------------------------------------------------
> > To subscribe:        [EMAIL PROTECTED]
> > To unsubscribe:      [EMAIL PROTECTED]
> > Problems?:           [EMAIL PROTECTED]
> 
> 
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> Problems?:           [EMAIL PROTECTED]


--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to