|
midrange.com
Thanks again Scott. We are going to do some testing to see how the
QZDASOINIT get handled by QRWTSRVR jobs? Talking with you it sounds like
the A/G would exist, as long as we didn't reclaim it, until the server
job(QRWTSRVR) has actually ended.
Copied from Mike Eovino's message
Just to confuse the matter a little further (I work with Jason and
know some of the details of this)...
We're not using CGI. The stored procedure is being called by a Java
servlet running from inside WebSphere Application Server, which is
hosted on another iSeries system. So the stored procedure should be
running in one of the QZDASOINIT jobs on the target system.
We are using connection pooling for database requests from WAS, so the
QZDASOINIT job should be reused to some extent. We're pretty new to
WAS, so we're not really sure how connection pooling and QZDASOINIT
work together, or how long the QZDASOINIT jobs last. Do they last
forever like DRDA requests that are handled by QRWTSRVR jobs?
I would think that the handling of the named A/G would be pretty
similar, however. So that once the first call sets up the A/G in the
QZDASOINIT job, subsequent calls that are serviced by that same
QZDASOINIT job would reuse the A/G.
And if we were to have a large enough volume of requests from WAS to
our target system, could we conceivably have several QZDASOINIT jobs,
each of which could have that named A/G?
Sorry if I'm moving into an area that would be better handled by the
midrange or Java list.
Thanks
Jason Bender
EDPS (Electronic Data Processing Services)
jbender@xxxxxxxxxxxx
804/353-1900 Extension 2887
Scott Klement
<rpg400-l@scottkle To: RPG programming on
the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
ment.com> cc:
Sent by: Subject: RE: Connection
Pooling - Activation Groups
rpg400-l-bounces@m
idrange.com
09/07/2006 11:32
AM
Please respond to
RPG programming on
the AS400 /
iSeries
To me it sounds like once the session becomes idle, thus the physical connection is lost, the activation group would be reclaimed. Correct me
if
I'm wrong, but once the session becomes idle, the activation group needs
to
be recreated.
It doesn't matter whether the network connection is lost. Ending a network connection won't end an activation group (and in fact, has absolutely no relationship to an activation group!) What matters is whether the job is ended. If the job on the server is ended and has to be restarted, then a new activation group has to be created in that new job.
The connection pooling feature enables the database server to timeout an idle session and use the connection to service an active session. The
idle
logical session remains open, and the physical connection is
automatically
reestablished when the next request comes from that session.
This states that the session remains active, and therefore the activation group would also remain active. If you're not sure, why don't you try it and find out? Surely this can't take a significant amount of time to test? -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
