Consider moving to the 64bit version. I've had some success with
improvements that way. Depending on how memory intensive the application is
you might have to add memory to the shared memory pool where it's running.
Which brings up another point, you should be moving these processes into a
shared memory pool and getting them out if *BASE.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: JAVA400-L [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark
Murphy
Sent: Friday, July 06, 2018 7:58 AM
To: Java Programming on and around the IBM i <java400-l@xxxxxxxxxxxx>
Subject: JDBC performance issues after moving to Java 8
We have a Java application running on IBM i v7.1. It was working fine with
Java 6, but when we moved to Java 8 in preparation for an upgrade to v7.3,
the program started taking over an hour to run. As far as I know, the only
change was to move to Java 8. We are using the 32 bit JVM for both Java 6
and Java 8.
Any ideas on where to look for issues? We are not getting any errors that I
know of, and everything is running through properly. It just takes over an
hour for the program to run now when it used to take minutes. The
application is using JDBC to communicate with a MS SQL Server. It is
basically synchronizing data for another process that runs on Windows.
--
This is the Java Programming on and around the IBM i (JAVA400-L) mailing
list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://archive.midrange.com/java400-l.
midrange.com
