bea weblogic server - freie universität...bea weblogic server release notes v contents introducing...

WebLogic ServerRelease Notes

A p r i l , 2 0 0 0

WebLogic Server 5.1

BEA

Copyright

Copyright © 2000 BEA Systems, Inc. All Rights Reserved.

Restricted Rights Legend

This software and documentation is subject to and made available only pursuant to the terms of the BEA Systems License Agreement and may be used or copied only in accordance with the terms of that agreement. It is against the law to copy the software except as specifically allowed in the agreement. This document may not, in whole or in part, be copied photocopied, reproduced, translated, or reduced to any electronic medium or machine readable form without prior consent, in writing, from BEA Systems, Inc.

Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the BEA Systems License Agreement and in subparagraph (c)(1) of the Commercial Computer Software-Restricted Rights Clause at FAR 52.227-19; subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, subparagraph (d) of the Commercial Computer Software--Licensing clause at NASA FAR supplement 16-52.227-86; or their equivalent.

Information in this document is subject to change without notice and does not represent a commitment on the part of BEA Systems. THE SOFTWARE AND DOCUMENTATION ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. FURTHER, BEA Systems DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE SOFTWARE OR WRITTEN MATERIAL IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE.

Trademarks or Service Marks

BEA, WebLogic, ObjectBroker, TOP END, and TUXEDO are registered trademarks of BEA Systems, Inc. BEA Builder, BEA Connect, BEA Manager, WebLogic Server, WebLogic jDriver, BEA MessageQ, Jolt and M3 are trademarks of BEA Systems, Inc.

All other company names may be trademarks of the respective companies with which they are associated.

Contents

Introducing BEA WebLogic Server 5.1About BEA WebLogic Server 5.1..................................................................1

Standards Compatibility..........................................................................2

Getting Started................................................................................................2

Using the Documentation...............................................................................3

Customer Support...........................................................................................3

Upgrade Notes for BEA WebLogic Server 5.1Upgrading from Pre-5.1 Versions ..................................................................5

WebLogic Server Upgrade.............................................................................5

Statically Starting WebLogic Server.......................................................5

WebLogic Server Tools and Wizards .....................................................6

Console ............................................................................................6

EJB Deployment Wizard is now EJB DeployerTool.......................6

Windows Convenience Program Names.................................................6

Java2 Enterprise Edition Upgrade Notes .......................................................7

EJB (Enterprise JavaBeans) 1.1 Upgrade ...............................................7

JMS (Java Message Service) Upgrade....................................................7

JNDI (Java Naming and Directory Interface) Upgrade ..........................7

JSP (JavaServer Pages) Upgrade ............................................................7

RMI (Remote Method Invocation) .........................................................8

Servlet Upgrade.......................................................................................8

Security Upgrade............................................................................................8

JDBC Drivers Upgrade Issues........................................................................9

jdbcKona/Sybase jdbcKona/MSSQLServer .................................................................9

jdbcKona/Oracle .....................................................................................9

BEA WebLogic Server Release Notes v

jdbcKona/Informix4jdbcKona/MSSQLServer4 ............................................................ 10

Platform Support Upgrade Issues................................................................ 10

Java Environment Upgrade Issues ....................................................... 10

Java 2 version 1.2 Support ............................................................ 10

Microsoft SDK for Java Upgrade ................................................. 11

Using Jview with RMI .................................................................. 11

Hewlett-Packard ................................................................................... 11

3rd Party Products Upgrade Issues.............................................................. 11

Website Pro and ISAPI (WebLogic to Microsoft IIS bridge) .............. 11

Changes in BEA WebLogic Server 5.1WebLogic Server Changes .......................................................................... 14

Starting WebLogic Server............................................................. 14

NSAPI Plugin................................................................................ 14

CLASSLOADER .......................................................................... 14

UTILITIES.................................................................................... 14

HTTP Extended Log Format Support .................................................. 15

CGI Support ......................................................................................... 15

Apache Support .................................................................................... 15

WebLogic Server Tools and Wizards .................................................. 15

Console.......................................................................................... 15

EJB DeployerTool Changes.......................................................... 16

ZAC Changes ................................................................................ 16

Extensible Markup Language (XML) .................................................. 16

Properties Changes............................................................................... 17

New and changed properties ......................................................... 17

Deprecated APIs................................................................................... 18

JDBC Drivers ................................................................................ 18

Platform Support Changes ................................................................... 19

Standard Compliance Support..................................................................... 19

EJB Changes ........................................................................................ 20

EJB 1.1 .......................................................................................... 20

Java Database Connectivity Changes (JDBC 2.0) ............................... 21

jdbcKona JDBC drivers renamed ................................................. 21

vi BEA WebLogic Server Release Notes

DataSource.....................................................................................21

JDBC/RMI and Clustered JDBC ...................................................21

JTS driver.......................................................................................22

jdbcKona/Oracle ............................................................................22

jDriver for Oracle available for the HP-UX 11 platform...............22

Java Message Service............................................................................23

Support for Fully Qualified Table Names .....................................23

JMS Issues Resolved in this Release .............................................23

Java Naming and Directory Interface Changes (JNDI 1.2) ..................23

Java Server Pages Changes (JSP 1.1) ...................................................23

Remote Method Invocation Changes ....................................................25

Remote Method Invocation (RMI) over IIOP ...............................25

RMI Issues Resolved in this Release .............................................25

Servlet Changes............................................................................................25

Servlet 2.2 ......................................................................................25

Servlet Issues Resolved in this release ..........................................26

JDBC Changes .............................................................................................27

jDriver for Oracle available for the HP-UX 11 platform...............27

jConnect Driver for Sybase now bundled with WebLogic Server 27

Security Changes..........................................................................................27

WebLogic Security Realms and New CachingRealm .........................28

Access Control Lists .............................................................................30

WebLogic SSL.....................................................................................30

Simple Network Management Protocol Support .........................................31

Third Party Products-Related Changes ........................................................32

Visual Age.............................................................................................32

VisualCafe/Webgain Studio..................................................................32

Third Party-Related Issues Resolved in this Release............................32

Jolt for WebLogic Changes..........................................................................33

WebLogic Enterprise Connectivity Changes ...............................................33

Example Changes .........................................................................................34

New Examples ......................................................................................35

Deprecated Examples............................................................................35

Tour Changes ...............................................................................................36

Documentation Changes ..............................................................................36

BEA WebLogic Server Release Notes vii

New Documentation Features .............................................................. 36

New Documentation............................................................................. 37

Installation ............................................................................................ 37

JDBC .................................................................................................... 37

Security................................................................................................. 38

Wireless Application Protocol ............................................................. 38

Known Issues with BEA WebLogic Server 5.1EJB Issues.................................................................................................... 39

WebLogic Server Tools and Wizards Issues............................................... 42

Console Issue........................................................................................ 42

ZAC Issue............................................................................................. 42

Servlets Issues ............................................................................................. 42

JMS Issue..................................................................................................... 43

Licensing Keys Issue................................................................................... 43

jDriver for Oracle Issues ............................................................................. 43

Remote Method Invocation (RMI) over IIOP Issues .................................. 45

Client restrictions ................................................................................. 45

CosNaming service .............................................................................. 45

WebLogic Server Issues .............................................................................. 45

Cloudscape Evaluation Version 2.0.1 ......................................................... 46

Examples Issues........................................................................................... 46

JMS Examples...................................................................................... 46

EJB Example Issues ............................................................................. 47

viii BEA WebLogic Server Release Notes

Introducing BEA WebLogic Server 5.1

About BEA WebLogic Server 5.1

WebLogic Server is an application server, a runtime environment that provides infrastructure services such as database access, transaction coordination, and a component framework for distributed applications. WebLogic Server also provides administrative features such as configurable security, management and application deployment tools, and clustering to promote high availability and scalability.

WebLogic Server operates at the center of a multitier architecture. Clients can be very light-weight, greatly simplifying application deployment. Complete enterprise applications can be built with nothing more than WebLogic Server and a web browser on the client.

WebLogic Server also manages access to database systems, Java Transaction Service (JTS), and other shared resources on behalf of clients. It presents a consistent development environment that is independent from the specific back-end services employed. For example, code to perform a database query is identical, whether the query actually executes on an Oracle, Sybase, Informix, or IBM DB2 database. Changing from one database vendor to another only requires changing the software layer that WebLogic Server uses to access the database.

WebLogic Server supports a variety of published application development standards that make it easy to develop or acquire software components that can be easily integrated into an enterprise application. WebLogic Server supports the Java 2 Platform, Enterprise Edition, a collection of Java APIs that allows developers to build powerful, component-based applications.

Standards Compatibility

WebLogic Server 5.1 supports the following J2EE standards:

For more information on specification compatibility, please see our Platform Support page at http://www.weblogic.com/docs51/platforms/index.html.

Getting Started

Follow these steps to learn about new the features and to get started with WebLogic Server 5.1:

1. Read these Release Notes. The Release Notes are provided in these formats:

l On the Web at http://www.weblogic.com/docs51/release_notes/index.html. This version is always the most up-to-date.

l As a printed document in the WebLogic Server product box.

JSP 1.1

EJB 1.1

JMS 1.0.1

Servlets 2.2

JDBC 1.1 and 2.0

Java RMI 1.0

Other Standards -

SSL v3

X. 509 v3

LDAP v2

HTTP 1.0

SNMP v1

6 BEA WebLogic Server Release Notes

http://www.weblogic.com/docs51/release_notes/index.html

http://www.weblogic.com/docs51/platforms/index.html

l On the WebLogic Server CD-ROM in the /documentation directory.

2. Install the product, following the Installation Guide, which is provided in these formats:

l On the Web at http://www.weblogic.com/docs51/install/index.html.

l As a printed document in the WebLogic Server product box.

l On the WebLogic Server CD-ROM in the /documentation directory.

Using the Documentation

WebLogic Server documentation for this release is available at these locations:

n On the Web at http://www.weblogic.com/docs51/resources.html. The Web is always the most up-to-date source for WebLogic Server documentation.

n Documentation in Adobe Acrobat PDF format is available on our PDF page at http://www.weblogic.com/docs51/API_users_guide.html.

n Printed copies of some titles are packaged in the WebLogic Server product box.

n On the WebLogic Server CD-ROM, in the /documentation directory.

Documentation for all BEA products can be accessed through the BEA documentation portal at http://e-docs.beasys.com.

Customer Support

BEA is always ready to offer our best customer support and help. Please contact [email protected] or call 1-888-232-7878.

Visit the WebLogic Server newsgroups, at http://www.beasys.com/support/newsgroup.html, to receive helpful information and to ask questions regarding our products. This is also an excellent way to give us your feedback.

BEA WebLogic Server Release Notes 7

http://www.weblogic.com/docs51/resources.html

http://www.weblogic.com/docs51/install/index.html

http://www.weblogic.com/docs51/API_users_guide.html

http://e-docs.beasys.com

http://www.beasys.com/support/newsgroup.html

mailto:[email protected]

Upgrade Notes for BEA WebLogic Server 5.1

Upgrading from Pre-5.1 Versions

This section contains upgrade information for the WebLogic Server 5.1 release. See Upgrade Notes for BEA WebLogic Server 5.1 and Known Issues with BEA WebLogic Server 5.1 for information about additional changes and known problems.

The changes described in this section are relative to the previous release of WebLogic Server, version 4.5.

For information on platform support, see WebLogic Platform Support at http://www.weblogic.com/docs51/platforms/index.html.

WebLogic Server Upgrade

The classpath and command line used to start WebLogic Server have changed in this release. The changes are discussed in detail in Installing and Setting Up WebLogic Server at http://www.weblogic.com/docs51/install/startserver.html.

You cannot use startup scripts or shortcuts that you used with previous versions of WebLogic Server with this verison. New scripts are included with this release. You can can modify them for your environment. For more information, see Starting WebLogic Server using scripts at http://www.weblogic.com/docs51/install/startserver.html.

Statically Starting WebLogic Server

To start the server statically (without the WebLogic Server classloaders that enable the hot deploy feature) set the weblogic.system.enableStaticStartup Java system property to true on the java command line to start WebLogic Server:


http://www.weblogic.com/docs51/install/startserver.html




-Dweblogic.system.enableStaticStartup=true

This may require changes to the scripts used to start the server with Microsoft SDK for Java, AS/400, MVS, and possibly other platforms or Java Virtual Machines (JVMs).

WebLogic Server Tools and Wizards

The WebLogic GUIs have cosmetic changes.

CONSOLE

The WebLogic Console has been upgraded. There are no upgrade issues.

EJB DEPLOYMENT WIZARD IS NOW EJB DEPLOYERTOOL

The EJB Deployment Wizard has been upgraded and renamed to EJB DeployerTool (weblogic.ejb.ui.deployer.DeployerTool).

Windows Convenience Program Names

The following native Windows NT programs have changed their names:

t3config is now wlconfigt3server is now wlservert3console is now wlconsole

If you have scripts that invoke these programs, you must edit the scripts to use the new names. Documentation for these programs is in Windows convenience programs at http://www.weblogic.com/docs51/install/startserver.html#convenience.

The names of the Administrative Servlets have changed:

n T3AdminEvents is now AdminEvents

n T3AdminClients is now AdminClients

n T3AdminServlets is now AdminServlets


http://www.weblogic.com/docs51/install/startserver.html#convenience

Java2 Enterprise Edition Upgrade Notes

EJB (Enterprise JavaBeans) 1.1 Upgrade

WebLogic Server 5.1 supports the Enterprise Java Beans 1.1 specification. Existing EJBs based on the EJB 1.0 specification must be upgraded to run with WebLogic Server 5.1, as per the EJB specification. See Upgrading EJBs to WebLogic Server Version 5.1 at http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_upgrade.html for instructions.

The EJB Deployment Wizard has been upgraded and renamed to EJB DeployerTool.

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.

JMS (Java Message Service) Upgrade

Internally, WebLogic JMS uses database tables to store the state of durable subscribers. In WebLogic Server version 5.1, the structure of the JMS tables has changed. Your existing tables are automatically upgraded to the new structure when they are first accessed by the server. Once the tables have been upgraded, you cannot revert the tables to the previous version.

For more information, please see Using WebLogic JMS at http://www.weblogic.com/docs51/classdocs/API_jms.html.

JNDI (Java Naming and Directory Interface) Upgrade

WebLogic Server 5.1 now supports the JNDI 1.2 specification. There are no upgrade issues.

JSP (JavaServer Pages) Upgrade

WebLogic Server now supports the JSP 1.1 specification.Updated JSP documentation is available in Using WebLogic JSP at http://www.weblogic.com/docs51/classdocs/API_jsp.html.


http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_upgrade.html


http://www.weblogic.com/docs51/classdocs/API_jsp.html

http://www.weblogic.com/docs51/classdocs/API_jms.html

RMI (Remote Method Invocation)

There are no RMI upgrade issues.

Servlet Upgrade

WebLogic Server now supports the Servlet 2.2 specification. There are no upgrade issues. Previous servlets should continue to work properly. For more information, please refer to section 1.7 of the Servlet 2.2 specifications.

Servlet 2.2 deprecates the methods getValue(), getValueNames(), setValue(), and removeValue(). These methods have new equivalent methods intended to improve the API naming consistency. The deprecated methods are supported in the 5.1 release, but you are advised to update your servlet code.

In addition, the constructor methods of UnavailableException have been replaced with simpler signatures. Again, see section 1.7 of the Servlet 2.2 specification.

For more detailed information, see Using WebLogic HTTP Servlets at http://www.weblogic.com/docs51/classdocs/API_servlet.html.

Security Upgrade

New features in WebLogic Server 5.1 make developing custom alternative security realms easier. An alternative realm installed with the weblogic.security.realmClass property is now hosted by a new built-in realm, CachingRealm. Custom realms should be written to extend the new AbstractListableRealm or AbstractManageableRealm, which are designed to work with CachingRealm. The Windows NT, LDAP, and RDBMS realms have been modified to use the new CachingRealm and AbstractListableRealm, as does the new UNIX realm. No upgrade procedures are required.

If you are using a custom realm or a modified version of the RDBMSRealm from a previous release, your realm should continue to work properly. However, we recommend that you update your realm to use the new CachingRealm scheme and take advantage of tunable caching and other new features.

The RDBMSRealm database schema has not changed, but that realm is no longer dependent on the DefaultRealmExtender and CachingRealm examples.


http://java.sun.com/products/servlet/2.2/

http://www.weblogic.com/docs51/classdocs/API_servlet.html

See the index to WebLogic Server security documentation at http://www.weblogic.com/docs51/classdocs/securityguide.html for a list of new and revised security documents.

JDBC Drivers Upgrade Issues

jdbcKona/Sybase jdbcKona/MSSQLServer

The jdbcKona/Sybase and jdbcKona/MSSQLServer JDBC type 2 drivers are no longer included with WebLogic Server. If you require connectivity to a Sybase database, you can use the jConnect pure-Java type-4 driver from Sybase, which is bundled with WebLogic Server. jConnect is also available free from Sybase at http://www.sybase.com/products/internet/jconnect/.

jdbcKona/Oracle

WebLogic jDriver for Oracle (formerly called jdbcKona/Oracle) is now available in several versions. The one you use depends on your Oracle client installation, the version of the Oracle API you will use to connect to the Oracle server, and your platform. You must place the appropriate file in your system’s path or shared library path for this driver to function properly. Unlike previous releases of WebLogic Server, which had a shared library in the default path, you must now set up your shared library and path variables explicitly. For instructions on setting these options, see the section Setting your path and client libraries in the JDBC Installation Guide at http://www.weblogic.com/docs51/install/install_jdbc.html.

WebLogic jDriver for Oracle is not available on all platforms in this release. For details, see the Platform Support page at http://www.weblogic.com/docs51/platforms/index.html and the jDriver for Oracle Issues section of these release notes.

For more information on using jDriver for Oracle, see Using WebLogic jDriver for Oracle at http://www.weblogic.com/docs51/classdocs/API_joci.html.


http://www.weblogic.com/docs51/classdocs/securityguide.html

http://www.sybase.com/products/internet/jconnect/

http://www.weblogic.com/docs51/install/install_jdbc.html#1062058

http://www.weblogic.com/docs51/classdocs/API_joci.html



jdbcKona/Informix4jdbcKona/MSSQLServer4

These pure-Java type 4 JDBC drivers are distributed separately from WebLogic Server. They are now called WebLogic jDriver for Informix and Weblogic jDriver for Microsoft SQL Server, respectively.

WebLogic jDriver for Informix and Weblogic jDriver for Microsoft SQL Server use a new XML licence format. For more information, see the installation guides for these drivers.

For JDBC additional documentation, see WebLogic JDBC Options at http://www.weblogic.com/docs51/classdocs/jdbcdrivers.html.

Platform Support Upgrade Issues

Java Environment Upgrade Issues

JAVA 2 VERSION 1.2 SUPPORT

WebLogic Server is designed to work both with Java 1.1 and Java 2. BEA tests WebLogic Server with both environments. BEA recommends that you use a version of the Java developers kit that we have certified for your hardware platform.

The Java 1.2 Runtime Environment (JRE) for Windows is included in the WebLogic Server Windows InstallShield distribution.

Please see our Platform Support document, at http://www.weblogic.com/docs51/platforms/index.html, and Running WebLogic with the Java 2 SDK, at http://www.weblogic.com/docs51/techsupport/java12.html.

Note: Windows NT only: The JRE mentioned above does not include classes that are required for use with certain tools such as the EJB compiler (ejbc). To use these tools you must install a JDK to use with WebLogic Server. For details and instructions see Installing using the InstallShield distribution at http://www.weblogic.com/docs51/install/install_shield.html.


http://www.weblogic.com/docs51/classdocs/jdbcdrivers.html


http://www.weblogic.com/docs51/techsupport/java12.html

http://www.weblogic.com/docs51/techsupport/java12.html

http://www.weblogic.com/docs51/install/install_shield.html

MICROSOFT SDK FOR JAVA UPGRADE

A special library is required by WebLogic Server and WebLogic COM to support RMI with the Microsoft SDK for Java. rmiForMs.zip is installed in the lib subdirectory by the InstallShield installer. This library is not included in the .zip file distribution. rmiForMs.zip must be added to the WebLogic Server classpath when starting WebLogic Server using Microsoft SDK for Java. This is done for you automatically if you start the server using the startWebLogic.cmd script, which is provided in the WebLogic Server distribution directory.

USING JVIEW WITH RMI

If you are using Microsoft SDK for Java as your JVM and will also be using RMI, you must add the following to your Java system classpath when starting Weblogic Server:

weblogic/lib/rmiForMs.zip

where weblogic is the directory in which you installed WebLogic Server.

Hewlett-Packard

This release only supports JDK 1.1.8 on Hewlett-Packard machines.

3rd Party Products Upgrade Issues

Website Pro and ISAPI (WebLogic to Microsoft IIS bridge)

O’Reilly Website Pro is no longer supported for use with the ISAPI plugin. For more information on the ISAPI bridge, see Installing MS-IIS-WebLogic Server Plugin at http://www.weblogic.com/docs51/admindocs/isapi.html.


http://www.weblogic.com/docs51/admindocs/isapi.html

Changes in BEA WebLogic Server 5.1

In addition to the items listed in the Upgrade section, this section discusses additional changes made since the 4.5.1 release. Changes have been made in the following areas:

n WebLogic Server Changes

n Standard Compliance Support

n Java Naming and Directory Interface Changes (JNDI 1.2)

n Remote Method Invocation (RMI) over IIOP

n Security Changes

n JDBC Changes

n Simple Network Management Protocol Support

n Third Party Products-Related Changes

n Platform Support Changes

n Jolt for WebLogic Changes

n WebLogic Enterprise Connectivity Changes

n Example Changes

n Tour Changes

n Documentation Changes

WebLogic Server Changes

For changes that apply to Java 2 Enterprise Edition features, see the Standard Compliance Support of this document.

STARTING WEBLOGIC SERVER

The following issues have been addressed in this release:

n If you start the server with weblogic.cluster.enable=true, but without a clustering license, the server will no longer quit with a NullPointerException.

n Issue 9036. The Java 1.1.7 JRE can be used with this release of WebLogic Server.

n Issue 6843. The setEnv.sh shell script requires a Bourne shell or another shell that is compatible with the Bourne shell, and must run on a UNIX platform. The script is not supported on Windows NT, even with UNIX shells such as MKS ksh or Cygwin bash. On Windows, use the setEnv.cmd command script or modify the setEnv.sh script to work with the shell you prefer.

NSAPI PLUGIN

The following issue has been addressed in this release:

n Issue 7398. Memory leak with NSAPI plugin was fixed.

CLASSLOADER


n Issue 7343. We have removed some harmless, but potentially confusing stack traces related to loading certain classes, stubs in particular.

UTILITIES


n Issue 6579. The output of the -verbose command has changed slightly from JDK 1.1 to JDK 1.2 , and no longer breaks.


HTTP Extended Log Format Support

The HTTP extended log file format provides finer control over the HTTP log information recorded. This release supports extended log format. For more information see Setting up HTTP server log files at http://www.weblogic.com/docs51/admindocs/http.html#logs.

CGI Support

This release provides support for CGI scripts. For more information, see Using legacy CGI at http://www.weblogic.com/docs51/admindocs/http.html#cgi.

Apache Support

This release incorporates support for the Apache Web Server. For more information, see Installing the Apache-WebLogic plug-in at http://www.weblogic.com/docs51/admindocs/apache_bridge.html.

WebLogic Server Tools and Wizards

CONSOLE


n Issue 8400. WebLogic Server no longer hangs, looping indefinitely when trying to run a stateless EJB after undeploying and redeploying in the Console.

n Issue 8168. Reload Servlet in the Console no longer throws a NullPointerException in the server stack and ReflectInvocationTargetException in Client Stack trace.

n Issue 8167. The Console no longer hangs and throws an ObjectNotFoundException when you click on a loaded servlet.

n Issue 7951. The Console has a new URL pattern field for registering a new Servlet 2.2 file.

n Issue 7921. The Console now uses the document root. In cases where a servlet classpath is in a different directory, the servlet classpath can be read using the XML file context-param or from the property in the weblogic.properties file.


http://www.weblogic.com/docs51/admindocs/http.html#logs

http://www.weblogic.com/docs51/admindocs/http.html#cgi

http://www.weblogic.com/docs51/admindocs/http.html#cgi

http://www.weblogic.com/docs51/admindocs/apache_bridge.html

n Issue 7440. The EJB Console now works when using primary key classes on containter-managed persistence beans that do not directly define hashCode and equals.

n The WebLogic Console now successfully starts WebLogic Server when running with Microsoft SDK for Java. The workaround used in previous releases is no longer necessary.

n The Console now supports EJB 1.1. deployment.

EJB DEPLOYERTOOL CHANGES


n Issue 9645. Problems running the weblogic.EJBDeployerTool in an X/Motif environment have been fixed. Select Jar File no longer has problems and the workaround is no longer necessary.

n Issue 9569. There is no longer a restriction on EJBs that can be in a single deployment unit. The restriction was that you could not have two EJBs in a single deployment unit with the same bean implementation class. Otherwise the generated files for these beans would have naming conflicts. The naming conflicts are now resolved.

n Issue 9313. The java.lang.NoClassDefFoundError exception no longer occurs.

ZAC CHANGES


n Resolved an issue when specifying the default installation directory in the ZAC installer. When specifying the directory using Windows backslash (\) directory separators, these may appear escaped as "\\" in the installer.

Extensible Markup Language (XML)

The document Using XML with WebLogic Server (http://www.weblogic.com/docs51/classdocs/xml.html) has been added and describes how XML interfaces with the other WebLogic Server services. New XML code examples are also included in your distribution.


http://www.weblogic.com/docs51/classdocs/xml.html

Properties Changes

NEW AND CHANGED PROPERTIES

n Issue 1067. A new property, weblogic.httpd.errorPage.HTTP.errorNumber=URL, allows you to specify a URL or page (relative to the document root) for a given HTTP error number.

n A new property, weblogic.httpd.logFileFormat, ="extended" or "common"> allows you to choose the log file format. The property can be set to “extended” or “common”

n A new property, weblogic.httpd.webApp.context=WebAppLocation sets the context for a Web Application.

n The property weblogic.httpd.indexDirectories=false has changed. The default, which used to be true, is now false. When false, it forbids browsers from viewing the contents of a directory if they only specify the directory in the URL, and returns error 403 File Forbidden.

n A new Java system property, weblogic.classloader.verbose, has been added to turn on verbose classloading.

n A new property, weblogic.httpd.postTimeoutSecs, is introduced in this release.

n The property -Dweblogic.system.disableWeblogicClassPath=true will cause the server to load classes from the Java classpath (static loading). The default is false. If an attempt is made to start the server with WebLogic classes in the Java classpath and this property is not set, the following message is displayed:

Cannot start server because weblogic.class.path is enabled and the Weblogic classes are not in the weblogic.class.path.

You should either alter weblogic.class.path to include the WebLogic classes or set -Dweblogic.system.disableWeblogicClassPath=true in the command line to allow classes to load from the Java classpath.

Note: Starting WebLogic Server with the static classloader disables EJB hot deployment.

n The weblogic.security.ciphersuites property allows you to specify the ciphersuites that are available when negotiating SSL connections.


n If you use an alternative security realm, the new CachingRealm offers several new properties you can use to tune caching of user, group, and ACL lookup results. See Administering the WebLogic CachingRealm at http://www.weblogic.com/docs51/admindocs/cachingrealm.html to learn about these new properties.

n The new weblogic.security.urlAclFile property gives the name of a policy file that contains extended ACLs for URLs. See Controlling Access on URLs at http://www.weblogic.com/docs51/admindocs/urlacl.html for more information about this new feature.

n In addition to the existing weblogic.security.clientRootCA property, three additional properties allow you to specify root certificates for up to four Certificate Authorities whose certificates are to be accepted. The new properties are:

l weblogic.security.clientRootCA2




n Issue 8458. During HTTP basic authentication, a dialog box pops up in the browser for authentication purposes. There is a field for “Authentication Realm” which displays “WebLogic Server” by default. You can change “WebLogic Server” to your own system name by setting the new name in the property weblogic.httpd.authRealmName.

n Issue 4670. The property weblogic.system.startupFailureIsFatal.fail=boolean has changed. It is false by default. If set to true, WebLogic Server will not start if the specified startup class or classes throws exceptions. The word “fail” is the virtual name of the startup class or classes, which are registered like this:

weblogic.system.startupClass.fail=class1,class2,...

Deprecated APIs

JDBC DRIVERS

The following drivers have been deprecated in this release:


http://www.weblogic.com/docs51/admindocs/cachingrealm.html

http://www.weblogic.com/docs51/admindocs/urlacl.html


n jdbcKona/Sybase

n jdbcKona/MSSQLServer

Platform Support Changes


n Issue 9513. Starting WebLogic Server using Microsoft SDK for Java requires you to specify the classpath differently. All classes should be specified using the CLASSPATH environment variable. Do not specify classes with the /cp option. You must also pass the following property on the Java command line:

/d:weblogic.system.disableWeblogicClassPath=true

n Issue 7528. Bug ID 4134584 in Sun’s Bug Parade describes a bug in JDK 1.1.7 on Windows NT and Solaris. This bug will occasionally cause the WebLogic Server JVM to crash with the error “*** panic: 16-bit string hash table overflow”. Because of this error, we recommend that you use JDK 1.2 on Windows NT and Solaris.

n Issue 7125 Solaris. You no longer have to work around a bug in the Java ksh wrapper script for Solaris SDK 1.2.2. The workaround was to place -native as the first option, before -classic.

Standard Compliance Support

The following new features supporting Sun Microsystems’ Java 2, Enterprise Edition have been added:

n EJB Changes

n Java Database Connectivity Changes (JDBC 2.0)

n Java Server Pages Changes (JSP 1.1)

n Servlet Changes


EJB Changes

EJB 1.1

WebLogic Server now supports the EJB 1.1 specification. Existing EJBs based on the EJB 1.0 specification must be upgraded to run with WebLogic Server 5.1. See Upgrading EJBs to WebLogic Server Version 5.1 at http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_upgrade.html for instructions.

WebLogic Server 5.1 introduces two XML files for defining EJB deployment properties. If you edit or create these files outside of the WebLogic Server utilities (DDConverter, DeployerTool), make sure that the files comply with their associated Document Type Definitions (DTDs). The DTDs for WebLogic Server deployment files are at these locations:

n http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd

n http://www.bea.com/servers/wls510/dtd/weblogic-rdbms-persistence.dtd

Note: Most browsers do not display the contents of files having the .dtd extension. To view the DTD file contents in your browser, save the links as text files and view them with a text editor.

For complete information on the new EJB implementation, see BEA WebLogic Server Enterprise JavaBeans at http://www.weblogic.com/docs51/classdocs/API_ejb/index.html.


n Issue 7813. A multithreaded client accessing an entity bean with findByPrimaryKey(Non-Existent-Pk) no longer fails.

n Issue 6004. The error message that is displayed when binding the same name twice is clearer.

n Issue 5888 and 5890. Stateful session bean instances are not destroyed after an exception has been thrown.

n Issue 5607. A new deployment no longer wipes out an existing EJB deployment.

n Issue 5591. The method new Instance() is now called after ejbCreate().


http://www.weblogic.com/docs51/classdocs/API_ejb/index.html

http://www.weblogic.com/docs51/classdocs/API_ejb/index.html

http://java.sun.com/products/ejb/index.html


http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd

http://www.bea.com/servers/wls510/dtd/weblogic-rdbms-persistence.dtd

n If you build an example EJB with the supplied build scripts and deploy it, you can now run the build script again and redeploy the bean from the same .jar without getting an error.

n The server no longer throws a NullPointerException when the transactionAttribute of a stateless session bean’s ejbCreate() method is marked either TX_REQUIRED or TX_REQUIRES_NEW and ejbCreate() throws an exception.

n The EJB deployment utility program weblogic.deploy now allows deployment of the same bean more than once.

n Binding the same name more than once does not throw an exception.

Java Database Connectivity Changes (JDBC 2.0)

JDBCKONA JDBC DRIVERS RENAMED

The following JDBC drivers have new names:

DATASOURCE

A DataSource object provides a way to obtain a JDBC connection from a connection pool using a JNDI lookup. For details, see Using a DataSource object to get a JDBC connection at http://www.weblogic.com/docs51/classdocs/DataSource.html.

JDBC/RMI AND CLUSTERED JDBC

A new JDBC/RMI driver has been added to WebLogic Server. This is a three-tier driver that operates with WebLogic Server using a DataSource object. When this driver is used in a cluster of WebLogic Servers, it can be configured to provide

Old Name New Name

jdbcKona/Oracle BEA WebLogic jDriver for Oracle

jdbcKona/MSSQLServer4 BEA WebLogic jDriver for Microsoft SQL Server

jdbcKona/Informix4 BEA WebLogic jDriver for Informix


http://www.weblogic.com/docs51/classdocs/DataSource.html

http://www.weblogic.com/docs51/classdocs/DataSource.html

Clustered JDBC. Clustered JDBC provides failover and load balancing for JDBC connections. For more information, see Using WebLogic JDBC/RMI and WebLogic Clustered JDBC at http://www.weblogic.com/docs51/classdocs/JDBC_RMI.html.

JTS DRIVER

The following issues have been resolved in this release:

Issue 6232. Problems were fixed with JTS synchronization during timeout handling and rollback problems with JTS/JDBC on multiple servers. Stricter illegal-state checking was also introduced.

Issue 7999. The JTS driver now creates an explicit T3Client to pass to the t3 driver. This ensures correct propagation of security information through JTS/JDBC driver. It also improves performance by caching T3Clients internally.

JDBCKONA/ORACLE

The jdbcKona/Oracle driver has been updated to incorporate some of the features available in Oracle 8, such as Blobs and Clobs, and also for new features available in the JDBC 2.0 specification. Using JDBC 2.0 requires that you run your driver with a JDK 1.2.x JVM.

JDRIVER FOR ORACLE AVAILABLE FOR THE HP-UX 11 PLATFORM.

WebLogic jDriver for Oracle (formerly called jdbcKona/Oracle) is now available for the HP-UX 11 platform for Oracle client versions 8.0.4 and 8.1.5. For more information, see Installing WebLogic jDriver for Oracle at http://www.weblogic.com/docs51/install/install_jdbc.html.

For information on using new Oracle 8 and JDBC 2.0 features, see the Developer Guides Using WebLogic jDriver for Oracle at http://www.weblogic.com/docs51/classdocs/API_joci.html.


http://www.weblogic.com/docs51/classdocs/JDBC_RMI.html

http://www.weblogic.com/docs51/classdocs/JDBC_RMI.html


http://www.weblogic.com/docs51/install/install_jdbc.html

Java Message Service

SUPPORT FOR FULLY QUALIFIED TABLE NAMES

A new property, weblogic.jms.tableNamePrefix, allows you to specify a prefix to add to the database table names when WebLogic Server accesses the JMS tables in a DBMS. This is useful for DBMSs that require fully qualified names when accessing tables. This property can also be used to host multiple sets of JMS tables within the same DBMS. For additional information, see Using WebLogic JMS at http://www.weblogic.com/docs51/classdocs/API_jms.html.

JMS ISSUES RESOLVED IN THIS RELEASE


n Issue 9396. Using DEFAULT_PRIORITY no longer causes an exception.

n Issue 7547. Expired queue messages are now properly cleaned from the JMS tables.

n Issue 7386. A problem with construction of JMS QueueRequestor was fixed. Previously an NPE would sometimes be thrown.

n Issue 6676. JMS messages 1MB or greater in size and sent at a frequency of 1 second or less no longer cause the JMS client to hang.

n The example documentation has been updated to explicitly point out all properties that must be set. The transaction timeout has also been fixed by only starting the transaction if the message received is an instance of MapMessage.

Java Naming and Directory Interface Changes (JNDI 1.2)

WebLogic Server now supports the JNDI 1.2 specification.

Java Server Pages Changes (JSP 1.1)

WebLogic Server supports the JSP 1.1 specification.


n Issue 9673. The JSP Servlet initialization argument packagePrefix is now supported. Using this argument will no longer cause JSP to break, throwing a


http://www.weblogic.com/docs51/classdocs/API_jms.html

http://www.javasoft.com/products/jndi/docs.html

http://java.sun.com/products/jsp/

ClassNotFoundException when requesting the JSP page. There is no need to remove the packagePrefix argument from your existing weblogic.properties file.

n Issue 9457. The JSP example EJBeanManagedClient has been fixed. The workaround is no longer necessary.

n Issue 9260. When a bean is used for more than one time, that is, it has no class attribute, the usebean tag can now be split over multiple lines without causing a an exception.

n Issue 8728. Previously generated JSP servlets are now compatible with the new implementation.

n Issue 8325. Fixed a problem with pre-compilation of JSPs at boot time. This is provided for web applications, and is turned on with a WebLogic-specific context parameter specified in the WAR’s web.xml file. For example:

 <context-param> <param-name>wl-jsp-precompile</param-name> <param-value>true</param-value> </context-param>

Additionally, all of the initParams to the JSPServlet (compileCommand, encoding, keepgenerated, etc.) can be specified via similar context params that all start with wl-jsp-*. These are illustrated in examples that have a web.xml file.

n Issue 7902. JSP Compiler running in the server no longer fails to pass the directory name to the Java compiler when there are spaces in the directory name.

n Issue 7661. A java.lang.StringIndexOutOfBoundsException is no longer thrown when compiling JSP files that have a section between two include tags that is exactly 1024 characters.

n Issue 7587. You can now use the flush attribute of jsp:include. Although the specicification mandates the flush attribute, it is still optional in the WebLogic JSP implementation.

n Issue 6240. When requesting a JSP page, your request should match the case formatting of the JSP file exactly. The known problems for this issue have been resolved in this release.

Remote Method Invocation Changes

REMOTE METHOD INVOCATION (RMI) OVER IIOP

WebLogic RMI over IIOP extends the RMI programming model by providing the ability for clients to access RMI remote objects using the Internet Inter-ORB Protocol (IIOP). This exposes RMI remote objects to a new class of client, the Common Object Request Broker Architecture (CORBA) client. CORBA clients can be written in a variety of languages including C++, SmallTalk, and Java. For additional information, see Using WebLogic RMI over IIOP at http://www.weblogic.com/docs51/classdocs/API_rmi_iiop.html.

Note: RMI over IIOP is currently offered only with version 1.3 JDKs.

Additional classpath requirements have been added for running the WebLogic RMI and EJB compilers with the -idl option. For additional information, see the Generate the IDL file section of Using RMI over IIOP at http://www.weblogic.com/docs51/classdocs/API_rmi_iiop.html .

RMI ISSUES RESOLVED IN THIS RELEASE


n Issue 7591. Unreferenced is now called appropriately.

n RMI Cluster. Setting either homeCallRouterClassName or statelessCallRouterClassName to a non-existent class no longer causes an AssertionError.

Servlet Changes

SERVLET 2.2

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, with the following exceptions:


http://www.weblogic.com/docs51/classdocs/API_rmi_iiop.html

http://java.sun.com/products/servlet/2.2/index.html

http://www.weblogic.com/docs51/classdocs/API_rmi_iiop.html

http://www.weblogic.com/docs51/classdocs/API_rmi_iiop.html#generateIDL

http://www.weblogic.com/docs51/classdocs/API_rmi_iiop.html#generateIDL

http://java.sun.com/products/servlet/2.2/index.html

n It is now recommended that HTTP servlets do not implicitly close or flush the servlet response. Following this convention will improve performance since persistent HTTP 1.1 connections can be used automatically by the server.

SERVLET ISSUES RESOLVED IN THIS RELEASE


n Issue 9720. Under Solaris JDK 1.1, running jsp/SessionServlet.jsp no longer throws ClassCastException when storing a session value.

n Issue 9424. A problem previously occurred with the <jsp-file> element instead of the <servlet-class> element in a <servlet> element of a web.xml descriptor. The server previously threw a NullPointerException such as: “<E> <ServletContext-cookie> Servlet failed with RuntimeException.” This problem has been fixed.

n Issue 9138. The name of the variable JDK_HOME has changed to JAVA_HOME. This variable no longer causes a problem.

n Issue 8326. The <welcome-file-list> element from the web.xml deployment descriptor is no longer ignored in this release.

n Issue 7657. The 0 bytes read problem in HTTP tunneling is now fixed. For more information, see Using WebLogic HTTP Servlets at http://www.weblogic.com/docs51/classdocs/API_servlet.html.

n Issue 7193. An issue where the query string data was handled inconsistently when running servlets with the ServerSideIncludeServlet is fixed.

n Issue 7002. The method HttpSession.getValueNames()no longer returns null if there are no parameters in the session. This method is now in agreement with the servlet specification which states that it should return an empty String[].

n Issue 6926. The method javax.servlet.ServletContext.getResourceAsStream()now complies with the Servlet 2.1 specification.

n Issue 5601. A problem with the Performance Pack occasionally killing the HTTPJVMSocket at inappropriate times has been fixed.


http://www.weblogic.com/docs51/classdocs/API_servlet.html

JDBC Changes

For information on using new Oracle 8 and JDBC 2.0 features, see Using WebLogic jDriver for Oracle at http://www.weblogic.com/docs51/classdocs/API_joci.html and the jdbcKona/Oracle in the Upgrade section of these release notes.

JDRIVER FOR ORACLE AVAILABLE FOR THE HP-UX 11 PLATFORM.

WebLogic jDriver for Oracle (formerly called jdbcKona/Oracle) is now available for the HP-UX 11 platform for Oracle client versions 8.0.4 and 8.1.5. For more information, see Installing WebLogic jDriver for Oracle at http://www.weblogic.com/docs51/install/install_jdbc.html.

The procedure for using Oracle Blobs and Clobs requires that you cast the Blob or Clob object to weblogic.jdbc20.common.OracleClob or weblogic.jdbc20.common.OracleBlob.


n Issue 8437. (jDriver for Oracle on the Solaris platform only) There was a duplicate copy of libweblogicoci36.so in the directory weblogic/lib/solaris. If this directory was included in your ld_library_path, it no longer causes an incorrect version of the jdbcKona/Oracle driver to be loaded. For details on setting your ld_library_path, see Installing WebLogic jDriver for Oracle at http://www.weblogic.com/docs51/install/install_jdbc.html.

JCONNECT DRIVER FOR SYBASE NOW BUNDLED WITH WEBLOGIC SERVER

n The jConnect type 4 JDBC driver for Sybase is now bundled with WebLogic Server. For information on using this driver, see Using the Sybase jConnect Driver at http://www.weblogic.com/docs51/classdocs/jConnect.html.

Security Changes

Many improvements have been made to WebLogic Server 5.1 security. Here is a summary of the important new security features.






http://www.weblogic.com/docs51/classdocs/jConnect.html


WebLogic Security Realms and New CachingRealm

The WebLogic Server security realm architecture has been redesigned to make pluggable realms easier to develop, deploy, and manage. A new CachingRealm (http://www.weblogic.com/docs51/admindocs/cachingrealm.html) delegates to an alternative realm that extends AbstractListableRealm or AbstractManageableRealm. If the custom realm does not find a result for a lookup, CachingRealm falls back to the weblogic.properties file. CachingRealm also provides configurable caching to improve the realm’s performance.

The NTRealm (http://www.weblogic.com/docs51/admindocs/ntrealm.html) (for Windows NT) and LDAPRealm (http://www.weblogic.com/docs51/admindocs/ldap.html) (for Netscape Directory Server and Microsoft Site Server) have been revised to extend the new AbstractListableRealm. LDAPRealm no longer uses EJBs for its caching, so it is now possible to use LDAPRealm with WebLogic Express.

A new UnixRealm (http://www.weblogic.com/docs51/admindocs/unixrealm.html) (supported on Solaris, HP-UX 11.0, and Linux for this release) provides UNIX authentication for WebLogic Server clients. Authorization uses ACLs in the weblogic.properties file. UnixRealm depends upon a small setroot binary, wlauth, to process authentication requests from WebLogic Server. The wlauth program uses PAM (Pluggable Authentication Modules) on operating systems that have it, or the standard password authentication libraries on other platforms.

The RDBMSRealm example (http://www.weblogic.com/docs51/examples/security/rdbmsrealm/index.html) has been thoroughly revised. It is now a fully-supported alternative realm for WebLogic Server, as well as a model for developing custom realms. As part of the revision, the rdbmsrealm.CachingRealm class and the defaultrealm example are gone, replaced by CachingRealm. An option to encrypt passwords in the database has been added. The utils.Schema utility is now used to initialize the realm’s tables in the database in place of code in RDBMSRealm from previous releases.

A DelegatingRealm example (http://www.weblogic.com/docs51/examples/security/delegatingrealm/index.html) shows how you can delegate authentication and authorization requests to multiple security realms. You configure DelegatingRealm to delegate specific realm methods to one or more realm classes, which are tried in the sequence you specify. You could use this feature to allow WebLogic Server access to multiple external realms, or use it to implement a failover for your primary security realm.


http://www.weblogic.com/docs51/admindocs/cachingrealm.html

http://www.weblogic.com/docs51/admindocs/ntrealm.html

http://www.weblogic.com/docs51/admindocs/ldap.html

http://www.weblogic.com/docs51/admindocs/unixrealm.html

http://www.weblogic.com/docs51/examples/security/rdbmsrealm/index.html

http://www.weblogic.com/docs51/examples/security/delegatingrealm/index.html

The SnoopProof realm example has been removed for security reasons. We recommend that you do not migrate forward any applications that you may have built using this example.

The weblogic.security.acl.Security class has a new doAsPrivileged() method that can be used to temporarily switch to a different WebLogic user and run some server-side code. doAsPrivileged() is called with a UserInfo containing the login information of the new User and a class that implements either the weblogic.security.acl.PrivilegedAction interface or the weblogic.security.acl.PrivilegedExceptionAction interface. Both of interfaces define a run() method that returns an Object. Use PrivilegedAction only for code that does not throw any checked exceptions; otherwise, use PriviledgedExceptionAction.

When you call doAsPrivileged(), WebLogic Server attempts to authenticate the UserInfo. If the realm returns an authenticated User, the new User is pushed onto the thread and the run() method is called. When run() returns, the new User is popped from the thread, restoring the original User. If the UserInfo cannot be authenticated, a SecurityException is thrown.

A new Auditing interface has been added. Implement this interface to receive and process notifications of security events such as authentication requests, failed or successful authorization attempts, and receipt of invalid certificates. Your class can filter the events and send messages wherever you choose. The LogAuditProvider example (http://www.weblogic.com/docs51/examples/security/audit/index.html) writes audit messages in the WebLogic Properties file.

A new weblogic.security.net.ConnectionFilter interface (http://www.weblogic.com/docs51/classdocs/javadocs/weblogic/security/net/ConnectionFilter.html) has been added to allow you to accept or reject WebLogic Server client connections based on the client’s origin and protocol. After a client connects, and before any work is performed on behalf of the client, WebLogic Server passes the client’s IP number and port, protocol (HTTP, HTTPS, T3, T3S, IIOP), and WebLogic Server port number to your ConnectionFilter implementation. By examining this information, you can choose to allow the connection to continue or throw a FilterException to terminate the connection. The SimpleConnectionFilter example (http://www.weblogic.com/docs51/examples/security/net/index.html) shows how to use this interface. It reads a “rules” configuration file and constructs an efficient rules engine to filter connection requests.


http://www.weblogic.com/docs51/examples/security/audit/index.html

http://www.weblogic.com/docs51/classdocs/javadocs/weblogic/security/net/ConnectionFilter.html

http://www.weblogic.com/docs51/examples/security/net/index.html

Access Control Lists

A new weblogic.security.urlAclFile lets you create a policy file that guards access on files with much finer control than is possible with the weblogic.properties file. In the policy file, you grant or deny users and groups permissions on files and directories, using a policy file syntax patterned after the Java Authentication and Authorization Service (JAAS). WebLogic Server tests the permissions specified in the policy file before granting access to a resource.

See Controlling access on URLs at http://www.weblogic.com/docs51/admindocs/urlacl.html for details.

WebLogic SSL

Note: The SSL 56-bit license is included in this release. In order to get a 128-bit SSL license, please contact [email protected].

New weblogic.security.clientRootCA properties have been added so that you can specify up to four certificate authorities to use for two-way authentication. The last three properties are new in this release:

weblogic.security.clientRootCA=CACert1 weblogic.security.clientRootCA2=CACert2 weblogic.security.clientRootCA3=CACert3 weblogic.security.clientRootCA4=CACert4

To authenticate successfully, a client must present a certificate signed by one of the specified certificate authorities.

A new weblogic.security.ciphersuites property allows you to specify the ciphersuites that may be offered on SSL connections. WebLogic Server and the client negotiate the ciphersuite to use when establishing a connection, selecting the most secure suite available to both.

The Acl http://www.weblogic.com/docs51/examples/security/acl/index.html example has a new client program, AltClient.java, which demonstrates how to get a secure SSL connection with JNDI using two-way authentication.

A new CertAuthenticator interface has been added. By implementing this interface and setting the weblogic.security.realm.certAuthenticator property in the weblogic.properties file, you can map the client certificate presented during two-way SSL authentication to a WebLogic Server user. The new SimpleCertAuthenticator example



http://www.weblogic.com/docs51/examples/security/acl/index.html

http://www.weblogic.com/docs51/classdocs/javadocs/weblogic/security/acl/CertAuthenticator.html

mailto:[email protected]

(http://www.weblogic.com/docs51/examples/security/cert/index.html) demonstrations how to implement this interface. It maps the name from the email address in the Certificate to a WebLogic Server user.

Simple Network Management Protocol Support

WebLogic Server now provides an SNMP link to SNMP-compliant management systems. Integrating WebLogic Server with SNMP allows you to effectively manage all of your large-scale applications using the SNMP-compliant network management tool of your choice. Since most management platforms support SNMP today, the WebLogic Server SNMP Agent can be integrated into virtually every management framework. Examples of such systems include:

n HP OpenView

n IBM Tivoli, NetView

n Sun Domain/SunNet/Site Manager

n CA Unicenter

SNMP manageability of WebLogic Server provides the following benefits:

n Enables you to move towards a single management console and thus provide integrated systems management of WebLogic Server based applications.

n Connects WebLogic Server to popular management systems such as HP OpenView, Sun SunNet Manager, and IBM NetView. This makes managing WebLogic Server more effective by providing a whole-system perspective instead of piecemeal solutions.

n Preserves your standard-based, compliant (SNMP-capable) management frameworks.

n Enables you to benefit from the experience of the large community of SNMP users.

The WebLogic Server agent will enable you to remotely monitor the status of your server or server cluster. It will report statistics including the availability of your server, the number of connections, and the average queue length.

For more information on WebLogic Server SNMP, see:


n WebLogic Server SNMP Agent at http://www.weblogic.com/docs51/admindocs/snmpagent.html

n BEA Manager 2.0, found at the BEA Documentation website http://edocs.beasys.com/

Third Party Products-Related Changes

For more information see Using WebLogic Server with third party software at http://www.weblogic.com/docs51/classdocs/3rdparty.html.

Visual Age

For information on using Visual Age with WebLogic Server, see Using the Integration Kit for Visual Age at http://www.weblogic.com/docs51/classdocs/visualAge.html.

VisualCafe/Webgain Studio

For information on using VisualCafe with WebLogic Server, see Using VisualCafé Enterprise Suite with WebLogic at http://www.weblogic.com/docs51/classdocs/vcafe.html.

Third Party-Related Issues Resolved in this Release

If you are using any third party containers or vendor products with the WebLogic Server, or any EJB-related tools (ejbc, DDCreator, ComplianceChecker, or EJB DeployerTool), you will need to specify the property weblogic.home when you start the Weblogic Server or the WebLogic tool, as shown in this example for Windows NT:

$java ... -Dweblogic.home=c:\weblogic... weblogic.Server

where weblogic.home is the root directory of your WebLogic installation. This is usually the same directory specified by the property weblogic.system.home, which sets the directory where WebLogic Server finds the global weblogic.properties file. If you locate your weblogic.properties files outside of the WebLogic installation, you need to redefine the weblogic.home property so that products from third party vendors can find the WebLogic installation.



http://www.weblogic.com/docs50/admindocs/snmpagent.html

http://edocs.beasys.com/

http://www.weblogic.com/docs51/classdocs/3rdparty.html

http://www.weblogic.com/docs51/classdocs/visualAge.html

http://www.weblogic.com/docs51/classdocs/visualAge.html

http://www.weblogic.com/docs50/classdocs/vcafe.html

http://www.weblogic.com/docs50/classdocs/vcafe.html

n Issue 7128. Problem fixed with startWebLogicJview.cmd not putting cloudscape.jar into the CLASSPATH.

Jolt for WebLogic Changes

Jolt has been updated to support WebLogic Server 5.1.

For this release we have updated the Jolt documents and added direct links to the Jolt User’s Guide at http://edocs.beasys.com/tuxwle/jolt12/insgd/jinstc2.htm.

With BEA Jolt for WebLogic, you can enable BEA Tuxedo services for the Web, using WebLogic Server as the front end HTTP and application server. Jolt is a Java-based client API that manages requests to BEA Tuxedo services via a Jolt Service Listener (JSL) running on the Tuxedo server. The Jolt API is embedded within the WebLogic API, and is accessible from a servlet or any other WebLogic application.

Because Jolt for WebLogic is an extension to the Jolt Java class library, the Jolt Java client class library can be used in HTTP servlets running in WebLogic Server. Jolt for WebLogic also uses Java HTTP servlets to provide an interface between HTML browser clients and BEA Tuxedo services.

Key features of the Jolt for WebLogic architecture include:

n Enabling the use of Java HTTP servlets to provide a dynamic HTML front-end for Tuxedo applications

n Providing session pooling to use Tuxedo resources efficiently

n Supporting transactions

n Integrating session pool management into the WebLogic Console.

The new documentation also includes sections on how to use the examples provided with your distribution of WebLogic Server.

WebLogic Enterprise Connectivity Changes

WebLogic Enterprise Connectivity is supported in this release. There are no new features.


http://edocs.beasys.com/tuxwle/jolt12/insgd/jinstc2.htm


Example Changes

For late-breaking examples and additional help with creating your applications, see our new Additional Examples page at http://www.weblogic.com/docs51/zips/index.html.


n Issue 9886. On Solaris, running the examples.jms.topic.TopicSend example client no longer produces a NullPointerException on WebLogic Server.

n Issue 9885. The jms.drawdemo example no longer throws a server side ClassCastException.

n Issue 9878. A NullPointerException is no longer thrown when running JMS PoolReceive example.

n Issue 9874. The ejb.basic.beanManaged example no longer throws a SecurityException.

n Issue 9832. The examples/ejb/basic/statelessSession bean example no longer throws a ProcessingErrorException.

n Issue 9875. The examples.jolt.ejb.bankapp.Client no longer throws examples.jolt.ejb.bankapp.TransactionErrorException.

n Issue 9769. Case sensitivity no longer causes a problem when running the jsp/tagext/sql example. You must change the attribute names from poolName to poolname and from fromQuery to fromquery.

n Issue 9720. The jsp/SessionServlet.jsp no longer throws a ClassCastException when storing a session value.

n Issue 9449. The JSP tagextcounter example has been fixed. It now uses a temporary working directory determined by the servlet context.

n Issues 8981 and 4668. The utils.Schema utility no longer attempts to execute blank lines at the end of a DDL file, causing an SQLException to be thrown.

n Issue 8473. The Jolt EJBean example, example.jolt.ejb.bankapp, has been fixed. The previous error concerned how the bean properties are extracted from JNDI.

n Issue 6839. The example examples.jdbc.t3client.bigblob, which uses a Sybase DBMS, now runs correctly on the Solaris platform.


http://www.weblogic.com/docs51/zips/index.html

n Incompatibilities with the browser JVMs and examples that use applets have been fixed. The examples will now work properly if you are running the server using JDK 1.2 or later. To deploy applets from a server running with JDK 1.2, you should install the Java Plug-in (http://java.sun.com/products/plugin/1.2/docs/index.docs.html ).

n In examples.xml.http, an error in the traderesult.dtd has been fixed so that the client application longer produces the following error:

[Error] :3:-1: Attribute "numShares" is not declared for element

New Examples

The following examples have been added in this release:

n Examples for using XML with WebLogic Server.

n New examples for web applications using cookies.

n Java plug-in versions of example applet html pages.

n Examples for using Java Plugin v1.1.3 and Java Plugin v1.2 from HTML and JSP files.

n The example jolt_ejb_bankapp.jar has been converted for use with EJB 1.1.

n New examples For JDBC DataSource and Oracle Blobs and Clobs.

n Examples for using the new security custom realms architecture, security auditing, certificate authentication, and network connection filtering features.

n The examples that accompany Introduction to WebLogic Server at http://www.weblogic.com/docs51/install/index.html have been included in the distribution. The EJB is upgraded to EJB 1.1 and the JDBC Java client example uses the new JDBC DataSource.

Deprecated Examples

n These examples have been removed:

l jndi.LDAPSearch

l security.carealm

l weblogic.html.FormServlet


http://java.sun.com/products/plugin/1.2/docs/index.docs.html



http://www.weblogic.com/docs51/install/index.html

l Utilities.sendMail

l event.stocks.MailStockInfo

l servlets.MailServlet

l WLSerializable

l WLObjectOutput

l WLObjectInput

l InitialContextExample

l SimpleProviderClient

l SimpleProviderServer

l SnoopProof realm

l defaultrealm

l ejb_sequence_oracle.jar

l The EJB “sequence” example is not included in this version of WebLogic Server.

Tour Changes

The tour has been fixed for this release. It is available from the Windows Start Menu.

Documentation Changes

New Documentation Features

n New design templates have been applied to all documentation on our web site.

n New PDF documents are available on our PDF page at http://www.weblogic.com/docs51/API_users_guide.html. You will need a copy of Adobe Acrobat Reader to view and print these files. You can go directly to the Adobe web site or use the link provided from the PDF page.

n For late-breaking examples and additional help creating your applications, see our new Additional Examples page at http://www.weblogic.com/docs51/zips/index.html.


http://www.weblogic.com/docs51/zips/index.html

ttp://www.weblogic.com/docs51/API_users_guide.html

n The Frames version of the documentation is no longer distributed.

New Documentation

n Documentation for Using WebLogic Server Clusters has been improved for this release.

n Documentation and examples have been added for Writing a Web Application at http://www.weblogic.com/docs51/classdocs/webappguide.html and Web Application (WAR) examples at http://www.weblogic.com/docs51/examples/webapp/index.html.

n For this release we have updated the Jolt documentation, which includes direct links to the http://edocs.beasys.com/tuxwle/jolt12/insgd/jinstc2.htm Jolt User’s Guide.

n For this release we have updated the JSP documentation, Using WebLogic JSP, at http://www.weblogic.com/docs51/classdocs/API_jsp.html.

Installation

The following Installation documentation has been updated for this release:

n The Overview of Installing WebLogic Server 5.1 at http://www.weblogic.com/docs51/install/install_overview.html.

n Introduction to WebLogic Server at http://www.weblogic.com.

n Testing Connections at http://www.weblogic.com/docs51/techstart/dbping.html.

n Installing WebLogic to Netscape Plugin.

n Installing WebLogic jDriver for Oracle at http://www.weblogic.com/docs51/install/install_jdbc.html.

JDBC

The following JDBC documentation has been updated for this release:

n WebLogic JDBC Options at http://www.weblogic.com/docs51/classdocs/jdbcdrivers.html


http://www.weblogic.com/docs51/classdocs/API_jsp.html

http://www.weblogic.com/docs51/examples/webapp/index.html

http://www.weblogic.com/docs51/examples/webapp/index.html

http://www.weblogic.com/docs51/classdocs/webappguide.html

http://www.weblogic.com/docs51/admindocs/nsapi.html



http://www.weblogic.com/docs51/classdocs/jdbcdrivers.html

http://www.weblogic.com/docs51/cluster/index.html


http://www.weblogic.com/docs51/techstart/dbping.html

http://www.weblogic.com/docs51/intro/index.html

http://www.weblogic.com/docs51/install/install_overview.html

An overview of WebLogic JDBC drivers and related information. These documents include links to information on using the WebLogic jDrivers, 3rd party information, and more.

n Using the Sybase jConnect driver at http://www.weblogic.com/docs51/classdocs/jConnect.html.

Sybase’s jConnect driver is now bundled with WebLogic Server.

n Using the Oracle Thin Driver with WebLogic Server at http://www.weblogic.com/docs51/classdocs/oraclethin.html.

How to use Oracle’s thin JDBC driver with WebLogic Server

n Javadocs for WebLogic JDBC extensions are not available with this release.

Security

A new index to the WebLogic Server Security Guides has been included with this release at http://www.weblogic.com/docs51/classdocs/securityguide.html.

Another new document to help with locking down a WebLogic Server deployment has been added. See Securing a WebLogic Server Deployment at http://www.weblogic.com/docs51/admindocs/lockdown.html.

Wireless Application Protocol

Documentation has been added for the new WAP feature of WebLogic Server, Using Wireless Application Protocol (WAP) with WebLogic Server at http://www.weblogic.com/docs51/classdocs/wap.html.

Other documents have been updated as needed.


http://www.weblogic.com/docs51/admindocs/lockdown.html

http://www.weblogic.com/docs51/classdocs/wap.html

http://www.weblogic.com/docs51/classdocs/wap.html


http://www.weblogic.com/docs51/classdocs/oraclethin.html



Known Issues with BEA WebLogic Server 5.1

This document lists problems you should be aware of in the 5.1 release.

n EJB Issues

n WebLogic Server Tools and Wizards Issues

n Servlets Issues

n JMS Issue

n Licensing Keys Issue

n jDriver for Oracle Issues

n Remote Method Invocation (RMI) over IIOP Issues

n WebLogic Server Issues

n Cloudscape Evaluation Version 2.0.1

n Examples Issues

EJB Issues

n 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.

n 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.

n Issue 9902. Spaces in file and directory names in the classpath cause ejbc and rmic to fail.

n 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.

n 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.

n 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.

n 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.

n 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.

n 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.

n 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.

n 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.

n 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.”

n 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.

n Issue 5997. Container-managed JDBC persistence uses an inappropriate stack trace.

n 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

n 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

n 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.

n Issue 9628. The <load-on-startup> XML tag is not honored.

n Issue 9150. HTTP tunneling through a Network Address Translating firewall is not supported in this release.

n 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.

n 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:


l Specify the -noverify command-line option when starting the Server under Java 2 v1.2.1

JMS Issue

n 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

n 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 at http://www.weblogic.com/docs51/techstart/license.html.

jDriver for Oracle Issues

n 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.

n Issue 9431. WebLogic jDriver for Oracle is not supported when using the Oracle 8 API and connecting to an version 7 Oracle DBMS.

n 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.


http://www.weblogic.com/docs51/techstart/license.html

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);

n 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:

l Oracle 8.0.5 Client running on HP connecting to an Oracle 8.1.5 DBMS running on Windows NT or Solaris.

l Oracle 8.1.5 client running on HP connecting to an Oracle 8.1.5 DBMS running on Solaris.

n Issue 9708. Using the CLOB datatype and using codeset conversions while running the Oracle client and Oracle server on different operating systems will fail.

n 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:

n Return values and parameters are limited to RMI value types.

n 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

n 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.

n Issue 9731. Possible security-related IOException when clients are multi-threaded. The exception is: java.io.IOException: weblogic.security.SSL.BadMACException.

n 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.

n Issue 7127 and 5730. The server will occasionally print erroneous “SocketException: bad file number” messages in the log file. These messages can be ignored.


n 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

n 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 at http://www.weblogic.com/docs51/techsupport/cloudscape.html and Setting up and Starting WebLogic Server at http://www.weblogic.com/docs51/install/startserver.html.

n 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

n Issue 9887. In order to run the JMS examples examples.jms.sessionpool, examples.jms.trader, and examples.jms.startup, you must un-comment


http://www.weblogic.com/docs51/techsupport/cloudscape.html

http://www.weblogic.com/docs51/techsupport/cloudscape.html



http://developer.java.sun.com/developer/bugParade/bugs/4134584.html

the following line in you weblogic.properties file: weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone.

n 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.

n 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:

l applications in the examples/intro directory that use the Emp EJB

l examples/xml/jms

l examples/xml/biztalk

l examples/jms

l examples/ejb

EJB Example Issues

EJB example applications exhibit the following problems in this release:

n 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.

n 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.

n 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:


http://developer.java.sun.com/developer/bugParade/bugs/4134584.html

<!DOCTYPE ejb-jar PUBLIC ’-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN’ ’http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd’>

n 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.

n 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.


bea weblogic server - freie universität...bea weblogic server release notes v contents introducing...

Documents