We are running V6R1. I am thinking that because the connection pool is created when Tomcat starts and not used for days, the iSeries is closing the connection. As the programmer has pointed out to me, (cause it ain't his problem) that the application ran fine for 14 months. (Bull) Over the weekend we introduced the WAS server application into production. That is when the land mines started being stepped on. There has to be some reason the RHEL Tomcat server is not holding the connection pool open. If the programmer will get off of his high horse and send me his configurations, I will share with you.
Here is what I have so far:
Apache's connection pool library: org.apache.commons.dbcp.BasicDataSource
I don't use a "toolkit". It's a JDBC driver from IBM and called: com.ibm.as400.access.AS400JDBCDriver.
Does this make any sense to you cause I am clueless.
Director of Information Services
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Wednesday, April 02, 2014 10:52 AM
To: Midrange Systems Technical Discussion
Subject: Re: JDBC connections and library lists
Again...it can't be happening that way...it just can't. The i isn't going
to allow an open connection to one box to be used by other at the TCP/IP
level let alone the JDBC level unless there's some sort of virtual
Do you have a network trace that proves it?
If not, what's your evidence that that the connection was started by tomcat
and picked up by WAS?
What version of IBM i?
I'm on 7.1, perhaps the library list reset that I see when a connection is
released is new and that Dan was right about it not being reset at older