Check javamail.jar version
To confirm if you need to replace your javamail.jar file, follow the steps below to check the current version.
If the version number is 1.4.7 or earlier, it is recommended to update it with the attached version (1.6.2).
- Log into the Primary node as root via SSH or Console, pressing ALT+F1 in a Console to log in.
- Open javamail.jar to check version number:
vi /usr/lib/loginsight/application/lib/lib/javamail.jar
- Find and highlight the META-INF/maven/javax.mail/mail/pom.xml file and press enter to open the file.
- Navigate to line 55 to check version.
Example:
<groupId>com.sun.mail</groupId>
<artifactId>all</artifactId>
<version>1.4.7</version>
- Quit the text editor by typing :q + enter twice.
Replace javamail.jar
- Copy the attached javamail.jar to all nodes under the /tmp directory using an SCP utility.
- Log into the Primary node as root via SSH or Console, pressing ALT+F1 in a Console to log in.
- Stop the loginsight service:
service loginsight stop
- Backup the original javamail.jar:
mv /usr/lib/loginsight/application/lib/lib/javamail.jar ~/javamail.jar_backup
- Remove javamail.jar from it's secondary location:
rm /usr/lib/loginsight/application/3rd_party/apache-tomcat-X.X.XX/webapps/ROOT/WEB-INF/lib/javamail.jar
- Copy the new javamail.jar to both known locations by running the following commands:
- copy /tmp/javamail.jar /usr/lib/loginsight/application/lib/lib/javamail.jar
- mv /tmp/javamail.jar /usr/lib/loginsight/application/3rd_party/apache-tomcat-X.X.XX/webapps/ROOT/WEB-INF/lib/javamail.jar
- Start the loginsight service:
service loginsight start
- Repeat steps 1-7 on all other nodes in the vRealize Log Insight cluster.