RE: JDBC performance issues after moving to Java 8

Richard Schoen <[email protected]>
Newsgroups gmane.comp.lang.as400.java
Message-ID <DM6PR08MB4156DEB93DE8E4E880D5E7A187460@DM6PR08MB4156.namprd08.prod.outlook.com>
Mark not sure if this is still relevant at V7R1 and above, but I know we had customers have issues related to IPV6 being enabled for Java. Was causing DNS timeouts like others have mentioned.

Old but maybe still relevant.
http://www-01.ibm.com/support/docview.wss?uid=nas8N1011363

Regards,

Richard Schoen 
Director of Document Management 
e. [email protected] 
p. 952.486.6802 
w. helpsystems.com 

----------------------------------------------------------------------

message: 1
date: Fri, 6 Jul 2018 08:57:41 -0400
from: Mark Murphy <[email protected]>
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-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at https://archive.midrange.com/java400-l.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.