Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > Java > Mutiple JVM in Single Os

Reply
Thread Tools

Mutiple JVM in Single Os

 
 
Senthil
Guest
Posts: n/a
 
      02-09-2007
Hi All,
Is there anybody who knows advantages and disadvantages of using
Multiple JVM in
Single OS. Actually we trigger a java program which will execute
normally and based on
some condition these will call a java program which will shell script
to execute some
other java program in seperate JVM. Will it Bad?? and disadvantage of
using like this.

 
Reply With Quote
 
 
 
 
=?ISO-8859-1?Q?Arne_Vajh=F8j?=
Guest
Posts: n/a
 
      02-09-2007
Senthil wrote:
> Is there anybody who knows advantages and disadvantages of using
> Multiple JVM in
> Single OS. Actually we trigger a java program which will execute
> normally and based on
> some condition these will call a java program which will shell script
> to execute some
> other java program in seperate JVM. Will it Bad?? and disadvantage of
> using like this.


There must be hundreds of thousands maybe millions of computers
out there running more than one JVM instance.

Whether it is a good solution or not is not possible to
say without more details.

Arne
 
Reply With Quote
 
 
 
 
Daniel Pitts
Guest
Posts: n/a
 
      02-09-2007
On Feb 9, 9:54 am, "Senthil" <(E-Mail Removed)> wrote:
> Hi All,
> Is there anybody who knows advantages and disadvantages of using
> Multiple JVM in
> Single OS. Actually we trigger a java program which will execute
> normally and based on
> some condition these will call a java program which will shell script
> to execute some
> other java program in seperate JVM. Will it Bad?? and disadvantage of
> using like this.



There is overhead associated with each JVM instance, including
initialization time and memory footprint.
If your approach is the easiest/cleanest way to do this, then I say
stick with it until you run into problems.

If you do run into problems, consider invoking the Java applications
from within your originating Java application. Or, consider writting
some of the functions of the other programs as services rather than
stand-alone applications.

 
Reply With Quote
 
Senthil
Guest
Posts: n/a
 
      02-09-2007
On Feb 9, 11:23 am, Arne Vajh°j <(E-Mail Removed)> wrote:
> Senthil wrote:
> > Is there anybody who knows advantages and disadvantages of using
> > Multiple JVM in
> > Single OS. Actually we trigger a java program which will execute
> > normally and based on
> > some condition these will call a java program which will shell script
> > to execute some
> > other java program in seperate JVM. Will it Bad?? and disadvantage of
> > using like this.

>
> There must be hundreds of thousands maybe millions of computers
> out there running more than one JVM instance.
>
> Whether it is a good solution or not is not possible to
> say without more details.
>
> Arne



Hi Arne,

My problem , we a running a Flux engine(scheduler) which will invoke
batch jobs, unfortunately some of the
batch jobs are killing the Flux(entire JVM: hot spot error). To
provide a solution for that i went for seperate
JVM so that if any kill operation is there, it will kill that JVM and
it won't affect other process.


 
Reply With Quote
 
Chris Uppal
Guest
Posts: n/a
 
      02-11-2007
Senthil wrote:

> My problem , we a running a Flux engine(scheduler) which will invoke
> batch jobs, unfortunately some of the
> batch jobs are killing the Flux(entire JVM: hot spot error). To
> provide a solution for that i went for seperate
> JVM so that if any kill operation is there, it will kill that JVM and
> it won't affect other process.


Then you have no choice but to run separate JVMs. The decision is made for
you -- you need the protection of running is separate processes no matter what
the implications for performance and memory use.

It's quite possible that either of those could be a problem. If so then you
could take a bybrid approach and use just two JVM processes (communicating via
TCP or some such). One is the master and it hands out tasks to do (but does
little else); the other is the slave, and it does all the hard work. Whenever
the slave dies, the master just starts up a new slave. More complicated, but
it avoids (normally) the startup overhead, and will probably be significantly
less of a memory hog, if you have several slave tasks all sharing the same JVM
than having them running in separate processes.

-- chris


 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Writing single client script block for mutiple controls Jason Barnett ASP .Net Building Controls 6 06-17-2006 01:36 AM
Mutiple external IPs on single interface Kevin Coles Cisco 5 01-10-2006 04:46 PM
display mutiple rows data fields for single record Chris ASP .Net 1 04-29-2005 03:14 PM
Mutiple server forms in single asp.net page Lakshmi Narayanan.R ASP .Net Web Controls 1 07-23-2004 12:43 AM
Mutiple Instance of Single EXE - VC++ varadha C++ 3 09-09-2003 07:33 PM



Advertisments