# WebLogic Server 5.1 Service Pack 6 |  |
4. Contents Installation and removal instructions Installation Installing client jars (optional) Removal Release notes for Service Pack 6 Resolved issues Additional details on new plug-in parameters Additional details on issue WebLogic_RDBMS.jar Known issues Miscellaneous issues and new items BEA WebLogic Enterprise Connectivity README ## 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. Service Packs function for both domestic and exportable versions of WebLogic Server. The service pack download is shipped as a .zip file (weblogic510sp6.zip) and contains: bin/iisproxy.dll bin/iisforward.dll bin/oci734_7/weblogicoci36.dll bin/oci805_7/weblogicoci36.dll bin/oci805_8/weblogicoci36.dll bin/oci815_8/weblogicoci36.dll bin/proxy30.dll bin/proxy35.dll bin/proxy36.dll bin/wlconfig.exe bin/wlntrealm.dll bin/wlserver.exe examples/applets/phonebook1.jsp examples/applets/phonebook2.jsp examples/jsp/tagext/sql/WEB-INF/classes/weblogic/taglib/sql/ConnectionTag.class examples/jsp/tagext/sql/WEB-INF/classes/weblogic/taglib/sql/QueryExtraInfoTag.class examples/jsp/tagext/sql/WEB-INF/classes/weblogic/taglib/sql/QueryTag.class examples/jsp/tagext/sql/WEB-INF/classes/weblogic/taglib/sql/ResultsTag.class examples/webapp/index.html examples/xml/http/StockClient.java lib/aix/libproxy.so lib/aix/libproxy20.so lib/aix/libproxy36.so lib/aix/libproxy40.so lib/aix/mod_wl.so lib/aix/oci805_7/libweblogicoci36.so lib/hpux11/libproxy.sl lib/hpux11/mod_wl_ssl.so lib/hpux11/mod_wl.so lib/linux/mod_wl.so lib/linux/mod_wl_ssl.so lib/linux/mod_wl_ssl_raven.so lib/persistence/WebLogic_RDBMS.jar lib/solaris/libproxy.so lib/solaris/mod_wl.so lib/solaris/mod_wl_ssl.so lib/solaris/mod_wl.ssl_raven.so lib/solaris/oci734_7/libweblogicoci36.so lib/solaris/oci805_7/libweblogicoci36.so lib/solaris/oci805_8/libweblogicoci36.so lib/solaris/oci806_8/libweblogicoci36.so lib/solaris/oci815_8/libweblogicoci36.so lib/tru64unix/mod_wl.so lib/tru64unix/oci805_7/libweblogicoci36.so lib/unixware/oci804_7/libweblogicoci36.so lib/weblogic-tags-510.jar myserver/ca.pem myserver/democert.pem myserver/demokey.pem README.html (this file) README.txt README2.html README2.txt README3.html README3.txt weblogic510sp6.jar weblogic510sp6boot.jar weblogic510sp6JMSClient.jar weblogic510sp6thinClient.jar wlec/README_wlec.html wlec/README_wlec.txt wlec/weblogic.properties wlec/wlec_classes.jar wlec/wlec_examples.jar wlec/wleorb.jar wlec/wlepool.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 weblogic510sp6.jar and weblogic510sp6boot.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 weblogic510sp6.jar and then weblogic510sp6boot.jar. Add the path of weblogic510sp6boot.jar to the beginning of the Java system classpath. Add the path of weblogic510sp6.jar to the beginning of the WebLogic classpath before you start the WebLogic Server:
         $ java ...
             -classpath c:\weblogic\lib\weblogic510sp6boot.jar;
             c:\java\lib\classes.zip;
             c:\weblogic\classes\boot;
             c:\weblogic\eval\cloudscape\lib\cloudscape.jar
             -Dweblogic.class.path=c:\weblogic\lib\weblogic510sp6.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 weblogic510sp6boot.jar file at the start of classpath (to be entered on one line):
         C:\> wlconfig -classpath c:\weblogic\lib\weblogic510sp6boot.jar;
               c:\java\lib\classes.zip;
               c:\weblogic\classes\boot;
               c:\weblogic\eval\cloudscape\lib\cloudscape.jar
   Include the weblogic510sp6.jar file at the start of weblogic.class.path (to be entered on one line):
         C:\> wlconfig -Dweblogic.class.path=c:\weblogic\lib\weblogic510sp6.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 weblogic510sp6.zip
         $ cp /tmp/lib/persistence/WebLogic_RDBMS.jar
        /weblogic/lib/persistence/WebLogic_RDBMS.jar
7. If you are using VisualAge, import lib/persistence/WebLogic_RDBMS.jar into your workspace. The following files are also included in the service pack and are not Java class files. Therefore you need to manually copy them into their appropriate locations to use them. This is optional and files should only be copied if you are interested in resolving an issue. Native NT Executables: bin/wlconfig.exe Issue 31853 bin/wlserver.exe Issue 31853 Plug-ins: Issues 10368,10381, 10610,10680,10885,9536, 10228,10399,10428, 10986,11017,31317,31397 ,31532,28929,31034,31315, 31317,31719,31878, 32053,32132,32133, 32136,32060 bin/iisproxy.dll bin/iisforward.dll bin/proxy30.dll bin/proxy35.dll bin/proxy36.dll lib/aix/libproxy.so lib/aix/libproxy20.so lib/aix/libproxy36.so lib/aix/libproxy40.so lib/aix/mod_wl.so lib/hpux11/libproxy.sl lib/hpux11/mod_wl_ssl.so lib/hpux11/mod_wl.so lib/linux/mod_wl.so lib/linux/mod_wl_ssl.so lib/linux/mod_wl_ssl_raven.so lib/solaris/mod_wl.so lib/solaris/mod_wl_ssl.so lib/solaris/libproxy.so lib/solaris/mod_wl.ssl_raven.so lib/tru64unix/mod_wl.so Database Drivers: Issues 9765,30410, 32061,32063 bin/oci734_7/weblogicoci36.dll bin/oci805_7/weblogicoci36.dll bin/oci805_8/weblogicoci36.dll bin/oci815_8/weblogicoci36.dll lib/aix/oci805_7/libweblogicoci36.so lib/solaris/oci734_7/libweblogicoci36.so lib/solaris/oci805_7/libweblogicoci36.so lib/solaris/oci805_8/libweblogicoci36.so lib/solaris/oci806_8/libweblogicoci36.so lib/solaris/oci815_8/libweblogicoci36.so lib/tru64unix/oci805_7/libweblogicoci36.so lib/unixware/oci804_7/libweblogicoci36.so Files for examples: examples/applets/phonebook1.jsp examples/applets/phonebook2.jsp examples/jsp/tagext/sql/WEB-INF/classes/weblogic/taglib/sql/ConnectionTag.class examples/jsp/tagext/sql/WEB-INF/classes/weblogic/taglib/sql/QueryExtraInfoTag.class examples/jsp/tagext/sql/WEB-INF/classes/weblogic/taglib/sql/QueryTag.class examples/jsp/tagext/sql/WEB-INF/classes/weblogic/taglib/sql/ResultsTag.class examples/webapp/index.html examples/xml/http/StockClient.java For each of these files you can follow the same procedure for deployment. As an example, here are the steps for deploying /weblogic/lib/aix/libproxy40.so. You would deploy this shared library if you are interested in resolving issue 32053, otherwise you would not need to use this file at all. To deploy the lib/aix/libproxy40.so, make a copy of the original to a safe location and then copy lib/aix/libproxy40.so from the service pack to replace the original file that you backed up in another location. For instance, if you installed WebLogic in /weblogic and want to use the NSAPI plugin on AIX (/aix/libproxy40.so), then these commands will backup the original library and copy in the new one:
         $ cp /weblogic/lib/aix/libproxy40.so /weblogic/lib/aix/libproxy40.so.backup
         $ cd /tmp
         $ jar xvf weblogic510sp6.zip
         $ cp /tmp/lib/aix/libproxy40.so /weblogic/lib/aix/libproxy40.so
8. 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 6 ...
## Installing client jars The weblogic510sp6thinClient.jar is included in the weblogic510sp6.zip. The weblogic510sp6thinClient.jar has to be prepended to the CLASSPATH of the client (i.e. $CLASSPATH="weblogic510sp6thinClient.jar:$CLASSPATH"). User's should install this client jar if they wish to resolve one or more of the following JMS issues.
     	33289
     	33794
The weblogic510sp6JMSClient.jar is also included in the weblogic510sp6.zip. The weblogic510sp6JMSClient.jar has to be prepended to the CLASSPATH of the client if the user wants to resolve the following issues:
       	27890
    	30485
    	30527
    	33244
7. ## Removing the Service Pack Shut down the WebLogic Server. Remove weblogic510sp6boot.jar from the start of the Java system classpath and weblogic510sp6.jar from the start of the WebLogic classpath used to start the WebLogic Server. Delete weblogic510sp6boot.jar, weblogic510sp6.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 weblogic510sp6boot.jar from the start of the classpath and remove the weblogic510sp6.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 6 ### Resolved issues: Below are the issues resolved in the current Service Pack and a link to the previous Service Pack release notes. Service Packs are cumulative, so all of the issues in Service Pack 1-5 have been fixed in the latest Service Pack. Service Pack 1-5 ### Service Pack 6 The following areas have had changes: Clustering EJB JMS JSP Plug-ins RMI Servlets Miscellanous Clustering Issues: ISSUE 32603: Fixed a problem with HttpSessionBindingListener not working in a cluster using in-memory replication. ISSUE 34627: Now we ignore case when checking secureProxy parameter in HttpClusterServlet EJB Issues: ISSUE 30857: Fixed bug where Application Exceptions were causing the bean to be deleted. The Bean is being deleted after an AppException and subsequent calls cause a NoSuchObjectException to be thrown. ISSUE 32495: TransactionManager now implements Serializable. ISSUE 33289: When the server had been running for some time, it was running out of file descriptors. There was a problem with the JarLoader loading multiple beans from a jar. Certain client jars were being opened multiple times and consuming all the file descriptors. This has now been fixed. ISSUE 33372: Fixed bug in the compliance checker which allows primary key class of java.lang.Object to work. ISSUE 34184: There was a thread synchronization problem that has been fixed. JMS Issues: ISSUE 27890: With an extremely large number of active durable subscribers the server was hanging. There was a problem with the server running out of execute threads. ISSUE 30351: When JMS was being used indirectly through an EJB, the JMS connection was having a problem; closing itself down after the caller that invoked the EJB first shuts down. ed min ISSUE 30485: Fixed a race condition in JMSMessageConsumer. There was a problem with the server hanging when sending PTP messages. ISSUE 31943: Selector's with compound expressions (specifically with long values) were not working. ISSUE 32634: Dealt with some minor JMS DataBase improvements. An extra database hit was being implied for every 16 message's message id's. This has been fixed. ISSUE 33227: To prevent the JMS server from failing from unusual client behavior, we now prevent messages from being sent/published when more than 75% of the server memory is used up. ISSUE 33794: All TxContext objects being serviced by a single static coordinator. ISSUE 34255: NullPointerException was occuring when trying a getMessage() on a message pointer cursor. ISSUE 34630: This change modified JMS initialization. JSP Issues: ISSUE 30900: We now have JSP caching tags. For more information, see our online docs ISSUE 31384: Using request.getSession(false) when there is no current session was creating a new session. ISSUE 32258: Fixed jsp/plugin syntax(added 1.1 syntax)plus added translation time expression capabilities for plugin applet-parameters ISSUE 33185: When the JSP referred to an EJB and the EJB JAR file is in the Web Application's WEB-INF/lib directory, it was throwing a classcast exception. This has been fixed. ISSUE 33320: There is now the ability to turn on/off HTTP Tunneling. The property weblogic.httpd.tunnelingenabled should be set to true to enable http tunneling. By default it is set to false. Plug-in Issues: ISSUE 031389: Fixed a problem with the iisproxy.dll not finding the location of the iisproxy.ini in the registry. ISSUE 032133: There is a new parameter, defaultfilename, for all plug-ins. (see additional details) ISSUE 032769: Fixed a problem with req.getRemoteAddr() returning the ipaddress of the proxy servers when the requests come via proxy servers. ISSUE 033343: Load balancing has been improved with WebLogic plug-in's support of multiple clusters. ISSUE 033909: IIS users may now proxy by path. See WebLogic's Isapi documentation for more detail RMI Issues: ISSUE 34628: Even when invoked with the -idlNoValueTypes flag."rmic -idl" would still generate some valuetypes. Servlet Issues: ISSUE 30648: Now it is possible to associate a character set to a mimetype (additional details) ISSUE 31292: The relative URL's ./ and ../ were not working with jsp pages. Basically this was caused by the JspStub reinterpreting the URI->JSP filename incorrectly. ISSUE 32058: This fix re-enables reporting of servlet exceptions. ISSUE 32104: Debug messages have been turned off in weblogic.servlet.internal.session.ClusterSessionJDBC. ISSUE 32120: Some classes used in our class loaders would generate class circularity errors. This is now fixed. ISSUE 032157: When the startup servlet was fully initialized the invalidation trigger would start and try to invalidate the existing sessions. This was causing NullPointer exceptions and has been fixed. ISSUE 32409: The servlet engine was losing the post parameters if the servlet was getting an input stream--even if it was reading nothing. ISSUE 32708: This fixes an issue where the originally requested URI was included by the FileServlet, instead of the intended include URI. ISSUE 32859: In order to make the JSP respect empty string query parameters, now add the initParameter "setEmptyStrings=true" to the JSPServlet registration. ISSUE 32873: When the CGI servlet was initiated in a Japanese environment (Windows NT 4.0), it was displaying corrupt strings. ISSUE 32935: This fixed a problem with Brazilian accented characters when the output is larger than 8k. ISSUE 32953: An error occurred when attempting to deploy the cookie war file example with WebLogic Server 5.1 using sp4 and sp5. This has been fixed. ISSUE 33887: Tag library performance suffered due to incorrect specification interpretation. This has been fixed. ISSUE 33775: Users were losing authentication status after their request. Now users using weblogic.serlvet.security.ServletAuthentication are valid for the length of their session. ISSUE 33773: We now accept extended HTTP 1.1 methods. ISSUE 33887: Tag library performance suffered due to incorrect specification interpretation. This has been fixed. ISSUE 34212: Removed unnecessary messages printed to weblogic.log when a http resource could not be found. ISSUE 34307: All .class and generated .java files in .war files are protected. ISSUE 34631: This change is to make environment properties which are set up in web.xml work in init() and destroy() methods of Servlet interface. ISSUE 34633: Fixed compiler message parser so that non-standard messages are still returned to browser. ISSUE 34634: Now web.xml files should reference Web Application 2.2 in their public id (as per the spec). ISSUE 34635: Request dispatching between web applications now works as specified. ISSUE 34703: Made write method non-final to extend the functionality of ServletOutputStream, if it is overridden. ISSUE 34737: Added handling of the old public ID. Now we print a warning if the old public ID is found. ISSUE 34836: We have fixed the XML servlet examples to set content type text/xml. This had to be changed to accomodate alterations to the Servlet engine in behavior of reading raw post data. Miscellaneous Issues: ISSUE 28155: Fixed a bug in adjusting the round trip time for getting the server time from the client. ISSUE 29085: JDBC drivers need to workaround new synchronization in DriverManager. ISSUE 30473: There was a problem with the jts driver doubly registering statements to close. This has been fixed. ISSUE 30768: Fixed a problem with NTRealm not authenticating if Primary Domain Controller is different other than "." (see additional details) ISSUE 30839: Java mail is functioning. We now ship the files that set up its defaults. These are in the service pack jar. ISSUE 31335: Fixed a bug in NTRealm authentication where the system user from the NTRealm is not authenticated. (see additional details) ISSUE 31490: Fixed bug in various JDBC 2.0 calls. ISSUE 31735: In pre-5.1 versions of WebLogic, calls to T3Services.getT3Services() would just return null. In 5.1 (sp3) it began causisng an NPE in RJVMManager. This has been fixed. Issue 32204: All calls to the method DriverManager.getConnection() were removed. The method that is currently used is Driver.connect(). This was done to enhance performance. ISSUE 32313: Now users can pass non-javac specific arguments to the compiler--if they use -J. ISSUE 33244: Messages processed by server session pools were not being acknowledged properly causing messages to reappear even though the they had already been acknowledged. This bug only affected server session pools receiving messages from queues. ISSUE 33258: Sun's ldap does not work with Microsoft Site Server 3.0. There is now a work-around for this problem. (additional details) ISSUE 33081: This fixes a problem created by Service Packs 3 and 4. When a dependency class of the EJB has a primitive array cast, EJB deploy fails, throwing a NPE. ISSUE 33633: This fixes an issue where an existing parameter name is augmented for an included servlet. Previously the parameter remained augmented when returning to the parent servlet from the included servlet. ISSUE 33794: A bug allowed all TxContext objects (ie, all transactions on a particular server) to be serviced by a single static coordinator. This fix now allows one coordinator per UserTransaction per server. ISSUE 34074: Under heavy load users were getting messages with "Expected content length 1000 bytes," when they were only reading -1 bytes messages from the WebLogic Proxy server. This has been fixed. #### Additional details on new plugin parameters: The following parameters have been added and are available for the specified plugins. For information on how to install plug-ins, see the online administrator's guides.
Parameter Name | Defaults | Pertains To | Description
--- | --- | --- | ---
DynamicServerList | ON/OFF (Default: ON) | ISAPI only | It will be "ON" by default. If set to "OFF" then the dynamic list returned by WebLogic with the response will be ignored by the plugin. There will be some shortcomings if the users go for this architecture. First, they cannot add new servers in the cluster as the plugin will try to connect only to the servers in it's static list. Second, if they add a new server to the list and it becomes the secondary, then the plugin will not failover (because of isServerInList) hence sessions will be lost. Finally, if any server goes down the plugin will hit that dead server again and again. This may affect the performance.
| Debug | ON/OFF (Default: OFF) | All Plug-ins | "Debug" will log the following messages to c:\tmp\wlproxy.log on NT and /tmp/wlproxy.log on UNIX: --All headers coming in from the client/browser --All headers sent to WebLogic --All headers returned by WebLogic --All headers returned back to the browser/client --Dynamic Cluster List --Connection info --Other informational, warning and error messages
| DebugConfigInfo | ON/OFF (Default: OFF) | All Plug-ins | This parameter is used to enable the magic query parameter "__WebLogicBridgeConfig". This is used to get details about configuration parameters from the plugin. For example, if you enable "__WebLogicBridgeConfig" by setting DebugConfigInfo=ON and then send a request like: http://www.mywebserver.com:8000/weblogic/foo.jsp?__WebLogicBridgeConfig, then the plug-in will gather the configuration information and return it back to the browser. Note that it will not connect to the WebLogic Server in this case. This parameter is strictly for debugging and the format of the output message can change with releases. For security purposes it is advised to keep this parameter turned OFF in production systems. | DefaultFileName | filename | All Plug-ins | If the URI is "/" then the default filename will be appended to the URI. This prevents redirects from the WebLogic Server. The DefaultFileName should be set to the default welcome page of the WebLogic Server. If the DefaultFileName is set to welcome.html, a http request like "http://somehost/weblogic" will become "http://somehost/weblogic/welcome.html". For this parameter to function, the same file must be specified in the weblogic properties file. For example, in this case, the weblogic properties file must be set to weblogic.httpd.initArgs.file=defaultfilename=welcome.html.
HungServerRecoverSecs | 10:300:600 for min:default:max | All plugins | You should set this to a very large value. If it is less than the time the servlets take to process, then you will see unexpected results. This implementation takes care of the hung or unresponsive servers in the cluster. So the plugin waits for HungServerRecoverSecs for the the server to respond and then declares that server dead and fails over to the next server.
Idempotent | ON/OFF (Default: ON) | All plugins | This is a URL level flag. By default it will be "ON" so if the servers do not respond within HungServerRecoverSecs, the plugins will failover. If set to "OFF" the plugins will not failover. It can be set differently for different URL's or Mime types.
MaxSkips | 5:10:1000 for min:default:max | ISAPI only | Currently if a server goes down the plugin marks it as bad and skips it for the next ten requests for that server. Ten skips doesn't mean ten requests but ten calls to getNextServer(). This happens when the request comes without the cookie, and the PRIMARY and SECONDARY are down. By using this parameter the user can change the MAX_SKIPS for dead servers.

#### 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 weblogic510sp6.jar file as follows:

- Server - Apply weblogic510sp6.jar to weblogic.class.path
- EJB Deployer/Developer - Apply weblogi510sp6.jar to CLASSPATH
- Client - Do not apply weblogic510sp6.jar

  #### Additional details on ISSUES 10228, 10399, 10428, and 10986:

    1. mod_wl.so for standard Apache (non EAPI) installations
    2. mod_wl_ssl.so for Apache + SSL/EAPI installations(Stronghold, modssl etc)
    3. mod_wl_ssl_raven.so for Apache + Raven installations
    mod_wl_ssl_raven.so was required because Raven applies frontpage patches which makes it incompatible with mod_wl_ssl.so
    mod_wl_eapi.so is no longer required. That has been removed from the GNUmakefile.
    These binaries have been certified against C2Net's Stronghold/3.0 (Apache/1.3.12) and Covalent's Raven/1.4.3 (Apache/1.3.12).

    #### Additional details on ISSUE 30648:

    If you set mimeType as the following:
    weblogic.httpd.mimeType.text/x-hdml;charset=Shift_JIS=hdml
    It will be stored as:
    extension="hdml"
    mimeType="text/x-hdml;charset=Shift_JIS"
    So that when you do a context.getMimeType("foo.hdml") it will return: "text/x-hdml;charset=Shift_JIS"

    #### Additional details on ISSUE 31492:

    The following properties need to be set in the weblogic.properties file:
    weblogic.system.startupClass.demojoltpoolStart=\
    bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
    weblogic.system.startupArgs.demojoltpoolStart=\
    poolname=demojoltpool,\
    appaddrlist=//lcsol1:6000,\
    failoverlist=//lcsol1:6000,\
    minpoolsize=1,\
    maxpoolsize=3,\
    recvtimeout=200 (number of seconds)

    #### Additional details on ISSUES 31822:

    The following diagram illustrates the differences between setting secureProxy=ON and secureProxy=OFF.
    secureProxy=ON
    BROWSER<------>HTTPS------>PROXY<------>HTTPS----->WEBLOGIC SERVER CLUSTER
    secureProxy="OFF"
    BROWSER<------>HTTPS------>PROXY<------>HTTP----->WEBLOGIC SERVER CLUSTER

    By passing the secureProxy parameter as an initial argument (in WebLogic init.Args) in the cluster servlet and setting it to ON, SSL between the proxy and the clusters will be enabled. Below is a demonstration of how to turn on the secure proxy feature.

    weblogic.httpd.register.cluster=weblogic.servlet.internal.HttpClusterServlet
    weblogic.httpd.initArgs.cluster=\
    defaultServers=server1:7001:7002|server2:7001:7002,\
    secureProxy=ON

    #### Additional details on ISSUES 31877:

- How to get userid: request.getRemoteUser()
- How to get referred/attempted URL: request.getAttribute("weblogic.formauth.targetURL")

  These will both work on the error page of the webapp.

  #### Additional details on ISSUE 32309:

  The WebLogic Server uses the "dispatch in-thread" optimization to handle in-memory replication traffic. Normally the request that is read off the socket is handled by a different thread once the request has been placed on the ExecuteQueue by the socket reader thread. In handling the "in-memory" replication traffic, the updates to the objects that are replicated need to be performed in a timely fashion. Hence the "dispatch in-thread" pattern is used to avoid a context switch and thread contention that is incurred by this request being placed on the ExecuteQueue. However, on rare occasions this pattern results in a deadlock when both sides of the connection try and update objects on behalf of each other. The deadlock has been fixed with this change by introducing an alternate ExecuteQueue--the NonBlockingExecuteQueue to service message traffic that is guaranteed not to block. This queue is used *only* by the Weblogic Server internally i.e. application requests are never placed on this queue--they are handled by placing them on the regular ExecuteQueue.

  #### Additional details on ISSUE 32806:

  Setting up access log rotation
  Note: Access log rotation requires WebLogic Server 5.1, Service Pack sp4 or later.

  Access log rotation allows you to rotate your HTTP access log when it reaches a certain size or after a specified amount of time has passed. When the access log rotates, a new log file with a new file name is started. The access log's file name includes a numeric portion that is incremented upon each rotation.

  To set up access log rotation, set the following properties (in addition to those properties you set to enable access logs) in your weblogic.properties file:

  weblogic.httpd.logRotationType

  Set to date to rotate your access log by date. If you choose this option, you must also set two additional properties: weblogic.httpd.logRotationPeriodMins and weblogic.httpd.logRotationBeginTime.

  Set to size to rotate your access log when it exceeds a certain size. If you choose this option, you must also set the weblogic.httpd.maxLogFileSizeKBytes property. The default value is size.

  weblogic.httpd.logRotationPeriodMins

  If you are rotating your access log by date, set this to the number of minutes after which the access log will rotate. (1440 minutes = 24 hours, 100080 minutes = 1 week). The default value is 1440.

  weblogic.httpd.logRotationBeginTime

  Sets the date when the first access log rotation will occur. If you do not set this property, the access log rotates after the amount of time specified with the weblogic.httpd.logRotationPeriodMins property. Enter the date using the java.text.SimpleDateFormat, MM-dd-yyyy-k:mm:ss. See the javadocs for the java.text.SimpleDateFormat class for more details. For example: 11-24-2000-12:30:00

  If, when you start WebLogic Server, this date has already passed, the first access log rotation will occur on the day you start WebLogic Server, at the hour, minute, and second specified by weblogic.httpd.logRotationBeginTime.

  weblogic.httpd.maxLogFileSizeKBytes

  Set to the maximum size, in kilobytes, for your access log file. When the access log reaches this size, it is rotated. If set to 0 (the default value) access log files do not rotate based on size. This property is ignored when weblogic.httpd.logRotationType is set to date.

  #### Additional details on ISSUE 33258:

  Sun's ldap does not work with Microsoft's Site Server, but Netscape's ldap 4.1 does. Please follow the following steps to configure WLS5.1 with MS Site Server 3.0.

  1. Download Netscape's ldap 4.1 from Netscape's web site http://www.iplanet.com/downloads/developer/index.html and decompress it to your local directory.

  2. Include Netscape's ldap4.1's jar files (ldapfilt.jar, ldapjdk.jar, ldapsp.jar) from your local directory in WEBLOGICCLASSPATH in the startweblogic startup script.

  3. Add the following line to your ldaprealm.properties file. weblogic.security.ldaprealm.factory=com.netscape.jndi.ldap.LdapContextFactory

  #### Additional details on ISSUE 31335 and ISSUE 30768:

  1. The "ntrealm.properties" file is no longer necessary for single domain systems.
  In the case of a single domain, the ntrealm.properties file need to be either removed or renamed from the system. Search for the existence of this file by doing a search on the root directory.
  2. If an additional trusted domain is to be added to the default domain, the ntrealm.properties file is still needed. In this case, in the ntrealm.properties, give the hostname of the other, trusted domain (note: not the domain name, the hostname).
  3. How ever the following property needs to be set in the weblogic.properties file in either case:
  weblogic.security.realmClass=weblogic.security.ntrealm.NTRealm
  4. For details on NTRealm see online docs.

  #### Known Issues

  ISSUE 34836 : For the HTTP XML example the "Content-Type" must be set to something other than the default value. For this example it has been set to text/xml. This shall be fixed in Service Pack 7.

  ISSUE 30561 : There was a typo in the weblogic.properties file shipped with the release.

  The weblogic.properties file with the release says:

  # Add a TXDataSource for the connection pool:
  #weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.demoPool=demoPool

  It should actually be:

  # Add a TXDataSource for the connection pool:
  #weblogic.jdbc.TXDataSource=demoPool

  #### 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 6".

- We have included demo security certificates with extended expiration dates in this release.

- We have included Apache plugins for Solaris, HP, AIX and Linux in this release.

  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 09/29/2000