Re: One JVM for batch job

    Hi Niall,

    As Joe observed, there's not enough information to specifically resolve
your issue, but it sounds like you are using commands that ask for a new VM
to be started.

    In a batch situation that may run sporadically, we've typically used
message queues.  They are reliable, perform reasonably well, are persistent,
allow graceful shutdowns and are available to any language on the '400.  We
either have a controller program that invokes the appropriate class or have
the class itself monitor the queue.

    Notice that I'm talking about the MSGQ we all know, not JMS.  I have
considered writing a JMS front end to standard message queues to make the
process portable,  but don't know if there is enough of a market to justify
the time.  Obviously, there are other solutions, but this one has really
worked well for us.


                                                         Joe Sam

Joe Sam Shirah -        http://www.conceptgo.com
conceptGO         -        Consulting/Development/Outsourcing
Java Filter Forum:       http://www.ibm.com/developerworks/java/
Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
Going International?    http://www.jguru.com/faq/I18N
Que Java400?             http://www.jguru.com/faq/Java400


----- Original Message -----
From: "Niall Mcloughlin" <niallsemail@xxxxxxxxx>
To: <java400-l@xxxxxxxxxxxx>
Sent: Tuesday, September 09, 2003 9:54 PM
Subject: One JVM for batch job


> All
>
> I have a batch job running as a daemon during the day.
> Whenever certain conditions are met, a java class is
> called. Each call appears to start up a separate JVM
> which obviously creates an unnecessary overhead.
>
> Is there a way to create a JVM at the start of the
> batch job and have each java call use that JVM ?
>
> Niall
>
>