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

Notes and Problems

The following sections describe levels of support and general problems in this release:

- Service Pack Information

- Certifications

- Standards Support

- Deprecated Features

- Applets

- HTML Pages and Netscape

- Java Development Kit

- Clusters, DNS, and Multihoming on NT

- WebLogic Tuxedo Connector

- WebLogic Tuxedo Connector

- Known Problems

Service Pack Information

BEA will release WebLogic Server 6.1 with Service Pack 4 in mid-November 2002. Service Pack 4 includes many new improvements and fixes to the original 6.1 release. It also includes the fixes that were made in Service Pack 1, Service Pack 2 and Service Pack 3.

For a list of issues fixed in Service Pack 4, see Resolved Problems. For a list of open issues still found in WebLogic 6.1 with Service Pack 4, see Known Problems in Notes and Problems.

The following sections detail notes on the Service Packs released for WebLogic Server 6.1. These are neither bug fixes or known issues but contain important information. If you are upgrading to a service pack you should read these carefully.

Service Pack 4

The following are important notes for WebLogic Server 6.1 Service Pack 4:

JDBC

With the release of WebLogic Server 6.1 Service Pack 4, BEA certified the Oracle 9.2.0 Thin Driver for use with WebLogic Server. The software distribution for Service Pack 4 includes the following new JDBC drivers:

- WebLogic jDriver for Oracle 9.2.0, in addition to versions for Oracle 8.1.7 and 9.0.1.

- Oracle 9.2.0 Thin Driver, which replaces the 8.1.7 version that shipped with previous releases of WebLogic Server 6.1.

For more information about using WebLogic jDriver for Oracle, see Installing and Using WebLogic jDriver for Oracle. For more information about using the Oracle Thin Driver with WebLogic Server, see Using Third-Party Drivers with WebLogic Server.

In the Oracle Thin Driver version 9.2.0, Oracle removed some extension methods that were previously available in the driver. These methods are no longer supported and were removed from WebLogic Server in Service Pack 4:

Class:

weblogic.jdbc.oracle.OracleConnection

Method:

isCompatibleTo816()

Class:

weblogic.jdbc.oracle.OracleStatement

Method:

getWaitOption()
setWaitOption(int i)
setAutoRollback(int i)
getAutoRollback()

Class:

weblogic.jdbc.oracle.OracleResultSet

Method:

getCURSOR(String s)

Service Pack 3

The following are important notes for WebLogic Server 6.1 Service Pack 3:

ACLs

In WebLogic Server 6.1 Service Pack 3, an error in the implementation of ACLs for JDBC was fixed, which makes ACLs very strict. If you define an ACL for connection pools, access is restricted to exactly what is defined in the ACL. For more information, see Permissions at ../jdbc/programming.html#programming006.

WebLogic jDriver for Oracle Version Support Changes

The following list details recent changes to supported versions of Oracle used with WebLogic jDriver for Oracle:

- As of the release of WebLogic Server 6.1 Service Pack 3, BEA no longer supports WebLogic jDriver for Oracle with Oracle 8.1.6. If you are using WebLogic jDriver for Oracle to connect to an Oracle 8.1.6 database, you must upgrade to Oracle version 8.1.7 or 9.0.1, which includes the following steps on the machines on which WebLogic Server is running:

  - Upgrade the Oracle client installation to the 8.1.7 or 9.0.1 version.

  - Update the ORACLE_HOME environment variable to point to the updated version of the Oracle client.

  - Modify your PATH (on Windows, varies on UNIX) to include the path to the new Oracle client and to the appropriate version of the WebLogic jDriver for Oracle.

    For more information, see Setting Up the Environment for Using WebLogic jDriver for Oracle in Installing and Using WebLogic jDriver for Oracle.

Oracle 9.0.1 Thin Driver Certification

For the release of WebLogic Server 6.1 Service Pack 3, BEA certified the Oracle 9.0.1 Thin Driver for use with WebLogic Server. For more information about using the Oracle Thin Driver with WebLogic Server, see Using Third-Party Drivers with WebLogic Server.

JMS

WebLogic Server 6.1 Service Pack 3 includes the WebLogic Messaging Bridge.

A messaging bridge is responsible for transferring messages between two messaging providers. The WebLogic Messaging Bridge allows you to configure a store-and-forward mechanism between any two messaging products—including separate implementations of WebLogic JMS.

For more information, see Using the WebLogic Messaging Bridge in the Administration Guide.

WebLogic Server 6.1 Service Pack 2 includes a new JMS message paging feature.

The WebLogic JMS Message Paging feature can free up valuable virtual memory during peak message load periods by swapping out messages from virtual memory to persistent storage when message loads reach a specified threshold. From a performance perspective, this feature can greatly benefit WebLogic Server implementations with the large message spaces that are required by today's enterprise applications.

Two metrics are used to determine when to start and stop paging: bytes paging and messages paging. Each metric is the basis of a single paging mode, which you can enable and disable individually, or use simultaneously, on JMS servers and/or destinations (topics and queues).

Paging is configured through the Administration Console. Using the paging attributes on the JMS Server node, you can specify a paging store for the server, enable bytes and/or messages paging, and configure the bytes/messages high and low thresholds to start and stop paging. Similarly, using the paging attributes on the Destinations node, you can configure bytes/messages paging for all topics and queues configured for the JMS server. The destinations use the paging store that is configured for the JMS server. Also, if you use JMS templates to configure multiple destinations, you can use the paging attributes on the Templates node to quickly configure message paging on all your destinations.

For detailed instructions on configuring message paging, see the section called "Tuning JMS" in the WebLogic Server Administration Guide.

Service Pack 2

The following are important notes for WebLogic Server 6.1 Service Pack 2:

Compatibility Issues

Weblogic Server 6.1 Service Pack 2 introduced two compatibility issues, which are explained in this section.

Mandatory Start Script Switch for WebLogic Server 6.1 Service Pack 2 Clients

By default, a WebLogic Server 6.1 Service Pack 2 client does not interoperate with a WebLogic Server 6.1 GA or 6.1 Service Pack 1 server. This is true both for a 6.1 SP2 client and a 6.1 SP2 server acting as a client to a 6.1 GA or 6.1 SP1 server.

To allow an SP2 client to talk to a 6.1 GA or 6.1 SP1 server, add the following switch to the WebLogic Server 6.1 Service Pack 2 start script:

-Dweblogic.61compat=true

Fix to SAX Parser May Result in Detection of Encoding Errors

Service Pack 2 fixes WebLogic Server's built-in SAX parser such that it now correctly parses deployment descriptor files that are written using any character set.

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 contained encoding problems and 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.

Certifications

- WebLogic Server 6.1 Service Pack 2 is certified with Sun's J2SE 1.3.1_01.

- WebLogic Server 6.1 Service Pack 2 is certified with HP JVM 1.3.1_01. For information on the patches required by HP JVM 1.3.1_01, see the following website:

http://www.hp.com/products1/unix/java/infolibrary/patches.html

- With the release of WebLogic Server 6.1 Service Pack 2, BEA supports WebLogic jDriver for Oracle for use with Oracle 9i. You can now use the JDBC driver to connect to an Oracle 9i database. For more information about WebLogic jDriver for Oracle, see Installing and Using WebLogic jDriver for Oracle.

For the most accurate and current information regarding platform support, see the Platforms Support Page.

HttpClusterServlet and HttpProxyServlet Updated to Support HTTP 1.1

Service Pack 2 includes new versions of the HttpClusterServlet and the HttpProxyServlet that support the HTTP 1.1 protocol. In addition, these servlets now use the same configuration parameters as the Apache, Netscape, and Microsoft IIS plug-ins.

For more information see the following documents:

- Proxying Requests to Another HTTP Server.

- Proxying Requests to a WebLogic Cluster.

- Parameters for Web Server Plug-ins.

Security

Weblogic Server Service Pack 2 includes two new classes related to security:

- weblogic.security.SSL.TrustManager allows you to override validation errors in a peer's digital certificate and continue the SSL handshake. You can also use the class to discontinue an SSL handshake by performing additional validation on a server's digital certificate chain. For more information, see the section called "Using a Trust Manager" in "Programming with the WebLogic Security SPI".

- SSLContext is used to implement a secure socket protocol that holds information such as Host Name Verifier and Trust Manager for a given set of SSL connections. For more information, see the section called "Using an SSL Context" in "Programming with the WebLogic Security SPI".

In addition, Service Pack 2 adds parameters for SSL session caching that eliminate the need for the connection to go through the SSL handshake again. For more information, see the section called "Modifying Parameters for SSL Caching" in "Managing Security".

Servlets and JSPs: Default Encoding

As of Weblogic Server 6.1 Service Pack 2, the default encoding used for servlets and JSPs has been changed to ISO8859_1. Previously the default encoding used was the JVM default. 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.

BEA recommends you explicitly set the encoding of the request and response objects in order to avoid any encoding problems. For further details on how to set encoding, point your browser to http://edocs.beasys.co.jp/e-docs/wls61/jconfig/wls61jconfig.html.

WebLogic 6.1 and 5.1 Interoperability

As of WebLogic Server 6.1 Service Pack 2, it is possible to bi-directionally interoperate with WebLogic 5.1 Servers. This allows a WebLogic 6.1 Server to remotely invoke EJBs or RMI objects hosted on a WebLogic 5.1 Server. It also allows the reverse-a WebLogic 5.1 Server can remotely invoke EJBs or RMI objects hosted on a WebLogic 6.1 Server. For further details, see the Interoperability Guide.

Certifications

See the Certifications Page for the most accurate and current information regarding platform support.

Standards Support

Standard | Version
--- | ---
HTTP | 1.1
J2EE Connector Architecture | 1.0
J2EE EJB | 2.0
J2EE JDBC | 2.0
J2EE JNDI | 1.2
J2EE JSP | 1.1
J2EE JTA | 1.0.1
J2EE JMS | 1.0.2
J2EE RMI | 1.0
RMI/IIOP | 1.0
J2EE Servlet | 2.2
LDAP | 2
SSL | 3
X.509 | 3

Deprecated Features

The following features are deprecated in WebLogic Server 6.1 and will not be supported in the future:

- weblogic.db.jdbc.EventfulTableDataSet

- WebLogic WorkSpaces

- WebLogic Events

- WebLogic Time

- WebLogic JDBC t3 driver

- ZAC

Applets

A problem with the tools.jar shipped with the JDK prevents Applets from being served to the client correctly. If tools.jar is located in your server CLASSPATH, you must ensure that weblogic.jar appears in the server CLASSPATH before tools.jar.

HTML Pages and Netscape

If you already have a Netscape browser running when you start WebLogic Server, some HTML pages will not display. For example, if you select the About WebLogic Server page from the Start menu, and you have Netscape running and do not have Microsoft Internet Explorer, the screen may flash but the page will not display.

Java Development Kit

A JDK provides a Java runtime environment (the Java Virtual Machine or JVM) and tools for compiling and debugging your Java applications. Your installation of WebLogic Server 6.1 includes the 1.3.1rc2 JDK from Sun Microsystems.

Clusters, DNS, and Multihoming on NT

Be aware of naming issues when using multihoming features on Windows NT in a cluster. For example, there may be naming conflicts if a cluster is running on a multihomed Windows NT machine and one of the servers in the cluster is bound to the same DNS name as the machine name. Attempts to contact that server using the DNS name in a URL may result in Windows NT converting that DNS name to any of the IP addresses of the multihomed Windows NT machine. In this case, the request may go to the wrong address. Avoid having DNS names that match your machine name.

WebLogic Tuxedo Connector

In WebLogic Server Release 6.1, the WebLogic Tuxedo Connector has the following limitations:

- Does not support dynamic configuration changes to WebLogic Tuxedo Connector gateway

- Does not support View buffers.

- Does not support in-bound RMI/IIOP transactions from a Tuxedo application..

- Does not support clustering. Only one instance of WebLogic Tuxedo Connector can be used in a clustered environment.

- Does not support Tuxedo 6.5 running on VMS, AS/400, and OS/390 platforms.

Known Problems

The following sections describe known problems with this software release. BEA is addressing these problems.

- Console Known Problems

- EJB Known Problems

- Examples and Pet Store Demo Known Problems

- Installer Known Problems

- JCA Known Problems

- JDBC and jDrivers Known Problems

- JMS Known Problems

- JSP Known Problems

- Security Known Problems

- Server Known Problems

- Servlet and Web Application Known Problems

- System Administration Known Problems

- Tools Known Problems

- Web Services Known Problems

- WebLogic Tuxedo Connector Known Problems

- XML Known Problems

- ZAC Known Problems

Console Known Problems

Change Request Number | Description
--- | ---
053277 | If you use Netscape to bring up the Administration Console and try to edit a template for an LDAP Realm configuration, using the arrows or the bottom scroll bar to go left or right in the Configuration Data window causes the displayed data to look garbled. If you click the Apply button, no corrupt data is saved in config.xml, but it is difficult to edit the template.

EJB Known Problems

Change Request Number | Description
--- | ---
035884 | The maximum number of Enterprise JavaBeans (EJBs) that can be deployed on one WebLogic Server instance is 390. This is due to a Sun bug and is a limitation caused by the 1.3 JDK; it may be fixed by the 1.3.1 release of the JDK. The Sun Bug ID is: 4390238.
051543 | If you try to deploy a completely incorrect EJB, the EJB container throws an exception from its deploy method. However, if you click on that EJB in the console, it still has the Deployed box checked.
062927 | Requesting an EJB served by WLE 5.1 from a JSP served by WLS 6.1 may give the following exception: java.lang.NoClassDefFoundError Add the location of the WLE 5.1 wlej2eecl.jar file to the CLASSPATH of your WLS 6.1 startWeblogic.cmd or startWeblogic.sh script.
079539 | WebLogic Server 6.1 sp3 is not compatible with Application Integration in WLI 2.1 sp1. Please contact BEA Customer Support for more information.

Examples and Pet Store Demo Known Problems

Change Request Number | Description
--- | ---
043156 | The ejbmanagedclient.jsp relies on a variable that is set to t3://localhost:7001 and does not get the port number dynamically. Thus, when the page is requested, it cannot find the server. The exception is thrown, although the stack trace is not printed out. The page shows up as: --------------UnexpectedError-------------- Customers running this example on a different port then 7001, will need to edit the jsp file. The variable you must edit is in this section: <!-- Here, we declare a class method --> <%! String pagetitle = "JSP example using EJBean-managed persistence"; String url = "t3://localhost:7001"; Edit the URL to point to the correct server/port number that has been installed.
044641 | There is some missing information in examples/ejb/sequence/userDesignated/package-summary.html. Make sure that you use the table.ddl file, included in the example's package, as the source for the table that needs to be built for this example. Also, make sure that table is named "NAMED_SEQUENCE_TABLE" not "NAMED_SEQUENCE-TABLE".
047654 | In the dbKona examples, a pool connection cannot be made and an error is thrown when trying to boot the example server.
047928 | When running the Web Application security example, there is no link in the console for creating a group and adding members to it. Also, on the group window, clicking on Name or Members causes a 500 Internal Server Error.
048358 | The security/rdbmsrealm/rdbmsrealm.ddl and utils/ddl/demo.ddl examples have problems with improper comment symbols.
052556 | The WebLogic Tuxedo Connector CORBA simpappcns example fails when run in the examples domain after running the WLEC examples. The problem is a conflict with the Simpapp client stubs left in the SERVER_CLASSES directory from the WLEC examples. Before running the simpappcns example, check the SERVER_CLASSES environment variable. If the WLEC examples have been run, delete all simpapp client stubs from SERVER_CLASSES.
053356 | The example samples/examples/wtc/corba/simpappcns does not have a run.sh UNIX script and will not work on UNIX machines.
062545 | WebLogic Server domain running Solaris simpappcns can't call Tuxedo Corba Server domain running on NT.
062799 | The documentation for three of the WIRELESS examples contains an error in Step 7 of the instructions. The examples in question are helloWorld, stockDemo and travelDemo. Step 7 should read: Path=./config/examples/helloWorld rather than: Path=./config/examples If uncorrected, the examples will not find the deployed applications.
064001 | examples.webservices.message.package-summary.html contains an incorrect instruction. Step 13 says "Right-click the Destinations node and choose Configure a new <JMSTopic>" from the drop-down list." JMSTopic should read JMSQueue.
078441 | Some examples fail when a data source is re-targeted. If, after re-targeting a data source, an example fails with the error message, "Cannot obtain connection after X seconds", make sure to restart the examples server in order for the change to take effect.

Installer Known Problems

Change Request Number | Description
--- | ---
039773 | The following misleading error message occurs when there is not enough space in /temp to run the installer: Preparing to install... The included VM could not be extracted. Please try to download the installer again and make sure that you download using 'binary' mode. Please do not attempt to install this currently downloaded copy. By default the installer tries to unpack all the installer files in the /temp directory. If there isn't enough temporary space there, you cannot install and you get this message. Make room in the /temp directory for the installer files.
040353 | Installation problems can occur on HP-UX and Solaris machines because shared libraries do not have execute permission. File permission changes made by the WebLogic Server installer are reverted by installer imposed standard attributes. A workaround is to issue the chmod +x command on all the shared library objects (under lib/hpux11 and lib/solaris).
043357 | If you are getting the following error on Solaris 2.6 or 2.7 UNIX systems: UnsatisfiedLinkError in AWT applications (libmawt.so: open failed: No such file for directory). The policytool will not open. The Java Plug-in Control Panel will not open. Usually you might workaround this problem by modifying the LD_LIBRARY_PATH. For example: setenv LD_LIBRARY_PATH /usr/j2se/jre/lib/i386/motif12:$LD_LIBRARY_PATH But, in some cases with problems with the libmawt.so files, you may require a patch from Sun: see http://java.sun.com/j2se/1.3/install-solaris-patches.html for Sun's patch information.
053469 & 055598 | When using the Administration Console, add the line, acl.modify.weblogic.admin=Administrators, to the filerealm.properties to grant permissions to users and/or groups. This ACL was in WebLogic Server 6.0, 6.0 Service Pack 1 and 6.0 Service Pack 2.
054058 | When encountering an unsupported browser, beaexec.exe may result in WebLogic Server crashing.

JCA Known Problems

Change Request Number | Description
--- | ---
049344 | The current BEA WebLogic J2EE Connector architecture implementation does not provide the ability to detect the errors discussed in section 6.8 (Scenarios: Local Transaction Management) of the J2EE Connector Specification, Version 1.0, Proposed Final Draft 2.

JDBC and jDrivers Known Problems

Change Request Number | Description
--- | ---
033423 | dbKona problems exist with QueryDataSet and the OCI805_8 driver. The problems are fixed on Windows NT, but this is still a problem on HPUX and Solaris.
035301 | There are problems using the RMI driver with Sybase connection pools.
035530 | Problems with enabling OS authentication and using Oracle 8.1.6/oci8 with the jDriver are fixed on NT and HP-UX, but are still an issue on Solaris. An error message that reports this problem: OS level authentication is not currently supported due to a defect in OCI 8 libraries.
040413 | Cluster hanging problems have been observed in some instances on Solaris machines. This appears to be caused by a libthread deadlock between SIGALRM and SIGLWP. The deadlock manifests itself when the server is attempting a JDBC connection. To help avoid the problem, use the Administration Console to set the InitialCapacity attribute equal to the MaxCapacity attribute in the JDBCConnectionPool entry. A similar problem was previously logged as a Sun Microsystems Bug (ID 4141709 libthread deadlock between SIGALRM and SIGLWP), against Solaris 2.6. There is currently no mention of the problem for Solaris 2.7. For Solaris 2.6, the patch for this problem is 105569-16.
043224 | Oracle supports of its own class of Array (oracle.sql.Array) through its ThinDriver. If you attempt to use these classes in an application that gets its connection using WebLogic Server JDBC, they will not work.
048219 | Flush doesn't seem to "commit" with RMI Clob character write. This only seems to affect flushing when you are using these write methods: write(char[] cbuf) write(char[] cbuf, int off, int len) write(String str) write(String str, int off, int len) It works fine with: write(int c) No problems with flushing occur when using an Ascii Stream with a Clob. Also, to commit your write, you have to explicitly close the stream. This may only be a problem if you wanted to read back from the Clob before you were ready to close out your write stream.
049519 | Due to a bug in Oracle's thin driver, the following method is not compliant with the java.sql.PreparedStatement API: PreparedStatement.setTimeStamp(int param index, Timestamp x, Calendar cal) The timestamp value is not adjusted according to the TimeZone specified in the Calendar object. The default TimeZone is always used. Oracle may fix this bug in future releases of the thin driver.
078936 | If you have the HP-UX UNIX patch, PHSS_24627, installed, an HP Server Bus error occurs when WebLogic Server 6.1 Service Pack 2 accesses Oracle upon start-up. With the newer aCC libraries version A.03.33, using the -AA CXXFlag, the user gets a java.lang.UnsatisfiedLinkError while accessing Oracle upon WebLogic Server start-up. Contact HP for a solution to this problem.

JMS Known Problems

Change Request Number | Description
--- | ---
037683 | The JMS Topic configuration tab in the console accepts any alphabetic characters as valid values for a Multicast Address. It should validate the value that is entered against an Internet Address format.
049229 | You may experience problems with JMS if you run the server with the unsupported JDK 1.3.0. This problem occurs when restarting the server when there are existing messages in the JMS store -- these messages are ignored. It is recommended that you use the 1.3.1 JDK that is bundled with the server.
083538 | In a multi-server configuration, an application or EJB on one server cannot lookup and get a connection from a TxDataSource on another server. The application or EJB must use a TxDataSource on the same server. This is a system limitation.

JSP Known Problems

Change Request Number | Description
--- | ---
049854 | The ejb2 JSP tool does not support EJB 2.0 local interfaces.

Security Known Problems

####

Change Request Number | Description
--- | ---
048159 | When a Log Audit Provider is being used, no messages are being sent to the WebLogic Log File notifying you that auditing is turned on.
051215 | When entering the system password during startup for WebLogic Server, if you use a CTRL/C sequence to interrupt the WebLogic Server startup, the terminal window stays in no-echo mode and characters that are typed are not echoed. If possible, wait to interrupt the WebLogic Server startup until after you enter the system password. If you do use a CTRL/C sequence when entering the system password, reset the terminal window or close the terminal window and start another window.
051315 | The Node Manager in WebLogic Server cannot process the private keys created by the Certificate Request Generator servlet. The wlkeytool converter tool has been provided to solve this problem. Use the wlkeytool converter tools as follows: wlkeytool inputkey.pem outputkey.pem where inputkey.pem is the name of the private key created by the Certificate Request Generator servlet. outputkey.pem is the name of the converted private key. If the private key is password protected (that is, if you specified a password in the Private Key Password field in the Certificate Request Generator servlet), the wlkeytool converter tool prompts you for the password. If the private key is unprotected, press Enter. The wlkeytool converter tool prompts you for a password for the converted private key. A password must be supplied, or the wlkeytool converter tool will not create an unprotected private key. A deployed WebLogic Server does not support the converted private key created by the wlkeytool converter tool, so you should retain the private key created by the Certificate Request Generator servlet and use it with your deployed WebLogic Servers.
053390 | If you are using an RDBMSRealm with a Caching Realm enabled, and the DatabasePassword is not specified in the RDBMSRealm tag in the config.xml file, the server halts with the error "<wlsstartuperror1>" and does not startup. Workaround: Open the config.xml file and add the DatabasePassword in clear text to the RDBMSRealm tag.
053409 | To use the Java Security Manager with WebLogic Server, specify the -Djava.security.manager property when starting WebLogic Server. The included startup scripts specify a policy file but no security manager. Therefore the policy file ends up getting ignored. You must set a security manager for the policy file to become effective.
078619 | Group Membership caching is not using the value set in GroupMembershipCacheTTL. It is instead using the value set in GroupCacheTTLPositive.
078894 | When FlatGroup.clearCache() is invoked to refresh the cache, and isMember is invoked for a second time, isMember is returning false. It is still using old cache data.

Server Known Problems

Change Request Number | Description
--- | ---
039575 | If your servlet makes an HTTP connection back to the same server there is the possibility of deadlock under load. To work around the problem, use a separate execute queue for the servlet that returns the DTD.
042556 | The weblogic.Admin command now requires the user and password options. For example: java weblogic.Admin -username system -password gumby1234 The username "system" is required for most functions (for example: VERSION). If you do not specify -username system, you will get the following error: Exception in thread "main" java.lang.SecurityException: Authentication for user system denied in realm weblogic <<no stack trace available>>
051980 | When using the 1.3 VM with HotSpot, doing a thread dump causes the JVM to exit and the server to crash.
052300 | Using Call-by-Reference doesn't work when you deploy your application as an .ear file that is not located in the applications directory and if you have set ServletReloadCheckSecs is set to -1.
052406 | Attempting to start Managed Servers in quick succession creates problems. A delay between starting them fixes the problem.
052543 | When passing complex objects server to server using RMI-IIOP, there will be many problems using com.sun.jndi.cosnaming.CNCtxFactory when getting an initial context; it is recommended to use weblogic.jndi.WLInitialContextFactory instead.
053328 | If you are having problems with out of memory errors while using HP, try increasing the kernel parameter called max_thread_proc to 1024.
053330 | The SNMP agent uses an object identifier (OID) for WebLogic in communicating with SNMP management systems. The WebLogic OID for 6.1 is different than the WebLogic OID for 5.1. In 5.1 it was .1.3.6.1.4.140.600, but in 6.1 it is .1.3.6.1.4.140.625.
054504 | We have encountered problems on Windows 2000 and NT when using the -hotspot option with the JVM. This is due to a Sun bug (http://developer.java.sun.com/developer/bugParade/bugs/4479571.html) and results in intermittent crashes of the server. To work around this problem, try setting: -XX:MaxPermSize=128m This option allows you to increase the size of the area HotSpot uses for class representations.
057008 | The NTSocketMuxer getCPUCount() is returning an incorrect value. A Service Pack from Microsoft that is installed does not recognize all of the CPUs.
058868 | Due to a HotSpot virtual machine error, a signal 11 may unexpectedly crash WebLogic Server running on Solaris.
059018, 063937, 063939, 063965 | By default, a WebLogic Server 6.1 Service Pack 2 client does not interoperate with a WebLogic Server 6.1 GA or 6.1 Service Pack 1 server. This is true both for a 6.1 SP2 client and a 6.1 SP2 server acting as a client to a 6.1 GA or 6.1 SP1 server. To allow an SP2 client to talk to a 6.1 GA or 6.1 SP1 server, add the following switch to the WebLogic Server 6.1 Service Pack 2 start script: -Dweblogic.61compat=true
065410 | Due to a Sun bug, a java lang.OutOfMemory error my occur when starting WebLogic Server if the number of classes being loaded is too high. As a workaround, increase the value of the JVM option -XXMaxPermSize when initializing WebLogic Server, using this syntax: java -XX:MaxPermSize=<value>K where <value> is some number of kilobytes. The JVM uses a default maximum value of 32 MB. This problem has been reported to Sun.
078289 | When a browser using Java Plug-in 1.3.1_02 or 1.3.1_03 refreshes a page with applets, the JVM issues simultaneous destroy() and init() calls to the applets. Because the calls are at the same time, applets may not properly close before trying to initialize. As a workaround, use thread.sleep() in the init() method of your applets to delay initialization by approximately 1000 milliseconds. The delay ensures that the destroy() call finishes any required cleanup before the applet attempts to reinitialize.

Servlet and Web Application Known Problems

Change Request Number | Description
--- | ---
041528 | Cookies generated by the first release of WebLogic Server 6.0 with no Service Pack applied are not recognized by WebLogic Server 6.1.
046536 | HTTPS does not work with Virtual Hosting.
046537 | Virtual Hosts should define their own security realms.
048678 | Previously, to log out a user from a Web Application you could use session.invalidate(). This now only works if the user has been to just one Web Application. If more than one Web Application is visited, session.invalidate() will not log out the user. This is not a known issue; rather it is a design change due to the implementation of Single-Signon. The server tracks the user at the Web server level and not the Web Application level--this behavior is mandated by the Servlet 2.2 specification. If you wish to log out users who have been to more than one Web Application, use: weblogic.servlet.security.ServletAuthentication.logout(request);
050811 | If you modify a filter class, you must redeploy the Web Application to apply the change.
051311 | You cannot not put white space in the name (context path) of a Web Application.
051329 | The following issue is merely informational and will not be fixed or changed because it is the desired functionality. In the WebLogic Server config.xml file, the Path attribute of an archived Web application should consist only of the path to the archive file, but not the archive file name itself. In contrast, the URI attribute of a Web Application Component should consist only of the archive file name. For example: <Application Name=foo, Path=/apps> <WebAppComponent Name=foo,URI=foo.war> </Application> For backward compatibility, WebLogic Server 6.1 accepts a config.xml that specifies both the path and the archive filename of an application in the Path attribute (for example, Path=/apps/foo.war). However, the XML file is overwritten to specify only the path (/apps).
052686 | The Web Application Deployment Descriptor Editor shipped with WebLogic Server 6.1 supports Public Final Draft 1 of the Servlet 2.3 specification. Because of this, there is no means within the editor for configuring the <ejb-local-ref> element of web.xml, which was introduced in Public Final Draft 2. Further, the editor will remove any <ejb-local-ref> that may be present in an existing Web App deployment descriptor.

System Administration Known Problems

Change Request Number | Description
--- | ---
034177 | The Administration Console does not set the correct attribute value for application status.
034955 | The application directory list used to scan for deployments is not persistent. Multiple application directories are not supported.
035670 | When you reset an MBean name, the configuration is not saved correctly. To work around this problem: In the Administration Console, clone the MBean. Rename the clone. Delete the original MBean.
036201 | Occasionally, after making modifications in the Administration Console, WebLogic Server cannot be restarted and a Fatal initialization exception Throwable: weblogic.server.ServiceFailureException: Initializing JNDI: javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'Protocol: 'unknown''] message is displayed.
038589 | If Managed Server(s) are communicating through HTTPS with the Administrative Server, the discovery of Managed Servers does not work. For example, if the Administrative Server is restarted with the -Dweblogic.management.discover=true command line argument and the running managed servers were booted with the -Dweblogic.admin.host=https://<adminhost>:<adminport> argument, then the discovery of managed servers does not work. Workaround: When Managed Servers are booted with an HTTPS connection to the Administrative Server, do not restart the Administrative Server with the -Dweblogic.management.discover=true argument. Instead, do the following: 1. Restart the Administrative server without the discover flag. 2. Once the Administrative Server is booted, force discovery by the Admin Server by running the following command: java weblogic.Admin -url <ADMINHOST>:<ADMINPORT> -username system -password <SYSTEM-PASSWORD> INVOKE -mbean "<YOURDOMAIN>:Type=Domain,Name=<YOURDOMAIN>" -method discoverManagedServers
039033 | WebLogic Server complains of an error undeploying an application that does not exist.
039311 | When you start a managed server that has been cloned, it throws a ConfigurationException. The workaround is to create a server instead of cloning it.
039532 | An .ear file can only be undeployed using the Administration Console once it has been exploded under the applications directory. Also, once the application is undeployed, the only way it can be redeployed is through the Administration Console.
040034 | Attempting to start a server as a Managed Server when it is already running as an Administration Server results in the following misleading error: <Dec 8, 2000 7:44:02 PM PST> <Error> <Configuration Management> <Error connecting to admin server and initializing admin home: admin URL: t3://localhost:7001 java.lang.NullPointerException Workaround: This is incorrect usage. The same server cannot be started as an Administration Server and a Managed Server. Define a new server for your Managed Server, and specify its name in -Dweblogic.Name during startup.
040124 | While the Administration Server is running, copying an existing .jar or .ear file to an applications directory does not redeploy the application. The following error is displayed in the server log: javax.naming.NameAlreadyBoundException: Can't rebind anything but a replica-aware stub to a name that is currently bound to a replica-aware stub; remaining name '' <Dec 12, 2000 12:09:37 PM PST> <Error> <J2EE> <Error deploying application <YOUR-EJB-NAME>: Could not deploy: '<YOUR-FILE-NAME>': JNDI name in use Make sure that either the guest user or the everyone group is granted lookup permission to weblogic.jndi. The fileRealm.properties file should contain the following: acl.lookup.weblogic.jndi=everyone
041290 | If the username property is set from the weblogic.Admin or weblogic.Server command lines, the username must be "system". Note however, that the username syntax is retained to prevent breaking a user's scripts. The username may not be modified in the config.xml file. The weblogic.management.password property value must be the system password.
042232, 055217 | It is no longer possible to have a domain with the same name as its Administration Server. This will not be fixed, as the namespace conflicts produces too many problems.
048833 | The ServletRuntime mbean contains the method getName(). In previous releases, this method returned the name of the servlet. For all other mbeans, the getName() method returns the name of the mbean. For consistency, in WLS 6.1 the getName() method on the ServletRuntime mbean has been modified to return the name of the mbean. A new method, getServletName(), has been added to the ServletRuntime mbean to return the name of the servlet.
052657 | If you set configuration attributes for an application in config.xml, yet the application does not really exist, you will see the application incorrectly displayed as deployed in the Administration Console.
077958 | When using NodeManager, the following exception may be thrown: <May 18, 2002 8:53:36 PM PDT> <Error> <NodeManager@localhost:5555> <SocketInputHandler: handshake failed 'FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable to negotiate an acceptable set of security parameters.' on socket /172.17.24.148> This exception could be due to one of the following: The JVM version being used to run NodeManager is not supported by WebLogic Server. A JSEE conflict if NodeManager is running on the AIX platform. If NodeManger is running on the AIX platform, see Weblogic AIX Platform Support in Platforms for more information.

Tools Known Problems

Change Request Number | Description
--- | ---
063745 | The documentation on the weblogic.refresh tool states that you can specify files using wildcards (e.g. "*.gif") and that you can use a comma-separated list to specify multiple files. However, in WebLogic Server Service Pack 2, weblogic.refresh does not allow the use of wildcards in comma-separated lists.

Web Services Known Problems

Change Request Number | Description
--- | ---
046807 | The exception messages generated by the Java client application in the Java client JAR file are not internationalized.
047435 | In RPC-style Web services, user-defined exceptions thrown by the EJB are not propagated to the client applications that use the Web services client API to invoke the service. Instead, they are propagated as generic SOAPFault exceptions.
> 049966 | If you use the WebLogic Server Web Service client API (version 6.1) in a WebLogic Server 6.0 component, such as an EJB, you get the error java.rmi.ConnectException: No available router to destination. This is because a 6.0 JNDI URL factory gets called rather than the initial context factory that you specify in your client code. To work around this problem, get rid of the 6.0 JNDI URL factories by adding the following code snippet when you make your initial context:
>     h.put(Context.URL_PKG_PREFIXES, "");
051917 | In message-style Web services, JMS exceptions that occur on the target JMS destination are not propagated to the client applications that use the Web services client API to invoke the service.
055062 | The path attribute of the clientjar element of the wsgen Ant task does not, as documented, default to client.jar if the path attribute is not specified in the build.xml file.
055096 | You cannot pass a JavaBean that has no package name as a parameter to a WebLogic Web service.
055596 | Interoperability issue. WebLogic Web services do not support SOAP 1.1 multi-reference compound data types.
056287 | Interoperability issue. WebLogic Web services do not support the xsd:timeInstant and xsd:dateTime in the SOAP encoding.
056452 | Interoperability issue. WebLogic Web services do not support multi-dimensional array data types.
056634 | Interoperability issue. WebLogic Web services do not support SOAP-ENV:Header attributes.
058175 | Interoperability issue. WebLogic Web services do not support xsd:ur-type array data types.
058840 | Interoperability issue. The WebLogic Web service client API cannot bind to a WSDL that specifies more than one return type.
059782 | Interoperability issue. The WebLogic Web service client API does not support invoking a Web service whose WSDL contains a <soap:header> element in its <binding> section.
> 059858 | Interoperability issue. WebLogic Web services use only the 1999 XML Schema URL in the generated SOAP request, as shown in the following SOAP request snippet:
>     xmlns:xsi='http://www.w3.org/1999/XMLSchema-instance'
>     xmlns:xsd='http://www.w3.org/1999/XMLSchema'
061161 | Interoperability issue. The WebLogic Web services client API does not support the use="literal" attribute of the <soap:body> element.
061335 | Interoperability issue. The WebLogic Web services client API does not support invoking a Web service whose WSDL contains a <part> element with an element attribute inside of a <message> element.
061350 | Interoperability issue. By default, the WebLogic Web services client API generates SOAP requests with qualified names. This does not interoperate well with some other non-WLS Web services, such as .NET. The workaround to this problem is to add the following code to your client application: CodecFactory factory = CodecFactory.newInstance(); SoapEncodingCodec codec = new SoapEncodingCodec(); codec.writeQualifiedName( false ); factory.register( codec );
061572 | Interoperability issue. The WebLogic Web services client API does not support the style="document" attribute of the <soap:binding> element of WSDL.
061606 | When assembling a message-style Web service using the wsgen Ant task, the task adds a literal encoding to the generated WSDL. This forces a programmer invoking the Web service to register the LiteralCodec with the CodecFactory, even when it is not required. The LiteralCodec forces the programmer to have the weblogic.jar file on the client computer.
061929 | Interoperability issue. The WebLogic Web services client API always uses qualified names in its generated SOAP requests, even if the client application includes the following code: codec.writeQualifiedName( false );
77911 | WebLogic Server correctly maps the built-in Java data type byte[] to xsd:hexBinary. However, the JAX-RPC specification states that byte[] should also have a mapping to xsd:base64Binary. Currently, there is no way to specify this mapping using Version 6.1sp3 of WebLogic Web services.
78062 | WebLogic Web services cannot interoperate with .NET Web services that use arrays and JavaBeans as parameters or return values.
78530 | The Web Service examples do not build on the Solaris operating system.

WebLogic Tuxedo Connector Known Problems

Change Request Number | Description
--- | ---
052737 | A misconfigured node name in the WebLogic Tuxedo Connector XML configuration file will cause the system to hang. Use the following step to restart your system: 1. Shut down WebLogic Server. 2. Verify your node names in your WebLogic Tuxedo Connector XML configuration file. 3. Update the WebLogic Tuxedo Connector XML configuration file with valid node names. 4. Restart WebLogic Server.
077553 | Integer array object passed by value from Tuxedo to WebLogic Server throws weblogic.utils.AssertionError.

XML Known Problems

Change Request Number | Description
--- | ---
050274 | When you use the Administration Console to add either a parser or entity XML Registry entry, and you do not specify a public ID, you cannot subsequently navigate to the entry to edit it. The workaround is to always enter a value in the public ID field when you create an XML registry entry.
052985 | The built-in Xalan transformer package weblogic.apache.xalan does not include the Xalan compatibility API. These classes are included in the xalanj1compat.jar file if you were to download Xalan 2.0.1 directly from the Apache Web site. For more information on the compatibility API, see http://xml.apache.org/xalan-j/usagepatterns.html#compat. Because these classes are not included in WebLogic Server, if your application uses code from Xalan 1.X that has been deprecated in Xalan 2.0.1, your application will not work correctly. Modify your code so that it does not use the Xalan 1.x deprecated classes, or rewrite your Xalan code to use JAXP instead.

ZAC Known Problems

Change Request Number | Description
--- | ---
061699 | WebLogic Server does not automatically register a default web application. Because ZAC gets classes through the default web application, users of ZAC must now explicitly configure a default web application. If you fail to explicitly configure a default web application, ZAC will not function, and the server log will contain a message similar to the following: <Nov 2, 2001 2:50:49 PM PST> <Error> <HTTP> <HttpServer(7908535,null default ctx,myserver) found no context for "/drp-exports/ZACHello/index.xml". This request does not match the context path for any installed web applications and there is no default web application configured.> <Nov 2, 2001 2:50:49 PM PST> <Error> <HTTP> <HttpServer(7908535,null default ctx,myserver) found no context for "/drp-publish/ZACHello/". This request does not match the context path for any installed web applications and there is no default web application configured.>

Copyright © 2001 BEA Systems, Inc. All rights reserved. Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.