Known Issues with BEA WebLogic Server 5.1
This document lists problems you should be aware of in the 5.1 release.
EJB Issues
- Issue 9988. To use the EJB DeployerTool utility on Solaris, you must use JDK version 1.2.2. Using other JDK versions on Solaris yields a java.lang.IllegalArgumentException or java.lang.NullPointerException at startup.
- Issue 9997. When running DeployerTool on Solaris, the utility may display exceptions when you load an existing EJB .jar file. These exceptions can be ignored, and you can use the utility to modify and deploy the .jar. When running DeployerTool on Solaris, you cannot deploy EJBs to remote servers on other Solaris platforms, or to remote servers on Windows NT platforms. This problem does not occur if you run DeployerTool on Windows NT, and it does not occur if you are deploying to a local server on Solaris.
- Issue 9902. Spaces in file and directory names in the classpath cause ejbc and rmic to fail.
- Issue 9897. When you create a new .jar file in DeployerTool and begin adding files to the .jar, you can only add files from subdirectories of directory you used to start DeployerTool. For example, if you started DeployerTool from c:\weblogic\myserver, you can only add files to a .jar that reside in \myserver, or in subdirectories of \myserver. If you attempt to load files from any other directory, DeployerTool displays an assertion error.
- Issue 9171. When you use DeployerTool to create a new .jar file that contains an entity EJB with WebLogic Server RDBMS-based persistence, DeployerTool highlights the EJB in red, indicating deployment errors. The Error messages are: "The following persistence types are invalid: Weblogic RDBMS persistence 5.1.0 The following finder methods contain invalid data: findByPrimaryKey". If you experience this problem, save the EJB .jar file with the indicated error message, and close the file. When you next open the same .jar file, DeployerTool reports only valid deployment errors. For example, you may still need to finish mapping EJB fields to database columns, but DeployerTool no longer reports an invalid persistence type.
- Issue 8107. If you use the JDK 1.1.7 jar utility to package EJB deployments, you may receive the following error when using a .jar file with WebLogic Server utilities: java.io.EOFException: Unexpected end of ZLIB input stream at java.util.zip.InflaterInputStream.fill. If you experience this problem, either use the JDK 1.2 jar utility to package the EJB, or use the -0 option with the JDK 1.1.7 utility to create an uncompressed archive.
- To use a WebLogic Server connection that you have created in the EJB DeployerTool utility, right-click on the connection name and select the Refresh command. DeployerTool indicates whether it was successful in connecting to the selected server. Connecting to a particular server enables you to view and assign principal names that are available in the server before deploying the EJB.
- DeployerTool enables you to create different transaction attributes and permissions for multiple EJB methods. To specify different transaction attributes for EJB methods, create multiple attribute names of tx-0, tx-1, tx-2, and so forth. Then click on each attribute name, select a method, and specify a transaction attribute for the selected method as described in the DeployerTool documentation. To specify different method permissions, create multiple permission names of perm-0, perm-1, perm-2, and so forth. Then click on each permission name, select a method, and specify permissions as described in the documentation.
- Reentrant calls for entity beans are only supported if both methods are executed under the same transaction context. Reentrant calls do not work for non-transactional methods.
- Issue 9714. In previous WebLogic Server versions, the isolation level for EJBs could be defined at the method-level, as required by the EJB 1.0 specification. In the EJB 1.1 specification, there is no such requirement, and the isolation level can be set only at the bean level.
- Issue 9569. You cannot have multiple EJBs in a single EJB deployment unit that share the same EJB implementation class name. If more than one class shares an implementation class name, the deployment unit will have naming conflicts when you compile using ejbc.
- Issue 9387. This release of WebLogic Server does not recognize method-permission and container-transaction settings for an EJB's home methods. By default, home methods receive access permission for "everyone," and transaction attributes are set to "Required."
- Issue 7376. If you manually edit or create XML deployment files for your EJBs, make sure you define the method-intf element for each method in your ejb-jar.xml file. If you do not define method-intf, WebLogic Server assumes that the method exists in the EJB's home interface, rather than the remote interface. This problem does not occur if you use the DeployerTool utility to automatically generate XML deployment files.
- Issue 5997. Container-managed JDBC persistence uses an inappropriate stack trace.
- Issue 2547. A multi-bean transaction of entity beans will fail because the JDBC drivers in a transaction with multiple resources do not support the two-phase commit protocol.
WebLogic Server Tools and Wizards Issues
Console Issue
- Issue 6022. EJB set ManagedProperty Value errors that occur during hot deployment in the WebLogic Console have a stack trace that is larger than the dialog can display.
ZAC Issue
- Issue 5755. Accepting null or empty when creating a shortcut icon on the bootstrap generator page can result in a NullPointerException and stack trace on the ZAC client. This does not cause a problem in practice and is a result of a Swing threading issue.
Servlets Issues
This release introduces support for the HTTP Servlet 2.2 specification, including the deployment of multiple Web Applications and multiple servlet contexts. All features of the Servlet 2.2 specification are supported unless otherwise stated.
- Issue 9628. The <load-on-startup> XML tag is not honored.
- Issue 9150. HTTP tunneling through a Network Address Translating firewall is not supported in this release.
- Issue 7640. The default value for the property weblogic.httpd.postTimeoutSecs may be too short for a slow network or Internet connection and may cause unexpected timeouts. To fix this problem, increase the value of weblogic.httpd.postTimeoutSecs.
- Issue 5403. There is a known issue using session persistence when running the server under Java 2 v1.2.1. JDBC Persistent sessions. The java verifier throws an exception: java.lang.VerifyError:(class:weblogic/servlet/internal/session/ClusteredSessionPSJDBC, method: findAllKeys signature: ()Ljava/util/Enumeration;. There are two workarounds:
JMS Issue
- Issue 7462. If the number of subscribers to a JMS topic is larger than the number of execute threads in WebLogic Server, the server can run out of execute threads while pushing messages out to the subscribers. This problem will only occur if you are using auto-acknowledge or have implemented the onMessage method in your message listener. As a temporary work around, you can use client-acknowledge while implementing the onMessage method in your message listener, or you can increase the number of execute threads in the server.
Licensing Keys Issue
- Issue 6347. The semantics of our licensing scheme has multiple keys for individual features. If the licenses are of varying permission levels, the license file needs to be edited in order for the most permissive key to be used. For information on editing licenses, see Installing a WebLogic License.
jDriver for Oracle Issues
- Issue 10026. WebLogic jDriver for Oracle is only supported on HP when the Oracle client and Oracle server are the same version. For example, an Oracle 8.0.5 client is only supported when connecting to an Oracle 8.0.5 server.
- Issue 9431. WebLogic jDriver for Oracle is not supported when using the Oracle 8 API and connecting to an version 7 Oracle DBMS.
- Issue 9283. CallableStatement.getResultSet()with a defined ResultSet Cursor does not work when using the Oracle 8.1.5 DBMS on the Solaris operating system.
When using Oracle client version 8.0.5 and executing a CallableStatement with a defined ResultSet Cursor, you must re-register the cursor prior to each CallableStatement.getResultSet() call. For example:
weblogic.jdbc.common.OracleCallableStatement cstmt2 =
(weblogic.jdbc.common.OracleCallableStatement)
conn.prepareCall("{CALL single_cursor(?, ?)}");
cstmt2.registerOutParameter(1, java.sql.Types.OTHER);
// You can also set input parameters, execute the statement,
// retrieve the query into a ResultSet, and print it
// for each set of input parameters.
System.out.println
("FIRST sproc 'single_cursor' exec for INT==1\n\n\n\n");
cstmt2.setInt(2, 1);
cstmt2.execute();
rs = cstmt2.getResultSet(1);
System.out.println("FIRST sproc 'single_cursor' exec for
INT==2\n\n\n\n");
// Add the following line to re-register the cursor:
cstmt2.registerOutParameter(1, java.sql.Types.OTHER);
cstmt2.setInt(2, 2);
cstmt2.execute();
rs = cstmt2.getResultSet(1);
Cross-platform incompatibility when using Oracle 8.0.5 and 8.1.5 clients running on HP. The following combinations are known to be incompatible:
- Oracle 8.0.5 Client running on HP connecting to an Oracle 8.1.5 DBMS running on Windows NT or Solaris.
- Oracle 8.1.5 client running on HP connecting to an Oracle 8.1.5 DBMS running on Solaris.
Issue 9708. Using the CLOB datatype and using codeset conversions while running the Oracle client and Oracle server on different operating systems will fail.
Issue 9992. The commented-out connection pool for Oracle (oraclePool) in the weblogic.properties file uses refreshMinutes. It should be changed to refrestTestMinutes.
Remote Method Invocation (RMI) over IIOP Issues
Client restrictions
Clients can call into RMI servers and EJB with the following restrictions:
- Return values and parameters are limited to RMI value types.
- Client-side callbacks are currently not supported.
CosNaming service
WebLogic Server's CosNaming service is restricted to lookup only (NamingContext.resolve()). This naming service delegates to WebLogic Server's JNDI implementation, so you only need to administer the JNDI tree to make objects accessible to CosNaming clients.
WebLogic Server Issues
- Issue 10065. Problems with the server connections when the client is an applet using the Java plug-in. The message "Connection rejected: 'Login timed out after: '5000' ms on socket:" is displayed. The port number increments indefinitely.
- Issue 9731. Possible security-related IOException when clients are multi-threaded. The exception is: java.io.IOException: weblogic.security.SSL.BadMACException.
- Issue 8925. If you want to start WebLogic Server without using dynamic classloading, pass the following property on the java command line when you start WebLogic Server: weblogic.system.disableWeblogicClassPath=true. You must then include all of the classes required to start WebLogic Server in the environment CLASSPATH variable. A WebLogic Server started in this way will be unable to deploy EJBs and servlets without restarting WebLogic Server.
- Issue 7127 and 5730. The server will occasionally print erroneous "SocketException: bad file number" messages in the log file. These messages can be ignored.
- Issue 9003. On Windows NT and Solaris, connection pools are sensitive to a JVM bug that crashes the server with a message "*** panic: 16-bit table overflow". See the Sun Bug Parade. The problem is more likely to occur with applications that use EJB and/or JMS and will only happen when running with the 1.1.7 JVM.
Cloudscape Evaluation Version 2.0.1
- If you are using the evaluation version of Cloudscape bundled with this release of WebLogic, and you are starting the server from the command line, you must also add weblogic/eval/cloudscape/lib/cloudscape.jar to the Java system classpath with the -classpath option. Both the JMS and EJB examples use the evaluation Cloudscape database. For details, see Using the Cloudscape database with WebLogic and Setting up and Starting WebLogic Server.
- Issue 9883. On some platforms, you may receive the following error when creating the demoPool connection pool using the evaluation version of Cloudscape bundled with WebLogic Server.
WARNING: Cloudscape (instance reference #) is attempting to boot the database /weblogic/eval/cloudscape/data/demo even though cloudscape (instance reference #) may still be active. Only one instance of cloudscape should boot a database at a time. Severe and non-recoverable corruption can result and may have already occurred.
This warning is harmless and occurs because a copy of a temporary locking file has been included within the demo database directory.
Examples Issues
JMS Examples
- Issue 9887. In order to run the JMS examples examples.jms.sessionpool, examples.jms.trader, and examples.jms.startup, you must un-comment the following line in you weblogic.properties file: weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone.
- Issue 9885. On Solaris, running the examples.jms.drawdemo example causes a ClassCastException on WebLogic Server during JMS message delivery. The exception repeats in an infinite loop.
- Issue 9003. On Windows NT and Solaris, examples that use a connection pool are sensitive to a JVM bug that crashes the server with a message "*** panic: 16-bit table overflow". See the Sun Bug Parade. The problem is more likely to occur with applications that use EJB and/or JMS and will only happen when running with the 1.1.7 JVM. The examples affected by this problem include:
EJB Example Issues
EJB example applications exhibit the following problems in this release:
- Issue 10066. The build.cmd script for the example in \weblogic\examples\ejb\subclass contains an extra newline character that causes the script to fail. To build this example, remove the extra newline character from build.cmd, or use the included make file.
- 10014. The example EJBs for the examples.cluster.ejb.Client application do not demonstrate load balancing, as described in the documentation. To view load balancing behavior with this example, open cluster_ejb_Account.jar and ejb_cluster_Teller.jar in the DeployerTool utility, and define clustering properties before deploying the beans.
- Issue 9009. wlec.ejb.simpapp example has a problem in its ejb\simpapp\ejb-jar.xml file. It uses an invalid DOCTYPE:
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.2//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
The valid DOCTYPE should be:
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
- Issue 7659. The example in /weblogic/examples/ejb/basic/containerManaged performs multiple operations against a pure Java RDBMS system, and generally takes six to eight seconds to complete.
- The servlet clients included with the examples in /weblogic/examples/ejb/basic/containerManaged and /weblogic/examples/ejb/basic/beanManaged do not function with Internet Explorer. Accessing these servlets with Internet Explorer yields the error "No credentials supplied," even if you specify the correct username and password. This problem does not occur with Netscape Navigator.
|
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.
|
