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
On Wed, Apr 2, 2014 at 1:32 PM, Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>wrote:
No Cluster, we have a windows WAS express server that is picking up the
database connections started from a Linux tomcat server connection pool.
This is causing major headaches. We have a fix going into tonight that
removes the libraries parameter from the connection and (don't kill me)
hard codes the library at the sql statements. (Well it is a variable set
for the environment, development, staging or production.)
I am trying to learn more about the connection from the tomcat server,
what JBDC driver is being used, and how it is defined, so we can fix it
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:25 AM
To: Midrange Systems Technical Discussion
Subject: Re: JDBC connections and library lists
That shouldn't be possible...
I could see two different apps on a single server. But not different apps
on different servers.
Unless perhaps the apps are running on a app server cluster?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives