Here's my situation. I have a process (identical copies running on
several iSeries machines) that runs a list of Java tasks, and this
process has "hot deployment" built into it. What that means is this:
There is a reference directory where the jar file for the application
resides. To hot-deploy the application, I simply drop the new version of
the jar file into that directory.
When the process detects the new jar file, it stops each task and copies
the jar file into the task's classpath. Then it starts the task again.
(It's Java code doing this, it just copies the jar file in the obvious
way.) And in the stdout of the process I see a lot of lines that say
"Attaching Java program to...".
The problem is, on some machines this hot-deployment procedure takes a
ridiculously long time. At present the application is less than 200
classes and the jar file is about 300K. On one machine it takes about a
minute and a half to do this for each task, whereas on another machine
it takes less than 10 seconds. And when you multiply that by 50 or 100
tasks, you can't even call it lukewarm deployment.
When I use DSPJVAPGM to see what the procedure did, it says
"Optimization... *INTERPRET" so I don't believe I can ask for anything
less than that. So what can I look at to see why it takes so long?
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.