# WebLogic Server 5.1 Service Pack 2 |  |
4. Contents Installation and removal instructions Installation Removal Release notes for service pack 2 Resolved issues Additional details on issue WebLogic_RDBMS.jar Known issues Miscellaneous issues ## Contents This service pack contains files that resolve issues pertaining to the released product. A detailed list of these issues is provided in this document. The service pack download is shipped as a .zip file (weblogic510sp2.zip) and contains: README.html (this file) README.txt images/bea_logo_small.gif bin/proxy36.dll lib/persistence/WebLogic_RDBMS.jar lib/solaris/mod_wl.so lib/solaris/mod_wl_eapi.so weblogic510sp2.jar weblogic510sp2boot.jar ## Installation and removal instructions ### Installation Read this document and the release notes. Unzip the contents of the service pack into a temporary directory, such as /temp. Copy weblogic510sp2.jar and weblogic510sp2boot.jar from /temp to a location where it can be referenced by your WebLogic Server installation. If you have installed WebLogic Server in its default location of /weblogic, then an appropriate place to copy the .jar file would be to the directory /weblogic/lib. If you are running the installation from a drive that is not writable, then you will need to copy the service pack jar to a directory outside of the installation, but whose path is accessible. The directory of the weblogic.properties file that you are using to start WebLogic Server is an alternative. Also, if the server is running under Java 2, the jar must be in a directory that has been made accessible in the security policy file. If you are using VisualAge, import both jars to your workspace, first weblogic510sp2.jar and then weblogic510sp2boot.jar. Add the path ofweblogic510sp2boot.jar to the beginning of the Java system classpath. Add the path of weblogic510sp2.jar to the beginning of the WebLogic classpath before you start the WebLogic Server:
         $ java ...
             -classpath c:\weblogic\lib\weblogic510sp2boot.jar;
             c:\java\lib\classes.zip;
             c:\weblogic\classes\boot;
             c:\weblogic\eval\cloudscape\lib\cloudscape.jar
             -Dweblogic.class.path=c:\weblogic\lib\weblogic510sp2.jar;
             c:\weblogic\classes;
             c:\weblogic\license;c:\weblogic\lib\weblogicaux.jar;
             c:\weblogic\myserver\serverclasses
             ... weblogic.Server
5. You can do this by editing the command line script that you use to start the WebLogic Server, as described in the Installation Guide, Setting up and Starting WebLogic Server 5.1. If you are running on NT and are using either the Start Menu commands or running as an NT Service, you need to use wlconfig.exe to set values for classpath, weblogic.class.path and JAVA_HOME. Save the current values of your configuration to a file before making changes in case you need to revert your changes:
         C:\> wlconfig > config.txt
   Include the weblogic510sp2boot.jar file at the start of classpath (to be entered on one line):
         C:\> wlconfig -classpath c:\weblogic\lib\weblogic510sp2boot.jar;
               c:\java\lib\classes.zip;
               c:\weblogic\classes\boot;
               c:\weblogic\eval\cloudscape\lib\cloudscape.jar
   Include the weblogic510sp2.jar file at the start ofweblogic.class.path (to be entered on one line):
         C:\> wlconfig -Dweblogic.class.path=c:\weblogic\lib\weblogic510sp2.jar;
               c:\weblogic\license;c:\weblogic\classes;
               c:\weblogic\myserver\serverclasses;
               c:\weblogic\lib\weblogicaux.jar
   Next, set JAVA_HOME to point to a JDK that you have installed, as the JREs that were shipped with the distribution do not support multi-byte character sets:
         C:\> wlconfig -JAVA_HOME c:\java117
6. The file lib/persistence/WebLogic_RDBMS.jar will need to be copied to your /weblogic/lib/persistence directory if you are developing or deploying EJBs, and are interested in resolving issues related to WebLogic_RDBMS.jar. To deploy the lib/persistence/WebLogic_RDBMS.jar, make a copy of the original to a safe location and then copy lib/persistence/WebLogic_RDBMS.jar from the service pack to replace the original file that you backed up in another location. For instance, if you installed WebLogic in /weblogic, here are the sample commands:
         $ cp /weblogic/lib/persistence/WebLogic_RDBMS.jar
        /weblogic/lib/persistence/WebLogic_RDBMS.jar.510
         $ cd /tmp
         $ jar xvf weblogic510sp2.zip
         $ cp /tmp/lib/persistence/WebLogic_RDBMS.jar
        /weblogic/lib/persistence/WebLogic_RDBMS.jar
7. Once you have made these changes and started the Server, you can check that installation was successful by checking the server version:
         java weblogic.Admin t3://Host:Port VERSION
   should return
         WebLogic Build: 5.1.0 Service Pack 2 ...
7. ### Removing the Service Pack Shut down the WebLogic Server. Remove weblogic510sp2boot.jar from the start of the Java system classpath and weblogic510sp2.jar from the start of the WebLogic classpath used to start the WebLogic Server. Delete weblogic510sp2boot.jar, weblogic510sp2.jar and any other files unzipped from the service pack download. If you used wlconfig.exe to make changes to your installation configuration as described under Installation, change your configuration back to the previous values: reset the JAVA_HOME if you changed it, remove the weblogic510sp2boot.jar from the start of the classpath and remove the weblogic510sp2.jar from the start of the weblogic.class.path. Restore any non-java class files that you replaced in the installation process (eg WebLogic_RDBMS.jar) You can then start the WebLogic Server without the service pack. Once you have made these changes and started the Server, you can check that the service pack is no longer in use by checking the server version, as shown below:
         java weblogic.Admin t3://Host:Port VERSION
## Release notes for WebLogic Server 5.1 service pack 2 ### Resolved issues Below are the issues resolved in each of the Service Pack releases. Service Packs are cumulative, so all of the issues listed below are included in the latest Service Pack. Service Pack 1 Service Pack 2 ### Service Pack 1 ISSUE 9488/9459/9512: Fixed a problem with clients not registering sockets correctly ISSUE 9665: Fixed session ID length problem so that it may be modified by session.sessionIDLengthURL ISSUE 9731: Fixed an IOExecption in SSL ISSUE 9737 & 10117: Fixed a problem with Verisign's global server id ISSUE 9879: Fixed a problem with NoSuchObjectException being thrown under concurrent entity access ISSUE 9902: Fixed a problem with ejbc and spaces in the classpath ISSUE 9936: Fixed a problem with debug messages being printed by default in servlets and socket communications ISSUE 9999: Fixed a post-compilation problem with postStoreGeneration (additional details) ISSUE 10032: Fixed a problem with rolling back transactions immediately which have been marked for rollback ISSUE 10132: Fixed an IOException exception that was being raised in FileServlet when serving multiple requests ISSUE 10138: Fixed a problem with some broken casts in the JDBC20 jts driver ISSUE 10149: Fixed a problem where debuggers were not notified of dynamic class loads ISSUE 10159: Fixed the rewriting of empty tags and namespaces which caused problems for XSL in combination with JSP ISSUE 10170: Fixed a problem with WebApp formauth ISSUE 10173: Fixed a problem with server-side stub clustering ISSUE 10175: Fixed a problem where an entire JSP file within a tag extension caused the compilation to fail ISSUE 10186: Fixed a problem with runtime evaluated attributes failing to compile when %lt;%=%%gt; is used instead of <%=%> for XML compliance ISSUE 10194: Allowed for isolation to be set in Session and Bean Managed Entity Beans ISSUE 10214: Fixed a problem with encoding when dealing with post data that is a form ISSUE 10340: Fixed a rebuild problem with taglib/jsp ### Service Pack 2 ISSUE 8463: Fixed a problem where ejbc silently accepted the lack of a weblogic-ejb-jar.xml file ISSUE 9282: Fixed a problem with EJB deployer element detail view not tracking the selected element correctly ISSUE 9665: Fixed a problem with our URL rewrites making it tough for WAP phones ISSUE 9692: Fixed a problem with getting a java.lang.ArrayIndexOutOfBoundsException when deploying EJB ISSUE 9945: Fixed a problem in the console after peer gone encountered by a cluster member ISSUE 9997: Fixed a problem with EJB Wizard throwing an exception when loading a jar file ISSUE 10027: Fixed EJB1.1 compliance check to allow transient Context in Entity Beans ISSUE 10054: Provide row locking for finders to simlulate passimistic locking ISSUE 10071: Fixed a problem with hot deploying a servlet in the Console ISSUE 10110: Fixed a problem with allowing access to EJBC compiler options ISSUE 10120: Fixed a problem with ambiguous homes not doing user selections ISSUE 10121: Fixed a problem with incorrect path to javac in the deployer tool ISSUE 10143: Fixed a problem with jhtml ISSUE 10172: Changed session-timeout from web.xml to minutes (converts to seconds) ISSUE 10189: Fixed a problem with console assuming t3s port being the t3 port erroneously ISSUE 10190: Fixed a problem with missing remote interface class not being properly reported ISSUE 10245: Fixed registering of weblogic.servlet.utils.ServletStartup failing to recognize the servlet alias name ISSUE 10257: Fixed a problem with JMS ObjectMessage.getObject returning null when called from server side code ISSUE 10258: Fixed a problem with StreamMessage throwing an exception on read when used in an EJB or servlet ISSUE 10262: Fixed an ArrayIndexOutOfBoundsException which was occurring during deployment ISSUE 10264: Fixed a problem with tx isolation level not having corresponding xml writing classes ISSUE 10279: Fixed a problem with an assertion error being thrown when certain files are added to the jar ISSUE 10283: Fixed a problem with timing out of read-only beans ISSUE 10294: DDConverter should just do the simple thing when mapping roles to principals ISSUE 10323: Improved documentation for LogOutputStream (replacement for LogServicesDef) ISSUE 10331: Fixed a problem with descriptors not being created early enough in the Provider project ISSUE 10334: Fixed a problem with setSessionContext not being called if initial-beans-in-free-pool is set to some value greater than 0. ISSUE 10348: Fixed a problem with MM:EndLock not being generated for useBean tag ISSUE 10360: Fixed a problem with RDBMS Deployer UI not holding container managed field mappings ISSUE 10368: Fixed a problem with the POSIX socket muxer losing threads ISSUE 10381: Fixed a problem with messed up headers to the browser from NSAPI plug-in causing problems with IE5 ISSUE 10384: Fixed a problem with the CMP finders which return Collections not working correctly ISSUE 10385: NFS is no longer required for EJBs to work in a clustered environment ISSUE 10417: Fixed problem with EJB Deployer and the save menu item ISSUE 10546: Fixed a problem with finding taglibs if the home is different from current dir #### Additional details on WebLogic_RDBMS.jar: We include the lib/persistence/WebLogic_RDBMS.jar file in the service pack to resolve issue 9999. This jar file requires special attention because it is not a jar file that gets pre-appended to any classpaths. Instead, this EJB CMP jar file just needs to replace the original WebLogic_RDBMS.jar file in the lib/persistence directoy. No modifications are needed to the java or weblogic classpaths. It is important to note that EJBs must be recompiled if the new WebLogic_RDBMS.jar file is installed from a service pack. They must also make sure that their classpaths are set correctly. In general, if you wish to resolve issue 9999, apply the weblogic510sp2.jar file as follows: Server - Apply weblogic510sp2.jar to weblogic.class.path EJB Deployer/Developer - Apply weblogi510sp2.jar to CLASSPATH Client - Do not apply weblogic510sp2.jar #### Known Issues 1. Issue 10249 - Fixed a problem with losing client connections after a short period of time. This will be fixed in Service Pack 3. 2. Issue 10308 - Fixed a problem with receiving assertion errors from MBuf.getHeader in ConnectionManagerLocal. This will be fixed in Service Pack 3. #### Miscellaneous General files included with every service pack: utils/version.class This file will update the message returned when you use the version utility to show that you are using "Service Pack 2". Copyright © 2000 BEA Systems, Inc. All rights reserved. Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher. Last updated 04/20/2000