<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.45">
<TITLE>RE: [Talk] A request of real-world SysAdmins/SysManagers/CIOs...</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>> Gary Schmidt <Gary.Schmidt@oz.quest.com> asks:</FONT>
<BR><FONT SIZE=2>> > What is the current attitude towards running JVMs on </FONT>
<BR><FONT SIZE=2>> production systems</FONT>
<BR><FONT SIZE=2>> > these days?</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> What is the issue? If software which you want to use is </FONT>
<BR><FONT SIZE=2>> written in Java</FONT>
<BR><FONT SIZE=2>> (and not natively compiled, which I suppose it might be but isn't what</FONT>
<BR><FONT SIZE=2>> you're asking about), then you have to run the JVM. It's </FONT>
<BR><FONT SIZE=2>> just one more</FONT>
<BR><FONT SIZE=2>> of many bytecode interpreters available to developers, </FONT>
<BR><FONT SIZE=2>> amongst which is</FONT>
<BR><FONT SIZE=2>> also included the Perl bytecode interpreter. Why should Java </FONT>
<BR><FONT SIZE=2>> be special?</FONT>
</P>
<P><FONT SIZE=2>The question is whether running a(nother) JVM on a production machine, let us say running Oracle/DB2/Informix/OraApps/Peoplesoft/SAP/apache/etcetera, _is_ an issue or not.</FONT></P>
<P><FONT SIZE=2>The JVM would be runiing while the machine is running. Basically we are talking abount adding another system daemon which happens to be written in Java to the system.</FONT></P>
<P> <FONT SIZE=2>Cheers,</FONT>
<BR> <FONT SIZE=2>Gary B-)</FONT>
</P>
</BODY>
</HTML>