![]() |
![]() |
|
|
| |
Notes and Problems
The following sections describe levels of support and general problems in this release:
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:
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:
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
http://www.hp.com/products1/unix/java/infolibrary/patches.html
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:
Security
Weblogic Server Service Pack 2 includes two new classes related to security:
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.
See the Certifications Page for the most accurate and current information regarding platform support.
The following features are deprecated in WebLogic Server 6.1 and will not be supported in the future:
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.
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.
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.
In WebLogic Server Release 6.1, the WebLogic Tuxedo Connector has the following limitations:
The following sections describe known problems with this software release. BEA is addressing these problems.
Console 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 |
---|---|
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: 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
JDBC and jDrivers Known Problems
Change Request Number |
Description |
---|---|
049854 |
The ejb2 JSP tool does not support EJB 2.0 local interfaces. |
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
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: |
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:
|
Tools Known Problems
Web Services Known Problems
WebLogic Tuxedo Connector 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
![]() |
![]() |
![]() |
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|