[olug] Java VM Issues

[Nick Walter]

I agree with Sean, if you want vendor support then you pretty much have
to adhere strictly to their requirements.  However, sometimes vendors
demand obscure or bizarre setups simply because their own QA departments
haven't validated anything else.  And then there is the ever enjoyable
conflicting-vendor-requirements game when multiple pieces of your
application stack have mutually contradictory requirements yet you need
to run them together.  

I have violated vendor supported config requirements in both development
and production servers in the past and gotten away with it.  If you want
to go this route but still need vendor support then you MUST have a lab
server that is within vendor config requirements available to reproduce
problems on.  Then you can simply call for support on the lab system and
get a solution that will work for both your lab and your non-supported
config.  Don't take this route unless you have time for extensive
testing to make sure your non supported config is pretty stable before
you launch it into a mission critical role.

Nick Walter



On Wed, 2003-10-08 at 09:36, Sean Edwards wrote:
> We use BEA's WebLogic Server as a platform for our
> custom Java applications.  Since WebLogic is a
> commercial J2EE platform, it is our experience to
> strictly adhere to the vendor requirements for the
> product.
> 
> Here is an example from trying to deploy Oracle Report
> server with WebLogic:  The requirements for WebLogic
> Server 7.0.2 are Sun JVM 1.3.1_06 on RedHat 7.2.  The
> Oracle Reports Servlet was compiled with Sun JVM 1.2. 
> The app server for one of our customers requires the
> JVM max memory set to a large value.  Every time we
> started the server, it would crash.  The issue was
> that the Oracle Reports Server was compiled with Sun
> JDK 1.2, and it did not like the values for the JVM
> memory settings.  We now have to run Oracle Reports
> from a database server, because the servlet would not
> work in our app server environment.
> 
> With RedHat dropping support of 7.2 in December, BEA
> is changing the environment requirements for WebLogic.
>  When we move off of RedHat 7.2, we will also move
> from Sun's JVM to JRockit (a JVM BEA has "optimized"
> for their WebLogic Server product).  By the way,
> WebLogic Server 8.1 requires Sun's JVM 1.4
> 
> So to answer your question about which JVM is the
> best, I would say what ever the vendor requires.
> 
> -=Sean=-
> 
> --- kent tegels <ktegels at Msn.com> wrote:
> > Ah, the joy of traveling in the undiscovered
> > country...
> > 
> > We're a Windows shop planning our move away from the
> > MSJVM to a SUN JVM. We
> > have an off-the-shelf application that seems to
> > insist on having 1.2.0 of
> > the VM installed. I'm wondering however, if that's
> > the safest version of the
> > JVM we could deploy. Can somebody point me to where
> > I can find information
> > on the difference security-wise between the various
> > JVM versions?
> > 
> > Please don't laugh and remind that I'm trying fix a
> > sandbag when there's
> > whole Ocean of issues waiting to pound us. I know
> > that. One headache a day
> > is my limit and I've already got that... <grin>
> > 
> > Also, am I correct in assuming that the versions of
> > the JDK and JVM are kept
> > "in-sync?"
> > 
> > Thanks!
> > Kent
> > 
> > 
> > 
> > _______________________________________________
> > OLUG mailing list
> > OLUG at olug.org
> > http://lists.olug.org/mailman/listinfo/olug
> 
> 
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Shopping - with improved product search
> http://shopping.yahoo.com
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> http://lists.olug.org/mailman/listinfo/olug
>