How to verify the jre level in effect after a jre upgrade?

How to verify the jre level in effect after a jre upgrade?

book

Article ID: KB0082084

calendar_today

Updated On:

Products Versions
TIBCO Data Virtualization 7.0.0 and later

Description

If you are running TDV v7.0.6 or earlier, you may have been advised for various reasons to upgrade the embedded jre from v1.7 to v1.8.
Once you have swapped in the newer jre under our <install dir>/jre directory and restarted the server, how do you verify it is in effect?

This question is more pertinent to those who employ a "soft-link" from their /jre dir as opposed to actually copying in the new jre into the installation, and you need to verify that the old jre is not being run anymore.
 

Resolution

Look at the bootup routine in our cs_server.log file.
About 18 lines into the bootup output, you should see these lines:


BEFORE

INFO [main] 2018-03-15 15:54:38.498 -0700 BasicServicesModule - Memory=2116812800
INFO [main] 2018-03-15 15:54:38.498 -0700 BasicServicesModule - JRE Version=1.7.0_71
INFO [main] 2018-03-15 15:54:38.498 -0700 BasicServicesModule - JRE Vendor=Oracle Corporation
INFO [main] 2018-03-15 15:54:38.498 -0700 BasicServicesModule - JRE Class Version=51.0
INFO [main] 2018-03-15 15:54:38.498 -0700 BasicServicesModule - JRE VM Mode=64-bit



AFTER

INFO [main] 2018-04-24 13:27:51.070 -0700 BasicServicesModule - Memory=2116812800
INFO [main] 2018-04-24 13:27:51.070 -0700 BasicServicesModule - JRE Version=1.8.0_171
INFO [main] 2018-04-24 13:27:51.070 -0700 BasicServicesModule - JRE Vendor=Oracle Corporation
INFO [main] 2018-04-24 13:27:51.070 -0700 BasicServicesModule - JRE Class Version=52.0
INFO [main] 2018-04-24 13:27:51.070 -0700 BasicServicesModule - JRE VM Mode=64-bit
 

Issue/Introduction

This discusses an in-place upgrade of the jre embedded in Tibco Data Virtualization.
Powered by Wolken Software