Antony Reynolds' Blog

  • April 19, 2011

Switching JVM Versions with WebLogic

Antony Reynolds
Senior Director Integration Strategy

Just a quick post to talk about a trick to make it easier to switch JVM versions when working with WebLogic and other tools.  When running WebLogic on platforms other than Windows and Linux, or when using a 64-bit JVM it is necessary to install the JDK before installing WebLogic.  I recommend that you put the JVM you are going to use in the Middleware home.  For example if installing the Hot Spot JVM you may get a directory called <MW_HOME>/jdk1.6.0_24.  To make it easy to switch JVMs I recommend that you create a symbolic link to the actual JDK (ln –s jdk1.6.0_24 jdk1.6).  When installing WebLogic make sure that you point at the symbolic link.  Then when you get an updated version of the JDK (say build 25) then you can just change the link to point to the later version.

Note this approach needs a little more work to behave properly with multiple types of JDK (say JRockit and Hot Spot) and I will cover this in a later post.

Join the discussion

Comments ( 2 )
  • guest Friday, February 3, 2012

    We have struggled to switch between JRockit and HotSpot, would love to understand what "little more work" involves :-)

  • Antony Tuesday, March 13, 2012

    When using JRockit you need to make sure that the JDK providor in the startup scripts is set to be "Oracle" rather than "Sun". This will make sure that the JRockit flags are set rather than the Sun flags.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.