WebLogic 4.5.1 Service Pack 14

Contents

Installation and removal instructions

Installation

JMS and Issues 33289, 33794

Removal

Release notes for service pack 14

Resolved issues

Additional details on new plugin parameters

Additional details on issues 5670 & 6602

Additional details on issue 7526

Additional details on issue 7599

Additional details on issue 8322

Additional details on issue 30648

Known issues

Miscellaneous issues

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 (weblogic451sp14.zip) and contains:

SERVICEPACK_README.html (this file)
SERVICEPACK_README.txt
images/bea_logo_small.gif
bin/iisproxy.dll
bin/iisforward.dll
bin/proxy30.dll
bin/proxy35.dll
bin/proxy36.dll
bin/stackdump.dll
bin/stackdump_g.dll
bin/wlntio.dll
bin/wlntio_jni1_1.dll
bin/wlntio_jdk12.dll
examples/security/rdbmsrealm/RdbmsRealm.java
examples/security/rdbmsrealm/weblogic.realm_properties
lib/aix/libproxy36.so
lib/aix/libproxy40.so
lib/aix/libweblogicoci34.so
lib/hpux10/libproxy.sl
lib/hpux11/libmuxer.sl
lib/hpux11/libproxy.sl
lib/hpux11/libweblogicunix1.sl
lib/hpux11/mod_wl.so
lib/hpux11/mod_wl_ssl.so
lib/hpux11/mod_wl_ssl_raven.so
lib/linux/mod_wl.so
lib/linux/mod_wl_ssl.so
lib/linux/mod_wl_ssl_raven.so
lib/solaris/libmuxer.so
lib/solaris/libproxy.so
lib/solaris/libstackdump.so
lib/solaris/libweblogicunix1.so
lib/solaris/mod_wl.so
lib/solaris/mod_wl_ssl.so
lib/solaris/mod_wl_ssl_raven.so
myserver/ca.pem
myserver/democert.pem
myserver/demokey.pem
weblogic451sp14.jar
weblogic451sp14boot.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 weblogic451sp14.jar and weblogic451sp14boot.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, you must first remove the file weblogic.rmi.internal.OIDManager$ServerIdentityWrapper.class from your workspace. Then, import both jars to your workspace, first weblogic451sp14.jar and then weblogic451sp14boot.jar.
Add the path weblogic451sp14boot.jar to the start of the Java system classpath and weblogic451sp14.jar to the start of the WebLogic classpath before you start the WebLogic Server:
```
  $ java ... 
      -classpath c:\weblogic\lib\weblogic451sp14boot.jar;
      c:\java\lib\classes.zip;
      c:\weblogic\classes\boot;
      c:\weblogic\eval\cloudscape\lib\cloudscape.jar
      -Dweblogic.class.path=c:\weblogic\lib\weblogic451sp14.jar;
      c:\weblogic\classes;
      c:\weblogic\license;c:\weblogic\lib\weblogicaux.jar;
      c:\weblogic\myserver\serverclasses 
      ... weblogic.Server
```
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 4.5. If you do not require the fix related to issue 7554, then adding weblogic451sp14boot.jar to the front of the Java system classpath is optional.
If you are running on NT and are using either the Start Menu commands or running as an NT Service, you need to use t3config.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:\> t3config > config.txt
```
Include the weblogic451sp14boot.jar file at the start of classpath (to be entered on one line):
```
  C:\> t3config -classpath=c:\weblogic\lib\weblogic451sp14boot.jar;
        c:\java\lib\classes.zip;
        c:\weblogic\classes\boot;
        c:\weblogic\eval\cloudscape\lib\cloudscape.jar
```
Include the weblogic451sp14.jar file at the start ofweblogic.class.path (to be entered on one line):
```
  C:\> t3config -Dweblogic.class.path=c:\weblogic\lib\weblogic451sp14.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:\> t3config -JAVA_HOME c:\java117
```
If you are using a 1.2 JDK, do the following:
```
  C:\> t3config -JAVA_HOME c:\java\java122\jre
```
Make sure that the $JAVA_HOME/bin (%JAVA_HOME%\bin) contains java.dll, as this is needed for all JDK 1.2.x versions.
The following files 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 completely optional and files should only be copied if you are interested in resolving the corresponding issue.
bin/iisforward.dll (issue 33909 31389)
bin/iisproxy.dll (issue 7399)
bin/proxy30.dll (issue 7398)
bin/proxy35.dll (issue 7398)
bin/proxy36.dll (issue 7398)
bin/stackdump.dll (issue 7398)
(issue 36076 bin/stackdump_g.dll (issue 7398)
(issue 36076 bin/wlntio.dll (issue 35012)
bin/wlntio_jni1_1.dll (issue 35012)
bin/wlntio_jdk12.dll (issue 35012)
examples/security/rdbmsrealm/RdbmsRealm.java (issue 8322)
examples/security/rdbmsrealm/weblogic.realm_properties (issue 8322)
lib/aix/libproxy36.so (issue 7366)
lib/aix/libproxy40.so (issue 7366)
lib/aix/libweblogicoci34.so (issue 7224)
lib/hpux10/libproxy.sl (issue 10005)
lib/hpux11/libmuxer.sl (issue 5653)
lib/hpux11/libproxy.sl (issue 7353)
lib/hpux11/libweblogicunix1.sl (issue 9517)
lib/hpux11/mod_wl.so(issue 32614 34596 34833 35240)
lib/hpux11/mod_wl_ssl.so (issue 32614 34596 34833)
lib/hpux11/mod_wl_ssl_raven.so (issue 32614 34596 34833)
lib/linux/mod_wl.so (issue 32614 34596 34833)
lib/linux/mod_wl_ssl.so (issue 32614 34596 34833)
lib/linux/mod_wl_ssl_raven.so (issue 32614 3 4596 34833)
lib/solaris/libmuxer.so (issue 34596)
lib/solaris/libproxy.so (issue 7398)
lib/solaris/libweblogicunix1.so (issue 8559)
lib/solaris/mod_wl.so (issue 8836)
lib/solaris/mod_wl_ssl.so (issue 32614 34596 34833)
lib/solaris/mod_wl_ssl_raven.so (issue 32614 34596 34833)
lib/stackdump.so (issue 36076
myserver/ca.pem (This file is a new demo certification, use it if your certification has expired)
myserver/democert.pem(This file is a new demo certification, use it if your certification has expired)
myserver/demokey.pem(This file is a new demo certification, use it if your certification has expired)

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/libproxy.so. You would deploy this shared library if you are interested in resolving issue 7366, otherwise you would not need to use this file at all.
To deploy the libproxy.so, make a copy of the original to a safe location and then copy libproxy.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/libproxy.so), then these commands will backup the original library and copy in the new one:
```
  $ cp /weblogic/lib/aix/libproxy.so /weblogic/lib/aix/libproxy.so.451
  $ cd /tmp
  $ jar xvf weblogic451sp14.zip
  $ cp /tmp/lib/aix/libproxy.so /weblogic/lib/aix/libproxy.so
```
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: 4.5.1 Service Pack 14 ...
```

Resolved JMS problems and Issues 33289, 33794

In order to fix the issues listed below, it is necessary to upgrade the client. To do this the Service Pack jar has to be prepended to the CLASSPATH of the client (i.e. $CLASSPATH="weblogic451sp14.jar:$CLASSPATH"). User's should install this client jar if they wish to resolve one or more of the following issues, although, in general, having the Service Pack on the client may solve potential issues.

 
        33289
        33794
        27890 (JMS)
        30485 (JMS)
        30527 (JMS)
        33244 (JMS)

Removing the Service Pack

Shut down the WebLogic Server.
Remove weblogic451sp14boot.jar from the start of the Java system classpath and weblogic451sp14.jar from the start of the WebLogic classpath used to start the WebLogic Server.
Delete weblogic451sp14boot.jar, weblogic451sp14.jar and any other files unzipped from the service pack download.
If you used t3config.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 weblogic451sp14boot.jar from the start of the classpath and remove the weblogic451sp14.jar from the start of the weblogic.class.path.
Restore any non-java class files that you replaced in the installation process.
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 service pack 14

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

Issue 5670 & 6602: International character set encoding (multibyte charsets) is now supported in servlets, including HTTP, JSP and JHTML (additional details)

Service Pack 2

Issue 5018: Fixed a problem where stateless session beans were still created even when an exception was thrown by ejbCreate().

Issue 6714: Fixed a problem with an AssertionError in the EJB LRUCache

Issue 6862: Fixed a problem with recovering from a MalformedCookieHeaderException

Issue 6956: Fixed a problem where a nullPointerException was thrown while creating a stateless sesison bean marked either TX_REQUIRED or TX_REQUIRES_NEW and ejbCreate() throws an exception

Issue 7139: Fixed a problem in JSP with relative URL specifications (page relative paths)

Issue 7167: Fixed a problem with failover of weight-based load balancing

Issue 7179: Fixed a problem with failover of the CallRouter interface

Issue 7201: Fixed a problem with running ejbc on EJBeans with clustered options

Issue 7224: Fixed a problem with a startup error when using the type 2 Oracle driver for AIX; you will need to install the copy of lib/aix/libweblogicoci34.so included in the service pack

Issue 7332: Fixed a problem with the display of EJB deployed beans in the WebLogic Console

Issue 7340: Fixed a problem that threw a java.lang.NegativeArraySizeException

Issue 7343: Removed a harmless, but potentially confusing strack trace related to the loading of certain classes

Issue 7346: Fixed a memory leak in SSL when using a SSL connection

Issue 7353: Fixed a multithreading problem in the HP-UX NSAPI plugin

Issue 7366: Fixed a multithreading problem in the AIX NSAPI plugin

Issue 7374: Fixed a problem with spurious error messages when building EJBeans with ejbc

Issue 7386: Fixed a problem with the construction of JMS QueueRequestor occasionally throwing a nullPointerException

Issue 7395: Fixed a problem with cluster servers hanging

Issue 7447: Fixed a problem with static initializers in generated code

Issue 7455: Fixed a problem with SQLException ErrorCode and SQLState not reaching the client when using JDBC T3

Issue 7547: Fixed a problem with expired queue messages not being properly cleaned up from the JMS tables

Issue 7591: Fixed a problem with unreferenced() not being called

Issue 7592: Fixed a problem with binding java.rmi.server.RemoteStub into the JNDI tree

Issue 7616: DGC client logging has been turned off

Service Pack 3

Issue 5653: Included a performance pack for HP-UX

Issue 6927: Fixed a problem where if ejbCreate() in a stateless bean threw an Exception, the client received an InvocationTargetException

Issue 7103: Fixed a problem where sendRedirect() used with SSL resulted in a "no 1st line" error

Issue 7105: Fixed a problem in applets over an SSL connection with Internet Explorer version 5

Issue 7139: Fixed a problem in JSP with relative URL specifications (page relative paths)

Issue 7254: Fixed a problem where a warning appeared on the server each time an applet class was loaded.

Issue 7398: Fixed a problem with performance of the NSAPI plugin

Issue 7448: Fixed a problem with setUID throwing a java.lang.NoClassDefFoundError

Issue 7526: Provided a method for specifying either JMS tablenames or a prefix (with database name) in JMS (additional details)

Issue 7587: Fixed a problem where JSP flushing option broke JSP includes

Issue 7640: Fixed a problem with the timeout being too short on the socket when a servlet reads POST data

Issue 7670: Fixed a problem where JMS transaction operations throw a NullPointerException

Issue 7680: Fixed a problem with receiving JSP compilation errors when there are concurrent requests for the same uncompiled or stale .jsp

Issue 7681: Fixed a problem with error handling in JSP when the URL is a directory and does not end in a "/"

Issue 7775: Fixed a problem with Cert Generator Tool only working for three-level domain names

Issue 7812: Fixed a problem with the EJB compiler (ejbc) failing when using primary key classes of bean-managed persistence that do not directly define hashCode() and equals()

Issue 7827: Fixed a problem where JSP includes failed if nested in different directories and debug filenames were incorrect

Issue 7846: Fixed a problem with JMS persistent store operations failing when the account guest is disabled

Issue 7956: Fixed a problem with Microsoft SDK for Java (JView) and Throwable replacements

Issue 7977: Fixed a problem with encountering an exception when re-registering a JSP taglib

Service Pack 4

Issue 5288: Fixed a problem with ClassCastExceptions thrown by stubs in 1.2 JVM EJB use

Issue 7974: Fixed an NullPointerException thrown when using JSP includes

Service Pack 5

Issue 6232: Fixed a problem with distributed transactions in a cluster

Issue 7389: Fixed a problem with distributed transactions in a cluster

Issue 7399: Fixed a problem with accessing jsp pages through the ISAPI plugin, where the wrong remote address and host information was shown

Issue 7404: Fixed a problem with rmic generated stub code not compiling correctly

Issue 7413: Fixed a problem with ejbLoad() not being called with dbIsShared set to true

Issue 7438: Fixed a problem with bean-managed transactions not maintaining across multiple method calls in a stateful session bean

Issue 7454: Fixed a problem with dbIsShared not being set consistently for CMP and BMP beans by default

Issue 7524: Fixed an NullPointerException in weblogic.servlet.internal.session.ClusteredSession.ejbLoad

Issue 7554: Fixed a problem with a ClassNotFound Exception being thrown with EJB and normal classes

Issue 7674: Included files related to OS/390 certification

Issue 7770: Fixed a problem with receiving a BadMACException when using https and t3s

Issue 7908: Fixed a problem with JMS message timeouts leading to a NullPointerException in the server

Issue 7946: Fixed a problem with relative links when a directory has no slash and is a JSP

Issue 7952: When request.getSession(new) returns null, we no longer swallow the exception

Issue 7999: Fixed a problem with JTS Driver not being able to pass user information to the T3 Driver

Issue 8008: Fixed a problem with BootServicesImpl unconditionally accepting AuthenticatedUser from a client

Issue 8010: Fixed a problem with the JTS driver needing to implement OracleCallableStatement

Issue 8016: Fixed a problem with an IllegalArgumentException being thrown on the version name cookie

Issue 8256: Fixed a problem where pools can deadlock while refreshing connections

Issue 8334: Fixed a problem where included pages could not include multiple pages

Issue 8395: Fixed a problem where WebLogic Logging was incorrectly throwing exceptions

Service Pack 6

Issue 6295: Fixed HttpSessions not cleaning on Server shutdown

Issue 6784: Fixed a problem where the <jsp:include> where file was not getting query parameters

Issue 7161: Fixed cookies being set multiple times

Issue 7438: Fixed not being able to maintain bean-managed tx across multiple method calls in a stateful session bean

Issue 7500: Fixed fixed a problem with the POST method through HttpClusterServlet

Issue 7599: Fixed a problem with large IIS proxy uploads (see additional notes)

Issue 7661: Fixed problem where compiling jsp throws StringIndexOutOfBoundsExcepiton when tags have similar length

Issue 7894: Fixed request.getServletPath jsp tag being broken

Issue 7902: Fixed a problem where JSP Compiler running in the Server failed to pass the directory name to the javac, if there were spaces in the directory name

Issue 8092:Decreased the reload time for static html pages with images using HTTPClusterServlet

Issue 8119: Fixed NPE in JspWriterImpl

Issue 8215: Fixed FileNotFoundException from JSP Include directive being swallowed

Issue 8337: Fixed JMS console items not being cleaned up when client is killed

Issue 8339: Fixed problem with closing connections affecting the rollback of transactions

Issue 8396: Fixed weblogic.httpd.indexDirectories so that it returns 403 forbidden vs 404

Issue 8413: Fixed NPE when compiling JSPs with old-style taglibs from command line

Issue 8482: Fixed weblogic.net.http.HttpClient and HttpsClient to initalize proxy settings correctly

Issue 8500: Fixed problem with extraneous ./ chars in URL for JSP URLs

Issue 8521: Fixed NSAPI plugin to work with NES 4.0

Issue 8559: Fixed problem with starting up WL as a web server on a priviledged port

Issue 8630: Fixed a problem where URLs of the form - prot://host/?foo=bar were not working correctly

Issue 8666: Changes necessary for certification on OpenVMS v7.1

Issue 8706: Fixed problem with IIS pluging not passing the remote user through

Issue 8713: Fixed syntax error in JSP causing an OutOfMemoryException on Solaris

Issue 8719: Fixed <jsp:include> not working when the previous page sent a POST

Issue 8751: Fixed problem with referencing a .jsp file in a directory that contains a space

Issue 8765: Fixed HTTPS connection problems occuring due to multiple registrations of SSLFilter with performance pack

Issue 8766: Fixed SSLSocket not closing completely with asynchronous IO

Service Pack 7

Issue 6699: Fixed a problem with JSP parameter forwarding

Issue 7573: Added NSAPI debug information

Issue 7576: Fixed an assertion error in ThreadStorage.popPreferredHost

Issue 7729: Fixed a problem with JSP/Servlets ignoring pageCheckSeconds=-1

Issue 7763: Fixed a problem with memmove in plugin

Issue 8296: Fixed a problem with plugin timing out for certain requests if there are more than one ppath and one of the ppath's is pointing to WebLogicCluster

Issue 8414: Fixed a potential server communication deadlock

Issue 8462: Fixed a problem with iPlanet and port 80 being recognized as the default port

Issue 8833: Fixed a problem with realms

Issue 8898: Fixed a problem NSAPI failover and firewalls

Issue 8940: Fixed the jts driver bombing on commit if the connection isn't actually used

Issue 8945: Fixed JMS runtime exception catching

Issue 8973: Fixed a problem with socket reader thread acknowledgements

Service Pack 8

Issue 6352: Fixed a problem with http HEAD request generating an error

Issue 7408: Fixed a problem with T3AdminRealm and null enumerations

Issue 7729: Fixed a problem with JSP/Servlets ignoring pageCheckSeconds=-1

Issue 8022: Fixed another problem with parameter forwarding

Issue 8322: Fixed a problem with the RDBMS security example and dynamic recognition of changes to groups

Issue 8585: Fixed a problem with the init method of a servlet implementing SingleThreadModel, which was being called repeatedly

Issue 8602: Fixed a problem with JSPC complaining about charset option and while doing an include

Issue 8676: Fixed a problem with getParameter() returning only the first found value for a specified name

Issue 8705: Fixed a problem with broken pipes on Solaris

Issue 8747: Fixed a problem with clusters running on different multicast addresses interacting incorrectly

Issue 8791: Fixed a problem with getRepMan being unable to obtain ReplicationManager for jvmid of second server in the cluster

Issue 8814: Added a property for classloading

Issue 8842: Fixed a problem with falling into a loop when including a JSP which throws an exception

Issue 8997: Fixed a problem with HttpSessionBindingListener not working in a cluster using in-memory replication

Issue 9148: Fixed a problem with sessions not timing out on Solaris 2.7 using file persistence

Issue 9181: Fixed a problem with plugins where HTTP requests would fail when the server hangs

Issue 9231: Fixed a problem when using weblogic.jms.tableNamePrefix, the original tables couldn't be deleted

Issue 9260: Fixed jspc parser bug related to usebean tag split problem - statement not reached

Issue 9317: Fixed a problem with a trigger scheduled from ScheduledTriggerDef being missed at the scheduled time

Issue 9342: Fixed a problem with displaying Japanese characters

Issue 9356: Fixed a regression with jhtmlc

Issue 9377: Fixed a problem with FileServlet being wrong when registered as *.ext

Issue 9382: Fixed a problem with JMS queue cursors being corrupted with multiple subscribers

Issue 9412: Fixed a problem with Cookie values not updating or sent back to the client browser

Issue 9460: Fixed a problem in clustering where HttpSessionBindingListener was not called when session.putValue is called

Issue 9517: Fixed a problem with setUID not working with HotSpot

Issue 9536: Fixed a problem with NSAPI load balancing over firewalls

Issue 9597: Fixed a problem where only the first servlet's output is displayed when the JSP includes two servlets

Issue 9599: Fixed a problem with removing rmi objects that share similar subcontexts

Issue 9685: Fixed a problem with IIS plugin not sending weblogic.system.DNSName properly

Issue 9792: Make JMS table scavenger configurable via properties file

Issue 9889: Fixed a performance issue with JSP's

Issue 9900: Fixed a problem with secure proxy and weblogic.net.http.HttpURLConnection

Issue 9920: Fixed a problem with request.getParameterValues() when the URI contains no name/value pair

Issue 10005: Fixed a problem with encoded arguments

Service Pack 9

Issue 4495: Fixed a problem with secure proxy and weblogic.net.http.HttpURLConnection

Issue 4495: Fixed a problem with getScheme() when using https

Issue 5832: Fixed a problem with applets hanging in getInitialContext() on reload with Java 1.2 plugin

Issue 6116: Provide applet Embed-ability to workaround the java plugin

Issue 7411: Introduced new property, weblogic.system.responseTimeout, which is used for failover and recovery

Issue 7657: Fixed a problem with reading bytes when using HTTP tunneling

Issue 8009: Fixed a problem with the Deployment Wizard failing to find home and remote interface when

Issue 8836: Introduce the proxy plugin for Apache on Solaris

Issue 9342: Fixed a problem with Japanese character recognition

Issue 9536: Fixed a problem with NSAPI plugin load balancing when a firewall is being used

Issue 9595: Fixed a problem with the weblogic.RMIC Compiler not accepting compiler arguments

Issue 9817: Fixed a problem with JSP and using Jview, blank spaces are not allowed

Issue 9913: Fixed a problem with IIS plugin not failing over correctly

Issue 10024: Fixed a problem with JMS message selector throwing a javax.jms.InvalidSelectorException

Issue 10095: Fixed a problem when proxying from WebLogic to Apache using the proxy servlet, the HOST information was not being passed

Issue 10117: Fixed a problem with verisign's global server id not working properly

Issue 10134: Fixed a problem with client using https trying to load stub classes from the server using http

Issue 10140: Fixed a problem with PosixSocketMuxer logging spurious error messages when closing an already closed socket

Issue 10181: Fixed a problem with content type not being set for directory listings

Issue 10214: Fixed a problem with not taking into account encoding when checking to see whether post data is a form

Issue 10224: Introduced new property, weblogic.system.sendAcksInSeparateThread, which is used for server tuning

Issue 10238: Fixed a problem with JMS only using the JDBC 1.0 driver

Issue 10255: Fixed a problem with debuggers not being notified when a dynamic class is loaded

Issue 10273: Fixed a regression with JDBC persisitence

Issue 10330: Fixed a problem with the HTTP proxy servlet not redirecting unfulfillable HTTP requests to an alternate HTTP server

Issue 10363: Fixed a problem with getScheme() when using https

Issue 10381: Fixed a problem with incorrect headers sent to the browser from NSAPI plug-in causing problems with IE5

Issue 10401: Fixed a problem with post request sent to the server not returning if there is a space character after the content-length header

Issue 10493: Provided an option to disable dynamic updating of the ISAPI cluster list

Issue 10586: Fixed a problem with the listen thread swallowing SSL handshake messages

Issue 10610: Fixed a problem with plugin so that it now has ability to disable failover with "connection reset"

Service Pack 10

Issue 8322: Fixed a problem with RDBMS example when a user is changed in a group, it's not recognized by WebLogic

Issue 8961: Fixed bug in Servlets with HttpSession.getLastAccessedTime()

Issue 9161: Fixed a problem with Server where JVMID.toPrettyString results in reverseDNSLookup

Issue 9994: Fixed a problem in JMS where Message.setJMSDeliveryMode (DeliveryMode.PERSISTENT) wasn't persisting a message

Issue 10001: Fixed a problem in EJB where an EJB client to stateful session bean was giving different results if a java application client was used versus a servlet client

Issue 10154: Fixed a problem in JMS where there was a race condition in JMSMessageConsumer.receive

Issue 10169: Fixed a problem in EJB with receiving an assertion error when creating bean managed entity beans

Issue 10322: Fixed a problem in Classloading where enable-call-by-reference was causing a classcastException when a Client is registered as a startup

Issue 10368: Fixed a problem in the Server with exception handling by the socket readers

Issue 10465: Fixed a problem in ClusterServlet having some failover problems

Issue 10642: Fixed a problem in ClusterServlet with an infinite loop tying up a thread.

Issue 10695: Fixed a problem in ClusterServlet adding use of ?__WeblogicBridgeConfig

Issue 10705: Fixed a problem in Plugins where we should revert back to static list if the dynamic list is dead

Issue 10724: Fixed bug in Plugins where we increased the max limit on ConnectRetrySecs from 10 to ConnectTimeoutSecs

Issue 10853: Fixed a problem in JSP where PageContext.include() should be able to take only 1 argument. Also used PageContextImpl instead of PageContext in getPageContextCode()

Issue 31317: Fixed a problem in the Apache Plugin to add virtual host support

Issue 31397: Fixed a problem with NSAPI Plugin sending one extra host header to WebLogic

Issue 31532: Added new features to ClusterServlet like pathtrim, trim extension, connection timeouts and changes for performance

Issue 31575: Fixed a problem in clustering where large amounts of multicast traffic are now more efficiently handled

Service Pack 11

Issue 10198: Fixed a problem in JMS where we were getting a weblogic.rmi.NoSuchObjectException

Issue 10787: Fixed a problem with WAP and UTF-8 support where parameter values were not being read in UTF8

Issue 28364: Fixed a problem in Clustering where we were failing to create new sessions on Solaris after running servers for a while with session replication

Issue 29968: Fixed a problem in Clustering where JDBC persisted sessions were not getting cleaned if we threw an exception while finding keys

Issue 30429: Fixed a problem in the Server where it was failing in the ListenThread

Issue 30707: Fixed a problem in Servlets where modifiying the virtual binding of FileServlet was causing problems

Issue 30925: Fixed a problem in the Server where it will no longer have any dependencies on AWT

Issue 31213: Fixed a problem in Servlets where if the header is not formed correctly, a 400 error code should be sent

Issue 31360: Fixed a problem in JTS where when one phase commit failed, the transaction rolled back but the lock to the entity was not being released

Issue 31492: Fixed a problem in Jolt where session pool's did not provide a mechanism to set RECVTIMEOUT

Issue 31551: Fixed a problem in HTTP where spaces in filenames were not handled properly

Issue 31738: Fixed a problem with Classloader where is was throwing an NPE when the service pack jar was put in the clients classpath

Issue 31758: Fixed regression in SP8 that had to do with the RequestDispatcher and how request parameters are forwarded to other servlets/JSP's

Issue 31775: Fixed a problem in Servlets where we made PathTrim and trimExt optional

Issue 31843: Fixed a problem in JMS where an NPE was being thrown when durableSubscribers were being used

Issue 31868: Fixed a problem in the ClassLoader where we were encountering a ConcurrencyModificationException

Issue 32037: Fixed a problem with JSPs to enhance security

Issue 32100: Fixed a problem in Server where an ArrayIndexOutOfBounds was being thrown due to incorrectly computing message size when the size field falls on a Chunk boundary

Issue 32105: Fixed a problem in EJB with stateful session bean handles in a cluster

Service Pack 12

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 29085: JDBC drivers need to workaround new synchronization in DriverManager.

Issue 29575: We added versioning to cookies for faster failover.

Issue 29968: Timed out transactions were not returning connections to the connection pool.

Issue 30023: This fixed a problem in JMS where setting "weblogic.jms.tableNamePrefix" in the properties file was resulting in all destID's equaling zero.

Issue 30334: EJB method calls were incorrectly throwing TransactionRolledbackExceptions when RequiresNew methods were called with a rolledback transaction.

Issue 30441: Japanese messages that jsp output were not being read correctly. This has been fixed.

Issue 30485 Fixed a race condition in JMSMessageConsumer. There was a problem with the server hanging when sending PTP messages.

Issue 30527: Fixed weblogic.rmi.NoSuchObjectException: RemoteInvokable while using JMS.

Issue 30648: Now we can associate a character set to a mimetype. (additional details)

Issue 30683: Fixed AssertionError in ejbPassivate for statefullSession, which has a reference to statelessSession bean's Home and Object. The EJBHome reference will be set to null after ejbActive() since we do not have to serialize EJBHome references in EJB 1.0.

Issue 30700: getEJBObject was returning null. Now it returns a valid EJBObject. For stateless session bean, create a reference in the context to the object, so that getEJBObject() will return a reference to the object.

Issue 31269: There is a new parameter MaxPostSize for all plug-ins. The default value is -1 (unlimited). If the content-length exceeds MaxPostSize, the plug-in returns an error message back to the browser and breaks the connection. Note: If the client has not finished sending the POST data it doesn't receive the error message from WebLogic. Instead it gets Connection Aborted error. Plugins will be able to handle this broken pipe and will send meaningful message to the browser.

Issue 31315: WebLogic now supports proxying by path for IIS.

Issue 31358: Fixed stickToFirstServer parameter for rmic.

Issue 31389: Fixed a problem with the iisproxy.dll not finding the location of the iisproxy.ini in the registry.

Issue 31719: Fixed a problem with NSAPI failing on large uploads.

Issue 31843: Added error checking to Durable Subscribers in JMS.

Issue 31943: Selector's with compound expressions (specifically with long values) were not working. For Example: String selector = 'DateProp >= 963464400000 AND DateProp <= 963550799999'. This has been fixed.

Issue 32092: If the Request-URI is greater than the buffer size (2048) the plug-in will return back 414 HTTP status code. Which means, "The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret."

Issue 32133: There is a new parameter, defaultfilename, for all plug-ins. (see additional details)

Issue 32174: Added locationKeys, pathTrimTable, and pathPaprendTable in ConfigInfo structure to handle more than one location tag used in virtual hosting.

Issue 32195: Fixed a problem using IBM Visual Builder to generate some servlets.

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 32258: Added translation time expression capabilities for plugin applet-parameters.

Issue 32501: JSPC's package argument points to jhtml files instead of jsp's. This has been fixed.

Issue 32614: The Apache plugin will return the following error with simple POSTS: Cannot read -1 bytes of postData from tmp file '/tmp/_wl_proxy/_post_0. This has been fixed.

Issue 32615: Fixed a problem with ConnectTimeoutSecs in Apache.

Issue 32634: Dealt with some minor JMS DataBase improvements to reduce an extra hit on the DataBase for every 16 messages message id's.7

Issue 32806: There was a problem with the log rotation feature and its handling of dates that has been fixed.

Issue 32952: We now avoid sending out the transaction context as part of the remote call to create, update or remove secondaries used by the replication machinery. Not doing so was leading to a potential deadlock while deserializing the transaction context.

Issue 32576: Until the buffer fills up it was using 8859-1 codeset. After the buffer overflows it is using UTF8. Now it uses the 8859-1 codeset before and after filling up.

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 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 33320: HTTP Tunneling has been added. By default tunnelling is disabled.

Issue 33343: Load balancing has been improved with WebLogic plug-in's support of multiple clusters. Maintaining a static variable "lastIndex" was breaking load balancing. This has been fixed.

Issue 33600: As of recent service packs, if page contentType is specified for a page and the page has any RequestDispatcher calls to other JSPs, then the content from the invoked JSP's is getting displayed first. For example, if page1.jsp has contentEncoding defined on the pageContext, then page2.jsp is getting generated first in the final html. This has been fixed.

Issue 33794: A bug allowed all TxContext objects (ie, all transactions on a particular server) to be serviced by a single static coordinator. All transactions bottleneck around one transaction coordinator. In a situation where a client needs to start multiple transactions on multiple servers (not clustered or different clusters), this wasn't safely possible because the static coordinator could be overwritten by the lookup to the second server. So, you could do a lookup of User Transaction on server1, do a begin xact, then lookup UserTransaction on server2 and call commit, commit the transaction on server1, and not get an exception thrown. This fix now allows one coordinator per UserTransaction per server.

Issue 33846: When using jsp:param with jsp:forward, the values are not passed to the forwarded page. This has been fixed.

Issue 33866: Now, every time a PeerGone message is created and sent over the wire, it is logged in. This makes it possible to tell why a peer gone has been declared without using debug.

Issue 33909: URLEncoding now works with iisforward.dll.

Issue 33910: This fix makes certain that the pool driver will implement the OracleCallable statement, so you can cast for it.

Issue 33914: If you changed the WebLogicSession cookie to some invalid value, such as 1, a NullPointerException was thrown. Now we do a minimal check of the session cookie before using it.

Issue 34021: When JTS defers the call to the T3 JDBC driver for a distributed transaction, it expects a non-null properties object.

Issue 34251: ClassCastException is thrown when EJB handle is retrived from HttpSession

Issue 34554: Fixed a bug with ejbc generating incorrect code for CMP entity beans when the field name did not match the database column name.

Issue 34596: There was a segmentation fault with SSL modules for Apache on Solaris. When a browser makes an https request and the user completes the certificate dialog the user sees a "document contains no data" dialog box in the browser and Apache has a segmentation fault error. This has been fixed.

Issue 34733: Fixed a potential deadlock involving problems with the native io.

Issue 34833: Now the Apache plug-in supports multiple MatchExpression entries.

Issue 34899: Users with an applet client making t3s connections to the server (under heavy loads) may have some of the clients hang in getInitialContext call. We now have the capability to specify timeout for getInitialContext.

Issue 35012: Now the build date/time is shown for the native socket muxer libraries if weblogic.system.nativeIO.enable=true. Note: To have the native socket muxer load for NT, you must copy the bin/wlntio.dll included in this Service Pack to your weblogic/bin directory.

Issue 35240: The apache proxy module appends a question mark to the URL that is sent to Weblogic Server. This was normally not a problem unless the URL specifies a web application mount point. This is now fixed to account for that possibility.

Issue 35328: When there were more servlet requests than the number of execute threads, all the requests were waiting for a message in the response queue which never arrived because there are no threads to process the message from the JMS client. This has been fixed.

Issue 35426: Permissions to individual JNDI objects was having problems as of WebLogic Server 4.5.1 with service pack 11. This has been fixed.

Issue 36361: Fixed potential crashes in IIS under teh following conditions: c:\tmp does not exists, WlForwardPath is empty in iisproxy.ini, i.e. "WlForwardPath=", IIS Admin Service is terminated from the control panel.

Issue 36455: Fixed a problem running JSP's by ensuring that the destination of a JVMID of the ConnectionManager is valid.

Issue 36505: Fixed the deadlock with dispatch-in-thread pattern by using a new ExecuteThreadQueue.

Issue 36507: Improvements were made to prevent multicast buffer overflow.

Issue 36509: The config timer was changed to incorrectly start 2 resend triggers. Fixed by ensuring only one is started.

Issue 36510: Now we make sure that the non-blocking execute thread queue will be initialized on clients.

Issue 36511: Now we use a non-blocking execute queue for SlidingWindow acks.

Issue 36513: Fixed a bug in calculating the time of the remote server to which this server is connected to. There was a bug in our implementation of SNTP and it was fixed.

Issue 36514: Revised JMS indices for performance improvements to the JMS store.

Issue 36515: We now print a more descriptive error message for errors that occur in the native poll system call in the POSIX muxer.

Issue 36916: The apache plugin returns a 200 status code when it cannot connect to the WebLogic Server. This is incorrect. Now it returns a 500 Status Code.

Issue 36994: If the connection to the socket fails we used to try to reconnect irregardless. Now we throw an exception and terminate unnecessary initialization.

Service Pack 13

Issue 26207: A SocketException error was occurring with the PosixSocketMuxer when connections were closed. This was due to the server trying to read from and close the socket at the same time. We have added synchronization to avoid this.

Issue 29512: The simultaneous deployment of a jar in two servers on the same file system creates an assertion error. This has been fixed.

Issue 31399: Fixed a problem with the libproxy.so for AIX with the NSAPI plug-in.

Issue 31721: Added a timeout property, weblogic.system.idleTimeout timer, to disconnect RMI clients from the server.

Issue 34045: NES 3.6 with SSL enabled on HPUX 11 was freezing on startup. This problem with the NSAPI plug-in has been fixed.

Issue 36295: If a stateless session EJB calling a second stateless session EJB within the same transaction throws an exception, then in certain instances the second EJB is not returned to the free pool.

Issue 37291: The encoding option, such as -encoding UTF8, was not working correctly with jspc. This has been fixed.

Issue 37568: A new property, weblogic.system.maxConcurrentSends, introduced in Service Pack 12, broke the security of Applets running inside a sandbox. This has been fixed.

Issue 37692: Service Pack 12 was treating all servlets as a SingleThreadModel. This has been fixed.

Issue 37815: Fixed an OutofMemory error that was occurring occasionally while loading libproxy.sl on HPUX11 during the startup of NES.

Service Pack 14

Issue 26806: Fixed a problem with the server dying when the clustering license had expired or was invalid.

Issue 27920: A log message, "tried to renew lease for lost reference," was flooding the log files. Now we only report this error when debugging is turned on.

Issue 28881: When the server is out of execute threads, SessionState.close can deadlock as it puts a message to the messagesPublished queue.

Issue 29639: We added an appropriate error message when the server stops because of an invalid cluster license.

Issue 30001: Fixed session ID length problem so that it may be modified by a new property, weblogic.httpd.session.sessionIDLengthURL. This can be set anywhere from 10 to Integer.MAX_VALUE. WAP dependent devices were having difficulty accessing some URLs due to increased URL length after rewriting. This property addresses a particular problem with the session id, which is lengthy and often appended in the rewrite of the URL.

Issue 30298: Introduced a new property to signal which encoding to use for the input stream. The property is weblogic.httpd.inputCharset and it allows users to specify charset for the post parameter. It can be set to different character sets. See additional details

Issue 30351:If JMS was used indirectly through an EJB, the JMS connection will close itself down after the caller that invoked the EJB first shuts down. This is because the peer gone detection in the connection object does not know that the connection was created by the bean rather than the client who called the bean.

Issue 30470: Fixed a problem with JDBC incorrectly trying to create statements with the DBMS connection.

Issue 30826: A new property "weblogic.system.maxExecuteThreadCount" has been added to configure the maximum number of the threads the weblogic will support. This is essentially the maximum the property "weblogic.system.executeThreadCount" will take. This property is configurable both from client and server.

Issue 31721: Added new property, weblogic.system.idleTimeout. This acts as a timer that can be set to the maximum idle period (in milliseconds) to wait before tearingdown an RJVM. A value of 0 means no timeout.

Issue 31786: Added a new property: weblogic.login.logAllReadTimeouts. By default it is set to true, if you set it to false the server doesn't log a message when a read on login times out.

Issue 34041: You can now rotate your jdbc log. We only allow you to do this based on date. You can specify how often we should rotate the log file and when we should begin that rotation. (See additional information)

Issue 35328: Fixed a problem when there were more servlet requests than the number of execute threads. All the requests were waiting for a message in the response queue which never arrived because there were no threads left to process the message from the JMS client.

Issue 36008: EJB's passing an array of a user defined object causes errors in JDK 1.1.7. The 1.17. JVM differed in the way it loads class arrays from the 1.2.2 JVM.

Issue 36076: Fixed a problem getting thread dumps using Solaris with the JDK 1.2.1_04. Users were getting the following output in the dump file instead of a thread dump: Problem loading native lib. Can't dump threads.

Issue 36269: Fixed a problem in JDBC with BigDecimals. Now we fully implement a getBigDecimal jdbc2.0 call.

Issue 37789: Sockets on the server were opened by the web server and then closed. But they still were stuck in the CLOSE_WAIT state on the server. Eventually all these sockets took up all the file descriptors available and the server hanged-- unable to answer requests. This has been fixed.

Issue 38353: Fixed JDBC Session Persistence for reading broken serialized data.

Issue 39411: Made improvements to the NSAPI plug-in to prevent segmentation faults and crashes.

Issue 39503: Fixed a problem with CGI requests. Sent requests being handled one by one were not being processed in the desired time intervals.

Issue 39959: JMS Sessions were remaining unclosed incorrectly in the console

Issue 40092: Fixed a problem with JSP where the JSP compiler was generating repetitive java statements on compilation.

Issue 40134: Fixed a problem with servlets. Using getHeader was returning the last element when there were multiple headers with the same name. Now, following the 2.2 spec, the server brings back the first.

Issue 40790: When using keepAliveSecs sockets reopen unnecessarily. To avoid this use ServletOutput.

Issue 40872: When a startup class took a long period of time to complete (~2 minutes), and the session timeout parameter was relatively short (1 minute), the session invalidation trigger fires only once. This meant that sessions were never automatically invalidated.

Issue 41161: Fixed a problem with buffer overflow in JSP/Servlets.

Additional details on new plugin parameters:

The following parameters have been added and are available for the specified plugins.

Parameter Name Defaults Pertains To Description

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.

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.

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. So if you think that your servlets are going to take more than 30 secs to process, don't reply on the default value and change it. There is a known problem about the usage of this parameter. If all servers in the cluster are hung or if a servlet request takes more than "HungServerRecoverSecs" for all the servers in the cluster, the plugin will hang. So please be advised to use this parameter very carefully. The bottom line is that if you don't care about hung server recovery then set this to a very high value (600 secs).

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.

MaxPostSize Default=-1 All plug-ins If the content-length exceeds MaxPostSize, the plug-in returns an error message. If set to -1 the size of POST data is not checked. This is useful for preventing denial-of-service attacks that attempt to overload the server with POST data. If set to zero, the size of the Post data is unlimited. The default value is -1.
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 issues 5670 & 6602:
International character set encoding (multibyte charsets)

International character set encoding (multibyte charsets) is now supported in servlets, including HTTP, JSP and JHTML

Using multi-byte character sets

In order to properly read and transmit multibyte JSP files, the JSP servlet needs to know which charset converter to use for a particular file. There are two ways to specify this:

Specifying an 'encoding' initArg to the JSP servlet in the weblogic.properties file:

weblogic.httpd.register.*.jsp=\
       weblogic.servlet.JSPServlet
weblogic.httpd.initArgs.*.jsp=\
       pageCheckSeconds=60,\
       packagePrefix=examples.jsp,\
       compileCommand=c:/java/bin/javac.exe,\
       workingDir=/weblogic/myserver/classfiles,\
       verbose=true,\
       encoding=SJIS

In this case, the encoding should specify a standard JDK charset converter. A list of standard JDK charsets is available at http://java.sun.com/products/jdk/1.1/docs/guide/intl/encoding.doc.html.

Specifying a contentType JSP page directive:
```
<%@ page contentType="text/html; charset=SJIS" %>
```
or
```
<%@ page contentType="text/html; charset=Big5" %>
```
When the JSP servlet parser sees the contentType JSP page directive, it will start using the specified charset to read the page, as outlined in the JSP specification.

The charset specified may be:

an IANA name, as listed at ftp://venera.isi.edu/in-notes/iana/assignments/character-sets
a JDK charset name, as listed at http://java.sun.com/products/jdk/1.1/docs/guide/intl/encoding.doc.html

Since the IANA charset names may be different than the JDK charset names, we have introduced a way to alias the names. Specifying the following property in the weblogic.properties file

  weblogic.httpd.charsets.IANA_name=JDK_name

will map an IANA name -- used in a JSP file -- to a JDK name.

For example, since Internet Explorer 5 recognizes 'Shift-JS' as the 'SJIS' charset, put an alias for 'Shift-JIS' to the JDK charset name 'SJIS'in your weblogic.properties file as follows:

  weblogic.httpd.charsets.Shift-JS=SJIS

A JSP file containing

  <%@ page contentType="text/html; charset=x-sjis" %>

will be parsed using the JDK's SJIS converter for a page in charset x-sjis.

For HTTP servlets, you can use

  ServletResponse.setContentType("text/html; charset=FooBar");

and the PrintWriter for that response will be initialized to the FooBar character set, as outlined in the Servlet 2.1 specification.

Additional details on issue 7526:
A method for specifying either JMS tablenames or a prefix

We now provide a method for specifying either JMS tablenames or a prefix (with database name) in JMS.

In your weblogic.properties file, specify the property weblogic.jms.tableNamePrefix with the prefix you want to use:

  weblogic.jms.tableNamePrefix=master.dbo.

This makes JMS reference master.dbo.JMSMessages rather than simpley JMSMessages. Note that the trailing dot is necessary and that the form of the prefix must be such that it generates a valid tablename.

This prefix could also be used to separate JMS tables used by two different WebLogic servers. For example, server A could use:

  weblogic.jms.tableNamePrefix=A

and server B could use:

  weblogic.jms.tableNamePrefix=B

Then, server A's JMS would reference AJMSMessages and server B's JMS would reference BJMSMessages.

Additional details on issue 7599:

A new parameter, weblogic.httpd.postTimeoutSecs, can be used to set the maximum time the server will wait between data packets. This parameter needs to be set in the weblogic.properties file. For example, to time out after 25 seconds, you would set it as:

weblogic.httpd.postTimeoutSecs=25

The default value is 30 seconds. The maximum value is 120 seconds, and the minimum value is 10 seconds. If your connections are very slow, or your network is very congested, this property may timeout. It is more likely that this property will timeout when the client unexpectedly hangs but maintains the socket connection. You may increase it to temporarily relieve the problem, but it is highly recommended you look into this issue with your network or clients. We introduced this property to guard against denial-of-service attacks where malicious clients would maintain many open sockets to the server, causing it to run out of file descriptors.

Additional details on issue 8322:
Fixed a problem with the RDBMS security example and dynamic recognition of changes to groups

In order to successfully utilize the fix pertaining to issue 8322, the following changes must be made:

1. In the weblogic.properties file

Make sure the following line exists:
weblogic.security.realmClass=examples.security.defaultrealm.DefaultRealmExtender
2. In weblogic.realm_ddl file

Add "system" to the users table. The WebLogic server will not start without this entry in users table. You will get the following error java.lang.SecurityException:

Authentication for user system denied in realm weblogic

Add "everyone" group to the groupmembers table. The WebLogic server will be started with an ACL status error without this entry

3. In the weblogic.realm_properties file

The default value for updateInterval is 300. You can adjust it for a faster or slower database refresh.

Finally, although database changes will show immediately on T3AdminRealm, you still need to wait for "updateInterval" seconds (in weblogic.realm_properties file) before a new user will be permitted.

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"

weblogic.httpd.inputCharset.<Dir name>=<charset name> (Issue 30298)

A new property can be used to specify charset for the getParameter() and getParameterValues().

Using GET/POST requests from a Client or Browser, the servlet container determines charset of the string using the request URI of the HTTP request.

To specify encoding for the string of GET or POST request, the following properties need to be set in the weblogic.properties file:

weblogic.httpd.inputCharset.<Dir name>=<charset name>

<Dir name> is for the resource path used in the request URI. <charset name> is IANA character set name.

For Example: If you want to use EUC-JP charset as a default, Shift_JIS for under /i and iso-8859-1 for under /en, such as:

public_html ---- products
(EUC-JP)         (EUC-JP)
            ---- about
                 (EUC-JP)
            ---- download
                 (EUC-JP)
            ---- i
                 (Shift_JIS)
            ---- en
                 (iso-8859-1)

In this case, then the following properties need to be set:

weblogic.httpd.inputCharset./*=EUC-JP weblogic.httpd.inputCharset./i/*=Shift_JIS weblogic.httpd.inputCharset./en/*=iso-8859-1

Additional Notes:

 1) Mapping IANA charset and JAVA encoding

 You can specify mapping between IANA charset and JAVA encoding as follows:

 weblogic.httpd.charsets.<IANA charset>=<Java encoding>

The following makes mapping from a IANA EUC-JP charset to Java EUCJIS encoding.

 weblogic.httpd.charsets.EUC-JP=EUCJIS

 2) Default Mapping

 WebLogic Server has a default mapping table between IANA charset and Java encoding. Normally, you don't have to specify 
 particular mapping specification.

 3) Default charset

 If you don't specify inputCharset, then WebLogicServer handles charset the same as the Server's VM default encoding.

For example, getParameter works on MS932 on Japanese NT without specification of inputCharset.

Additional detail on CR34041

You can now rotate your jdbc log. We only allow you to do this based on date. You can specify how often we should rotate the log file and when we should begin that rotation. For example, rotate every 6 hours and start the first rotation at 4pm today.

If rotation is enabled we will automatically append a date/time stamp to the end of the log file, you can control the format of this timestamp with the property weblogic.jdbc.logFileNameFormat. The reason we have to do this is that we do not control the output stream of the jdbc.log, this is handling in java.sql.DriverManager, so we cannot lock the file, move it to a backup and then restart the log file with the same name. Thus the current jdbc.log file is the file that has the most recent date timestamp at the end of the file name.

Added properties:

weblogic.jdbc.rotateLog

Whether or not to rotate jdbc log file. This is false by default.

weblogic.jdbc.logRotationPeriodMins

Defines the period in minutes when the jdbc log will be rotated. 24 hours is 1440 minutes. One week is 10080 minutes

weblogic.jdbc.logRotationBeginTime

Defines the date when the first rotation of jdbc log will begin. The format follows java.text.SimpleDateFormat, MM-dd-yyyy-k:mm:ss see the javadocs for more details. For example: 11-24-2000-12:30:00 Note: If not set, the next rotation is the next weblogic.jdbc.logRotationPeriodMins. If the date has already past, then the DAY_OF_WEEK, HOUR_OF_DAY, MINUTE and SECOND are used with the current date to recalculate.

weblogic.jdbc.logFileNameFormat

Defines the format of the date string that is appended to the jdbc log when rotation is turned on. The format follows java.text.SimpleDateFormat, and defaults to: dd_MMM_yyyy__HH_mm_ss see the javadocs for more details.

Known issues

There are no known issues at this time

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're using "Service Pack 14".

Note: If you are using an NT platform, in order for the native socket muxer to load, you must copy the bin/wlntio.dll included in this Service Pack to your weblogic/bin directory.

Last updated 03/17/2001