BEA Logo BEA WebLogic Server Release 6.1

  BEA Home  |  Events  |  Solutions  |  Partners  |  Products  |  Services  |  Download  |  Developer Center  |  WebSUPPORT

 

  |  

  WebLogic Server Doc Home   |     Release Notes   |   Previous Topic   |   Next Topic   |   Contents   |   View as PDF

Resolved Problems

 

The following sections describe problems that will be resolved for the release of WebLogic Server 6.1 Service Pack 4. Service Pack 4 is not yet released. We publish this list for informational purposes only. Be advised--it is highly subject to change, and is not final until the Service Pack is released.

The following sections describe problems that were resolved for the release of WebLogic Server 6.1 Service Pack 3:

The following sections describe problems that were resolved for the release of WebLogic Server 6.1 Service Pack 2.

The following sections describe problems that were resolved for the release of WebLogic Server 6.1 Service Pack 1:

The following sections describe problems that were resolved for the release of WebLogic Server 6.1:

 


WebLogic Server 6.1 Service Pack 4 Solutions

The following sections describe problems that will be resolved for the release of WebLogic Server 6.1 Service Pack 4. Service Pack 4 is not yet released. This list is published for our customer benefit, but be advised--it is highly subject to change, and is not final until the Service Pack is released.

Classloader

Change Request Number

Description

077067

Setting the property PreferWebInfClasses in the config.xml now works correctly for resource files; if set, the files will now be taken from the users Web Application.

077344

When a class file was in a JAR file in the WEB-INF\lib folder, the java.lang.ClassNotFoundException: org.apache.commons.logging.impl.LogFactoryImpl was being thrown. This problem has been fixed.

079738

Fixed potential memory leaks when a web application with static references to a large memory structure is deployed or undeployed.

081377

Fixed a problem that resulted when classes were loaded via the context class loader at deployment time.

083752

If a class tried to create an InitialContext and the java command line specified weblogic.jar using the -Xbootclasspath argument, a NullPointerException was being thrown from weblogic.i18ntools.L10nLookup.loadProps. This has been fixed.

084236

The example samples.examples.iiop.wls2wls.package-summary.html now contains correct URL information.

Cluster

Change Request Number

Description

043366

Comma delimited ip addresses can now be specified for the cluster address when the server is started in development mode.

078455

A WebLogic Server Cluster no longer hangs in Session Replication with F5/IIS Cluster Proxy.

078677

HttpClusterServlet now performs failover during the graceful shutdown of the managed server.

081908

Fixed a problem with HTTP session replication when the secondary server is unavailable at the TCP level. This solves a long delay when the server tries to connect to a secondary server that can obviously not receive a TCP request and has already been removed from the cluster view.

083532

Fixed a Null Pointer Exception at weblogic.rmi.cluster.ReplicaAwareRemoteRef.getCurrentReplica that was causing the server's shutdown sequence to be aborted prematurely.

087870

When using high-availability multi-pools, Weblogic now correctly fails over upon hardware failure when the pools have been created with an initialcapacity equal to zero. The ResourceException that was being thrown was not the type that the multipool interpreted as reason to fail over--that was the problem.

Console

Change Request Number

Description

057307

There is no longer an NullPointerException thrown when an attempt to change user password in the RDBMS realm is made.

061975

Fixed a problem in createColumnsSql when auto key gen is used.

073536

It is now possible to choose optional two-way SSL in the console by checking the check box.

074998

Fixed a problem receiving authentication errors when using form-based authentication and multiple locales. Credentials in languages other than English could be successfully added to the fileRealm.prorperties file but could not be used to authenticate via the servlet form-based authentication. The credentials can now be used to authenticate via the servlet form-based authentication.

079130

It is now possible to browse the JNDI tree for EJBs that are Deployed on the Managed Server.

079805

Now Web Applications that are targeted to the source server show up as targeted to the cloned server.

082578

Added a WAP-Enabled flag on the server config->http tab.

083107

The console now supports Mozilla 1.0 browsers.

083330

It is now possible to target a Multipool to a cluster via the console.

083377

If you specify each cluster node with a DNS name at WebLogicCluster, HttpClusterServlet is now able to maintain the stickiness of HTTP requests with references to the static server list.

083578

Increased the text field size for max message size on the server protocols tab.

084114

When trying to monitor the web applications in the console via the mydomain --> Servers --> myserver --> Deployments tab --> WebApplications tab --> monitor all active Web Applications link, an exception was being thrown. This has been fixed.

086652

Now if you create a new domain within the console, the file realm tab will work in the left hand pane of the console.

EJB

Change Request Number

Description

069899

Many to Many CMR no longer throws an SQL exception if both tables have the same column as the foreign key.

076112

When a stateless session bean is deployed with the <max-beans-in-free-pool> parameter in the weblogic-ejb-jar.xml file, this value is not respected when concurrent calls are made to stateless session bean. WebLogic Server was creating further new instances of stateless session beans than the value specified in the parameter. This has been fixed.

076597

The ejbRemove() method was never being called when undeploying a stateless EJB with <max-beans-in-free-pool> to 0. This has been fixed.

077049

If an application uses dynamic proxies as parameters in EJB methods, a remote client can now use the interface even when the parameter interfaces are put on the server classpath.

078456

The client and server output that is documented in some of the EJB examples was difficult to read because the text was not wrapping. Now, the text does not wrap and is easier to read.

079745

EJBC no longer fails to deploy when another XML file is included in the weblogic-ejb-jar.xml file.

080569

After running ECperf, the EJBCacheRuntime statistics appeared with the CachedBeansCurrentCount on one stateful session bean (CartSes) printing out an incorrect (and negative) number. This has been fixed.

081355

EJBC no longer throws a NullPointerException when traversing relationships in an EJB 2.0 JAR file.

081807

EJB Deployer hard wired the replicateBindings to 'true' on context object before binding home to the JNDI tree so that even if the user set the home-is-clusterable to 'False' in the weblogic-ejb-jar.xml file, announcements to the rest of the nodes in the cluster are still being attempted a NameAlreadyBoundException is being thrown. This has been fixed.

081817

Provided an option to set dispatchPolicy at bean level in the weblogic-ejb-jar.xml file.

081991

A Message Driven Bean no longer fails to reconnect to MQSeries after "inhibited" and then "allowed" is selected for getting messages from the queue.

082029

Fixed a problem using EJB's and connecting to a database with an XA driver when using an openString property for the connection pool.

082451

There is no longer a ClassNotFoundException thrown for third party JAR files for a Message Driven Bean that has a JMS provider that is not WebLogic Server.

083050

When calling context.getCallerPrincipal() from ejbRemove(), an exception is no longer thrown.

083098

The number of connections to MQSeries increases when the Queue is closed.

083689

CMP Entity beans with automatic key generation using SQLServer no longer results in a javax.ejb.NoSuchEntityException.

083896

When setting the max-beans-in-cache to 10 and then running the client to access the bean with the same primary key 200 times get 200 beans in the cache, if concurrency-strategy was set to exclusive, the database cache was ignored. This has been fixed.

083896

Fixed problems where the property max-beans-in-cache was being ignored.

084224

The invalidate() method was not being called by the container when a Read-mostly pattern was being used.

084978

You can now add and change EJBC parameters from the Administration Console. This allows you, for example, to change the amount of memory allocated to stub compilation.

085320

Fixed a problem with stateless session beans and the server; the 'idle beans count' displayed in the Administration Console was incorrectly continually increasing.

085659

Fixed some problems and delays with EJB failover when a machine is disconnected from the network.

Examples

Change Request Number

Description

079543

The example server did not start when BEAHOME had a space in the name. This has been fixed.

084236

The example samples.examples.iiop.wls2wls.package-summary.html now contains incorrect URL information.

084903

The WTC simpappcns example has been fixed to work over the network and not just on a single machine.

JDBC and jDriver

Change Request Number

Description

077974

Added OS authentication for Solaris because the OCI bug is fixed in Oracle 8.1.7 OCI.

080487

The JTS driver no longer leaks a pool connection if the DBMS rollback fails.

082438

Whereas statically defined pools absorb a property to define the prepared statement cache size, a pool created dynamically, via the console, weblogic.Admin, or an API was unable to do so. This has been fixed.

082484

The JDriver for Oracle no longer raises an ArrayIndexOutOfBoundsException if more than 511 parameters in a PreparedStatement are set.

086557

We have included the windows, HP, and Solaris jDrivers for Oracle 9.2 and updated the 8.1.7 and 9.0.1 drivers as well.

087005

A thin driver for Oracle 9.0.1 and 9.2 has been added/

087803

Fixed problems creating a JDBC store configured for a JMSServer using Oracle 9.0.1; the updated thin driver for 9.0.1 has been provided and solves this issue.

088156

Fixed a potential JDBC deadlock condition caused by the EJB persistence manager.

JMS

Change Request Number

Description

063743

Fixed a problem that was resulting in Message Driven Beans not acknowledging object messages

079547

Fixed a deadlock that created problems while creating Durable Subscribers to JMS servers deployed in a clustered environment.

080668

In a clustered enviroment that sets listeners for the JMS Server, a NoSuchObjectException was being thrown if one of the nodes of the server was started after some time, rather than immediately. This has been fixed.

082298

The number of durable JMS subscribers was incorrect. An extra increment was occurring each time a consumer attached to a durable subscription. The number is now incremented when the subscribers are created and decremented when they are deleted.

082438

Prior to Service Pack 4, for JDBC connection pools that were created dynamically, the STATEMENT_CACHE_SIZE parameter was not implemented. This is corrected in Service Pack 4, so that dynamic connection pools can use the Statement Cache to cache and reuse prepared and callable statements.

083290

Fixed problems with JMS recovery in mangaged servers when the primary server goes down and then is restarted.

083503

Fixed a problem with JMS and Message-Driven-Bean recovery when starting and stopping managed servers.

084175

Messages were being lost when sent through MessagingBridge and interrupted by a server re-start. If while messages were being processed by the MessagingBridge (messages being processed from MQ Queue to WebLogic JMS Queue), and the WebLogic server was stopped and then re-started, then in some cases, some messages were lost. The number of messages lost corresponded to the BatchSize of the MessagingBridge. This problem has been fixed.

084182

The setExceptionListener method no longer throws a NullPointerException when exceptionListener is set to null.

086487

see 83503

Miscellaneous

Change Request Number

Description

049340

The DeploymentOrder on the ComponentMBeans can now be initially set based on the ordering in the application.xml file making re-deployment consistent with initial deployment.

053054

Fixed a problem where the server was not copying the transaction context. There were rjvm errors when a client that spawned a new JVM after binding an implementation class into the JNDI tree; the new JVM was not able to make RMI calls on the method.

053957, 071626, 075394, 076265, 078527, 079652, 079655, 082693, 082830

This Service Pack improves WebLogic's handling of RJVMs in multiple ways. Fixes include:

WebLogic Server now ensures that a valid connection has been fully established between servers running on local and remote Java virtual machines before it attempts to send a message to an RJMV.

Possible deadlocks resulting from establishing a valid connection between servers running on local and remote Java virtual machines have now been fixed.

Previously, it was possible for RJVMs to get into an infinite-wait state while waiting for the connection to be established because the notification of a successful connection was issued before the RJVMs went into a wait state. The fix makes it possible for a success notification to be detected, even if it happens before a wait.

Multiple threads trying to establish a connection to an RJVM at the same time now rely on the success or failure of the first thread that actually manages to establish the connection.

Previously, each thread would always attempt to establish a connection in turn, rather than using the connection established by the first thread that succeeded.

Peer WebLogic Servers running on different computers now correctly detect when a peer server with which it has previously established a connection has gone, and correctly cleans up the broken connection.

The Remote Method Invocation (RMI) layer now receives proper exceptions to failover when an attempt to get an OutputStream fails.

Previously, when two peer servers where trying to establish a connection but failed to, an exception was not thrown to the RMI layer, causing improper failovers or delays to a proper failover.

Possible deadlocks have been fixed between 2-way calls from T3JVMConnection to ConnectionManager to RJVM.

056403, 063910, 076409, 076903, 078288, 078918, 079599, 080292, 080744, 081010, 081116, 081856, 082700,083623, 086362.

We fixed multiple muxer problems and added improvements including:

Collections in all muxers (Java and native-code) that map to sockets now have unique keys.This has solved a variety of problems, including data corruption, bad pointer references, WebLogic Server hangings and crashes.

Data structures and state machines in muxers now have proper synchronization. This fixed certain classic deadlocks caused by conflicting order of locking.

The call stacks between the muxer and the protocol layers above the muxer are now 2-way, which means a close of a socket or connection can be initiated from any point in the stack. Safeguards have been added to prevent deadlocks.

State machine transitions in the muxer have been fixed, resulting in sockets no longer remaining in a CLOSE_WAIT state.

064301

If the application server is killed abruptly, there is a high probability of creating a distributed in-doubt transaction.In WebLogic Server 6.1 service pack 1, the distributed in-doubt transaction still continued to exist and needed to be resolved by manual DBA intervention. In WebLogic Server 6.1 service pack 4, the transaction log file is re-scanned and a recovery process is initiated after re-starting the application server.

071510

It was not possible to start the server using JMX through the NodeManagerMBean. In WebLogic Server 6.1 service pack 4, new methods were added in the ServerMBean to start and kill ManagedServers via the JMX client.

072188

The admin server was not closing the network connection that it established with NodeManager after completing the task. This has been fixed.

073023

Node manager no longer randomly throws the OutputHandler error when trying to start a remote server.

074844

Fixed a problem that was causing an assertion error when using dynamic proxies.

075406, 076002

Fixed problems occuring under heavy load where NullPointer and ClassCast exceptions were occuring; also made some improvements to the NT muxer.

076605

Fixed a problem that was causing the message: <ExecuteThread: '12' for queue: 'default'> <> <> <000000> <No IORecord present for fd> to appear.

076705

Message Driven Bean deployment no longer fails and results in a NoAccessRuntimeException for guest if the destination is remote.

076997

Now, when deploying an EAR component to a cluster through MBeans, the JNDI bindings appear in all managed servers without the need to re-start the servers.

077248

Fixed problems connecting to EJB's over IIOP when native IO is turned off.

077831

When the AppletArchiver utility was used to generate a client JAR file and if the applet in question used the javax.swing.JApplet class in its code, then the AppletViewer was producing an error. This has been fixed.

077919

Using patch CR064447_61sp2.jar was causing an error in the log file after calling ObjectOutputStream.writeObject() on EJBHandle. The output of the EJBObject in the log was changing from LocalServerRef to LeasedRemoteRef. This has been fixed.

078431

Fixed a problem that was causing a deadlock between MuxableSocketHTTP and PosixSocketMuxer.

078952

An org.omg.CORBA.MARSHAL exception is no longer thrown while a null value in a serializable object from an EJB's remote method is being returned.

079220

When running JMS, the client was getting the exception:
Could not find RJVM for $Proxy68.. (IllegalArgumentException) in a cluster environment. The client was contacting one of the managed servers to drive. This has been fixed

079672

A VM crash is possible when WarClassFinder.getSource is invoked. Sun's fix for this problem are in JDK's 1.4.1_02 and 1.3.1_07. The Sun bug is: http://developer.java.sun.com/developer/bugParade/bugs/4369396.html.

080177

Using weblogic.deploy no longer causes memory leaks if you continually deploy and delete the same EJBs.

080740

If a web application that creates a file that got deleted when the server was shutdown, when running as a Windows Service, this file got deleted as expected when the server was shutdown from the command line (using the java weblogic.Admin SHUTDOWN command) or from the administration console. However, this file did not get deleted when the server was shut down by going to:

Start Menu --> Settings --> Control Panel --> Services --> Press Stop button for the service.

This capability is now implemented.

080895

When a stand-alone java client was calling a stateless session EJB, after about 500000 iterations, the following exception was being thrown on the client side:
Exception in thread "main" java.lang.ClassCastException: Assigning instance of class java.io.ObjectStreamClass to field weblogic.rmi.internal.ClientMethodDescriptor#signature at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2271)

This has been fixed.

080929

Now, if using wildcards, weblogic.refresh can refresh files.

081311

A SAXParseException on the DTD now has a severity of <Warn> instead of <Info>.

081404

The JMS Bridge Resource Connectors (jms-xa-adp.rar, jms-notran-adp.rar, jms-notan-adp51.jar) for Messaging Bridge are packaged with WebLogic Server 6.1 Service Pack 4.

081568

SNMP Agent can now monitor the ServletRuntime of Servlets.

081732

Using WebLogic Server 6.1 service pack 3, an exception was being thrown when using the Sybase database while trying to start the server. This has been fixed.

081765

There were problems with SSL closing sockets prematurely and causing muxer errors.

081853

Fixed some complicated problems with RMI-IIOP and the marshalling of complex objects, notably in environments using a mixture of JDKs.

081868

In WebLogic Server 6.1 service pack 2, when the admin server was shutdown using java weblogic.Admin SHUTDOWN, the SNMP agent was not generating the serverShutDown trap. It was able to generate serverStart trap when the server started up. Now, when the admin server is shutdown, the SNMP Agent will issue a self shutdown trap.

082004

The CR073910_61sp2.jar patch on WebLogic Server 6.1 service pack 2 was resulting in a memory leak. when getting a new InitialContext().

082263

The weblogic.deploy tool is now able to update the web app (WAR file) from Win2k to a server running on Solaris.

082533

Debug messages were being written to std.out when using the Xerces Parser. These messages have been removed.

082693

In WebLogic Server 6.1 service pack 1 and 2, if the server received a call from the old generation stubs, the server correctly sent peerGone to the client and logged an error. In WebLogic Server 6.1 service pack 3, the server printed a NullPointeException and the client waited until timeout. Now we have restored the earlier, correct, behavior.

083102

When deploying a couple of EJBs (that conform to the EJB 2.0 specification) with J2EE12OnlyModeEnabled="true", the server was throwing a couple of warning messages for a few beans and then crashing with a DistributedManagementException. This has been fixed.

083485

When invoking a t3 client, the client no longer hangs in JavaSocketMuxer with t3 as the default protocol.

083652

In WebLogic Server 6.1 service pack 3, applications were undeployed at startup and then redeployed twice. This has been fixed.

083654

Improved the performance of WebLogic Server 6.1 service pack 3, when continuous requests are issued from the Microsoft WAS tool.

083721

The FailureIsFatal option of the startup class no longer suppresses the runtime exception on a Solaris Environment.

083920

Supressed any startup traps when the admin server is re-started and it discovers that managed servers are up to avoid redundant traps being sent when the admin server is re-started.

084127

In production mode, even with auto-deployment turned off, WebLogic Server was still validating some application files that were not configured in the config.xml file. This has been fixed.

084622

Using ZAC no longer results in an assertion error when getInitialContext() is called.

085463

JNDI lookup failover now no longer takes such a long time when the network plug is pulled.

085914

SNMP request was timing out after a managed server was dropped. The SNMP agent no longer becomes unresponsive for a while on getnext requests when a managed server is down.

085979

Fixed a problem with MBeanHome.getAllMBeans() unnecessarily throwing an exception when a custom Mbean is defined.

086108

We improved performance; the ListenThread now consumes less memory than in Service Pack three.

086248

The component type for boxed RMI sequences was being forwardly declared twice-once correctly and once as an interace; the wrong type for sequences of valuetypes.

086350

Fixed a problem where if an exception's classname ended in a capital 'I' the IDL generated from it is mangeld and corrupt.

086362

Fixed a possible problem with the server hanging under heavy load when all the sockets were stuck in a CLOSE_WAIT state.

086761

The Weblogic.admin tool now correctly creates an execute queue so that it will be functional on server start-up.

087265

Fixed several incompatible serialVersionUID's so as to keep interoperability between WebLogic versions.

088372

Now, under load, we have fixed the problem that was generating multiple exceptions like: ArrayIndexOutOfBoundsException in weblogic.security.acl.TTLCache.cleanup.

089044

Loading the Administration Console no longer causes a browser/OS compatibility check.

Plug-ins

Change Request Number

Description

074128

Fixed a problem that was resulting in IIS getting a 10053 socket error.

076936

When specifying a multiple-level path at PathTrim under the ISAPI environment using WlForwardPath together such as:

WlForwardPath=/
PathTrim=/path/to/weblogic

ISAPI plug-in was not able to trim the specified path. This has been fixed.

078713

Added a new parameter set FilterPriorityLevel in the iisforward.ini file. The value for this parameter is 0, 1, and 2, which means low, medium and high for the filter priority. The default value is 2. If it is not possible to use a virtual host to set this property, use the iisforward.ini file.

079186

In accordance with the HTTP 1.1 specification, all plug-ins will now parse folded headers properly.

079683

Chunked Transfer Encoding HEX numbers were displayed to the browser when using mod_wl_ssl.so. This only happened when using jsp:include on Weblogic. The mod_wl.so worked correctly, but there was a long delay before the browser rendered the page completely. This has been fixed.

079973

In WebLogic Server 6.1 service pack 4, if Idempotent is off, failover is prevented and if ConnectTimeoutSecs=0, core dump is prevented. Retries are no longer attempted after ConnecyTimeoutSecs is set to 0 in the iPlanet config. The retries were attempted either with the default setting, which is 10, or with 0. Furthermore, when Idempotent was set to ON, the retries occurred five times, instead of two when it was set to OFF.

080219

There is no longer an iPlanet core dump when shutting down all WebLogic Server instances.

080382

An unexpected error message is no longer logged in the WebLogic Server error log when using the NSAPI plug-in.

080746

A 64-bit platform on native webserver plug-in is now supported.

081185

The CPU load no longer increases when cancelling the uploading of files.

081493

Fixed a problem that was resulting in HPUX-11 iPLanet crashing.

082093

When WebLogic Server is being hit via an iPlanet proxy with an NSAPI plug-in and a QALoad is used to generate a number of concurrent client connections, extra calls are no longer being made by the proxy plug-in to the app server under a heavy load.

082096 & 083386

With Idempotent=OFF, the IIS proxy plug-in no longer still attempts one re-try (two requests = one original + one re-try) for all POST requests after HungServerRecoverSecs.

082113

If the plug-in receives an error while reading data from the client, it no longer tries to send the incomplete data (request) to the back-end WebLogic Server.

082206

You can now exclude certain pages from being forwarded to WebLogic and have them be served by an IPlanet front-end. Add WLExcludePathOrMimeType to your obj.conf to exclude certain requests that match with the expressions you define (i.e: WLExcludePathOrMimeType="/test,/*.html")

083174

Using the latest IIS plugin, failover was not working when new values were being added to the session.

083643

Fixed a performance problem in NSAPI. The netbuf_getc function was very slow and not able to distinguish between '\0' and 0 in the postdata.

083558

Certified the newest Apache-Apache 2.0.42.

Servlets, JSPs, and Web Applications

Change Request Number

Description

042655

When using the access.log in the extended log format, the times at which the http requests are made are no longer given as the local time, instead of the GMT time.

053974

Besides being able to configure the name of the access.log, users can now select the convention for the rotated log for manageability.

058389

When getInputStream() is called against javax.servlet.http.HttpServletRequestWrapper, it no longer returns null.

063630

If a Web Application failed to deploy, then no other applications were getting deployed to a cluster. This problem has been fixed.

065967

Taglibs no longer fail when <type> is specified and the type is an array. Weblogic Server no longer sees it as a string when it is actually an array.

068577

In the generated code, the method _releaseTags() was not being called upon a <jsp:forward> although according to the JSP specification 1.2, all tag handlers need to be released upon DO_END_TAG. This has been fixed.

069731

When using JSPs in a webapp, the .java files that get created from the JSPs live under _tmp_war (under the webapp root). If it does not exist already, the _tmp_war directory is created at the time of WebApp deployment (during the initialization period after you start the server). If the server is run as root, the _tmp_war directory gets created by, and is owned by, root. At the end of initialization, nonPrivUser was being used to switch to a nonpriviledged user and the _tmp_war directory was inaccessible by the JSP servlet and WebLogic. This has been fixed.

071513

WebLogic Server is now validating the weblogic.xml file in the webapp.

073780

Improved the performance of JSP tags when using WebLogic Server 6.1 service pack 2 and the following three patches: CR065452A_610sp2.jar, CR063457A_610sp2.jar, and CR063829_610sp2.jar

073791

Fixed problems were customers were getting a NullPoinerException in the ChunkUtils.getEnd method after calling ServletOutputStreamImpl.write from their servlet code.

074265

The ServerMBean has a new attribute called MaxBackoffBetweenFailures. The default is 10 seconds. Set this to change the time period in which the server listen thread will send a "Failed to listen on port" if it is still trying to accept the socket connection.

074940

A NullPointerException is no longer thrown when using the size Cache Tag Attribute of the Cache Tag of the weblogic-tags.jar.

075471

JRun tag libraries are working on WebLogic Server service pack 4.

075721

The jsp:useBean tag with the beanName of TimeExpression is no longer interpreted incorrectly.

076375

weblogic.log will now be renamed based on the configuration of the log filename. Usage of % symbols in the logfile name will invoke the logic which renames log files based on the date/time when it gets rotated. The file being currently logged into will be the log filename stripped off its % symbols if they exist.

Examples of valid formats:
weblogic_%YYYYMMdd%_%HH%_%mm%.log
foobar_%YYYY%-%MM%-%dd%_%HH%_%mm%.log

Invalid formats will fallback into our default log filenames. Anything that's enclosed within two %'s will be decoded based on SimpleDateFormat. As of now this format will apply to the filename only. Not to the directories.

077018

Prevented a ClassCastException in ServletAuthentication when using request/response wrappers.

077306

Temporary patches no longer cause recompilation of included (precompiled) JSP classes.

077422

The CookieParser.cookieToString creates the expires cookie with a SimpleDateFormat that contains a comma, ','. The comma in the expires date is causing the cookie to be parsed incorrectly when it is returned in the request. The comma is interpreted as a cookie separator and breaks the parse of the expires date. This has been fixed.

077888

setCharacterEncoding will now throw UnsupportedEncodingException.

078090

According to the JSP specification, if you use jsp_precompile in the request parameter, the container should compile the JSP (if not compiled), but must not display the JSP. Since WebLogic Server parses the query string and finds the jsp_precompile, it was not displaying the page on the browser.

078262

Added getResourcePaths(String) to the ServletContext.

078325

Fixed a problem that was resulting in an UnsupportedEncodingException if there were extra quotes around the charset value.

078698

The access.log file is now rotating by size when the log size exceeds 2MB.

079582

WebLogic Server 6.1 service pack 3 threw a SocketException during data sync. This has been fixed.

079767

When redeploying EAR, WAR, or JAR files to WebLogic Server, with every redeployment of an application or component, the .wlnotdelete directory of the managed server no longer increases in size.

079892

The CPU usage no longer pegs to 100% while executing a CGI script and hitting the stop button in the middle.

080090

When re-directing, the location header will always use the following parameters, if they are specified:

FrontendHTTPPort
FrontEndHTTPSPort
FrontEndHost

080384

The HttpClusterServlet was marking a server as bad, even if just one response had been scrambled in the status code header. This has been fixed.

080751

Custom exceptions extending servlet exceptions will now be redirected to error page if configured.

080791

Folded headers in the cluster/proxy servlets are now considered.

080837

Added a new element in the weblogic.xml file:

<!--
The wl-dispatch-policy can be used to assign the webapp to a configured execute queue by identifying the execute queue name. This webapp level param can be overridden at the individual servlet/jsp level. eg:
<servlet>
...
<init-param>
<param-name>wl-dispatch-policy</param-name>
<param-value>CriticalAppQueue</param-value>
</init-param>
</servlet>
-->
<!ELEMENT wl-dispatch-policy (#PCDATA)>

081071

There is no longer a NullPointerException thrown at weblogic.servlet.internal.ServletContextManager.trimAbsUrl.

081484

Session attributes are no longer lost when using the HttpSessionListener with PersistentStoreType as replicated but able to retrieve the session attributes when non-replicated.

081521

It is now possible to call a CGI script from a JSP.

082156

Changed the implementation of isRequestedSessionIdValid so that it does not always return true.

082238

CreateSessionServlet was checking for the existence of the Cache-Control header, setting it to a valid value if it exists, or adding it to the header list if it does not exist. In both cases, it added another bogus header. This problem was fixed by setting CacheSessionCookie to true in weblogic.xml.

082310

JSPs with a page contentType directive can now be deleted or overwritten in an exploded WAR file.

082461

FileServlet was not working in WebLogic Server 6.1 service pack 3. It is working now.

082580

HTTP POST parameters were not preserved if a form-based authentication is invoked and authentication is successful when accessing a URL in WebLogic Server 6.1 service pack 3.

082671

Made HttpSession.getServletContext() public in the internal implementation.

083191

The console is no longer displaying incorrect values for Servlet Average Execution Time.

083200

WebLogic Server is now filtering correctly with nonProxyHosts.

083487

CGIServlet now works with exact match <url-pattern>.

083517

HttpClusterServlet was not proxying a request to SSL even when SecureProxy was ON. This has been fixed.

083597

In WebLogic Server 6.1 service pack 3, if the content type using the page directive is set as:
<%@ page contentType="text/html;charset=UTF-8" %>
the content type was not set properly and the desired output was not obtained. This has been fixed.

083912

An ORA-01461 error no longer occurs while the server is trying to write the session data in the JDBC managed persistence when using the Oracle thin Driver.

084002

When WebLogic Server returned an HTTP code 204, it set the Content-length to 886 with an HTML error page. Therefore, the load runner client was failing and generating an error stating that "204 responses codes should not have a body but the Content-length was set to 886 (with an HTML error page)". This has been fixed.

084030

When an exploded web-app was shared by two servers, the generated tmp lib directory got deleted at the second server's start. The directory is no longer deleted.

084058

The request.getUserPrincipal() method was returning guest after ServletAuthentication.logout(). Now, the getRemoteuser() returns null.

084536

Fixed a problem where the patch for CR083377 was causing problems with security and the SSL connection.

084649

There are certain environment variables that a CGI server is expected to provide to scripts that run within it. SERVER_URL, HTTP_COOKIE, and QUERY_STRING, which are present in Netscape's CGI server, were unavailable when running the same CGI program inside of WebLogic's CGI servlet. When a request was made for one of these variables, NULL was returned instead of a value. This has been fixed.

084785

The GenericProxyServlet can now handle wrapped responses.

084847

For chunked transfer, WebLogic Server was including a hexadecimal number which other servlet engines used to ignore. This has been fixed.

085754

If newlines/comments were put in the intermediate JSP BEATestCase2.jsp, when used with a request dispatcher, the client got a blank page. There was no exception thrown on the server side. This has been fixed.

086026

The parameter, CacheSessionCookie, used to default to false. Now, it defaults to true.

086052

HTTPS connections outbound from WebLogic Server did not work without a trailing slash '/' on the URL. This has been fixed.

086280

There is no longer a NullPointerException thrown when accessing a servlet over a Keep alive connection.

086481

Fixed some problems when a web application downloads a larger file and the buffer overflows while reading the multi-part form data.

088301

Fixed problem where an included resource was not sent to the servlet output stream when dispatched from another resource that was Forward dispatched inside a JSP BodyTag.

NOTE: The nested BodyTag tag output stream was not being flushed since the forward dispatched request caused the tag to exit - but WebLogic still presumed the output should go to the Tag's nested output stream. This was resolved by clearing out reference to the BodyTag nested output stream when the Forward request was dispatched.

Security

Change Request Number

Description

058355

When a user called login() on the LoginContext, this call was directly mapped to the LoginModule's login(), but the logout() method was not implemented. Therefore, a call to this method could not be mapped to the LoginModule's logout(). In WebLogic Server 6.1 service pack 4, LoginModule.logout() is implemented.

068729

The weblogic.security.SSL.SSLCertificate class is now documented.

075109

LDAPRealV2 now caches memberships.

075451

When trying to obtain an InitialContext to a remote WebLogic Server from within a WebLogic Server, after making an SSL connection with weblogic.net.http.HttpsURLConnection, an exception is no longer thrown.

076783

Using the RDBMS realm, extra calls were being made. The caching realm is now fixed to avoid having these extra calls made.

077233

The absolute path of SSL certificates is now given.

077425

When a custom realm was used with a caching realm and the case insensitive cache was set to a default of true, the caching realm was throwing an error message, "Server cannot check in a case-insensitive way". This has been fixed.

078893

If weblogic.management.password is not blank, the custom login module never got called. For j_security_check to use the JAAS loginmodule, it is necessary to use programatic authentication (servletauthentication.weak()) in combination with JAAS loginmodule.

079183

After calling weblogic.security.acl.ManageableRealm.setName, weblogic.security.acl.ManageableRealm.getAcl no longer returns null.

079364

deleteAcl was only working with the getACLOwner principal. This has been fixed.

079637

Added the pkpassfiile property to specify the name of the file containing the private key password.

082003, 087419

Using an LDAP realm configured for Microsoft Active Directory Server, basic authentication was failing while form-based authentication worked fine. This has been fixed.

082098

Credentials are now used / verified against the remote server realm.

083478

Even though the email is not required in the certificate form, EMAIL= was appearing in the certificate. This has been fixed.

084166

Fixed the caching of delegate groups so that with a nested group there is improved server performance.

087485

With WebLogic Server 6.1 Service Pack 3, LDAP was calling Group.isMember() for every member of group. In this Service Pack we restored the original behaviour of an LDAP realm: now if the groupmembershipcache value is set to 0 then WebLogic checks the LDAP realm for group membership, thus preventing loading all members() if the group contains many members.

System Administration

Change Request Number

Description

059779

Data sources can now be bound to the same JNDI name on different servers.

062102

Applications are no longer copied to the managed servers upon startup if they do not need to be copied which results in increased disc space.

063630

It is now possible deploy remaining applications to the managed servers upon a failed deployment.

072833

When a managed server was configured from the admin console with the listenAddress field blank, WebLogic Server was allowing the multiple instances of this managed server with the same name to be run from different machines. This is no longer possible.

074370

When using WebLogic Server 6.1 service pack 2, a javax.management.AttributeNotFoundException was being thrown when using the EJB descriptor editor in the admin console. This has been fixed.

074653

The Admin console Deployment Descriptor Editor now replaces "&" with "&amp;" when writing to memory/disk because "&" is a special character which must be escaped as "&amp;" in XML files.

075949

Fixed a problem that was causing weblogic.deploy to undeploy the JAR file immediately after deployment.

076539

Web apps with load-on-startup are now loaded in the correct order according to DeploymentOrder.

078257

The admin server JNDI was not showing the managed servers' MBeanHome causing a NameNotFoundExceptions to be thrown. This has been fixed.

079270

The application redeployment (delete & deploy) operation was not always successful when some of the targeted managed servers were down. For example, the JNDI entries for EJB were not registered in running servers, or "Targets" attributes in the config.xml file were lost because of a warning message. This has been fixed.

079455

A ConfigurationError is no longer thrown upon deployment failures.

079819

The time it takes managed servers to start up with a large number of deployed applications has been shortened.

080016

There is no longer an error deploying an application while starting the admin server if the application targeted to the virtual host (which has been targeted to managed server) and the admin server.

080324

Exposed the setParent method to a public API.

080690

If the admin server was bounced and re-started, it re-established a connection to the managed server, but the JNDI tree did not show the managed servers. As a result, the application was getting a NameNotFoundExceptions. It would only show up in the admin JNDI tree once the managed servers were re-started. This has been fixed.

080778

Turning on session monitoring no longer causes traffic to the admin server every time a new session is created.

081736

After weblogic.Admin -help prompts for a guest password, it no longer ignores the password.

082765

When calling shutdown to shutdown a managed server, removeManagedHome is also called to remove the managed server from the cache. Otherwise, needless RMI calls would be made when any other managed server boots causing startup delays.

082910

It is now possible to remove a JDBC Connection Pool using MBeans when a customer MBean is registered from within an EAR file.

083400

There is no longer a StackOverflow during managed server startup using T3s as the default protocol.

084484

When starting a server from a directory other than the domain directory, the option -Dweblogic.RootDirectory=<root directory> can be specified. If the start script is changed to go to the root directory, it would find the application, but the config.xml path got modified to be an absolute path with the RootDirectory appended. The config.xml path no longer gets changed to an absolute path.

084740

When deploying an application on a cluster using weblogic.deploy, the deployment was not effective until the server was restarted.

086235

When trying to get the server version out of the ServerRuntimeMBean.getWeblogicVersion method, only the version info for the patch that was the first in the classpath was returned. In WebLogic Server 6.1 service pack 4, the whole version information is returned by the weblogic.Admin command.

Web Services

Change Request Number

Description

076510

When there was a webservice that had a method that received a String as a parameter that is actually an XML document with CDATA sections, after invoking the method, the following response was sent:

weblogic.soap.SoapFault: Connector - Bad request to the server.

This has been fixed.

082661

Now, wsgen handles an extra classpath.

084960

Fixed a problem using the URLConnection method to make an HTTP connection to a Web Service. Weblogic overrides java.net.HttpURLConnection with its own version which will throw an exception from the getInputStream method if a status code is greater than 400. When the exception is thrown there is no way for the WebService client to retrieve the inputstream, and thus the HTTP SOAP Binding is broken. If you have this problem, set the new command line option -Dweblogic.net.http.ignore500status to true.

085214

Fixed a problem that occurred with webservices when he passing dates as parameters. A java.lang.IllegalArgumentException is no longer being thrown.

XML

Change Request Number

Description

080756

When converting Japanese characters by using the built-in XSLT processor, the characters got changed into the unexpected code. This has been fixed.

080961

Fixed a Xerces 1.3.1 bug in org.xml.sax.helpers.AttributesImpl.removeAttribute().

081372

DocumentBuilder.parse() is no longer multi-thread unsafe when input encoding is 'Unicode'.

081870

When the XSLT output method was set to HTML (required):

<xsl:output method="html"/>

the spaces in HREF attributes in anchor tags were encoded to "%20". Netscape failed to interpret the "%20" as a space, breaking the link. This has been fixed.

 


WebLogic Server 6.1 Service Pack 3 Solutions

The following sections describe problems that were resolved for the release of WebLogic Server 6.1 Service Pack 3.

Classloader

Change Request Number

Description

063742

There was a java.lang.VerifyError thrown during skeleton generation for the Remote interface of Entity bean. This has been fixed.

064273

In the Classloader, weblogic.utils.classloaders.GenericClassLoader, the definePackage() method now sets the package information according to the manifest.

069506

ClassLoader.getResources is now working when trying to access an XML file which is in the Class-Path: entry of the EJB's manifest file.

075553

Fixed a memory leak that was occurring because the core classloader was being stored unnecessarily.

Cluster

Change Request Number

Description

072281

HttpClusterServlet now works properly when WAPEnabled=true.

072464

A NullPointerException no longer occurs during failover using SFSB handles created within the server.

073917

NoSuchObjectException was being thrown on failover from SFSB's handles in a cluster. This has been fixed.

073920

The Execute Queue length doesn't appear in the console and this functionality is not implemented with WebLogic Server 6.1.

074058

When using the IP name instead of the DNS name for the WebLogicCluster parameter, the secondary was marked NONE if the primary went down. This has been fixed.

074236

Added the attribute, MemberWarmupTimeoutSeconds, to ClusterMBean.The default value is 0 which results in no cluster warm-up. By default, the cluster start-up sequence remains unchanged. If a value > 0 is set, the cluster members wait for that period of time to synchronize with other members during start-up. All MessageDriven Beans are deployed after the warm-up time. Only then do we start accepting client requests. There is no separate property for delayed MessageDriven Bean deployment.

Console

Change Request Number

Description

051136

Broken monitoring link removed from the console.

055821

Forced the Public ID to be non-null for editing.

056161

Using the console EJB runtime monitoring customization, it is now possible to view the machine on which the EJB is deployed.

058271

Using the console to modify the deployment descriptor no longer changes the bean's manifest file.

059784

wls_management_internal{1,2} is no longer selectable as a DefaultWebApp.

059963

Added Max Open Sock Count to server->config screen in the console.

060116

The admin console no longer displays the Automatic Deployment checkbox when you startup WebLogic Server in production mode.

061664

The server shutdown message is now correctly displayed using a Netscape browser.

061686

Fixed broken deployment descriptor help links.

061838

It is now possible to start the managed server without restarting the admin server.

062020

The console XML editor is now aware of <validate-db-schema-with>.

062788

Fixed the Netscape default value for the refresh button so that a page in the security console was not re-appearing every time you clicked the OK button.

062991

Added information to the console help files to explain how to set up the five fields for using Node Manager to remotely start the managed server.

063543

The ConsoleMainAttribute for servlet monitoring in the console is now enabled.

064849

Modified the weblogic.xml descriptor editor to handle the PersistentStoreTable parameter.

067101 & 073625

Remote context viewing the local JNDI tree via the console is now possible.

067362

The console no longer references the wrong login timeout attribute.

070018

Start Default Console no longer fails when default browser is Netscape 6.2.

072909

The correct JMS pool name is now displayed in the runtime table.

073536

The console now has a check box that allows for optional mutual authentication.

074693

The link used to save realm implementation changes is now more explicit.

075338

The console now displays the correct information during monitoring of a Web Application.

EJB

Change Request Number

Description

047305

Fixed an error in the TxCommits value in Console.

054789

The message-driven bean no longer throws a NoSuchElementException and the message listener is no longer being removed from the list before the listener was finished processing it.

056081

Deployment of EAR stops short of setting component target.

057608

Now able to save more than 4K of data with CMP beans.

059045

run-as works in ejbCreate().

059250

A NullPointerException no longer occurs in ejbc when the persistence element is missing in WLDD.

060720

In 6.1 service pack 2, if you are using Blob/Clob, you have to set <isolation-level> to TRANSACTION_READ_COMMITTED_FOR_UPDATE. Otherwise, you will get the following exception:
java.io.IOException: ORA-22920: row containing the LOB value is not locked
If this happens, when using Blob/Clob, the container will lock all the tables within the transaction. In 6.1 service pack 3, you don't need to set <isolation-level> to TRANSACTION_READ_COMMITTED_FOR_UPDATE anymore. The container will only lock the table that contains the Blob/Clob, and the other table within the transaction will not be locked. This make Blob/Clob much easier to use.

060738

Multiple phantom message-driven bean connections are no longer created without new corresponding sessions being added to the list after a JMS client reconnects to a restarted JMS server.

060867

EJB2.0 deployer no longer throws AssertionError when RemoteMethod name starts with 'find'.

061700

Some identifiers in generated SQL Query were missing quoted identifier escape which may have caused the generated EJB CMP SQL to fail to escape the Quoted Identifiers. This has been fixed.

062256

The -c flag in DDConverter now converts the input JAR files into ejb20 and combines the JAR files. DDConverter would not work with the destination JAR file specified as follows: java weblogic.ejb20.utils.DDConverter *****-c new.jar***** -d . convert.jar.

062481

Added an attribute in weblogic-ejb-jar.xml to indicate if EJB is collocated with web tier.

062518

DDConverter no longer throws an exception when it encounters a findAll finder query.

062626

An empty ejb-ql tag is now allowed.

062676

Load-balancing of Stateless EJBs in a cluster no longer fails for random load algorithm.

062916

In 6.1 service pack 2, a caller's transaction was not being resumed after a transaction started on the server completed. When this happened, the caller's transaction would never complete. This problem would only occur when a remove method that had a transaction attribute that would cause the client's transaction to be suspended was called on an EntityBean in a transaction and a new transaction was started on the server to service the call. Transaction attributes that cause this behavior are NotSupported and RequiresNew. In 6.1 service pack 3, a caller's transaction is being resumed after a transaction started on the server completes.

062974

When a single-digit finder was defined on a 1.1 CMP bean, it did not throw a FinderException when more than one result was returned from the query. This has been fixed.

063077

The transaction time out attribute in weblogic-ejb-jar.xml now works.

063146

When a BMP EJB's concurrency strategy was set to Exclusive and the transaction attribute was set to NonSupported, a different instance was assigned when the transaction timeout threshold was met. This has been fixed. In addition, a remote exception is no longer being thrown when the local transaction is rolled back.

063387

WebLogic Server no longer fails to clear a lock on an entity bean after a deadlock situation. The waiters in the LockManager are now being cleared.

063469

A NullPointerException is no longer thrown while creating CMP EJB relations.

064293

ExclusiveLockManager is now removing waiters from the list even if the waiter happens to be TimedOut.

064425

Each ejbHomeMethod call was creating a new bean instance instead of utilizing pooled bean instances. This has been fixed.

064447

When decoding an EJB object handle from a cookie, an InvalidClassException is no longer being thrown.

064561

When <finders-load-bean>=false, new bean instances were being created disregarding pooled instances. This has been fixed.

064625

No longer getting 'local interface must not include java.rmi.RemoteException in its throws clause' from the JDBC when this should not be gotten.

064967

The ejbc no longer fails due to empty strings environment variables.

064969

The DDConverter now generates correct assembly descriptors.

065092

For EJB1.1 beans in 6.1 service pack 2, in a single transaction if the persistent field of a bean is changed and then a finder is invoked which returns the same bean, the new value of persistence field is overwritten by the value retrieved from the database. In 6.1 service pack 3, changes made to the EntityBean are no longer lost in the middle of a transaction.

065290

EJBC/RMIC generates XML descriptors with clusterable=true even for beans for which clusterable is false.

065321

Fixed a locking issue with an entity bean.

065571

When the entity bean didn't have a create method, DDinit was not generating the Descriptor files. This has been fixed.

066245

The ctx.getCallerPrincipal no longer returns run-as principal.

066644

A JMS message-driven bean and Queue with persistent file store was carrying over the transaction context in onMessage. This has been fixed.

067018

Calling EntityContext.getEJBLocalHome from the home method was throwing an IllegalStateException. This has been fixed.

067515

When invoking a JSP during 5.1/6.1 interoperability testing, the first time succeeded and the second time produced an error. This has been fixed.

068262

For EJB1.1 beans we were using setBytes to insert a value into a LONG column. This failed when the data was larger then 4K. We are using setBinaryStream now, which avoids causing the following exception:
ejbCreate(): java.sql.SQLException: ORA-01461.

068569

A tmp_ejb directory was being created even if not using server-side ejbc. This has been fixed.

068971

The ejbc no longer generates JDBC code for CMP EJBs with deprecated methods.

069280

An Illegal Reentrant Error is no longer incorrectly thrown by WebLogic Server during concurrent client calls to an entity bean.

069391

Fixed the CMP Manager cascadeDeleteRemove which was broken for CMP Partners.

070099

DDConverter fixed to generate the method-permission tags.

070565

Added a property to weblogic-ejb-jar.xml, called "clients-on-same-server", to indicate that the EJB is collocated with the web tier. This is a performance fix, designed to reduce multicast traffic. The default is false.

070754

In 6.1 service pack 2, afterCompletion was being invoked on a StatefulSession bean while the bean method was still busy processing. This behavior is counter to the EJB 2.0 specification. In 6.1 service pack 3, serializing Business methods and EJB Callbacks are being invoked which means that afterCompletion will not be invoked on a StatefulSession bean until the bean method has completed processing.

071027

Previously, the container checked for the CMP table by firing an SQL query (select * from tableName where 1=0). This way of checking is not efficient in the case of DB2 where the query generates a full table scan and is very slow if table has a lot of data. The container now provides an option to check the table using DatabaseMetadata. Although usually slower than checking using an SQL query, this way works well for DB2. See the <validate-db-schema-with> tag in the weblogic-rdbms-jar.xml file for more information.

071296

When doing an ejbCreate() on an entity bean ( EJB 2.0 ), a java.lang.IllegalStateException was being thrown. This has been fixed.

071377

Now WebLogic Server supports the ability to generate the EJB QL extension ? IS [NOT] NULL.

074710

An error no longer occurs while running a stateful session bean in a cluster. When a stateful session bean was passivated, the remote entry was removed and when the bean was activated, the remote entry was not returned, resulting in a NullPointerException.

075867

Message-driven beans deployed on WebLogic Sever had a problem re-establishing a connection to an MQSeries JMS server. Extra connections were created because of the number of triggers scheduled. This has been fixed.

076167

In 6.1 service pack 2, if an SQLException was thrown in ejbLoad of a read-only bean, the caller's (global) transaction was not being resumed. In 6.1service pack 3, it is being resumed.

078147

Fixed a problem that was causing the following exception when using an EJB11/ CMP11 bean:

Exception in ejbCreate(): java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column

Examples

Change Request Number

Description

048185

The ACL example is now documented with the client example.

053467

The second compilation of the i18n.logging.message directory no longer gives errors.

056884

Fixed an error in the instructions for an example.

057904

Changing the connection pool is now mentioned in petstore.html.

062962

The username/password authentication in the JAAS example now works on a UNIX environment using the CertLoginModule .

062999

Fixed a problem that was occurring when establishing a WLEC connection between WebLogic Server and Tuxedo. The WLEC simpapp example now connects to Tuxedo service.

063229

Made improvements on examples/iiop/ejb/stateless/server/tux.

071478

JMS Draw demo example is no longer broken with unique windows.

077055

Fixed a problem that was causing the Petstore server to begin with an error making it impossible to deploy Petstore.

JDBC

Change Request Number

Description

052393

Updated the thin driver so that it does not have an error in JDBC session persistence while putting StringBuffer object.

054864

In 6.1 service pack 2 the server was hanging when using MultiPool with more than one database under heavy load. The MultiPool request would hang because the database was not responding which resulted in the whole server locking up at weblogic.jdbc.common.internal.MultiPool.searchHighAvail(MultiPool.java:200).The cause was over-synchronization in the code which has been fixed in 6.1 service pack 3.

057340

When a connection pool is empty, the message now says "No available connections in pool."

057977

Connection pool does not rollback anymore on cleaning up JTS connections

059020

Deadlock no longer occurs if weblogic.jdbc.common.pool.shutdownSoft() is called when the connection pool is used by another user.

061786

CREATE_POOL now fires the connection pool just after DESTROY_POOL.

064198

Several classes were directly referencing optional Oracle classes in the server side code. This no longer occurs.

066001

Added a property to the JDBCConnectionPool XAPassword to encrypt the database's password.

066964

When using the WebLogic jDriver for Oracle/XA for a JDBC connection pool, refreshing the connection pool after a DBMS failure and restoration occasionally resulted in a core dump. This has been fixed.

066966

The ResourceAllocator monitor is no longer held while making a JDBC call to test table.

068490

Synchronized the call to xa_open at the java level.

068952

Provided automated build scripts for jDrivers.

070209

It is now possible to use the Oracle 9.0.1 Thin Driver to connect to an Oracle database. To use the driver, include the path to the driver class files (classes12.zip) to your CLASSPATH before the entry for weblogic.jar.

071974

PreparedStatement cache size set to 0 by default.

073640

Added a new attribute for a JDBC connection pool: Open String Password (or XAPassword in the config.xml file). This new attribute allows for encryption of the database password in the open string for connection pools that use an XA JDBC driver that requires an open string. For more information, see Database Passwords in Connection Pool Configuration in the Administration Guide.

076090

Improved the behavior of database passwords included in the Properties attribute of a JDBC connection pool. If you specify a database password as part of the connection properties or open string, WebLogic Server parses the values and moves them to the Password and Open String Password attributes, respectively, which are encrypted when stored in the config.xml file. For more information, see Database Passwords in Connection Pool Configuration in the Administration Guide.

jDriver

Change Request Number

Description

056531

There is no longer a performance regression in jDriver.

061643

weblogic.Admin RESET_POOL no longer fails after the database recovers.

063872

When a string value is returned from the out parameter of a stored procedure, trailing spaces are no longer stripped.

063874

The time component of an SQL DATE was not removed when the JDBC getDate() methods were used.

069109

Modified JDBC test scripts to make Oracle 8.1.7 the default.

069676

The WebLogic jDriver for Oracle now supports the we8iso8859p15 character set.

070878

If PreparedStatement.setString was used with an incorrect positional index of '0' with a DBMS connection created using the WebLogic jDriver for Oracle, the JVM would crash. Now, the jDriver gracefully handles the coding error and throws an exception.

JMS

Change Request Number

Description

044976

Made sure that returned values and exceptions from any get method in MapMessage conform to the JMS specification.

058876

Disabling or enabling the JMS server through the Administration Console was causing WebLogic Server to throw an exception for any registered durable subscribers. This has been fixed.

061094

In a clustered environment, a NoSuchObjectException is no longer thrown for JMS clients listening on a JMS server if one of the WebLogic Server nodes in the cluster is not immediately restarted after shutting down.

061552

JDBC connection is no longer reset after the server is idle for three hours.

062669

JMS now supports selectors with unicode strings. Specifically, the expression parser now uses a StringReader and the charVocabulary range was increased.

062744

A NULL value is now accepted for a JMS MapMessage property to conform with the JMS specification.

064727

Fixed a problem with creating ObjectMessage for JMS in an applet.

067134

Added weblogic/management/configuration/JMSConstants.STORE_ENABLED_XXX.

067286

JMS paging no longer fails to page during a server restart.

068667

Upon booting, JMS non-persistent-message-paging file stores was failing to make available all disk-blocks for re-use. This has been fixed.

069757

JMS with SSL no longer throws the weblogic.jms.common.LostServerException.

070454

Message recovery no longer fails nor is delayed upon server crash when using message- driven beans with durable subscription.

072556

No more JMS Queue deadlock in addReader( ).

073403

Fixed a problem that was due to a JNDI object having the same JNDI name of a different type.

JTA

Change Request Number

Description

062681

WebLogic Server no longer fails on JDBC connection request to the pool whenever the connection object is left unclosed in the JDBC code.

063053

The XA connection can now specify the openString property.

064232

The javax.transaction.HeuristicMixedException is no longer being thrown sporadically at commit.

064403

After a Transaction timeout using the XA driver and a Stateless Session Bean, the XAConnection became unusable until WebLogic Server was restarted. This has been fixed.

064825

Method descriptors for SubCoordinatorImpl are now getting parsed at runtime.

065495

Added a system proprety to allow users to set the amount of time they are willing to wait to obtain the Coordinator reference. To specify the wait time, specify -Dweblogic.JTA.ContactCoordinatorWaitSeconds=<seconds> when starting the client or server.

066420

JTA server-resource cache was not being updated correctly on a member server peerGone event. This has been fixed.

068447

XA transactions with TestConnectionsOnReserve="true" no longer fails.

070855

JTA server-resource cache updates delayed under load no longer causes aborted transactions.

076439

Fixed a problem that was causing random XA transactions to be rolled back with an Illegal State (Expected: preparing) message.

Miscellaneous

Change Request Number

Description

042372

The API URL() provided in WebLogic now functions properly. For some URLs, it was causing an exception error.

050388

Statistical information for the Jolt connection pool is now being displayed in the console.

052478

A timing related JVM bug on Solaris is encountered that causes the VM to exit during object deserialization of management objects at server startup. If you run into this JVM bug:

  • Re-start the server.

  • Upgrade the Virtual Machine to JDK version 1.3.1_04.

053029

The RA component is now removed during delete.

054080

In 6.1 service pack 2 on a Solaris machine, when WebLogic Server was using SSL to communicate (both as a client and a server) and was using NativeIOEnabled="true", the JVM instance consumed more and more memory and eventually hit the heap size limit. This bug was encountered at a WebLogic Integration installation which relied on SSL communication between trading partners. In 6.1 service pack 3, this problem no longer exists.

055007

Created a configurable parameter, weblogic.system.openSockCount, that would determine the number of allowable connections.

056622

Added a new system property: weblogic.net.http.URLStreamHandlerFactory

056698

Fixed a problem with installing customer protocol handlers.

057313

Fixed ConcurrentModificationException while iterating through AbbrevMap.

057357

Fixed a problem that occurred when defining an error page 401.

057743 & 060981

The WebLogic Server verboseToZip and logToZip utilities have corrected problems with versioning information. Manifest entries, on which WebLogic classes depend for versioning information, are now pulled from weblogic.jar. The verboseToZip output file no longer includes entries for dynamic proxy classes. If a message log contains any instance of i18n messages, then logToZip now pulls all of the i18n related files from weblogic.jar to the client jar.

058327

Getting ClassCastException when trying to make a look-up to DataSource from an Applet

058358

The <alt-dd> tag in the application.xml file is now being recognized.

059054

Added the following symbol as a cookie separator: ","

059104

A property called javaHome which specifies the JVM that is used to start up a managed server was added for node manager.

060062

The Connections High column in the connection pool monitoring screen no longer includes connections refreshed by WebLogic Server.

060079

When using JMS over t3s, a MaxMessageSizeExceededException was being randomly thrown even though the message size never exceeded 50k.

060211

Fixed the placement and quotation of startup arguments passed to node manager from the Remote Start tab in the Console.

060739

UserTransaction now works properly under load. Now, transaction-managed EJBs control the isolation level automatically if the EJB starts the transaction as well as if the user starts the transaction.

061059

It is no longer possible to find a record after it has been removed from a database.

061458

WebLogic Server now supports starting NodeManager on Solaris and HP-UX without using Native libraries.

061512

Fixed problems starting WebLogic Server as a service on Windows NT and Windows 2000.

061847

There are no more error messages when using HTTP with examples.io.FileBrowser.

062086

Using DDConverter to convert from CMP 1.1 to CMP 2.0 no longer thows exceptions for JAR files that contain more than one EJB.

062177

There are no longer any peer to peer connections in clustered nodes.

062375

PeerInfoable.getPeerInfo no longer returns null when marshalling a transaction's propagation context in a clustered environment.

062439

Added error handling code in the native layer of Windows.

062565

The 1.2 JVM client no longer causes a socket connection leak.

062752

jDriver was giving an ORA-24347 error on an outer join operation which selected more than 100 rows. This has been fixed.

062926

JSP page tags can now handle MS932 specific characters on Solaris or HP.

062989

A JMS client running on a slow modem connection and trying to establish a JMS topicConnection with a cluster of two WebLogic Servers no longer gets a ClassCastException.

062997

The servlet engine now removes the servlet stub of the generated JSP file if the source file has been deleted.

063103

Context lookup was failing within a spawned thread. This has been fixed.

063147

Applets no longer fail during downloading of Home interface Stub with the JDK 1.3.1_01 plug-in.

063310

CGIServlet no longer fails under load due to File Descriptor leak.

063354

No longer receiving a ClassCastException from rjvm.MsgAbbrevInputStream.readClassDescriptor() when looking up a session bean from a servlet.

063671

Client side using HTTPS tunneling was producing the get java.net.ProtocolException: Tunneling result not OK, result: 'DEAD'

063830

No longer throwing a javax.transaction.TransactionRolledbackException when the cache is full.

064117

Fixed a problem that was causing the server to abort the connection and result in a java.net.SocketException.

064125

When a server was started via the node manager, the password is no longer being seen in the start command.

064130

ReplicaLists are now serializable in order to allow more than one lookup under IIOP.

064391

When deploying applications that contain malformed MANIFEST.MF entries, exceptions are no longer being thrown.

064404

When the same instance of IE is used to configure a webApp using the console and then to access the same webApp (containing French characters for instance), sometimes accented characters were not being displayed correctly. This has been fixed.

064434

If a servlet used RequestDispatcher.include() to include the output of a JSP, the post-processing filter was not able to add a header to the reponse. This has been fixed.

064860

WebLogic Server no longer fails to execute CGI scripts with JSPs that use page buffering.

065697

When SetUID was enabled, the server wouldn't start. This has been fixed.

066130

Corrected an error message that was being thrown by the ejbc during compliance checking.

066158

When a Log Filter is defined and targetted to the managed server, the trap is now invoked when using the NonCatalogLogger.

066252

Using a specific Factory/Trader pattern, a ReplicaAwareRemoteRef warning log was being displayed on the client side. This log is no longer displayed.

066504

Updated the SP installer with JDK 131_02 for Solaris and Windows.

067508

A generic classloading exception was being thrown when generating a thin client with AppletArchiver. This has been fixed.

067516

The appletArchiver now spools the i18n and manifest files to the thin client jar.

067517

AppletArchiver no longer generates L10n type exceptions when building the client jar.

067648

Fixed a problem that was causing WebLogic Server to hang due to the PosixSocketMuxer code.

068570

Upgraded the SNMP kit to ensure Agent is not affected by DOS attacks.

069043

When using HttpProxyServlet in conjunction with a filter, a SocketResetException no longer occurs in NTSocketMuxer.

069675

Reading from a file with @file option on the BEASVC command line no longer has a limitation of 4K.

069991

No longer receiving a ClassCastException from rjvm.MsgAbbrevInputStream.readClassDescriptor() when looking up a session bean from a servlet.

070575

After the server had been running about two days, a client running on a separate JVM was not able to look up a bean due to the JNDI tree and JNDI objects eventually becoming out of sync. This had been fixed.

071580

WebLogic Time service thread is now setting Context Class Loader.

071822

In order for jCOM to successfully find the WebLogic license file, the beahomelist file must be located in C:\bea.

072010

Configuring WLEC connection pool was interfering with command line properties. This has been fixed.

072061

The node manager -Dweblogic.nodemanager.sslHostNameVerificationEnabled=true option now performs host name verification.

072211

Improved the Solaris native implementation of node manager for handling error conditions.

072228

WebLogic Server was not firing a trap for the JDBCConnectionPoolRuntime on the admin server. This has been fixed.

072278

Improved the HPUX native implementation of node manager for handling error conditions.

072327

Attributes with type LONG can now be montiored with SNMP.

072495

Fixed a memory leak caused by Timer Services.

072904

When CallRouter was used, ReplicaList was being corrupted. This has been fixed.

073116

Fixed the weblogic.Admin SERVERLOG command-line utility.

073201

When running multiple HTTP tunneling clients over a modem connection, the server was eventually hanging. This has been fixed.

073400

Enhanced verboseToZip with an option to filter out all of the javax packages from the output JAR file in order to decrease the size of the client JAR.

073529

Fixed a problem that was causing clustered servers to lock under heavy stress testing.

073569

Eliminated <DGCserver> info messages in the weblogic.log file in order to save space in the file.

073578

Installing Windows NT service by specifying JRE directory as its JAVA_HOME failed with an error when trying to start the service. This has been fixed.

073788

The HP Installer was failing to build. This has been fixed.

074991

Fixed a problem that was resulting in WebLogic Server crashing in the performance pack under heavy load.

075271

A NullPointerException is no longer thrown at weblogic.utils.BubblingAbbrever.getValue (BubblingAbbrever.jaava:163). The Abbrev tree is no longer getting corrupted.

075700

For WebLogic Server instances that run as a Windows service, you no longer need Windows Administrator privileges to start the service.

076395

For WebLogic Server instances that run as a Windows service, using the Administration Console or the weblogic.Admin utility to shut down the server no longer causes the Windows service to report an error condition.

076705

Deploying a MessageDriven Bean no longer fails with a NoAccessRuntimeException for guest if the destination is remote.

077238

Startup scripts now specify the correct value for the Oracle jDriver path. Before this service pack, startup scripts specified LD_LIBRARY_PATH=oci816_8, which is no longer supported. Now the scripts specify oci817_8.

077278

Removed the Oracle 816/806 driver from the WebLogic Server 6.1 service pack 3 installation.

077919

Fixed a problem with an earlier bug fix that was causing calls to ObjectOutputStream.writeObject() on EJBHandle to throw the following error: Closing:'weblogic.rjvm.t3.T3JVMConnection@49c89f' because of: 'Server received a message over an uninitialized connection.

078523

The java version bundled with the WebLogic Server 6.1 service pack 3 installer is:

  • Win 2k & Solaris installer bundled with java version 1.3.1-03

  • HP installer bundled with java version 1.3.1.05.

Plug-Ins

Change Request Number

Description

054344

WebLogic Server can now proxy all requests except a certain MIME type.

057448 & 059142

Fixed a memory problem that occurred when using SSL under heavy loads.

058886

Fixed an IIS Proxy memory leak with SSL.

060325

Concurrent GET and POST requests led to a hang in the Apache plug-in

060863

On HPUnix11, the NSAPI plug-in was writing a POST timed-out error on the browser even after the second retry worked and printed the HTML content in the browser.

061229

A request is now declined if handler is not set to weblogic_handler explicitly.

061379

RequireSSLHostMatch=true now works with NSAPI.

061386

The plug-in systematically puts the previous proxy/client's address in the header.

061561

The request is not timed-out in case of failover from a hung server.

061881, 065980 & 076503

The NSAPI Proxy plug-in no longer fails to handle large (greater than 2k) POST Requests.

062607

When the KeepAlive is enabled on the plug-in IIS, the connection is now closed immediately with a HEAD http request.

062641

With the IPlanet plug-in, from a Java client using JSSE, the servlet access now works.

062778

Plug-in is now able to proxy requests to the primary/secondary servers without checking if those are in the current server list.

062808

Added support for the latest beta version of Apache 2.0.

063004

The Apache proxy plug-in no longer generates an incorrect URL under a heavy load.

064268

In the response header the status, HTTP/1.1 200 OK, the string "OK" is no longer being stripped off by the iisproxy.dll.

064472

Apache 1.3.12 EAPI, Solaris 2.8, with mod_wl_ssl.so was generating "Segmentation Fault - core dumped" while using port based virtual host. This has been fixed.

064890

Cookie Path no longer gets mangled when PathTrim is used in Apache.

065188

Fixed the iPlanet plug-in so that it no longer gives a WRITE_ERROR with a 404 error for a static page.

065443

Now able to proxy to both 5.1 and 6.1 backends with the NSAPI plug-in.

065660

The HTTP header is malformed with the last ISAPI plug-in.

067100

The build information of a plug-in now includes the version number.

068243

ISAPI plug-in PathPrepend path is no longer prepended twice when using FORM authentication for a web application.

068517

The proxy plug-ins no longer load the ECC crypto module.

068562

When setting up IIS to proxy to multiple sites, the plug-in was not working when putting a firewall or a load balancer in front of the IIS server. This has been fixed.

068634

A 413 error is now returned if Content Length exceeded the plug-in parameter MaxPostSize.

068790

Now supporting Apache2.0.32.

068985

Added the ability to exclude certain requests from being proxied in WebLogic Server.

070358

Apache-plug-in no longer gives response code 500 when the server is not available.

072895

When secondary is killed, request was not going to the same server (primary). Now it is.

073838

When using iPlanet, WebLogic Server no longer loses the HTTP session ID if CookiesEnabled is set to false.

073936

Apache Plug-ins have been ported to OpenVMS 7.3 platform.

074137

The NSAPI plug-in was returning "unknown" if x-forwarded-for and client-proxy-ip headers were not sent or set. This has been fixed.

074286

Now able to proxy to both 5.1 and 6.1 backends with the Apache plug-in.

074393

Added URL parameters to the correct requesturi variable because the latest iPlanet plug-in was dropping URL parameters.

074656

If the password to start WebLogic Server was provided on the command line, the property, weblogic.security.jaas.Configuration, was not initialized at all. This has been fixed.

076457

Fixed the problem with READ_TIMEOUT(os error=22) on NSAPI for Solaris. The NSAPI plug-in is now stable under a heavy load (800 or more users).

076578

The NSAPI plug-in no longer keeps trying to connect to a dead server.

076701

The Apache server no longer crashes when Content-Length is zero in a POST request by requiring that the server not read post data if Content-Length is 0.

076722

The Apache server no longer crashes when Content-Length is zero in a POST request.

076731

The NSAPI plug-in can now fail over to the active server when the primary and secondary servers are locked if it is specifically requested to do so.

076996

Fixed an SSL memory leak problem.

077440

The IP address of the proxy is now in the HTTP request headers.

077794

The keep-alive feature for Apache 2.0 is disabled for this release.

078265

MaxSkips is used if DynamicServerList=OFF.

078883

The NSAPI plug-in no longer dumps core when URL rewriting is used with a long URL.

RMI over IIOP

Change Request Number

Description

047057

Support for complex objects is fixed in IIOP implementation.

062082

Improved parsing of IIOPs URLs.

067013

Now, only if debugging is turned on, are onMessages printed whenever there is failure to renew lease.

072179

Resolved the difference in behavior for JDBC connections taken from pool driver or DataSource when not closed.

073028

Now, chunk continuations before encapsulation body are allowed.

073889

If MuxableSocketIIOP received more than one message in a chunk and if the overshoot was less than the length of the message header, then subsequent attempts to read the message length were wrong. This has been fixed.

074100

Muxer boundary condition no longer causes garbaged message.

Security

Change Request Number

Description

061659

WebLogic Server now starts with NTrealms configured

061694

When running the SSLClient example, a NullPointerException was being thrown at weblogic.security.provider.MD2.<init>(MD2.java:24). This has been fixed.

062172

Now, if cookies are disabled in a browser, form-based authentication redirects to the secure JSP/Servlet.

062261

Fixed a security issue with EJB SessionContext.getCallerPrincipal().

062988

Fixed a problem with the NT realms and multiple PDCs.

063349

When implementing an AuthFilter class, the methods doFailAuth() and doSuccessAuth() are now being called.

063763

Two-way SSL java client connection now works with encrypted private keys.

064250

The web server is no longer vulnerable to session ID forcing. This applies to web applications protected with form-based authentication.

064263

Lockout Duration above 322122 will now lock out the user.

064285

When running the SSLClient with ssl.proxyHost/ssl.proxyPort, the SSLHostnameVerifier now works as expected.

064342

It is now possible to redirect the echo $password command output to the Java interpreter to start WebLogic Server other than by using password.ini or by specifying the -Dweblogic.management.password=$password property.

065046

ManageableRealm.newAcl() no longer returns NULL when the System password is changed.

065314

LDAP version 2 no longer causes issues with usernames containing natural language.

066232

The 2-way SSL with RMI/IIOP PingClient example is now working.

066264

Fixed a problem with the lockout mechanism using Japanese Windows 2000. A 500 error was occurring.

066491

The browser is no longer able to get access to a file in the mydomain directory of the server.

067726

Fixed a problem with form-based authentication.

068524

Two-way SSL with RMI/IIOP and EJB access and authentication is now working for the SimpleCertAuthenticator example.

069083

Fixed a problem with perimeter authentication.

069160

There is now a way to set ClientCertProxyEnabled for unclustered servers.

070870

LDAPRealmv2 is now fully implemented.

071167

There is no longer a ProtocolException when tunneling HTTPS through iPlanet proxy server.

072096

Now able to start a managed server using SSL and DebugRC4="true".

072916

Changed class weblogic.security.X500Name to implement Serializable.

075109

LDAPRealmv2 now caches memberships.

Servlets, JSPs and Web Applications

Change Request Number

Description

044528

Under certain situations, isUserInRole was returning false when it should have been returning true. This has been fixed.

051065

XML fragments on the XML view of a JSP page were not being passed to out. Non-standard fragments, which are neither standard nor custom tags (tag libraries), are now being sent to the current value of out as is.

054694

RequestDispatcher will now invoke filters upon include/forward properly.

055333

When detecting contentType directive at the middle of the JSP, the JSP compiler was failing.

056153

The File Servlet now supports initialization parameters as well as context parameters.

058352

It is now possible to access a web application that has a one-character name like "i.war" or "j.war".

059026

In a web application that contains a servlet, when the mapping defined for this servlet is in the form of *.aBc, accessing the servlet no longer fails.

059102

The compression filter now works correctly with RequestDispatcher. The forward was causing an invocation of the filter, but the servlet engine was sending the empty response back to the client. This has been fixed.

059219

WebLogic Server no longer returns the default port number if Host Header is missing.

060023

The FileServlet now includes the SERVLET_PATH when calculating the source filename which means that it is possible to only explicitly serve files from specific directories by mapping the FileServlet to "/dir/*" etc.

060184

PathInfo is now decoded and preserves characters in the original URI.

060351

The method PageContext.include(String relativeUrlPath) was not throwing any exception when the URL to be included was not found. Added a log message that appears in the context log file and indicates the parent resource and which resource could not be included. The log message appears in the mycontext.log file - where mycontext is the context-path of the webapp.

060825

BodyTagSupport method, getBodyContent(), incorrectly returned null when body tag was empty.

061377

jspc no longer generates EVAL_BODY_TAG instead of EVAL_BODY_AGAIN.

061782

ServletResponseImpl.setContentType() can now handle multipart type properly.

061784

While getting the log from a managed server, the admin server java process was pegged at 90%. This has been fixed.

061864

WebLogic Server now prevents the display of secure cookies.

061948

Added a new semantic-predicate to distinguish between tags with body-content set to "tagdependent" or "jsp". Added a new rule before the existing opening-tag rule in the lexer. When the tagdependent rule is invoked, it does the same as the ordinary open-tag rule, but also looks ahead and matches the content of the JSP until it finds a matching closing tag. Everything it finds is escaped for \n, \r, and \ and printed to "out". It then returns to the parent lexer rule which should immediately find the closing tag.

061968

HEAD method no longer returns request body with use of jsp:include.

062109

Fixed a problem with JSP scripting variable synchronization

062160

The parameters <compileFlags>, <encoding>, and <compilerSupportsEncoding> are no longer ignored during precompilation.

062289

WebLogic Server now decodes the spaces in a URL.

062395

load-on-startup in web.xml is now be optional

062536

The JSP response that contains Japanese characters is no longer garbled when filtered with HttpServletResponseWrapper.

062538

Pages will now be properly parsed regardless of the location of the contentType.

062542

Now, requesting aux.jsp / AUX.jsp / PRN.jsp / prn.jsp on a WebLogic Server that is running on a Windows box either succeeds or fails instead of staying in an undetermined state.

062579

CGI scripts will now be resolved properly even if CGIServlet is registered as a default servlet.

062896 & 063009

When the JSP parameter, precompile, was set to true in the web app (WAR) weblogic.xml, only the document root level JSPs were being recompiled each time the server restarted. The subdirectory JSPs were not being recompiled. JSPs are now recompiled, even during pre-compilations, only if they have changed.

062920

When specifying an <exception-type> in web.xml in a webapp (the exception class is located under WEB-INF/classes) when the webapp is deployed, WebLogic Server was not finding the exception class and throwing a ClassNotFoundException. This has been fixed.

063007

Session table name for JDBC persistence is now configurable.

063127

ServletInputStream now returns data if the session is new.

063169

Having accented characters and a Charset=UTF-8 no longer yields the weblogic.utils.ParsingException and the nested TokenStreamException.

063288

WebLogic Server now only looks for SessionCookie in the cookies if CookiesEnabled is true.

063414

When trying to migrate applications from WLS 5.1 to 6.1 SP1, there is no longer high CPU utilization.

063524

A NullPointerException is no longer thrown using FileServlet with nativeIO turned on.

063563

weblogic.jspc was not passing -encoding JAVAENCODING value to javac from the page tag. This has been fixed.

063904

The inclusion of each page directive in a JSP was leading to the insertion of an extra line feed character in the generated HTML output. If the HTML consisted of an image, the image lost its formatting. This has been fixed.

063925

If a language-specific character encoding is specified for a web-app, binary data written to the response outputstream is no longer garbled.

064294

Fixed a problem with the WebLogic Server SessionID reuse using a virtual host.

064383

HEAD request from an applet no longer issues a ClassCastException from ClasspathServlet.

064446

When using two levels of proxying, a call to getRemoteUser was always returning NULL. This has been fixed.

064449

Web application deployment was failing and resulting in a StringIndexOutOfBoundsException. This has been fixed.

064650

WebLogic Server is now able to load a class from a JAR file with a period in its name.

064880

In form-based authentication, when the user directly went to the login page, WebLogic Server was forwarding the user to the welcome page. This has been fixed.

064988

JSP precompilation no longer aborts after a compile error when the -k flag is set.

065104

Fixed by 064650 and 065213.

065194

A multi-part request in the SSL process was failing through a slow connection. This has been fixed.

065213

When both xalan.jar and xerxes.jar were in the lib directory, NoClassDefFound was occurring. This has been fixed.

065924

In a non-clustered environment, webapps with cluster specific properties can now be deployed using the new option: replicated_if_clustered

066395

response.addHeader was failing with null character being inserted erroneously. This has been fixed.

066500

Forwared JSP pages will now terminate the execution of the current page.

066569

request.getParameter() is now returning the paramater for post request with Javaclient.

066708

request.setCharacterEncoding was not working for JSP includes. This has been fixed.

067001

When using the Http Proxy/Cluster servlet, a request was sent to some backend server and the response body was not returned to the client if the request came back with a status of 100. This has been fixed.

067072

When a JSP had pageEncoding without contentType charset specification, the generated .java file was in VM default encoding and the compile failed. This has been fixed.

067073

Generated .java and -encoding for javac did not match when both contentType and pageEncoding existed. This has been fixed.

067077

When there was an encoding setting in jsp-param of weblogic.xml at a JSP file with pageEncoding, pageEncoding was not used. This has been fixed.

067292

Latin one characters in request parameters, when re-directing from one JSP to another, were getting lost. This has been fixed.

067505

Fixed a problem with port in Location header for an HTTP re-direct.

067748

It is now possible to compress the output stream of a servlet.

067948

Page buffer directive is no longer ignored if it is in an included JSP page.

068024

Removed the need to use sync blocks in HttpServer or HttpClusterServlet. A new enumeration is constructed each time it is required that references a Set that is guaranteed not to change.

068560

Certain JSP pages' source code was being shown on the browser. This has been fixed.

068648

Limiting maximum POST size now works properly.

068674

There is no longer a ClassCastException thrown when using HttpProxyServlet in conjunction with a filter.

068809

Now, the write signature is honored when using encoding that is different from the default.

068821

getRequestURI from Request Object is now returning the full length of the URI.

069304

HttpClusterServlet now re-reads the post data from the input stream up to the declared content-length.

069511

Error page attributes are now being set on request for JSP error directives.

069630

If the property of a custom tag in a JSP contained an escape sequence (\"), the JSP was not compiling. This has been fixed.

069652

The response header (ContentType) and the JSPWriter now have the same character set while serving a page to client.

069956

For replicated sessions, the open session count is incremented only once.

070090

When sending session cookies in the response to the client, WebLogic Server did not specify the cache-control appropriately to prevent caching proxies from caching the cookie. This has been fixed.

070132

It is now possible to request a filename with Chinese characters.

070151

weblogic.jspc no longer silently exits when <load-on-startup> contains an empty value.

070470

Subsequent reload/refresh was at times executed by the old code that was still deployed in the container. This is now prevented by reloading of the stale class in the case where the JSP fails to parse.

070755

No longer sending wlsproxy specific headers if the requests are not coming via wlsproxies.

070823

Eliminated inconsistent behavior of index directories parameter across WAR and EAR components.

071076

Fixed classloading behavior problem that resulted in having both child1 and child2 using the same classloader, BUT additional classloaders being created and destroyed.

071082

Fixed broken URLEncoding.

071634

Fixed chunked transfer encoding issues that occurred when WebLogic Server 6.1 was communicating with WebLogic Server 5.1.

072557

response.addCookie(name) now honors the order in which cookies are sent to the browser.

073203

Now able to use the + character in a <url-pattern>.

073380

Improved the error messages for CGIServlet.

073516

Fixed a problem with the CGI NonParsedHeader.

073792

Active sessions will no longer be invalidated.

073797

JSP useBean tag is now parsed properly.

074015

There was a NegativeArraySizeException if PROTOCOL is missing in the first line of the request. This has been fixed.

075201

The security-constraint is now working when the url-pattern refers to a two-character directory.

075607

Socket exceptions squashed by PrintWriter could have tied up execute threads in servlets and JSPs. This has been fixed.

075628

When a program submitted data to a servlet using Content-Type that was set to include a charset, getParameterValues("..."), returned every submitted value twice. This has been fixed.

076056

When a JAR file's MANIFEST.MF contained a JAR file that was in a different directory, WebLogic Server was throwing a StringIndexOutOfBoundsException and the web app was not being deployed. This has been fixed.

076476

When using multiple frames, the last accesstime set by one frame was not being honored by the other frame. This has been fixed.

076742

Added a check for the <env-entry-value> element.

077329

HttpSessionListener failed to work correctly when the session is set to replicated. This has been fixed.

078930

Requesting http://host:port/webApp/aux%20.jsp no longer hangs the thread servicing the request.

System Administration

Change Request Number

Description

050136

You can now unset the property values for MBeans from the command line.

052774

Applications in the config.xml file that do not actually exist are no longer being deployed.

054836

When migrating a cluster of servers from WebLogic Server 4.5 or 5.1 to WebLogic Server 6.0 or 6.1, an InstanceNotFoundException was thrown. This has been fixed.

056158

Undeploying an enterprise application that contains a default web app caused an exception at undeployment. This has been fixed.

056832

The WLEC Connection Pool was not trying to start when in a cluster. This has been fixed.

058946

Now, JSPs that are pre-compiled on the admin server do not compile again on the managed server.

061426

Servlets load-on-startup after, not before, the Start Up classes have run

061676

The converter utility now puts all log files in the SERVER/DOMAIN/logs directory.

061703

weblogic.deploy was always using the default .wlstaging directory, even if the application was originally deployed using a path other than .wlstaging (i.e., the config.xml was hand-edited). This resulted in update not working for applications that were installed any other way than by using weblogic.deploy. This has been fixed.

062135

Re-deploying an exploded webapp that has a subdirectory with the same name as the webapp results in an error. This has been fixed.

062151

Now, managed servers on a remote machine retain webapp name/timestamps.

062749

It is now possible to update the webapp if the webapp is deleted, deployed, updated, and then updated again.

064101

The admin server JNDI now shows the managed servers' MBeanHome.

064280

Fixed a performance regression that occurred when using the weblogic.refresh utility to update JSPs on the managed servers.

064575

weblogic.refresh did not refresh JSPs and static files from Windows 2000 to a server running on Solaris. This has been fixed.

064722

Is is now possible to deploy an EJB using weblogic.deploy if a deployed component does not exist at start-up time.

066480

Registering a custom MBean with an object name of null, the server was throwing an exception. This has been fixed.

066704

The FailuresFatal property was not getting automatically generated upon migration from WebLogic Server 5.x to WebLogic Server 6.x. This has been fixed.

067917

The property, Console Context Path, on the <domain>->Configuration->General page of the console application now enables a domain to be accessible by a contextpath other than console.

068231

Re-deploying an enterprise application to a managed server (using weblogic.deploy) after modifying the context-root now makes the new context-root effective until a server restart.

068579

Redeployment to Virtual Host was returning javax.management.InstanceNotFoundException. This has been fixed.

068745

Increased the console speed in a 100-node cluster.

069145

For auto deploy in the applications directory, the admin server has been added to the targets if it's not empty.

069407

Multiple senders can now be saved in the MBeanServerNotificationListener's list.

069686

It is now possible, using MBeans, to change the weblogic.xml cookie name after the web application is deployed.

071633

Fixed svuid for MBean interfaces.

072676

Added LoadBeforeAppDeployments to console for startupclass.

072964

Fixed a problem that was causing a javax.management.AttributeNotFoundException when using the EJB Descriptor editor in the console.

073674

After webapp deployment, the weblogic.xml session persistence type is now changed.

075139

Fixed a problem that was preventing weblogic.deploy from deploying an application to a cluster.

075667

Managed servers were not discovered by the admin server when the admin server was restarted. This has been fixed.

077750

Fixed a problem with deploying an EJB when the JNDI name was already in use.

Web Services

Change Request Number

Description

046215

You can now correctly use the protocol attribute of the wsgen Ant task to specify that you want to use HTTPS (rather than the default HTTP) when invoking a WebLogic Web service.

You must, however, peform the following additional steps if you want to use HTTPS:

  • Add the following line of Java code to the client application right before creating a URL:
    System.setProperty( "java.protocol.handler.pkgs", 
    "weblogic.net" );
    

  • If you are running the examples server with the SSL certificate shipped with WebLogic Server, you need to specify the following on the command line when running your client application:
    -Dweblogic.security.SSL.ignoreHostnameVerification=true
    

062976

MSSoapClient.ConnectorProperty for AuthUser and AuthPassword is now passed to InitialContext of EJB.

065205

Web Services FaultHandler was never being invoked. This has been fixed.

065669

Now able to use security ACL on a WSDL URL.

066226

WebLogic Web services now support two-way SSL authentication between client applications and RPC-style Web services.

To use two-way SSL authentication, add the following Java code to your client application before you obtain the context you are using the look up your Web service:

InputStream certs[] = new InputStream[3];
certs[0]=new PEMInputStream(new
           FileInputStream("sample_key.pem"));
certs[1]=new PEMInputStream(new
           FileInputStream("sample_cert.pem"));
certs[2]=new PEMInputStream(new
           FileInputStream("sample_ca.pem"));
h.put(SoapContext.SSL_CLIENT_CERTIFICATE, certs);

066703

There were excessive error messages being generated on SOAP client. This has been fixed.

072788

Now, wsdl is generated with element instead of attribute for complex types.

073897

SOAP Fault now uses CDATA.

WebLogic Tuxedo Connector

Change Request Number

Description

052022

Codeset translation between WebLogic Tuxedo domains and Tuxedo domains is provided using the WebLogic Server weblogic.wtc.encoding property. For more information, see Configuring WebLogic Tuxedo Connector for Non-ASCII Codesets.

055170

Fixed problem with Fchg method of the TypedFML(32) class in the WTC package.

056230

tbridge no longer fails to initialize the wlsErrorDestination JMS queue

062843

Fixed a problem with the Fdel method of the TypedFML(32) class in the WTC package.

063290

When loading large code tables from Tuxedo to WebLogic Server, the duration of service calls (tpcall) is no longer dramatically longer with WTC compared to with Jolt.

066489

Now able to call an EJB from a Tuxedo client when using FML32 buffer.

XML

Change Request Number

Description

061660

Using JAXP API to parse XML document, there is no longer the error message "Failed to open XML document".

062297

You can now set the cache memory size, cache disk size, and cache timeout interval for the external entity cache using the Administration Console. In previous WebLogic Server versions, these fields did not accept any values.

063433

Fixed a regression with the XSLT processor embedded within WebLogic Server 6.0. When an MFL file contained a group containing a String and either a Literal or XSLT processor embedded within a WebLogic Server 6.0 Filler field, the transformation was hanging.

067966

Due to a fix in the WebLogic Server classloader, you can now plug-in any version of the Xerces XML parser.

065345

Fixed a problem that was causing CharReader.fillCurrentChunk to throw a java.lang.ArrayIndexOutOfBoundsException.

067022

The transformer shipped with WebLogic Server 6.1 now transforms an XML document as expected (using a given XSL).

068656

Fixed a problem that was causing a NullPointerException in weblogic.xml.jaxp.ChainingEntityResolver.pushEntityResolver.

073311

Using the weblogic.apache.xalan.xslt to transform huge amount of data led to javax.xml.transform.TransformerException: String index out of range. This has been fixed.

075800

The built-in XML parser now correctly parses XML files that use external entity references to include external chunks of XML within the original XML file.

Third-Party JAR Files in WebLogic Server 6.1 Service Pack 3

JAR File

Description

J2EE, javax and subdirectories

JTA 1.0.1


JCA 1.0


JMX 1.0


EJB 2.0


Servlet 2.3


JSP 1.2


JMS 1.0.2

XML

org.apache.xalan 2.0.1


org.apache.xerces 1.3.1


Xerces 1.2.0 - DOM and SAX parsers


org.w3c.dom interfaces


org.xml.sax interfaces

LIBRARIES

antlr 2.7.0 - runtime classes of antlr compiler construction toolkit


bsh 1.2b3 - bean shell


certicom - SSLPlus/Java 3.1.12B (used by Node Manager)


netscape - Netscape Directory SDK 4.1 for Java


Oracle 8.1.6


Oracle 8.1.7


Apache Jakart Ant - 1.3 Apache build system


Apache Jakart Oro 2.0.6 - regular expression matching library

 


WebLogic Server 6.1 Service Pack 2 Solutions

The next sections describe problems that were resolved in WebLogic Server 6.1 Service Pack 2.

EJB

Change Request Number

Description

044294

Fixed a memory leak that could occur when creating multiple entity beans; the garbage collector was not reclaiming all of the used memory.

049590

The ejbc compiler now will produce IDL files in the correct order, putting primitive value types before non-primitives.

049709,

055644,

059540


Previously, due to timing problems, exceptions/errors were thrown when EJBs were deployed in a cluster and then a re-deploy or un-deploy was attempted.

It was possible that an undeploy JNDI message would arrive after local undeploy had taken place. This would cause unmarshaling errors, as the classloader for an EJB is discarded once local undeployment of an EJB is done. This unmarshal problem would result in DistributedManagement exceptions popping up in log files, and the EJB could never be un-deployed from a cluster.

Similarly it was possible that a JNDI binding announcement would arrive before local deployment was successful, resulting in same unmarshaling/ de-serialization errors (as EJB classes required to unmarshal are not there yet).

Fixes in 6.1 Service Pack 2 take care of both these problems and remove any timing dependencies in local deploy/undeploy and JNDI Announcements. Now you can successfully deploy/undeploy/redeploy EJBs in a cluster without any exceptions and problems due to race conditions.

051454

In the case where an EJB has been idle longer than the value of idle-timeout-secs, it is removed from the cache and ejbremove() is called.

055113

The examples\ejb\basic\statelessSession\build.xml file had a typo where the name of the EJB jar file was misspelled. This has been fixed.

055163

Fixed a problem with stateful session beans that are configured with in-memory replication across a cluster. The bean was failing over when an EJBException was thrown, but not when the bean was removed.

055502

A message-driven bean now recovers messages after an application throws an exception.

055510, 056543

Fixed problems with container-managed persistence 1.1 EJBs not re-reading deployment descriptors after being redeployed.

057119, 054806

Fixed an out of memory problem that occurred when redeploying EJBs several times over; the <max-beans-in-free-pool> descriptor was being ignored and exceeded.

058210

The ejbRemove() method is now invoked at undeployment for both stateful session beans and stateless session beans with both home and remote interfaces.

058857

Fixed problem where entity beans weren't being recognized if the home didn't have a create() method.

059043

ejbc no longer complains when the EJBLocalObject() method has a throws exception clause that does not throw a RemoteException.

059046

Accessing a stateful session bean from a stateless session bean in a cluster no longer fails.

060018

Accessing a ReadOnly EJB with container managed relationships no longer causes a LockTimedOut exception.

055842

Fixed a problem where a message-driven bean could not access a remote queue on another physical machine because it the client could not be authenticated.

058074

Storing a reference to an EJB local interface in an instance field in a stateful session bean no longer causes an assertion error during passivation.

053523 and 060032

Fixed a problem where the guess method getURL() in weblogic.ejb20.internal.BaseEjbHome was using a non-secure port when the protocol was t3s and https.

054335

Removing a ReadWrite entity bean now invalidates its corresponding ReadOnly entity. Previously, the ReadOnly entity would remain cached.

059674

Using a read-only bean-managed persistence entity bean no longer calls ejbLoad() twice when the bean has been loaded via a finder.

060142

Fixed a problem in the getEJBHandle() method such that failover is now working in a 2-node cluster.

060416

Fixed a problem where performing an EJB lookup in a tiered environment caused a ClassCastException to be thrown when the EJB Home object was cast to its specific type.

061883

Fixed a problem where reentrant calls to read-only beans failed because of a lock timeout.

062515

The findByChar(char c) method no longer fails for a container-managed persistence EJB home.

Examples

Change Request Number

Description

055155

A problem was fixed in the following sample file:

ejb20\cascadeDelete\one2many\table.ddl

The problem resulted in a "SQL not properly ended" error message (error number 933).

055370

Broken links are now fixed in the following examples under wlserver6.1\samples\examples\jsp\:

SimpleSession.jsp

URLEncode.jsp

For SimpleSession the link on Session Timeouts was missing.

For URLEncode the link Writing Web Application Deployment Descriptors was missing.

056711

Building the wtc/simpFML32 example no longer generates a warning about container transactions.

057237 and 056063

The RMI-IIOP C++ examples have been fixed to work on UNIX platforms. They are located in the following subdirectories:

/samples/examples/iiop/ejb/entity/tuxclient
/samples/examples/iiop/ejb/stateless/server/tux
/samples/examples/iiop/ejb/stateless/tuxclient /samples/examples/iiop/rmi/server/tux
/samples/examples/iiop/rmi/tuxclient


JDBC

Change Request Number

Description

055044

Dynamically created connection pools are no longer treated as persistent within the config.xml.

055435

The JDriver for Oracle now retrieves the correct number of `null' values when it queries the database and the database has more than 500 rows.

056268

When trying to execute SQL queries with the language set to Russian, the use of hyphens in the timestamp no longer contain error causing hyphens.

jDriver

Change Request Number

Description

046149

Fixed a problem where when WLS wrote a multibyte string to a CLOB or NCLOB column, it wrote an incorrect string length.

JMS

Change Request Number

Description

055293

JMS default connection factories are now properly bound as a function of the JMSDefaultConnectionFactoriesEnabled property in the config.xml file. Previously, if no other JMS objects (JMSConnectionFactory, JMSServer) were defined on a given WebLogic Server, then the default connection factories were not bound into JNDI.

056320

Fixed problems in JMS with an error deserializing an object in the case of using a Topic to send a string as an ObjectMessage and then sending a RemoteObject stub as another ObjectMessage.

061783

Fixed a problem that occurred when trying to simultaneously deploy instances of different message driven beans that subscribe to the same JMS topic

Previously, one or both beans would stop working.

Miscellaneous

Change Request Number

Description

036679

The Administration Console now functions correctly when resizing the Netscape browser frames on Solaris.

041873

Fixed problems with the weblogic.policy file when users started up the server with -Djava.security.manager. Even when the user had correct permissions, a java.security.AccessControlException: access denied exception was being generated.

041991

When attempting to get the MBeanHome from the RemoteMBeanServer, an application no longer receives "null".

043010

If WebLogic is running as a Windows service it will no longer shut down when you log out of the Windows session that the server is running in.

050437

When running under WebLogic Express, WebLogic no longer prints out: <Error> <JMS> <JMSServer "null", JMS license validation failed, com.bea.utils.misc.NoSuchProcessException: No such license: WebLogic Server 6.1, JMS.>. This message was misleading and harmless.

053732 and 054781

Introduced a -delay option to the beasvc.exe utility which ensures that Managed Servers only start up provided that an Administration Server is already running. The new -delay option lets users delay the Managed Server's JVM thread execution for a specified number of milliseconds.

Previously, a Managed Server failed to start up because it depended on a running Administration Server.

053990

The Node Manager will now load up servers that have whitespace in their names.

055007

WebLogic Server now implements a throttling mechanism to reject outstanding requests after a certain limit. Previously, the acceptBacklog value was not effective in limiting the number of new connections that could possibly overwhelm the server.

055442

Fixed a problem involving sending XML over HTTP. The problem was that WebLogic Server was erroneously calling the getInputStream() method.

056332

Fixed a problem causing an IllegalStateException when calling a RPC-style Webservice.

057091

Fixed a problem with applets in Internet Explorer, where `didn't meet stated Content-Length' errors were being thrown because the content length check was being performed at the wrong time.

058832

Fixed a problem where HttpSession failover service failed and a session was lost if a client accessed the session just when a primary server was shutting down. This occurred only in a two-server cluster.

059119

Fixed a problem where a Java client talking to a Weblogic cluster performed more slowly on a 3-server cluster than on a 2-server cluster. Moreover, performance would keep degrading with addition of more servers until the client ensured that there were at least as many socket reader threads on client as the number of servers in the cluster. This involved configuring Execute Thread count and Percent Socket readers client-side properties.

This fix removes the dependency of such a configuration, as the number of servers can grow or shrink dynamically. Now, WebLogic Server creates new threads for socket reading on fly making sure there is one thread per outgoing socket from client. This means customers don't have to tweak those properties for the client for optimal performance when a WebLogic client talks to a WebLogic cluster.

059219

Fixed a problem encountered by wireless application where WebLogic was retrieving the port number from a location that could have incorrect information.

060557

The FileT3 attribute now creates a file with the correct path when the path is targeted to a managed server.

061060

The getTimeout() and setTimeout() methods are no longer missing from the class HttpURLConnection.

056911

Previously, if an entry was added to the manifest Class-Path for a
.war file, it would be loaded by the web applications's ClassLoader.
With this fix, the application's ClassLoader now loads it. The net
effect is that all web applications now share instances of classes loaded from the manifest Class-path, whereas before they all got their own copies.

051220

Fixed a problem where multi-byte system messages in WLS log or console were corrupted and, therefore, unreadable.

054871

The Administration Console now displays a JNDI tree correctly. Previously, deployments were appearing under the wrong context.

057466

Fixed a problem where executing the weblogic.Admin PING command to a server running on Solaris with Japanese locale (LANG=ja_JP.PCK) resulted in a java.net.SocketException displaying on the server.

058786

The Netscape Enterprise Server Plug-In (NSAPI plug-in) enables requests to be proxied from Netscape Enterprise Server (NES, also called iPlanet) to WebLogic Server. The plug-in enhances an NES installation by allowing WebLogic Server to handle those requests that require the dynamic functionality of WebLogic Server.

Previously, reading the HTTP header in the NSAPI plug-in resulted in an unexpected EOF: "PROTOCOL_ERROR [line linenumber of filename]: unexpected EOF reading HTTP headers at line linenumber.

The underlying problem proved to be with parsing large cookies.

This problem is now fixed.

061460

You can now configure Weblogic 6.1 to restrict the number of client
connections. There are two methods:

1. Edit the config.xml file to set the weblogic.system.openSockCount parameter, which limits the number of permitted connections:

<Server ListenPort="7001" Name="myserver" NativeIOEnabled="true" TransactionLogFilePrefix="config/mydomain/logs/" MaxOpenSockCount=1000>

2. Use weblogic.Admin to set the socket count or write a JMX Java client to do so and utilize the API in weblogic.management.configuration.ServerMBean, as in this code fragment:

/**
* Returns the maximum number of open sockets allowed
* in server at a given point of time. When max threshold is reached,
* server stops accepting any more new requests until no of sockets
* drops below threshold.
*
* @default java.lang.Integer.MAX_VALUE
* @legalMin 0
* @legalMax java.lang.Integer.MAX_VALUE
*
* @configurable
*
* @oldprop weblogic.system.openSockCount
*/

int getMaxOpenSockCount();


/**
* Sets the maximum number of open sockets allowed
* in server at a given point of time. When max threshold is reached,
* server stops accepting any more new requests until no of sockets
* drops below threshold.
*
* @default java.lang.Integer.MAX_VALUE
*
* @legalMin 0
* @legalMax java.lang.Integer.MAX_VALUE
*
* @configurable
*
* @oldprop weblogic.system.openSockCount
*
*/
void setMaxOpenSockCount (int sockCount);

051882

If web.xml is missing from your web application and you attempt to edit or enter a deployment descriptor through the console, a blank screen no longer appears.

Plug-Ins

Change Request Number

Description

053641

Now the plug-ins correctly respond to the setting of the KeepAliveEnabled parameter. The Connection: Keep-Alive header was not being sent back to WebLogic when using HTTP 1.1.

055276

There are no longer problems when disabling caching with the ISAPI plug-in.

055750

Fixed problems using MatchExpression with Stronghold versions of Apache.

056628

Fixed a problem that occurred when setting the Apache HTTP Server Plug-In PathTrim parameter. Setting the PathTrim parameter to "/" no longer causes the loss of session information.

060064

Fixed a problem where installing the Apache HTTP Server Plug-In as a statically linked module on the Solaris platform generated fatal errors.

RMI over IIOP

Change Request Number

Description

056233

ejb11.security.HomeMethodPermissionTest.testHandleRemoveWithoutPermission() no longer fails with an out of memory error.

Security

Change Request Number

Description

060491

Fixed a problem where single sign-on (SSO) did not work when the initial resource in the web application was not a protected resource.

057950

The Certificate Request Generator servlet has been enhanced to better protect private keys. If you generated a certificate and did not supply a string in the Random String field on the form displayed in the Certificate Request Generator servlet, you should generate a new certificate. Refer to http://edocs/wls/docs61/adminguide/cnfgsec.html#1053930 for more information.

Servlets, JSP and Web Applications

Change Request Number

Description

046879, 057371

A cgi executable now successfully serves an image to the browser (.gif, .jpg or .png format). Previously, attempting to do so resulted in an exception being thrown in the WebLogic Server log.

047698

The IndexDirectoryEnabled property now works correctly for managed servers: both directories and files will be listed.

Previously, if IndexDirectoryEnabled was set to "true" for a particular web application and that web application was requested on a managed server, directories were not listed, only files. Also, if files were added or removed from the web application, the changes were not reflected when browser page was updated.

050402

Fixed a problem that occurred when redeploying a web application with a different name. Previously, when a web application was already deployed through the Administration Console and then mbeans were used to programmatically deploy the same .war application under a different name, WebLogic Server would go into an infinite loop.

053513

Fixed a problem where, when using HttpClusterServlet to proxy requests, a page sometimes displayed improperly in the browser.

053706

Fixed problems when AuthFilter is registered in a web application and ServletAuthentication.weak is called. Now, doSuccessAuth is correctly called in AuthFilter when this is the case.

053965

If characters between ASCII 128 and 156 are a part of a URL parameter which is then subject to a response.sendRedirect, the second servlet no longer receives those characters as ASCII 63 and the characters are sent to the second servlet correctly.

054206

weblogic.servlet.internal.ServletRequestImpl—the implementation class of HttpServletRequest—now properly handles "folded" HTTP header lines. Previously, code would be incorrectly parsed.

054211, 055987

You can now configure the lifetime of HTTP persistent connections, through the new client-side properties http.keepAliveCache.lifeTime and http.keepAliveCache.proxyLifeTime. Previously, the lifetime was hardcoded on the client side. This value overrode the server-side keepAlive value and led to scalability problems.

054852

A web application with a configured error handler now redirects to this error handler when JSP1 forwards to JSP2 where JSP2 throws an exception.

Previously, the server returned a blank page and showed a status code of 200. The server logged the exception, but the client did not see it.

054898

Fixed a problem with JSP pages using Authfilter and doSuccesAuth, where the first JSP page is in a series of JSP pages that are contained within different web applications.

055333

Fixed a JSP compilation problem when using a contentType tag in the middle of the JSP rather than in the beginning.

055466

Fixed a problem with servlet filters unable to call EJBs and causing ClassCastExceptions.

055535

Fixed a problem where, when using the JSP refresh tool, the file distribution servlet was copying files to the wrong location.

055583

When implementing TryCatchFinally in a JSP custom tag, the correct java code is now created upon compilation.

055595

WebLogic Server now resolves tag library URIs in JSPs.

055636,56265

When using a getParameter() method in a JSP, if the value entered is empty, null is no longer returned. Now an empty string is returned. This fixes certain problem with leaving out equal signs in a query string.

056092

The JSP compiler no longer complains erroneously of duplicate variable declarations.

056189

WebLogic Server now supports clients using "Transfer-Encoding: Chunk", i.e., the client no longer needs to send the "Content-Length" Header if "Transfer-Encoding: Chunk" is used in the post request.

056322

Intermittent RMI errors are no longer thrown when two different servlets in separate web applications attempt to access the same EJB.

056668

When a parameter is empty, the getParameter() method now returns "empty" instead of "null".

056955

Fixed a problem where the post data from a request was lost after a forward() (one servlet forwards the request with post data to another) when a web application had <charset-params> defined in its weblogic.xml or <context-param> defined in its web.xml, the post data from a request is lost after a forward().

057101

Fixed a problem where the getParameter() method was not returning the first of multiple values when including a JSP.

Previously, the second value was being returned instead of the first.

057279

Fixed a discrepancy in behavior between exploded directory and packaged web applications. In an exploded directory scenario, classes were being loaded in the incorrect order with WEB-INF/lib classes being loaded before those in WEB-INF/classes.

057620

Special characters such as '+' and '&' are now decoded correctly when the codeset encoding is 'UTF8'.

057684, 057559

A ClassCastException no longer occurs when calling PortableRemoteObject.narrow() when an applet is a client to an EJB.

058125

The client.jar that is generated for web services is now compatible with JDK 1.2 java clients.

058187

Fixed a problem with weblogic.deploy where a JSP refresh was failing; a new directory added to an exploded directory application was not being propagated to the managed servers and hence refresh was failing.

058220

The servlet error java.lang.NullPointerException at servlet.internal.ChunkOutput.clearBuffer

no longer occurs when trying to send a SOAP request.

058352

You can now access web applications with one-character names, such as "i.war." Previously, although such an application would deploy, access would fail with a 404 error.

058714

Fixed a problem where a .gif image was improperly displayed when streamed through a cgi-bin executable versus when the image was 'streamed' directly via the web container.

058738

The HTTP version is now maintained correctly in a response header when the request is sent via HTTP 1.0.

058931

Deleting a JSP now results in a 404 error instead of a 500 error.

059054

Fixed a problem where WebLogic Server failed to parse "," separators in cookies, resulting in new sessions erroneously being created.

059180

Fixed a problem where WebLogic Server was overwriting an existing cookie created by another entity, rather than simply adding its own cookie.

059412

Fixed a servlet problem where if you called session.removeAttribute() twice, then called session.setAttribute() once, one removeAttribute remains rather than both removes being overridden.

060192

Fixed a problem where requests were not pinned to a primary server and sessions were lost when using URL rewriting to track sessions. (Cookies were disabled on the browser.)

060536

Fixed a problem where jspc was erroneously exiting with an exit code of SUCCESSFUL.

060595

Fixed a problem where WebLogic Server threw a ClassCastException with nested JSPs when using a filter that wrapped the HTTPServletRequest.

060615

Fixed a problem where session ids were not consistent across web applications. Now, each web application sees a single, consistent session id for a given user's session.

060963

WebLogic Server no longer reuses a sessionid when the web application is not participating in single signon.

061277

(JSP 1.1)

javac compile error messages are no longer corrupted on a Japanese platform.

061387

Fixed a problem where WebLogic Server created a new session every time the page was requested, when the JSESSIONID cookie was sandwiched between two user defined cookies.

061488

Fixed a problem where request parameters were parsed incorrectly when a "=" was used in the value.

066184

In 6.1 SP1, the default encoding used for servlets and JSPs was the JVM default. As of 6.1 SP2, the default encoding has been changed to ISO8859_1. This change is in accordance with the latest servlet specification. Servlet Specification 2.3 SRV 4.9 states that the default encoding should be ISO8859_1.

System Administration

Change Request Number

Description

045780

Multiple server definitions with the same name are now disallowed. If you have started a server and then attempt to start up the second server with the same name, the server startup aborts, with this error message:

"Server: <yourservername> already exists, make sure that you do not have duplicate copies of this Server name in your XML config file"

055190

Fixed a problem where JSP refresh failed if the application was targeted to a cluster. Previously, you could not add new JSPs or change or delete existing JSPs from a running web application without having to undeploy and redeploy the application.

056091

A new procedure is available to restart an Administration Server on a different machine while Managed Servers are still running. For more information, see the section "Failover Considerations for the Administration Server".

058946

Fixed a problem where precompiled JSP's on a Managed Server would recompile even without if the pages hadn't been modified. As a result it took a long time to start up the Managed Server.

With this fix, if classes are already compiled on an Administration Server, when the Managed Server starts up the classes are shipped and their timestamps are preserved, to the Managed Server will not try to recompile them.

054624

weblogic.deploy now behaves as expected when its -component option is invoked.

Previously, it did not behave as expected when using the -component option: the application was unintentionally deployed to a server that was not in the component list of servers.

054573

Fixed a problem where any configuration error involving a JDBCConnectionPool, MultiPool, or (Tx)DataSource, did not get reported in an error dialog in the console. Rather, it appeared to be correctly configured.

058183

Fixed a problem where WebLogic Server was deploying .war files before .jar files, At server startup, a web application would deploy before an EJB, resulting in a NameNoteFoundException.

059702

Fixed a problem where web applications could not be deployed when network cards were disabled.

Previously, WebLogic Server would try to validate with the DTD at http://www.bea.com/servers/wls610/dtd/weblogic-web-jar.dtd. When it cannot reach www.bea.com, it failed. Now, when there is no network access, the server find weblogic-web-jar.dtd in weblogic.jar and continues.

060244

Fixed a problem where, when using the Administration Console to target a cluster for just one application, individual servers were also pulled into the target list. With this fix, the cluster is no longer expanded to a list of servers.

061642

Fixed a problem with converting a 5.1 weblogic.properties file to a 6.1 config.xml file. The conversion utility was not converting the password for the JDBCConnectionPool correctly. As a result, attempts to start the server in the new domain failed.

055067

Fixed a problem that caused web applications that had dependencies on classes in EJB .jar files not to deploy when precompile was turned on.

060411

(EJB 1.1)

Fixed a problem where a second call to a required EJB transaction method cause the transaction to roll back. The first call removed some entities and then created some. The second call removed the previously created entities and then created some new ones.

042052

Fixed a problem occurring in migration from one release to another: the weblogic.properties file was not converting completely, such that the web.xml file of the web application did not contain all of the properties.

061300

Fixed a problem where the WebLogic Server console was executing in the default queue (a lower priority queue) instead of "__weblogic_admin_html_queue" (a higher priority queue). This compromised the console's ability to respond when the server was experiencing heavy load.

Web Services

Change Request Number

Description

055415

There is no longer an interoperability problem when using the SoapWare test specification and the UserLand client (reference implementation).

054749

It is no longer true that when using the wsgen Ant task to assemble a stateless session EJB into an rpc-style Web Service, wsgen fails with a parsing error if the package level of the EJB contains only one level, such as:

package mytest;

055645

The Remote2WSDL class, used to assemble a WebLogic Web service manually, now correctly includes a protocol option for specifying a protocol other than http, such as https.

056332

Previously, if an exception occurred while WebLogic Server was processing a SOAP request to invoke a WebLogic Web service, the WebLogic Server executed the ServletResponse.getWriter() method twice. This in turn created another exception. This does not happen anymore.

056382

WebLogic Web services now support the xsd:decimal data type.

056631

WebLogic Web services now support the xsd:hexBinary data type.

056639

You no longer get an error when you use the WebLogic Web services client API to invoke an rpc-style WebLogic Web service whose stateless session EJB has security constraints defined for it in the ejb-jar.xml and weblogic-ejb-jar.xml files.

058230

The WebLogic Web services client API now correctly constructs a complex Java object on the client side after receiving the object inside a SOAP request. This complex object consists of an array of JavaBeans, one of whose attributes is itself an array of a different type of JavaBean.

058431

WebLogic Web services now correctly return nested array data type values.

059653

When using Remote2Wsdl to manually assemble Web services, you can now specify the context and jndi_name part of the URL equivalent to the location attribute of the <soap:address> element of the WSDL. This means that you can now successfully invoke a method on the Web service proxy obtained from the WSDL.

WebLogic Tuxedo Connector

Change Request Number

Description

055889

A TPReplyException thrown with TPESVCFAIL from WebLogic Tuxedo Connector will now be received by the Tuxedo Client.

057150

WTCValidateCF utility no longer throws an error when validating a configuration file that has FldTblClass elements.

XML

Change Request Number

Description

044211

The xmlx.jar file now correctly contains the HTMLEntities.res resource file.

046934

The built-in SAX parser now correctly parses deployment descriptor files that are written using any character set.

Warning: Prior to this fix, WebLogic Server would have failed to detect encoding problems in your .xml files for English-only applications. Consequently, English-only applications that ran without fail in the past may now fail with this Service Pack 2 fix; WebLogic Server will report an encoding-not-supported error.

If WebLogic Server reports this error, check the specified .xml file for the correct encoding name and syntax.

055082

The XSLTInfo.properties file in the weblogic.jar archive is now correctly called /weblogic/apache/xalan/res/XSLTInfo.properties rather than the incorrect /org/apache/xalan/res/XSLTInfo.properties, causing transformations to work correctly and not throw a SAXException.

056839

The weblogic.apache.xalan.serializer.Encodings class now contains the correct mapping between MS932 and Shift_JIS.

062320

The WebLogic FastParser now parses very large strings (> 1MB) in seconds rather than minutes.

 


WebLogic Server 6.1 Service Pack 1 Solutions

The next sections describe problems that were resolved in WebLogic Server 6.1 Service Pack 1.

Deployment Descriptor Editor

Change Request Number

Description

041479

Fixed a memory leak that was occurring during updates (redeployment of) J2EE applications.

048757

Removed all yellow caution icons that were next to deployment descriptor editors on the console.

048804

The Container Transaction Trans Attribute no longer has the '(none)' option for the EJB deployment descriptor editor in the console.

049465

In the console EJB deployment descriptor editor, the display name for the Weblogic RDBMS Jar is derived from the filename where the descriptor was read.

051858

All RDBMS descriptors referenced in the weblogic-ejb-jar.xml file are now available in the deployment descriptor editor.

051939

Fixed the ejb-jar.xml parsing code to accept Auto-acknowledge and Dups-ok-acknowledge as legal acknowledge-mode elements for Message-Driven Beans.

052613

The link to edit the deployment descriptor is now hidden during application configuration.

052665

If the web.xml file has a valid element called <run-as>, it is no longer lost when using the deployment descriptor editor.

052804

The <charset-params> entities and all child entities are now persisted to the weblogic.xml file by the deployment descriptor editor.

052963

Access to the deployment descriptor editor for .war, .jar, or .rar files no longer exists in the component table of the console.

053089

The deployment descriptor editor now indicates that the Primary Key that is used with the Automatic Key Generation feature must be of Java Type: java.lang.Integer.

053098

Added a legal values list to the MessageDrivenDestinationMBean's SubscriptionDurability attribute. Removed the SubscriptionDurability attribute from the MessageDrivenMBean and removed the SubscriptionDurability property from MessageDriven.jsp.

053282

Added the exclude-list tag to the EJB 2.0 deployment descriptor editor.

053375

The deployment descriptor editor is no longer blank after a modified bean is redeployed using the check box in the console.

054682

When persisting EJB deployment descriptor settings from the deployment descriptor editor, the contents of all description elements are now enclosed in CDATA sections to prevent possible parsing errors.

EJB

Change Request Number

Description

031350

The EJB compiler now correctly validates that a primary key class for an entity bean has all public fields. Previously, the validation existed but was broken.

044294

Fixed a memory leak that was occurring when repeatedly creating entity beans.

047050

If a message-driven bean's onMessage throws an unchecked exception, rolling back the transaction is now called instead of setRollbackOnly.

048506

Fixed a memory leak where multiple beans were created and not removed.

048716

EJB compliance error messages now indicate which bean is faulty.

049180

EntityPool did not call unsetEntityContext() when asked to release a bean. This has been fixed.

049658

Fixed a problem with using arithmetic operators with input parameters in ejb-ql. Capability was added for these three symbols: + - /

050134

The weblogic.ejbc debug flag is now working. To compile with debugging, use -g instead of -debug. For example:
java weblogic.ejbc -g foo.jar bar.jar

050860

The DDConverter now generates ejb-ql with updated syntax for the cmp20 bean.

051528

Added an optional <description> tag element in the <weblogic-query> tag in weblogic-rdbms20-persistence-600.dtd, so you can describe your query.

051653

Fixed a problem with SQL query generation in a many-to-one relationship where the primary key field is part of the foreign key.

051670

When an EJB that referred to another EJB's handle was passivated, a ClassCastException was thrown. This has been fixed.

051735

The EJB compiler was not recognizing the -j option when the compiler was specified as sj and hence was failing to execute the command. This has been fixed.

051803

The compliance checker now disallows local or local home to be passed as a parameter type or return type for the remote interface. See section 10.3.10.1 in EJB spec for more detail.

051807

The compliance checker no longer allows remote and local components to share the same CMR mapping.

051875

The XML generator no longer ignores values that are explicitly set. Even if the values are equal to their default values, they are generated.

051941

Fixed a problem with the EJB container that involved improper handling of a business method named remove.

052075

SELECT DISTINCT is now working when an ejbSelect() returns a collection of fields.

052502

Changes to EJB deployment descriptors are now picked up when EJBs are redeployed through the Deploy checkbox in the console.

053093

When the auto create tables feature is turned on, sequence tables are now generated.

053096

The ejbSelect method is now returning a set of local beans instead of returning a set of bean instances.

053101

Compliance checker no longer gives the wrong value for <acknowledge-mode>.

053287

The following entry in the ejb-jar.xml file no longer causes the entire file not to load:

<message-driven-destination>
<destination-type>javax.jms.Topic</destination-t
ype>
<subscription-durability>Durable</subscription-d
urability>
</message-driven-destination>

053596

The Number of Active StatelessSessionBeans is no longer allowed to exceed the max-beans-in-free-pool setting.

053599

Improved the ability of the EJB DDInit tool to determine bean classes.

053643

If an EJB without a local interface calls SessionContext.getEJBLocalObject(), an IllegalStateException is now being thrown.

053646

When validating an ejb-jar.xml file, the compliance checker and XML validator now refer to "relationship-role-source" instead of "role-source" to comply with a change in the EJB specification.

053735

A null pointer exception is no longer thrown in StatefulSessionManager when invoking local method.

053768

Updated the deployer so that it does not look for the weblogic.EJB20Enabler class to enable EJB 2.0. Also, removed license error messages referencing a separate download because they are now irrelevant.

053801

A Compliance Checker error is no longer thrown when a message-driven bean's class does not contain an ejbCreate() method but its superclass does.

053827

The DDConverter utility can now be accessed using java weblogic.ejb20.utils.DDConverter as documented.

053884

If an ejbPostCreate method was defined with a throws CreateException and if SQLServer AutoKey Generation was enabled, the generated code was incorrect. This has been fixed.

053905

When you use EJB2.0 BLOB/CLOB mapping on an UPDATE, if the UPDATED field was shorter than the original field, the newly UPDATED result no longer contains the left-over data from the original field.

053944

Fixed the exception handling code so that if a stateless session EJB's constructor was throwing a RuntimeException or RuntimeError, the caller's java:comp/env JNDI context was correct after accessing the EJB.

053970

Default role and relation names are now generated, making it possible to set up EJB 2.0 relationships without setting the ejb-relation-name element in the relation declaration of the ejb-jar.xml descriptor.

053986

The descriptor mbean is now consistent regarding XML case sensitivity.

054021

An assertion error is no longer thrown when a clusterable entity bean is called from a non-clusterable EJB.

054225

Fixed a problem with ear file deployment when it contains a circular reference in the Class-Path entry of the Manifest.mf file in jar files.

054449

The code generated for EJB 2.0 entity beans that use container-managed persistence was changed to work around a limitation in Oracle. A cmp-field that is mapped to an Oracle LONGRAW column can now have a length greater than 4096 bytes.

Examples

Change Request Number

Description

045300

Added new JTA example that uses both Oracle's thin driver and JDriver. This example involves two database instances. For each database, the user must set up a single table and create a new transactional connection pool and a new transaction datasource. This example uses J2EE 1.3 features which use non-final API specifications.

048031

Clarified the instructions, syntax, and examples for specifying the cluster address and the listen port when invoking the example clients. Two files changed:

...\samples\examples\cluster\ejb\package.html 
...\samples\examples\cluster\rmi\package.html

050429

Standardized table creation sql script to be vendor independent.

051476

A problem was fixed in examples/ejb20/bands. demoPool connection pool now points to oraclePool connection pool.

051491

Corrected the reference and example code in the examples/jta/jmsjdbc/build.xml file.

051714

A problem was fixed in examples/ejb/sequence/mssqlserver /package-summary.html. demoPool connection pool now points to an mssqlserver connection pool.

052595

The second compilation of the i18n.logging.message directory is no longer producing errors.

052689

Fixed a problem running more than one client using Petstore.

053008

Corrected information in the SSLClient example document. Now, there is no reference to a production_apps directory as the applications directory and, the SnoopServet is located in the /WLS_HOME/samples/examples/jsp directory, not in the /WLS_HOME/config/examples/jsp directory.

053463

053466

The logging internationalization examples no longer have broken links.


WL_HOME/samples/examples/i18n/logging/package-summary.html now contains a link to WL_HOME/samples/examples/i18n/logging/message/UserSMessagesServlet.html.


The "Setting up your environment", "examplesweb application", and "Start the WebLogic Server with the examples configuration" links in WL_HOME\samples\examples\i18n\logging\message\UserSMessagesServlet.html now correctly go to WL_HOME\samples\examples\examples.html.


053383

Added a set-up step that was missing from the JSP Form validator example.

053396

The wireless stockDemo example is now returning a live quote instead of an outdated quote.

053525

Starting the default server in mydomain in development mode was causing the Defaultweb application and certificate.war file in the applications directory to be deployed twice.

053852

Updated DOCTYPE to register latest version of DTDs.

053871

Modified build script to compile JSPs consistently across all platforms.

054963

The generated startscript for migrated domains is now consistent with other scripts.

056080

Fixed a problem that was resulting in the examples\i18n\logging\message build script failing.

056114

Added literal encoding to fix a problem with the message webservice sample.

056347

Petstore Shopping cart EJB no longer uses clustering.

056495

Removed the time example.

JDBC

Change Request Number

Description

034041

Added the capability to rotate the JDBC log based on date. You can specify how often the log file should be rotated and when rotation should begin. The current jdbc.log file is has the most recent date timestamp at the end of the file name.

034046

It is no longer possible to create data sources based on multipools containing mixed XA and non-XA-aware connection pools because it could result in incorrect transactional behavior.

035380

It is now possible to dynamically create a JDBC DataSource using JMX APIs in addition to using the properties file.

042924

Creating a TxDataSource that points to a multipool now works. Previously, doing so resulted in a ResourceException.

045991

When you define a connection pool in the console by specifying a login and password as part of the URL instead of as properties, an exception is no longer thrown.

049963

Added a description to the javadoc comments for JDBCConnectionLeakProfile and JDBCStatementProfile interfaces that serve the connection pool runtime MBean.

051058

Changed checking of the "reserve" ACL to "admin" ACL in weblogic.jdbc.common.internal.ConnectionPool.startup(Deployment MBean).

051165

Added reset methods to corresponding profile so that profile storage can be reset programatically to initial zero size.

051371

The weblogic.Admin JDBC usage message now includes connection pool commands.

052540

The size of the PStatement cache is now handled explicitly through the Administration Console and through the JDBCConnectionPoolMBean. Setting size of the PreparedStatement cache via database properties is deprecated.

052960

The getter and setter methods for HighAvailability and LoadBalance in JDBCMultiPoolMBean.java are now deprecated. They are replaced by the AlgorithmType getter and setter methods.

053085

Added synchronization to the close() and isClosed() methods in the JDBC pool driver's Connection class.

053721

The getPoolList() method still exists in JDBCMultiPoolMBean in 6.1 and is documented in the javadoc.

054187

Upon multiple invocations, the PreparedStatement query no longer returns an incomplete ResultSet.

055655

JDBC driver DLL for Oracle 8.1.6 is no longer broken.

JMS

Change Request Number

Description

051938 & 053464

If a destination becomes unavailable, producers can now properly detect them as unavailable (peerGone) and will send and receive exceptions while the destination remains unavailable. Once the destination becomes available, producers will recover and resume working properly.

053635 & 054655

To get the proper transaction semantics, applications should always use an XA connection factory when inside an EJB. Furthermore, the default connection factory used by Message Driven Beans (MDBs) is now an XA connection factory. To configure user-defined connection factories used inside of an EJB as XA, use the Administration Console to select the XA Connection Factory check box (XAConnectionFactoryEnabled="true") under the Configuration-Transactions tab under the Connection Factories node.

053649

WebLogic JMS was only acknowledging messages up to and including the message being acknowledged. It now acknowledges all messages (unless the Acknowledge Policy attribute is set to Previous).

054154

When a message is serialized outside of JMS (pass by value to an EJB or an RMI call), the destination is no longer dropped.

054365

The behavior of the pro-active assignment of messages performed by session pool connection consumers has been corrected. Regardless of the messagesMaximum setting on the connection factory, a connection consumer will consume at most the connectionConsumer.messagesMaximum setting to any given session.

055364

When attempting to set properties on a message that is received in read-only mode, users can now call the clearProperties() method to make the properties writable. Previously, if a received message had no properties to clear, clearProperties() would not make the properties writable.

056556

When multiple subscribers are created under the same session, asynchronous subscribers no longer hang after receiving the first message.

JTA

Change Request Number

Description

024199

The JTA driver no longer requires read permission in the top level workspace.

048979

Fixed the JTA race condition that caused the following error if multiple clients used the same resources simultaneously:

Unable to create resource runtime mbean

050789

The auto-update interval for picking up applications deployed in a domain appears under Domain options and no longer appears under JTA Subsystem.

050849

Improved JTA resource health monitoring. There is now a distinction between an unhealthy/blocked transaction and an unhealthy resource. Once a resource is marked dead, a general mechanism informs the resource provider so that it can refresh itself. Hard-coded constants, such as the two-minute interval (after which an unresponsive resource is declared unhealthy), are now configurable.

051631

Using prepared statements with testConnectionOnRelease results in an SQLException for the Weblogic OCI XA driver.

051673

Heuristic exceptions are no longer being reported inconsistently in single versus multiple server configurations.

053638

A work-around is provided for the Oracle XA driver limitation that results from accessing the same database instance from multiple servers.

054513

Fixed checked transaction behavior check.

Miscellaneous

Change Request Number

Description

032447 & 054281

WebLogic Server no longer prints to the server log "Emergency," "Critical," and "Alert" messages that directly pertain to shutdown when the server is intentionally shut down by an Admin user.

047596

When the SHLIB environment variable is not defined, WebLogic Server no longer fails to find the performance pack when started.

048222

The console monitoring graphs are now working in Netscape 4.75.

048524

The LoginContext class always threw a LoginException with the message "Authentication Failed" regardless of the exception thrown by the underlying custom LoginModule implementation. The LoginContext class now propagates the exception thrown by the LoginModule implementation.

049668

The Service Pack installer can now delete empty directories.

050345

Now, there can be multiple versions of either the i18n_user.properties file or the weblogic/msgcat/i18n.properties file. This feature allows users to place their message information more flexibly and to update the system messages if necessary.

050385

Added the reset connection pool option to the console for Jolt connection pool. This option is also available in WebLogic Server 6.0 SP1 and SP2.

050489

It is now possible to pass an argument that contains a comment into the startup class without the parser splitting the value into two arguments.

050517

OBJ_ADAPTER is no longer thrown when a valuetype is passed to a CORBA server on Solaris.

050888

Fixed network classloading for classes stored in the server's classpath. Previously, a ClassNotFoundException was thrown in the client while the client unmarshalled objects of those classes.

051297

Improved the ZipException message when the application path is misconfigured.

052146

Fixed a problem with weight-based load balancing.

052349

Fixed a password-related problem that arose when migrating to WebLogic Server 6.1 from WebLogic Server 5.1 SP7 or later. Previously, if you had LDAP configured in ldaprealm.properties, after running the weblogic.properties file conversion, you had to add the password for the LDAP server to the config.xml file manually. This is no longer required.

052567

Added a detailed error message to be used if the performance pack is missing.

052666

Corrected the error message that relates to the startNodeManager.cmd script which is started from the WL_HOME/config directory. The error message now points to the correct directory.

053308

The Tuxedo server in the simpappcns example can now boot.

053320

Deleted these two examples:

time.ServerTimer
time.ClientTimer

WebLogic Time is deprecated. Use java.util.Timer instead.

053422

Fixed a problem with the Deploy checkbox in the console. If you de-selected this checkbox, the application was not deployed, but the next time the serer was booted, the application was deployed anyway.

053426

The conversion utility no longer creates and uses the production_apps directory.

053559

The weblogic.ant.taskdefs.ejb[20].DDInit tool is now better able to determine bean classes.

053584

Merged the Path field and the URI field used in the console when configuring a standalone component.

053617

Client-side rollbacks now release transaction data structures immediately.

053693

The weblogic.net API is now exposed in the javadoc.packages.

053725

The SNMP Agent screen in the console now has a field called "TargettedTrapDestinations" which is of type SNMPTrapDestinationMBean.

053952 and 054777

Fixed problems with starting Managed Servers from the command line. Also, the error log message did not indicate whether the error came before or from the current start-up instance. This has been fixed.

053955

Added %JAVA_HOME\bin to the PATH environment variable in the startNodeManager.cmd script and in the startNodeManager.sh script. Because of these additions, starting a Managed Server via the NodeManager no longer fails if the NodeManager has been started up without "java" in its PATH variable.

054131

In a cluster environment with a ProxyServer (HttpClusterServlet), when calls are made from a client through the ProxyServer, the nodes in the cluster now receive the true client details instead of the ProxyServer's details.

054281

ListenThread no longer fails during WebLogic Server shutdown.

054517

Fixed an HTTP tunneling problem with making RMI calls through user-launched threads on the server.

054608

Added attributes to dialog and table pages of the console for the properties, SNMPAtributeChange and SNMPLogFilter. The attributes provide the option to enable a server for each property.

054673

The snmpwalk command, a command line utility, is now working correctly.

054734

Fixed problems that occurred with the connection pool after the resource adapter threw a CONNECTION_ERROR_OCCURRED exception.

054738

Added support to allow an ear to contain a rar but have the rar's Java classes packaged in a jar that exists in the ear rather than in the rar itself. The classpath entry is now supported in the rar's Manifest.mf file.

054771

When the connection leak detector was in effect, ManagedConnections were automatically destroyed in the time specified by connection-cleanup-frequency and connection-duration-time elements in the weblogic-ra.xml deployment descriptor file. However, if the resource adapter itself recognized that the ManagedConnection was currently active, it had no way to abort the ManagedConnection destruction.

The resource adapter can now abort the automatic destruction of a recognized active ManagedConnection by throwing javax.resource.spi.IllegalStateException from a ManagedConnection.cleanup() method call.

054777 and 053952

Fixed problems with starting Managed Servers with the command line. Also, the error log message did not indicate whether the error came before or from the current start-up instance. This has been fixed.

054795

The installer now only permits a single 30-day trial period for a given product or release, service packs included. A license to extend the initial period can be obtained from the BEA Web site.

055090

During various interactions with WebLogic Server, the resource adapter received NoAccessRuntimeExceptions exceptions, which prevented the resource adapter from performing various operations. These access problems have been fixed.

055121

The start script that is generated by the converter tool now quotes

%CLASSPATH%.

055681

All nav.jsp files now send out the nav tree in UTF-8 encoding so that the JNDI tree on Solaris can be displayed properly.

056481

Fixed bean deployment path in the connector config.xml file. The connector.ConnectorEJBTest.testOpenConnection no longer fails.

Plug-ins

Change Request Number

Description

047784

The iisforward.dll file now supports multiple websites for the same IIS instance

050080

The PathPrepend and PathTrim parameters for the Apache plug-in can now work simultaneously when they use HTTPS over an SSL.

050253

The ISAPI plug-in now allows the content-length to be equal to 0 for POST and for PUT.

051912

The NSAPI plug-in (proxy35.dll) for Netscape Enterprise Server 3.5.1 on Windows NT was giving the error message, ns-httpd36.dll could not be found in the specified path. Because there is no such DLL in NES Server 3.5.1, this error message has been deleted.

052444

When you use the HttpClusterServlet plug-in and the primary server shuts down, a more informative error message is now displayed.

052480

The ISAPI plug-in now flushes the buffer even when the request is not served completely.

053773

Added a plug-in option to specify to which IP address the plug-in should bind when it connects to WebLogic Server.

054140

Added a new parameter, WLProxySSL, for all of the plug-ins whose default value is OFF. This parameter indicates whether HTTPS is used by the users' browser on which the proxy is based. The proxy then determines to which URL to send users in the case of response.sendRedirect.

054526

Fixed problems that resulted from using the same socket for the keep-alive connections.

054998

Fixed a problem with downloading a file from WebLogic Server 6.1 through IIS Web Server 5.0 as proxy. The error saying that inetinfo.exe has crashed no longer occurs.

055093

Fixed a problem that resulted from using SSL with the IIS plug-in.

RMI over IIOP

Change Request Number

Description

052086

Fixed a problem that arose from calling outbound using IIOP after re-deploying an EJB.

052300

Fixed a problem with ear classloaders that prevented call by reference from working.

054182

In the 6.1 release, there was an IIOP/SSL outage. This has been fixed. A convenience class for accessing the SSL socket factory in the client was added.

054376

Security credential propagation is now supported over IIOP.

055330

Corrected the IIOP JVMID discriminators that are generated for remote JVMs.

055394

Fixed the SVUID for weblogic.iiop.IIOPRemoteRef.

056505

Fixed a problem with encoding value types in Anys with the IBM JDK on AIX.

Servlets and JSP

Change Request Number

Description

043659

Shortened the session ID for WAP in a cluster.

049139

The following JSP no longer fails to compile.

<%@ taglib uri="accents.tld" prefix="accents" %>
<%@ page contentType="text/html; 
charset=ISO-8859-1" %>
<accents:test>
fail
</accents:test>

049147

When you start the default server, a warning message referencing the servlet 2.2 DTD no longer occurs.

050343

ResponseHeaders.writeHeaders() generates an HTTP header for single byte strings only.

050370

Added the PrefetchTag class to the weblogic-tags.jar file.

050398

Added the weblogicx.jsp.tags.PrefetchTag class to the weblogic-tags.jar.

051396

Load-on-startup now produces a warning if an invalid value is entered.

052109

A NullPointerException is no longer thrown every time ServletSessionRuntimemBeanImpl.getMainAttribute() is called.

052134

Added support for two Web applications or two ejb-jars with the same name in different ear files. Previously, deploying two ear files that each contained a web application foo.war file caused an InstanceAlreadyExists error.

052665

Added the capability to configure a <run-as> element for a servlet from the web application deployment descriptor editor.

052786

Exception-type mapping implementation no longer looks at the exact match for the exception type. Multiple classes can now be registered in the hierarchy. Exception-type mapping picks up the closest match.

053314

Added performance optimizations for in-memory replication and memory session persistence.

053333

The JSP page is now used as an error page if an exception is thrown in the Web application.

053344

Fixed a problem caused by using multiple slashes in a URL.

053377

The exception weblogic.servlet.internal.session.MemorySessionDataMissing no-arg constructor for class is no longer thrown when:

    • A servlet invoked an EJB method and passed it a reference to its HTTPSession object.

    • The servlet and EJB had been deployed in the default Web application.

    • Memory-based session persistence was used by the servlet.

053573

When more than one call for Forward() of RequestDispatcher is made within a Servlet service method, the container now throws an exception instead of returning a blank response.

053634

The query parameters added in a forward or an include now take precedence over the existing ones, in accordance with the servlet specification.

053722

Introduced a switch in the weblogic.xml file that redirects the client using the absolute URL. For example:

<container-descriptor>                  
<redirect-with-absolute-url>false</redirect-with
-absolute-url>
</container-descriptor>

If set to false, the absolute URL is used.

053743

Now, in accordance with the servlet spec, an IllegalStateException is thrown if ServletA tries to forward the same request to the JSP after having forwarded it to ServletB.

053932

The HttpClusterServlet no longer throws a Null Pointer Exception and weblogic.utils.AssertionError if secureProxy is on.

053959

BodyTags can now return EVAL_BODY_INCLUDE from their doStartTag method.

054016

Fixed the response header format corruption problem when the Content-Disposition header is present.

054194

The content in the response buffer is now flushed as soon as the amount specified by the setContentlength is fulfilled.

054427

Added a mapping for jnlp files to the weblogic/servlet/internal/web applicationServletContext.java file.

054694

RequestDispatcher now invokes Servlet 2.3 filters.

055002

A file can now be downloaded, instead of only appearing in the browser, after setting up mime-type in the web.xml file.

055106

Parameters for the request are now returned after the HttpServletRequest.getParameter (param) method for a POST request is executed in the doPost() method in a servlet.

055241

The request.getAttribute and request.setAttribute are no longer broken when Content-Type=text/xml and the method is POST.

055265

New parameters no longer appear lost when getServletContext().getRequestDispatcher and request.getParameter are used in the arguments.

055591

A null pointer exception is no longer thrown in request.getParameterMap() if the method is called with any of the getParameter() methods.

055630 & 055962

Fixed a problem with internal ServletResponse implementation.

056188

Fixed a parse error. The JSP container was failing to parse when pageEncoding was omitted.

056277

There is no longer an ArrayIndexOutOfBoundsException thrown on POSTs when using the Netscape browser.

057022

The JSP compiler no longer generates a classpath that is too long for the Win32 command line when Class-Path is used.

System Administration

Change Request Number

Description

045203

The message produced due to an incorrect password when using weblogic.Admin is now consistent regardless of the command used.

049177

Fixed an error related to Web application deployment in clusters.

049178

Fixed an error that occurred when deploying the default Web application.

049919

Redundant copies of ServerConfigMBeans are no longer created on the Administration Server and the Managed Server.

050374

Converting the weblogic.properties file no longer fails when DeliveryMode=persistent.

050853

Configuration and deployment can no longer take place with the wrong path and URI.

050874

A cloned server can now be started as a Managed Server.

051618

weblogic.Admin now fetches the information from MBeanHome of the server running at the address specified in the -URL option. If the -URL option is not specified, weblogic.Admin fetches information using the AdminHome of Domain.

052046

When a password is not specified using the -password option in the command line for weblogic.Admin, the user is prompted to enter the password.

052095

When launching the Admin startup script, the Administration Server was started but did not detect running Managed Servers. Now, when the Administration Server starts up, it always loads the root directory from the properties directory (-Dweblogic.RootDirectory) or uses the default directory (current directory).

052198

A cloned server no longer fails during start-up.

052261

Fixed a problem with using the weblogic.deploy utility to deploy multiple EJB targets.

052326

If an erroneous root directory is specified in the config.xml file,

WebLogic Server gives a warning message and the configuration is persisted to the directory where the Server is booted.

052349

When the deployment descriptor converter is run to generate a config.xml file from the weblogic.properties file that has the property weblogic.security.realmClass=weblogic.security.LDAPRealm set, a Password attribute now gets created in addition to the ConfigurationData for the CustomRealm. Values for both ConfigurationData and Password are based on the information contained in the ldaprealm.properties file. When the config.xml gets saved, the Password gets encrypted.

052656

Applications in the auto-deploy directory are no longer deployed twice.

052753

Starting the Administration Server and then starting two Managed Servers simultaneously no longer causes a server failure.

052804

If the <charset-params> entry exists in the weblogic.xml, then the deployment descriptor editor displays it. Previously, it failed to display and gave a ClassCastException.

053053

Fixed a problem with redeploying a message-driven bean after undeployment.

053485

This is a known issue with the conversion utility for customers migrating from earlier releases of WebLogic Server as well as those users following the migration tutorial.

The JDK automatically specified by the conversion process under the compileCommand tag in the weblogic.xml is set to JAVA_HOME\javac. This setting is no longer missing the bin subdirectory, which is set to JAVA_HOME\bin\javac. A corrected version of the conversion utility has been posted at http://developer.bea.com/tools/techguides.jsp.

053926

When the Administration Console was used to convert weblogic.properties on src510sp10_117sj to the config.xml file on src_ag_131sj, the root directory was not converted. This has been fixed.

053980

Fixed a problem that involved deploying a Web application in a cluster that was using an MBean API.

053991

MBean name patterns specified by JMX can now query the MBean server and find MBeans.

054173

Fixed a problem with starting Managed Servers simultaneously in a clustered environment.

054485

Improved the accuracy of Managed Server startup URL error messages.

055150

Fixed serialVersionUID for outer and inner classes following Sun's recommendation.

055945

A ClassCastException was caused by deleting MBean references. This has been fixed.

Web Services

Change Request Number

Description

048800

Fixed a problem with array elements. Array elements are no longer in the SOAP-ENV namespace. The .NET array always ends up as a non-null array of zero elements.

51222

You can now use the WebLogic Web Service client API to invoke a Microsoft-hosted Web service, as long as you add the following lines to your Java client program:

CodecFactory factory = CodecFactory.newInstance();
SoapEncodingCodec codec = new SoapEncodingCodec();
codec.writeQualifiedName( false );
factory.register( codec );

053249, 053254

When a static Java client invokes a message-style Web service by sending or receiving an XML document, the client no longer receives an error due to the WSDL of the Web service not supporting the literal encoding style.

058431, 054687

Null exceptions are no longer thrown when you try to invoke a remote procedure call Web service from a static Java client by using an array on primitive integers.

XML

Change Request Number

Description

046955

Loading an XML document with xsl:inlcude in it from a Web application was causing an SAX exception. This has been fixed. The path for the xsl:include must be page-relative.

048165

It is now possible to circumvent caching, in general and on specific entities.

049063

After you create parser and entity XML registry entries in the Administration Console, the public ID, system ID, and root tag fields become read-only and you cannot modify their values. This is the correct behavior.

049066

Changes in the console are now propagated to the entity cache.

049082

Debugging is now supported through an attribute in the ServerDebugMBean.

049855

The xsl:inlcude was leading to the wrong path for the include stylesheet when used in stylesheets that were loaded by JSPs that used the XSLT tag library. This has been fixed. The path for the xsl:include must be page-relative.

050469

The Administration Server now correctly converts XMLRegistryEntryMBeans to the new MBean formats, even if an XML registry is not assigned to the Administration Server.

050620

When an entity was resolved, the registry entry was called once to resolve and once to get the timeout interval for entering into the cache. These functions are now performed by a single call.

052258

There are now default JAXP factories for standalone java applications. If the system properties are not set on the command-line, the weblogic factories are instantiated instead of the Apache factories.

054332

Fixed a problem that was causing an error to occur when parsing a well-formed XML document with the default parser.

054670

The error message that the parser produced when parsing an XML file if the user specified an undeclared tag is now easier to understand.

055499

When the cloneNode(true) method of weblogic.apache.xerces.dom.Node is called on a root element that contains a namespace attribute (i.e. xmlns="http://www.abc.com/xml";) an erroneous DOMException is no longer thrown.

 


WebLogic Server 6.1 Release Solutions

The following sections describe problems that were resolved for WebLogic Server 6.1.

Deployment Descriptor Editor

Change Request Number

Description

048382 & 049320

Fixed some problems with displaying the Connector Deployment Descriptor Editor in the Administration Console when clicking on the menu item "descriptor."

048965

Fixed some problems with displaying the EJB, web application, and WebServices nodes in the Deployment Descriptor Editor of the Administration Console. An error message was displaying when these nodes were clicked.

048966

Fixed problems with displaying Security Role Assignments in the web application node of the Deployment Descriptor Editor. Clicking Security Role Assignment caused an IllegalArgument exception to display and an error message for the web application.

048971

Fixed some problems in the EJB 2.0 Deployment Descriptor Editor when clicking on existing Resource Reference instances.

048973

Fixed some problems in the EJB Deployment Descriptor with persisting EJB entities. Clicking on the Persistence tab sometimes caused an exception.

049458

Fixed problems cloning the following: WebLogic RDBMS bean, WebLogic RDBMS Jar, transaction isolation, session beans and entity beans.

049460

The EJB Deployment Descriptor Editor had problems creating description folders for new WebLogic EJBs. Also, it was not possible to configure a new entity descriptor, stateless session descriptor or stateful session descriptor for a newly configured/cloned WebLogic EJB. These problems have been fixed.

049413

Fixed problems with persistence in each of the Deployment Descriptor Editors.

EJB

Change Request Number

Description

042794

Deploying Message-Driven Beans into a full cluster through the Console's "Clusters" panel was broken. This is now fixed.

046960

Fixed a known problem with two servers hanging when a distributed transaction involving message-driven beans (MDBs) spans both servers.

Examples

Change Request Number

Description

041463

Using UNIX, the config/petstore/StartPetStore.sh script has been modified to use the Hotspot VM on HP. This modification is a workaround for a bug in the HP client VM.

047509

When running the RMI examples, it was necessary to reboot the server after deploying. Before rebooting, the server was throwing a javax.naming.NameNotFoundException. This has been fixed.

049011

Fixed some problems with the build.xml file in WEBLOGIC_HOME/samples/examples/xml/sax.

049264, 048678

The PetStore demo now logs you out correctly when you do "sign out".

Internationalization

Change Request Number

Description

035036

When WebLogic Server boots and prompts for the boot account's password, the prompt used is now internationalized.

041021

Fixed a problem failing to generate properties files for some message catalogs after executing l10ngen.

041078

Fixed some duplicated keys in the english.xml file.

041264

Fixed some internationalization problems with certain tags not being in english.xml.

041266

The time stamp is now internationalized.

JCA

Change Request Number

Description

049346

WebLogic Server now supports "javax.resource.spi.security.GenericCredential" credential-interface or the "Kerbv5" authentication-mechanism-type. Previously, specifying either value for the <authentication-mechanism> in the ra.xml file for the resource adapter being deployed resulted in a failed deployment.

JDBC

Change Request Number

Description

033423

There were dbKona problems with QueryDataSet and the OCI805_8 driver. This has been fixed on Windows NT, but is still a problem on HPUX and Solaris.

033920

There was a problem in JDBC when running tests which access the connection pool. This has been fixed.

035530

There were problems enabling OS authentication and using Oracle 8.1.6/oci8 with the jDriver. This has been fixed on NT and HP-UX, but still is an issue on Solaris. We have added an error message that reports this problem: OS level authentication is not currently supported due to a defect in OCI 8 libraries.

037589

Added Oracle thin driver support and fixed some outdated command line help.

037591

Added support for ORACLE_THIN database type. Removed obsolete database types and command line options.

037596

Fixed PreparedStatement.setBlob and PreparedStatement.setClob.

037693

There are no longer problems with the Oracle driver and ROWID selects when running examples.dbkona.rowid.

037893

Fixed getBytes() to return null instead of a zero-length byte array with Oracle LONG RAW columns.

038143

JDBConnectionPoolRuntimeMBean's were not working. Added a RuntimeMBean implementation to ConnectionPools.

038229

The jDriver for Oracle 8.1.6 no longer causes Managed Servers to run out of memory.

038275

We no longer refer to the weblogic.classpath in JDBC error messages. The weblogic.classpath does not exist in WebLogic 6.1.

040379

The following error occurred when the server and serverName properties in a JDBC connection pool were specified with the same value:

<Cannot startup connection pool "jtaXAPool" server and serverName properties must have the same value>

This problem occurred when the XA driver required the server or serverName property to be set. It was occurring with the WebLogic jDriver for Oracle, but not the Oracle thin driver, or the Cloudscape driver. It has been fixed.

040509

Fixed a small problem with Solaris 2.6 and the jdriver.

041286

Better error message for misconfigured connection pools.

041302

The MS SQLServer driver has been updated.

041514

Added support for JDBC and connection pool monitoring in the Console.

048764

Killing connection pools through the console is fixed.

JMS

Change Request Number

Description

039726

If a pre-6.0 WebLogic Server was shut down when it had active database operations, after upgrading to 6.1 some durable consumers may have received messages that were sent to the topic after the durable subscriptions were created. There was a race condition between the scavenger (which updates the database periodically) and Ctrl+c killing the pre-6.0 server. This has been fixed.

039809

The JMS messages types, TextMessage, ObjectMesssage, MapMessage and XMLMessage now implement in read-only mode so that the receiver cannot modify the message before calling clearBody().

041031

The JMS flow control no longer stalls asynchronous messages from a consumer.

041165

If a user receives a JMS ObjectMessage and calls the toString method before calling getObject, the message is now automatically deserialized.

041821

The JMS connection is now cleaned up properly when the client terminates without closing.

042096

Calling a setRollbackOnly in an MDB no longer yields a verbose log message.

042458

JMS can now handle sending messages that are received from a foreign provider.

042792

JMS can now process multiple messages concurrently with the JMSServerSessionPool.

042997

Server session pools no longer deadlock on multi-CPU boxes.

043077

The message listener no longer fails to auto acknowledge messages in server session pools.

043155

JMS topic messages now expire since they are checked at the time the message is given to the consumer.

043223

JMS can now send a TextMessage with more than 32K characters.

043225

When performing a setObject, the JMS ObjectMessage is longer unnecessarily unserialized.

043445

Sending a WebLogic Server JMS message using Fiorano 5.0 no longer generates an exception.

043447

When a JMS server session pool is shut down, its server sessions are now cleaned up and closed.

043519

A session rollback and recover no longer prevents asynchronous consumers from receiving messages.

043752

Recovering expired messages no longer causes a NullPointerException.

043884

JMS provides better performance by not synchronizing writes to the file stores. Synchronous writes are configurable via the command line using properties and are enabled by default.

Dweblogic.JMSFileStore.SynchronousWritesEnabled=(false|true)

Dweblogic.JMSFileStore.<store name>.SynchronousWritesEnabled=(false|true)

The first property applies to all JMS file stores running on the server. The second more specific property takes precedence over the first. The order where the properties are specified makes no difference.

043973

TopicSesssion.unsubscribe() is now rejected if a message has been received as part of a transaction or has not been acknowledged in the session.

044200

The JMSConnection Mbean destroy() function now destroys the Connection when run on the server side. After destroying the Connection, the consumer is able to retrieve messages and the producer is able to send messages.

044285

JMS persistence mechanism no longer locks up when there are not enough server threads.

044450

The JDBC Store code no longer prepares "COMMIT WORK" unnecessarily.

044605

The serialization of an unsent JMS message no longer generates a NullPointerException.

044891

On a JMS transacted session, Session.close() now rolls back the in-progress transaction instead of committing it.

044961

The getBooleanProperty() correctly returns false if a value for name is not found. All of the other getProperty methods return NumberFormatException if a value is not found.

044976

The returned values and exceptions from getXXX() in MapMessage now return the correct values, as follows:

If the value for the field does not exist, then getByte() should return NumberFormatException.

If the value for field can not convert, then getByte() should return MessageFormatException.

If the value for the field does not exist, then getBoolean() should return false.

If the value for the field can not convert, then getBoolean() should return MessageFormatException.

045531

A NullPointerException no longer occurs when a JMS durable subscription is configured but a store is not configured.

045956

The connection consumer now behaves properly when creating a server session pool that is using default factories.

045963

The connection consumer no longer ignores the maxMessages field that caused it to swallow all the selected messages.

045980

A detailed log message was added for failures of the first SQL query, which describes the likely problem and provides a work-around. The work around ensures that the connection pool being used has permission to access the given tables. It also fully qualifies the table names by configuring a table name prefix in the JMS JDBC store that includes the schema and catalog names: ([schema.[catalog.]]prefix).

046705

When setting the message listener on a subscriber, JMS now remembers the context classloader at the time of setting so that when it calls onMessage on that message listener it can set the context classloader appropriately. This allows EJB to send messages to a web application subscriber that contains classes only present in the EJB.

046726

There is a new configuration option for "acknowledge" to specify the new or old behavior. This has been added because JavaSoft has proposed changing the meaning of "acknowledge" based on the description in the JMS 1.0.2 specification as opposed to the one specified in the Javadoc, as follows:

"Section 4.4.13: Acknowledging a consumed message automatically acknowledges the receipt of all messages that have been delivered by its session."

047424

JMS no longer throws a NullPointerException when the message size exceeds the quota size.

048181

When creating a temporary topic, and then closing the connection, the following exception is no longer thrown when looking up the topic name: weblogic.jms.common.JMSException: Error unregistering RuntimeMBean.

049518

Fixed a problem migrating text messages generated using WebLogic Server 6.0 to WebLogic Server 6.1. The messages could not be received and the following message was thrown:

The corresponding file block will be zeroed out on disk, and this corruption will no longer be reported in the future. java.io.StreamCorruptedException: Unknown object stream version.

Miscellaneous

Change Request Number

Description

035039

When WebLogic Server needs to prompt for the boot password, it now logs (in security.xml) that it is prompting. This allows an administrator on a remote machine to know why the machine is apparently "hung".

036141

A Managed Server did not start if guest had been disabled (in order to do a JNDI lookup in an ACL). This has been fixed.

036604

The method ClusterMBean.setDefaultLoadAlgorithm() no longer accepts illegal values and now throws the proper IllegalArgumentException.

036986

Using Weblogic Server's XA driver with CMP no longer fails at deployment time.

038883

Specifying the root directory when starting the server was not working when the root directory was not under a /config directory. This has been fixed.

039066

If you entered an incorrect password when prompted at system startup, the server tried to start anyway. The startup eventually fails. Now you are re-prompted for the password when the password is wrong.

039182

When binding two clusterable objects implementing the same interface to the same JNDI name on a single server, an exception was not being thrown and the first clusterable object was being bound. This has been fixed.

039249

A Managed Server had a memory leak when it monitored JMSServer using the Administration Console. This has been fixed.

039361

If you create a group in the RDBMS realm, you can now delete the group.

039891

The server now sets the context attribute correctly during servlet initialization.

039960

Log Viewer is now working in non-U.S. locales.

039995

A server startup error no longer occurs after a WLEC Connection pool was created using the Administration Console.

040168

The logging example for internationalization failed when a dot (.) occurred in the path. This has been fixed.

040177

Additional user information was required when converting weblogic.properties files for use with WebLogic Server 6.0. This has now been added to the product documentation.

040178

When you were using the conversion utility, if a weblogic.properties file included the property weblogic.httpd.register.Name=weblogic.servlet.FileServlet and the servlet did not have initial arguments associated with it (it did not have the property weblogic.httpd.initArgs.file=arg1=value defined in the same weblogic.properties file), then the conversion utility was throwing a Null pointer exception. This has been fixed.

040213

The listenport of a Managed Server cannot be the same as the Administration Server listenport. You cannot, for example, use localhost or 127.0.0.1, with the 7001 host number on both the Managed and Administrative Servers. A more descriptive and informative error message has been added.

040297

Fixed a bug that prevented attributes set in application.xml from propagating from Administration Servers to Managed Servers.

040405

The config.xml file is now serialized using the Apache XML serialize classes. This results in the correct XML, including escapes for built-in entities and an XML header with encoding specified. The encoding used is the platform default. This also fixes problems with the "&" character.

040659

When specifying getParameter() encoding as iso-8859-1, the POST method is now working properly.

040688

When a mail session was targeted to a server that is part of a cluster, the following exception was being thrown because the mailsession was not serializable: java.io.NotSerializableException: javax.mail.Session. This has been fixed.

040698

The Application Manager no longer throws an unnecessary exception if the poller tries to deploy an application that is still in the process of being copied.

040899

Fixed a problem with a start-up class that occurred when the converter utility converted startup weblogic.properties into .xml.

040950

Fixed a problem in JTA. For XA connections, the Connection Pool test connection logic was attempting to start a distributed transaction before executing the testing SQL. This had the potential to create a javax.transaction.NotSupported exception.

041157

The dialog tabs in the Console were not working correctly when the Mbean name contained Kanji characters.

041290

If the username property is set from the weblogic.Admin or weblogic.Server command lines, the username must be the system password. Note however, that the username syntax is retained to prevent breaking a user's scripts. The weblogic.management.password property value must be the system password and the username may not be modified in the config.xml file.

041662

To improve JTA, we now advertise resources on JNDI. Resources were dynamically discovered as transactions go along, but now it is also possible to find out which resources are currently being supported at which servers.

041757

Fixed a problem with JTA. Resource advertisement (JNDIAdvertiser) was incorrectly done under the caller's identity. We now use the system identity while doing this operation.

041845

Updated the NTRealm to improve general usability and functionality.

041854

To help support Java WebStart with WebLogic Server, we now provide a default web application with the web.xml configured for this mime type. We have also provided other mime type mappings.

041995

Fixed an Unexpected Error being received in the console when resuming an active server. Also deleted some extraneous informational messages in the console when adding users.

042183

When the config.dtd was being generated in the console it was appearing with some errors. This has been fixed.

042362

According to the JTA spec documentation of setTransactionTimeout():

"seconds: The value of the timeout in seconds. If the value is zero, the transaction service restores the default value."

If the value was zero, WebLogic Server was not resetting the default value. This has been fixed.

042794

Deploying message-driven beans into a full cluster through the Console's Clusters panel was broken. It is necessary to specify each server individually as a target through the Servers panel.

043369

Applications deployed across a domain now keep their original packaging, meaning that if an application was exploded on the Administration Server, it will stay exploded on the Managed Server.

043388

Clusters of WebLogic Servers no longer require the use of a shared network drive. Both the WebLogic Server installations and your applications can now reside on local file systems.

049417

The Password Converter Tool shipped with the Beta Release has been fixed and no longer returns a SAX Parser error for all files.

Plug-ins

Change Request Number

Description

038831

The Apache plug-in no longer fails under heavy load.

040817

When using IIS to browse and call a regular JSP page that calls a Java Bean and getting a ResultSet reference, there were problems when submitting through the FORM POST method. The HTML stream was getting truncated when it came back to IIS--in other words, the page was only partially painted. This has been fixed.

041332

Using plug-ins, MatchExpression can now contain multiple, comma-separated expressions.

041534

Using the mod_wl.so, Apache was not proxying without Debug and DebugConfigInfo in the httpd.conf. This has been fixed.

041580

The Apache plug-in MatchExpression now works if an encoded URL is used.

041745

Added a log message when the trusted CA file isn't specified and SSL is used with the Isapi plug-in.

041754

Fixed an infinite loop when ISAPI was configured for SSL but using a non-secure port.

041939

The Apache plug-in wasn't filtering out the header "transfer-encoding"="chunked". So the browser was failing to handle these responses, causing Netscape to hang and IE to display an error page. This has been fixed.

042482

The NSAPI and Apache plug-ins no longer have a READ timeout on HPUX-11.

044988

Fixed a problem with the NSAPI plug-ins where the socket was not properly closed by the plug-in side. The un-closed socket on the webserver side will be left in CLOSE_WAIT state.

046018

There are new binaries for Apache 2.0.

046392

It is now possible to have different cookie names set for different <Location> blocks when using the Apache plug-in.

046423

Weblogic Server now supports static libraries for Apache.

046424

KeepAliveEnabled and KeepAliveSecs parameters have been added for the Apache 2.0 plug-in.

046546

Cookie name is now configurable for persistent sessions. There is a new parameter, PersistentStoreCookieName (default=WLCOOKIE), in weblogic.xml.

046946

Fixed a problem with large deployments of WebLogic Server, wherein for a period of time a cluster node behaves as if it is the only one member in the cluster when it's not. Now, using ListenDelaySecs, you can delay the http request handling until it finds the other members. For example:

<Server> ListenDelaySecs="30" </Server>

Delay the http listen thread for a configurable amount of time so that the new node has time to acknowledge the existence of other cluster members.

046956

Resolved some problems caused by DefaultFileName and VirtualHost with Apache Stronghold/Raven proxies.

047987

Resolved a problem that occurred with NSAPI when streaming a large number of bytes (500,000 bytes) using SSL from the browser to the proxy and from the proxy to the server.

047636

WebLogic Server now supports DSO as well as statically linked modules for Apache 1.3.X.

Servlets and JSP

Change Request Number

Description

026488

Fixed a problem with servlets when the parameter for method println(String) was null.

029989

The wrong error message is no longer sent when an UnavailableException was raised within a servlet.

030880

Fixed problems compiling JSPs when debugging was turned on. Now you can specify compiler flags in weblogic.xml. For example:

<!-- weblogic.xml: weblogic-specific web app descriptor --> <weblogic-web-app>
<session-descriptor>
</session-descriptor>
<jsp-descriptor>
<jsp-param>
<param-name>compileCommand</param-name> <param-value>jikes</param-value>
</jsp-param>
<jsp-param>
<param-name>compileFlags</param-name>
<param-value>+E -nowarn</param-value>
</jsp-param>

037771

Optimized the checking of JSPs for reloading.

038739

Improved support for JSP debugging.

039083

The RequestDispatcher and forwarding a JSP page now works correctly.

039193

When users forgot to make their servlet class public, a vague and unhelpful error was being thrown. This no longer happens.

039530

Fixed internal servlet tags to reset their state on release. If you used the same tag more than once on a page the additional tags kept the stale data from the previous tag.

040171

You can now set the attribute SingleThreadedServletPoolSize through the Administration Console.

040338

All functioning servlets are now displayed in the mydomain>web applicationlications>Defaultweb application_myserver>ActiveServlets window of the console.

040662

When JSP files had a page tag, the JSP compiler was not generating a class, or java file. This happened only with command line jspc. This has been fixed.

040766

Fixed a problem in servlets with using ../ for a relative URL when doing a response.sendRedirect.

040814

Added more informative error messages for instances when servlet user errors cause exceptions.

040843

Fixed problems with deploying web applicationComponents using virtual hosts.

040981

Fixed problems associated with WAP and session cookies using the pipe characters.

041234

Fixed a problem in JSP/Servlets using POST and HTTPS.

041478

A change to session cookie format fixed some problems with URL rewriting.

041605

JSPs compiler error pages no longer display a corrupt error message from javac.

041684

Fixed a problem in servlets. The XSLT tag threw a SAXParseException while processing XML content.

041729

The weblogic.servlet.jsp.Precompiler now honors weblogic.xml parameters, like workingdir, packagePrefix, etc., for the JSPs that it precompiles.

041945

When the web.xml had the setting inputCharset./A*=Shift_JIS inputCharset./B*=EUC-JP, and two clients simultaneously accessed the JSP/Servlet, WebLogic Server failed to handle these string correctly. It was possible to get the correct result from one client, but not from the other. This has been fixed.

042031

In the web application data table, when you click the monitoring icon for any web application and then click on the monitor link in the Servlets column, the correct heading is now displayed.

042293

Servlet URL rewriting was working fine with IE 5.0 but wasn't working with Netscape 4.7. This has been fixed.

042509

Fixed problems with forwarding from one web application to another web application and using authentication in both. Session data is no longer sharing inappropriately across the applications.

044873

When you compile a JSP manually with weblogic.jspc, the -version argument is now working.

044926

WebLogic Server 6.1 now correctly generates Java code from JSPs that include 2Bytes code.

049760

The weblogic-vtags.jar file containing the JSP tag library for Form Validation Tags is now in the ext directory as stated in the documentation.

Web Services

Change Request Number

Description

046032, 046808

The WSDL of a WebLogic Web Service is now generated by a JSP, which by default dynamically sets the host and port of the WebLogic Server instance that hosts the service. You can specify that the host and port be hard-coded in the WSDL by explicitly specifying their values when you assemble the Web service using the wsgen Ant task.

046215

When you assemble a WebLogic Web Service using the wsgen Java Ant task, you can now specify that you want to use HTTPS (rather than the default HTTP) when invoking the Web service.

047794

When you use the wsgen Java Ant task to assemble a WebLogic Web service, the generated Enterprise Application archive no longer contains both a web application directory and a web application *.war file; it now contains just the *.war file.

048797

WebLogic Web Services now interoperate correctly with Array types in the Microsoft SOAP Toolkit.

XML

Change Request Number

Description

034785

WebLogic Server now supports namespaces in the XML registry.

034785

Provided methods to retrieve namespace information about the document, such as localRoot, qualifiedRoot, and namespaceURI. If the XML document has namespace defined, then the lookup in the registry will be based on the qualified name.

036428

Previous releases of the XML subsystem included an error in Apache's implementation of the javax.xml.*.parse(File) method, included in the xmlx.jar file. Because WebLogic Server no longer includes this JAR file in the product and WebLogic Server's own implementation of the method has always been correct, this problem does not apply to the current release.

036642

Generated custom parsers no longer convert newline characters that are embedded in attributes and tag bodies into a single space character.

Note: The ability to generate custom parsers is deprecated in this release of WebLogic Server. Instead, use WebLogic Server's high-performance parser.

039096

You no longer have to restart WebLogic Server to make it aware of a newly added entry to the XML registry.

039247

Custom parsers are now correctly invoked when an XML document that has been configured to be parsed by the custom parser is parsed using the setAttribute() method of the Servlet API.

040479

Fixed a bug in JMSHelper that was causing incorrect XML to be written to the config.xml file.

041540

The Xerces parser serializer bundled with the WebLogic server now supports multi-byte encodings, such as Shift_JIS or EUC-JP.

041541

The Xerces parser method apache.xml.serialize.BaseMarkupSerializer.printEscaped() bundled with the WebLogic server now supports multi-byte encodings such as Shift_JIS or EUC-JP.

041734

WebLogic Server's JAXP implementation no longer requires the input stream to be resettable when it contains an XML document that is about to be delegated to a particular parser for parsing.

041778

A NullPointerException error is no longer thrown when an XML document that contains an external entity that has been correctly registered in the XML registry is parsed.

041797

After you create a new server, the server no longer fails to reboot and the config.xml file no longer has some incorrectly parsed headers.

46951

The method weblogic.xml.sax.XMLInputSource.getNamespaceURI(), part of WebLogic Server's extension to the org.xml.sax.InputSource class, is implemented in the current release.

48809

The SaxParserFactory is now being selected correctly when parsing a document from a SAX Version 2 Servlet attribute.

48810

You can now configure a parser for a particular document type by mapping the class name of the parser to a Public ID. NOTE: Specifying the parser class name when configuring a parser for a particular document type is deprecated in this release. Instead specify the Factory name.

 

back to top previous page