• Subject: Re: JDBC lock after update
  • From: shahar mor <shahar_mor@xxxxxxxxx>
  • Date: Mon, 20 Dec 1999 06:31:02 -0800 (PST)

--- cujo@us.ibm.com wrote:
> This will get you around the problem, but I think it
> is going to really
> tank performance of anything but a trivial
> application.  The problem with
> this change is that  you are going to pay the price
> of job creation on
> every connection.
> The suggested solution should work for getting
> around the problem, but a
> better long term solution should be used.  I will
> request this be looked at
> by someone here.
> Regards,
> Richard D. Dettinger
> AS/400 Java Data Access Team

Thank you for your time and effort. i'm looking
forward to hear from you (since the suggested maxuse
on the prestart job entry is not acceptable on our
application dcue to performance issues).

Thanks again

Shahar mor
Do You Yahoo!?
Thousands of Stores.  Millions of Products.  All in one place.
Yahoo! Shopping: http://shopping.yahoo.com
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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