Re: SQL stored procedures and activation groups via JDBC -- MIDRANGE-L

Subject: Re: SQL stored procedures and activation groups via JDBC
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Thu, 14 May 2009 14:13:13 -0700 (PDT)
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

From: Mark S. Waterbury
Or, is there a way to force the QZDASOINIT jobs to terminate,
and the replace them with a new instance, in the connection pool,
periodically?

It may be a difficult or disagreeable obligation to the application vendor, but I'd put the onus back on them to provide a solution.

What kind of thought did they put into connection pool management?

How can they justify a design that essentially leaks memory, and doesn't allow for end-user or administrative control?

Nathan.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.