Re: Validating JDBC Connection to iSeries

    Hi Ken,

    I ( very ) recently had a similar question posed at the developerWorks
Java Filter Forum.  See "is connection alive?" at

http://www-106.ibm.com/developerworks/forums/dw_forum.jsp?forum=177&cat=10

for my generic thoughts.

    If your pool is *only* for AS/400/iSeries, the the standard method is to
use AS400JDBCConnectionPool in JTOpen/Toolbox and it will handle the
issue for you.  Basically, it uses an internal AS400 object to ping the
database port.

    There was a series of messages to do with using a DataSource and
AS400JDBCConnectionPool, July 28-30, 2003 that may be helpful.  Search
the list archive for "dataSource.getConnection jt400".

    I also have some thoughts and comments regarding your earlier "RPG to
Java Conversion" messages if I can ever get to it.  Right now for a planned
product  I'm going through design, code, test, accessibility, i18n and
back...and back...and back...possible reporting project...possible database
conversion project...whoops! and back...    ;-P  Take care,


                                                         Joe Sam

Joe Sam Shirah -        http://www.conceptgo.com
conceptGO         -        Consulting/Development/Outsourcing
Java Filter Forum:       http://www.ibm.com/developerworks/java/
Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
Going International?    http://www.jguru.com/faq/I18N
Que Java400?             http://www.jguru.com/faq/Java400


----- Original Message -----
From: "TitanRebel" <TitanRebel@xxxxxxxxxxx>
To: <java400-l@xxxxxxxxxxxx>
Sent: Thursday, August 14, 2003 1:30 PM
Subject: Validating JDBC Connection to iSeries


> Is there a "standard" way to validate that a JDBC connection to the
> iSeries is
> still valid?  I've implemented my own connection pooling and I thought
> that I
> had been validating the connections by doing  "conn.getMetaData()".
>  Evidently,
> this method does not "make a trip" to the iSeries.  Is there anything
other
> than "querying a file that will always be there".  It just doesn't seem
> to be
> an elegant solution, but if this is the only way then so be it.
>
> I'm testing this by:
> 1. Creating and testing some valid connections to the database in the pool
> (running Tomcat on my PC).
> 2. Disable my network connection via Win2k.
> 3. Try it again, getting an error of course.
> 4. Re-enable my network connection.
> 5. Try it again.  This is where my connection pool should determine that
the
> existing connections in the pool are invalid, and re-establish a new
> connection returning the new one.
>
>
> Thanks,
>
> Ken K.
>