We have developed a J2EE, JBOSS application (on Linux O/S) with DB2 as backend database. As customer wanted a failover of database in real time and hence application was developed without any connnection pool.

We have used prepare statements and open and close JDBC connection for each method.

When we we connect to Linux DB2 UDB (in development environment), the performance of the application is fine.
(1 second for simple screen with simple select statements and 7 seconds for complex screen with multiple Database select/inserts/updates).

Whereas, when we connect to DB2 V5R3 on i-series (AS/400 - QA / Prod environment) using JT400.JAR the application becomes very slow. (3 second for simple screen with simple select statements and 24 seconds for complex screen with multiple Database select/inserts/updates).

Both Linux and DB2 databases contain the same amount of data and schems is same.

Please note the connection query used for AS/400.
SANFRANCISCO_DB1_READ_URL=jdbc\:as400\://IPaddress;libraries\=QGPL;extended dynamic=true;package criteria=select;package cache=true;dateformat\=jis;


We are looking for performance improvement / tuning suggestions to improve performance of J2EE application when connected to DB2 V5R3 on AS/400.

first of all you need more information and you wil get it by using the
database monitor, it will show up the times needed for connecting, access
plans of the query engine and if you could speed up the database access by
creating missing indexes. For some driver versions extended dynamic was
buggy and lowed down database access.

Dieter Bender

goodbazaar (AT) yahoo (DOT) com wrote:

V5R3 also is not supported any longer, there a number of SQL performance
enhancements in V5R4 and V6R1. The customer needs to strongly consider upgrading
to a supported release.

In addition to creating indexes, I'd also verify that the latest Database Group
PTF for V5R3 is installed.

dieter.bender (AT) t-online (DOT) de wrote: