|
Chris, What type of work your 'extract' process does? If it's SQL type of work, did you try running those queries outside java (i.e. STRSQL or RUNSQLSTM)? I'm thinking that could help you eliminate database as culprit so you know you're correct to focus on enhancing Java performance. Elvis -----Original Message----- Subject: Re: [WDSCI-L] MS SQL Server JDBC connections Thanks for the reply guys, but the problem is occurring after the JVM has started - my timings are generated in the main method being executed. Before creating the SQL Server connection, which is what seems to hang, an iSeries JDBC connection is already created, which is much quicker. I think the problems are either: - something to do with the SQL Server JDBC driver, (perhaps a property needs setting somewhere). - are network related (but since both the iSeries and development PC's are on the Lan and the SQL server is in a DMZ, I would have though that the connection speeds would be similar.) - resource related - it just happens to be at this point the jvm runs out of memory and starts asking for more? (does anyone have any tuning pointers?) Once the connection created the actual data transfers take roughly the same amount of time. Regards, Chris.
As an Amazon Associate we earn from qualifying purchases.
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.