× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Slow JDBC access to AS/400 (over 56k remote connection)
  • From: dclowe@xxxxxxxxxx
  • Date: Mon, 10 Jul 2000 09:32:46 -0230

I find that JDBC access is very slow when connecting to a remote database
on the AS/400.  Here is my configuration:  Client/Server application was
created using VisualAge for Java 2.0 enterprise edition.  Accessing a DB2
database on a IBM AS/400 (720) using V4R4.  It uses the AS/400 toolkit for
Java JDBC driver.  When the clients are connected to the AS400 using a 56k
frame relay, I am getting approximately 1 JDBC insert per second.  It is a
little faster on a 128k frame relay and it runs fine on the local network
(10 megabit).  The clients are Win9x running the Java application in the
Sun JRE for Win9x.  All the JAR files for the runtime, database access,
and our application reside on the client.   Only the database access is
being done remotely.

Does anyone know of any tips that would help improve performance in this
situation, or any articles talking about Win9x clients accessing AS/400
DB2?  Any help would be appreciated.

Thanks... Dean Clowe


+---
| 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-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.