Patch Name: PHSS_23998 Patch Description: s700_800 11.04 VirtualVault4.0 JSS start failure Creation Date: 01/05/16 Post Date: 01/05/18 Hardware Platforms - OS Releases: s700: 11.04 s800: 11.04 Products: VirtualVault A.04.00 US/Canada Release VirtualVault A.04.00 International Release Filesets: VaultJS.JS-CORE,fr=A.04.00,fa=HP-UX_B.11.04_32/64,v=HP Automatic Reboot?: Yes Status: General Release Critical: No Category Tags: defect_repair general_release Path Name: /hp-ux_patches/s700_800/11.X/PHSS_23998 Symptoms: PHSS_23998: Modification of obj.conf causes inability to start/remove java servlet server. PHSS_22445: When starting a Java Servlet Server through the VirtualVault administration user interface, the Java Servlet Server fails to start even though it appears to start successfully. PHSS_22152: When Web Proxy is installed and configured for use with a outside web server, if a Java Servlet Server has been configured, the servlet server may not start. The Servlet Server may fail to run (due to Java configuration problems) even though the admin interface reports the Servlet Server started. If Web Proxy is installed and configured with an outside web server and a new Java Servlet server is to be installed, the installation process may fail. PHSS_21011: The Java Servlet Server component (VaultJS) on VV 4.0 does not provide for latest Java Servlet Development Kit. Defect Description: PHSS_23998: Custom modified obj.conf, from name=jsproxy to name='jsproxy'. In jsscheck.sh and remove.sh scripts, they only look at name=jsproxy and name="jsproxy" but not name='jsproxy'. PHSS_22445: When the java configuration is incorrect or classpath setting is incorrect, the Java process will not start. The admin start interface just checks for the return value from the SHELL to see that the JVM was forked. However, if there is a Java configuration problem the jsswd (watchdog) will attempt to restart the JVM upto MAXEXEC defined in the /sbin/init.d startup script. PHSS_22152: Both the Web Proxy (vaultWP) and the Java Servlet (vaultJS) place entries in the outside web servers obj.conf file. vaultJS searches the obj.conf file for a send-proxy entry and if found, assumes that the entry is for vaultJS. vaultWP now uses the same type of entry, so the vaultJS configuration logic searches the obj.conf file and if there exists an entry for vaultWP, vaultJS will read the vaultWP entry and try to use the vaultWP entry information to start the vaultJS server. PHSS_21011: The existing VV 4.0 JSDK2.0 servlet development kit does not support new features and improvements such as Java Server Pages. SR: 8606194163 8606154942 8606127919 8606161714 Patch Files: VaultJS.JS-CORE,fr=A.04.00,fa=HP-UX_B.11.04_32/64,v=HP: /opt/vaultJS/bin/remove.sh /opt/vaultJS/bin/start.sh /etc/opt/vaultJS/jsdk.conf /etc/opt/vaultJS/jswdk.conf /etc/opt/vaultJS/jss1441.template /etc/auth/system/files.fcdb/20.packages/vaultJS.fcdb /etc/auth/system/files.fcdb/20.packages/SunJSDK.fcdb /etc/auth/system/files.fcdb/20.packages/HPJavaVM.fcdb /opt/vaultJS/bin/jsscheck.sh /opt/vaultJS/bin/install.sh /opt/vaultJS/bin/jss.create /var/opt/vaultTS/inside/vault/bin/web-servlet /var/opt/vaultTS/inside/vault/loc/C/include/ web-sletattr.html /usr/lib/nls/C/js-admin.cat /opt/vaultJS/bin/jsswd what(1) Output: VaultJS.JS-CORE,fr=A.04.00,fa=HP-UX_B.11.04_32/64,v=HP: /opt/vaultJS/bin/remove.sh: @(#)90 1.8 src/shells/remove.sh, vaultJS, vaultJS_ 4.0 05/08/01 14:13:45 PHSS_23998 /opt/vaultJS/bin/start.sh: @(#)92 1.6 start.sh, vaultJS, vaultJS_4.0 05/07/01 14:15:09 PHSS_23998 92 1.1 src/shells/start.sh, vaultJS, vaultJS_dev, 302a01 09/27/00 11:02:00 /etc/opt/vaultJS/jsdk.conf: @(#)11 1.2 jsdk.conf, vaultJS, vaultJS_4.0 02/17/0 0 11:07:32 /etc/opt/vaultJS/jswdk.conf: @(#)12 1.5 jswdk.conf, vaultJS, vaultJS_4.0 09/27/ 00 00/09/27 11:20:03 PHSS_22445 /etc/opt/vaultJS/jss1441.template: @(#)66 1.13 jss1441.template, vaultJS, vaultJS_4.0 08/16/00 08:29:17 /etc/auth/system/files.fcdb/20.packages/vaultJS.fcdb: @(#)97 1.11 vaultJS.fcdb, vaultJS, vaultJS_4.0 02/ 17/00 11:22:29 /etc/auth/system/files.fcdb/20.packages/SunJSDK.fcdb: @(#)78 1.6 SunJSDK.fcdb, vaultJS, vaultJS_4.0 02/2 2/00 15:22:45 /etc/auth/system/files.fcdb/20.packages/HPJavaVM.fcdb: @(#)77 1.5 HPJavaVM.fcdb, vaultJS, vaultJS_4.0 02/ 22/00 07:23:01 /opt/vaultJS/bin/jsscheck.sh: @(#)73 1.8 jsscheck.sh, vaultJS, vaultJS_4.0 05/07 /01 14:17:18 PHSS_23998 73 1.3 src/shells/jsscheck.sh, vaultJS, vaultJS_de v, 302a01 11/29/98 21:40:05 /opt/vaultJS/bin/install.sh: @(#)89 1.17 install.sh, vaultJS, vaultJS_4.0 08/03 /00 13:36:37 89 1.6 src/shells/install.sh, vaultJS, vaultJS_dev 11/29/98 19:45:14 /opt/vaultJS/bin/jss.create: @(#)70 1.6 jss.create, vaultJS, vaultJS_4.0 02/17/ 00 11:30:48 /var/opt/vaultTS/inside/vault/bin/web-servlet: @(#)82 1.8.1.6 src/admin/cgi/servlet/web-servlet.c , vaultJS, vaultJS_4.0 02/17/00 14:17:20 VVO S 11.04 PHSS_21011 /var/opt/vaultTS/inside/vault/loc/C/include/ web-sletattr.html: 80 1.5 web-sletattr.html, vaultJS, vaultJS_4.0 02/ 10/00 14:17:55 -- /usr/lib/nls/C/js-admin.cat: None /opt/vaultJS/bin/jsswd: @(#)36 1.4 src/jsswd/jsswd.h, vaultJS, vaultJS_4.0 12/03/98 18:01:52 @(#)35 1.14 src/jsswd/jsswd.c, vaultJS, vaultJS_4. 0 02/10/00 07:56:53 VVOS 11.04 PHSS_21011 cksum(1) Output: VaultJS.JS-CORE,fr=A.04.00,fa=HP-UX_B.11.04_32/64,v=HP: 3941585300 5126 /opt/vaultJS/bin/remove.sh 1659221819 1470 /opt/vaultJS/bin/start.sh 3641716829 1325 /etc/opt/vaultJS/jsdk.conf 3238114144 1863 /etc/opt/vaultJS/jswdk.conf 3599731390 3400 /etc/opt/vaultJS/jss1441.template 3129799948 4709 /etc/auth/system/files.fcdb/20.packages/ vaultJS.fcdb 647149408 141741 /etc/auth/system/files.fcdb/20.packages/ SunJSDK.fcdb 4091785020 623004 /etc/auth/system/files.fcdb/20.packages/ HPJavaVM.fcdb 583457639 4511 /opt/vaultJS/bin/jsscheck.sh 1996913966 12443 /opt/vaultJS/bin/install.sh 3824469301 1020 /opt/vaultJS/bin/jss.create 2836903261 45193 /var/opt/vaultTS/inside/vault/bin/ web-servlet 1100433418 5267 /var/opt/vaultTS/inside/vault/loc/C/include/ web-sletattr.html 201450074 1263 /usr/lib/nls/C/js-admin.cat 783837932 36979 /opt/vaultJS/bin/jsswd Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_21011 PHSS_22152 PHSS_22445 Equivalent Patches: None Patch Package Size: 910 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHSS_23998 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHSS_23998.depot By default swinstall will archive the original software in /var/adm/sw/save/PHSS_23998. If you do not wish to retain a copy of the original software, use the patch_save_files option: swinstall -x autoreboot=true -x patch_match_target=true \ -x patch_save_files=false -s /tmp/PHSS_23998.depot WARNING: If patch_save_files is false when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. For future reference, the contents of the PHSS_23998.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHSS_23998.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_23998.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: To utilize the new JSWDK the system administrator must obtain and install the UNIX version of the JSWDK 1.0.1 (jswdk1_0_1-solsparc_tar.Z compressed tar file) from the Sun (http://java.sun.com/products/jsp/download.html) site. The administrator has the option to install the JSWDK 1.0.1 using the default JSDK_HOME and JAVA_HOME path identified in the /etc/opt/vaultJS/jswdk.conf file or modify the JSDK_HOME and JAVA_HOME path attribute according to local site requirements. Configuration file attribute details are defined in the /etc/opt/vaultJS/jsdk.conf and jswdk.conf Data Type Definition (DTD) section. This patch requires a system reboot. Installing this patch does not change the configuration or operation of existing servlet servers. If you remove this patch you will need to change the /sbin/init.d/jssXXXX startup files for servers created since the installation of this patch. The change consists of removing the "-d $SERVLETDIR" argument in the SHELL function StartJavaServlet.