The "textbook" answer to this concern is to use separate connection pools for separate applications. :-)
________________________________________
From: web400-bounces@xxxxxxxxxxxx [web400-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin [nandelin@xxxxxxxxx]
Sent: Monday, October 27, 2008 5:57 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Persistent Sessions in DB connection for QZDASOINIT, implemented by Nathan
From: Walden H. Leverich
In my case I don't draw the line, each request is a "new"
connection [from the pool]...
I appreciate the response. And it sounds like a textbook answer. Do you see any dilemma occurring as the number of applications increases, and consequently the number of tables opened in the database server jobs increases? A financial system may not use the same tables as a human resource system, but if all applications get connections from the same pool, it seems to me that the server jobs will end up maintaining open data paths to all the files in both systems. A user may have opened a table under one connection, but if that connection is not available for a subsequent request, then the table is reopened in another connection.
Nathan.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/web400.
midrange.com
