Re: How do I keep JVM open after first call?

Hi Steve,

Dan's right: not enough information. Some suggestions:

Are you sure it is Java that's slow? I'd put in some debugging code for begin and end time for each transaction, also for any exceptions, and you should be able to verify whether the connection is open or not. I assume the CL is only called once. Does the weight data include timestamp info? If so, you could verify that time as well. Depending on how the scale is connected, check system logs for retries.

Do you have another Java programmer or trusted outside resource for review? Sometimes a second pair of eyes picks up on things that get past someone familiar with the code.


Joe Sam

Joe Sam Shirah - www.conceptgo.com (904) 302-6870
conceptGO - Consulting/Development/Outsourcing
Java Filter Forum: www.ibm.com/developerworks/java
Just the JDBC FAQs: www.jguru.com/faq/JDBC
Going International? www.jguru.com/faq/I18N


-----Original Message----- From: Steve Fekete
Sent: Tuesday, October 16, 2012 10:24 AM
To: java400-l@xxxxxxxxxxxx
Subject: How do I keep JVM open after first call?

Hi folks,



I have a CL calling a Java program that retrieves a weight from a scale and
moves the weight to a either a database or a data area in the java program.



If it is the database option, it takes 5 to 7 seconds to write to the
database file and if we use the chgdtaara command it takes 5 seconds to open
the connection to the iSeries and another to execute the command. The
programmer says he is trying to leave the connection(s) open, but it doesn't
seem to be working.



What do we have to do to speed up this process?



Thanks!