Michael sent me a mail with a screenshot where it was showing a dialog box with
The publisher could not be verified, Are you sure you want to install this software.
Name: oaj2se.exe
Publisher: Unknown publisher
There were two buttons Install and Don't Install.
The DBAs had recently migrated from jintiator to Sun JRE plugin on this instance. I checked by downloading JRE directly http://dev11i.justanexample.com/OA_HTML/oaj2se.exe
appesx76@tnsd2005 $ file j2se16014.exe.old
j2se16014.exe.old: executable shell script
$ head oaj2se.exe
#!/bin/sh
PATH=/usr/bin:/bin
umask 022
release_comp() {
if [ "$1" = "$2" ] ; then
echo "eq"
else
lrel=`printf "%s\n%s\n" $1 $2 | \
sort -t . -k 1,1n -k 2,2n -k 3,3n -k 4,4n -k 5,5n | \
appesx76@tnsd2005 $ head -100 j2se16014.exe.old
#!/bin/sh
PATH=/usr/bin:/bin
umask 022
release_comp() {
if [ "$1" = "$2" ] ; then
echo "eq"
else
lrel=`printf "%s\n%s\n" $1 $2 | \
sort -t . -k 1,1n -k 2,2n -k 3,3n -k 4,4n -k 5,5n | \
head -1`
if [ "$1" = "${lrel}" ]; then
echo "lt"
else
echo "gt"
fi
fi
}
.
.
.
This was strange. That file is supposed to be binary. So I downloaded Sun JRE client 1.6.0_14. Sure enough the file sizes differed. I uploaded the file and did these steps:
Login as applmgr on the web tier
cp jre-6uX-windows-i586-p.exe $COMMON_TOP/util/jinitiator/j2se160x.exe
X is the latest update version, for example:
mv jre-6u14-windows-i586-p.exe $COMMON_TOP/util/jinitiator/j2se16014.exe
cp $COMMON_TOP/util/jinitiator/j2se16014.exe $OA_HTML/oaj2se.exe
I stopped Apache.
Cleared Apache Cache: rm -rf $COMMON_TOP/_pages
Restarted Apache.
The problem was resolved. I informed the DBA team about this issue so that they could avoid this in future. Most probably the DBA got mixed up between Sun JRE migration and JDK upgrade. Sun JRE migration requires JRE package on client PC, which runs on Windows. Sun JDK upgrade requires JDK which runs on server, which is Solaris SPARC 10 in our case.
No comments:
Post a Comment