![]() |
![]() |
|
|
| |
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
Cluster
Console
EJB
Examples
JDBC and jDriver
JMS
Miscellaneous
Plug-ins
Servlets, JSPs, and Web Applications
Security
System Administration
Web Services
XML
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
Cluster
Console
EJB
Examples
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
JMS
JTA
Miscellaneous
Plug-Ins
RMI over IIOP
Security
Servlets, JSPs and Web Applications
System Administration
Web Services
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
Third-Party JAR Files in WebLogic Server 6.1 Service Pack 3
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
Examples
JDBC
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
Miscellaneous
Plug-Ins
RMI over IIOP
Change Request Number |
Description |
056233 |
ejb11.security.HomeMethodPermissionTest.testHandleRemoveWithoutPermission() no longer fails with an out of memory error. |
Security
Servlets, JSP and Web Applications
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
WebLogic Tuxedo Connector
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
JTA
RMI over IIOP
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
WebLogic Server 6.1 Release Solutions
The following sections describe problems that were resolved for WebLogic Server 6.1.
Deployment Descriptor Editor
Web Services
![]() |
![]() |
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|