Known Issues in WebLogic Server 7.0 Service Pack 7
WebLogic Server 7.0 Service Pack 7 has the following known issues:
Core Server Known Issues
Change Request Number
Description
Release Fixed
CR174779
Requests from an existing session are directed to the primary server even after the primary server starts to shut down.
Workaround: Refesh the page after a short duration.
EJB Known Issues
Change Request Number
Description
Release Fixed
CR262695
Fully classified class names are not generated in the ejb.xml and weblogic-cmp-rdbms-jar.xml deployment descriptor files. Instead, only simple class names are generated for method param values.
Workaround: When using unloadable classes in your EJBs, manually edit the deployment descriptor files to refer to those EJBs with their fully classified names.
JTA Known Issues
Change Request Number
Description
Release Fixed
CR259037
When a transaction times out at logging time, you could experience a deadlock situation. The thread that is trying to write the transaction to the transaction log (TLOG) times out, a different thread trying to execute the rollback to clean the same transaction from the TLOG and deadlock each other.
Workaround: Decrease the value of the CheckpointIntervalSeconds attribute and move TLOGs to a directory where they will not run out of memory.
RMI Known Issues
Change Request Number
Description
Release Fixed
CR258722
WebLogic Server 6.1 has some limitations when acting as a client to WebLogic Server 7.0 SP7 over the IIOP protocol. This is because WebLogic Server 6.1 does not support class evolution, so only identical classes can be passed between WebLogic Server 6.1 and WebLogic Server 7.0 SP7.
Workaround: Be aware of this issue.
CR261149
Remote requests over IIOP that involve medium to large size Strings may be a little slower in WebLogic Server 7.0 SP7 when compared to 7.0SP6. This is due to changes in JDK 1.4.2_10, which is being used in WebLogic Server 7.0SP7.
Workaround: Pass the XX:+UseTLAB JVM option flag. This flag turns on thread-local memory allocation. This flag is enabled by default only for the server VM on SPARC.
Upgrade Known Issues
Change Request Number
Description
Release Fixed
CR265197
A License exception occurs when you start WebLogic Server after upgrading from any previous WebLogic Platform 7.0 release to WebLogic Platform 7.0 SP7 using the WebLogic Platform or WebLogic Server upgrade installer.
This problem occurs only when you use the evaluation license, and only on a HP-UX system.
Workaround: Replace the license.bea file in the BEA_HOME directory with the evaluation license file that is generated by installing WebLogic Platform or WebLogic Server 7.0 SP7 using the full installer.
Known Issues in WebLogic Server 7.0 Service Pack 6
WebLogic Server 7.0 Service Pack 6 has the following known issues:
Administration Console Known Issues
Change Request Number
Description
Release Fixed
CR213792
The help information for defining security roles and security policies for EJBs is missing from the Administration Console in this release of WebLogic Server. For information about assigning security roles and security policies to EJBs, see Securing WebLogic Resources.
CR215117
The attribute, JavaVMVendor (of weblogic.management.runtime.JVMRuntimeMBean), was added to the Administration Console server monitoring versions page for WebLogic Server 7.0 Service Pack 6.
There is currently no corresponding popup for it in the Administration Console online help. As a result, a 404 error occurs when an attempt is made to access the online help popup for this attribute.
JDBC Known Issues
Change Request Number
Description
Release Fixed
CR192616
The API getXAConnection() through the net driver is not supported in the IBM DB2 UDB type 2 JDBC 2.0 driver.
It is recommended that you use a different driver that supports the getXAConnection() API.
Plug-ins Known Issues
Change Request Number
Description
Release Fixed
CR217777
Deadlock occurs in Apache HTTP Server plug-in under load.
Problem: When using the Apache HTTP Server plug-in for distributing client connection requests to WebLogic Server instances in a cluster, clients may be unable to connect to the cluster and the following message is logged in the Apache HTTP Server plug-in:
[error] server reached MaxClients setting, consider raising the MaxClients setting
This problem occurs under load.
Platform: All
Workaround: When configuring the Apache HTTP Server plug-in, set the value for the MaxClients parameter in the httpd.conf configuration file to be equivalent to the number of client connections that the cluster needs to be able to support.
For more information about configuring the Apache HTTP Server plug-in, see "Installing and Configuring the Apache HTTP Server Plug-In" in Using Web Server Plug-Ins with WebLogic Server at the following URL:
Known Issues in WebLogic Server 7.0 Service Pack 5
WebLogic Server 7.0 Service Pack 5 has the following known issues:
Core Server Known Issues
Change Request Number
Description
Release Fixed
CR123714
Network classloading can fail when multiple servers, each with its own Network Interface Card, are operating in a single cluster or domain.
Failures occur because in the JVMID of the server the hostAddress is always assumed to be the default channel address. The client uses RJVMImpl.getCodeBase to locate the URL from which to download the class, tries to connect to the default channel, and fails.
In 8.1 the hostAddress of the JVMID is based on the channel the request comes from, and thus the hostAddress correctly registers the address of the channel.
8.1
CR079543, CR084568
On Unix, some server start scripts will fail if the name of the directory in which you install WebLogic Server (BEAHOME) contains a space.
Cluster Known Issues
Change Request Number
Description
Release Fixed
CR168598
In WebLogic Server 7.0, the Managed Server starts in the same mode as the Administration Server even if you specify a different mode on Managed Server startup.
For example, if you start the Administration Server in development mode and then start the Managed Server with a command line option of -Dweblogic.ProductionModeEnabled=true, the Managed Server still starts in development mode.
The Managed Server starts up in production mode only when Administration Server has been started in production mode.
CR135944, CR100373, CR130592, CR135864
Staged one-phase applications on a Managed Server in Managed Server Independence mode, that is, with the Administration Server down, do not deploy when the Managed Server is on a separate file system or machine from the Administration Server. When the Managed Server is brought up in MSI mode, a deployment error such as the following occurs:
<Feb 5, 2004 5:06:36 PM EST> <Error> <Management> <141006> <Application 474001:Name=DefaultWebApp,Type=Application not found at \home2\mks\bea70sp4\user_projects\474001\applications\DefaultWebApp><Feb 5, 2004 5:06:36 PM EST> <Error> <Management> <141004> <IOException opening application 474001:Name=DefaultWebApp,Type=Application, loading from path \home2\mks\bea70sp4\user_projects\474001\applications java.io.FileNotFoundException: File does not exist:
\home2\mks\bea70sp4\user_projects\474001\applications\DefaultWebApp at weblogic.management.mbeans.custom.Application.adminLoad(Application.java:627)
This error occurs because there is no staging mode for one-phase applications, and the file is not cached (staged) on the Managed Server.
8.1
Documentation Known Issues
Change Request Number
Description
Release Fixed
CR196210
Previous versions of this document and various other sample documents erroneously described using weblogic.management.Admin.getInstance().getAdminMBeanHome() as a way to look up the MBeanHome interface on the Administration Server.
However, the weblogic.management.Admin class is not public. Instead of using this non-public class, use JNDI to retrieve MBeanHome. See Determining the Active Domain and Servers in Programming WebLogic Server JMX Services.
EJB Known Issues
Change Request Number
Description
Release Fixed
CR112260
The <security-permission> element for an EJB was not displayed in the Administration Console, and the descriptor validation failed for the security-permission attributes. When the bean was deployed and its client called, it was possible to change the java.vm.version property.
Workaround: A code change was made to allow <security-permission> to be viewed and modified in the Administration Console.
To correctly configure the desired security permission, it is necessary to perform the following steps:
1. Change the grant permission in <security-permission-spec> to { permission java.util.PropertyPermission "java.vm.vendor", "read"; }
2. Add this line to the %WL_HOME%\server\lib\weblogic.policy file:
add grant codeBase "file:/<Your
user_projects dir>/YourDomain/lib/-"
{permission java.security.AllPermission;
} ;
This is required because the dynamically generated stub's
classpath is lib.
3. Start the server with the -Djava.security.manager option.
Deployment Known Issues
Change Request Number
Description
Release Fixed
CR099037
Configuring a default Web application for a cluster and then targeting or redeploying that Web application to either a single server within the cluster or to the cluster itself will result in a deployment failure.
JDBC Known Issues
Change Request Number
Description
Release Fixed
CR173725
An invalid batch value exception occurred using Oracle 10g thin driver. Analysis revealed that the exception was caused by an Oracle thin driver limit for the batch size. The limit seemed to be 16383 (half the max value for a short).
Workaround: Limit the batch size or use 920 driver.
Oracle has stated that the bug has been fixed and is now being backported on top of the 10.1.0.2 drivers.
JMS Known Issues
Change Request Number
Description
Release Fixed
CR108664
The queue browser returns an expired message even if the message had already expired at enumeration time.
The note in the weblogic/security/SSL/SSLSocketFactory.java file is incorrect. The note should read as follows:
This SSLSocketFactory cannot be plugged into JSSE because the getDefault() method used by JSSE returns an instance initialized to use the old Phaos SSL implementation, instead of the Certicom SSL implementation currently used by the server. The Phaos implementation does not allow you to configure the trusted certificates, while Certicom's would be configured according to the server SSL trust configuration. If you really need to access the Certicom implementation from JSSE, you can extend the javax.net.SocketFactory class and implement its getDefault() method to return an instance of your class that wraps the SocketFactory instance returned by the weblogic.security.SSL.SSLSocketFactory.getDefaultJSS() method. The following code example shows how to extend the javax.net.SocketFactory class to access the Certicom implementation from JSSE:
public class MySSLSocketFactory extends javax.net.SocketFactory {
public static javax.net.SocketFactory getDefault() {
if (defFactory == null) defFactory = new MySSLSocketFactory(); return defFactory; }
public Socket createSocket(InetAddress host, int port)
throws IOException {
return factory.createSocket(host, port); }
// implement the other three abstract createSocket
// methods the same way. ... }
WebLogic Tuxedo Connector Known Issues
Change Request Number
Description
Release Fixed
CR074356
When you configure a redirect for tBridge, the redirect configuration information appears at the wrong place in the config.xml file. The redirect configuration appears as a child of the tBridgeGlobal MBean. It should appear at the same level as the tBridgeGlobal MBean.
Workaround: Manually edit the config.xml file.
8.1
Web Services Known Issues
Change Request Number
Description
Release Fixed
CR091230
On Microsoft Windows, the clientgen Ant task may overwrite entities whose names differ only in capitalization. This occurs because Windows is case insensitive.
Known Issues in WebLogic Server 7.0 Service Pack 4
WebLogic Server 7.0 SP4 has the following known issues.
jDriver Known Issues
Change Request Number
Description
Release Fixed
CR094209
Using WebLogic Server applications with distributed transactions and Oracle Server 9.2.0.x causes problems with the Oracle thin driver 9.2.0.x.
Workaround: Use the Oracle 9.2.0.3 driver with patch 2717235. Check the Oracle Web site and apply any necessary patches.
In addition to the workaround, the following tuning technique may help alleviate the problem:
Set the number of connections in the JDBC configured connection pools to equal the number of default execute threads, so that WebLogic Server does not have to wait for a connection to complete an activity on an XA resource.
JSP Known Issues
Change Request Number
Description
Release Fixed
CR061104
When you run the JSP compiler on Windows systems, output files names are always created with lower-case names. To prevent this behavior, and preserve the case used in classnames, set the system property weblogic.jsp.windows.caseSensitive to true. You can set the property at the command line when compiling a JSP using the following command:
Or include this command in your WebLogic Server startup scripts:
-Dweblogic.jsp.windows.caseSensitive=true
Web Services Known Issue
Change Request Number
Description
Release Fixed
CR092268
Using clientgen through a proxy from behind a firewall sometimes fails because the proxy user name and password are not sent.
Known Issues in WebLogic Server 7.0 Service Pack 3
WebLogic Server 7.0 SP3 has the following known issues.
Browser Known Issues
Change Request Number
Description
Release Fixed
CR106615
When using Netscape version 4.79 on HP-UX 11.0 and 11i, a browser session may fail due to bus errors.
CR107134
(JRockit) When using Oracle server version 8.1.7.3, running on Linux, and using JRockit as your JVM, creating a new EJB may result in an end-of-file error. The subsequent version of Oracle server, 8.1.7.4, does not present this problem.
CR108206
An exception thrown by libCsup.2 in HPCode is not handled by WebLogic Server jDriver code, possibly causing Weblogic Server to dump core. This problem occurs when there are three layers of code: HPCode, native code, and Java. The problem has been observed while running Oracle 9.2.0.
Workaround: Use client libraries from Oracle 9.2.0.3.
CR094639
A wildcard URL (/*) added to the security-constraint of an EJB changes the return from req.getSession(false) after a session timeout. When the security-constraint contains a single non-wildcard URL, the return from req.getSession(false) is a null. When the security-constraint contains a non-wildcard URL, AND an additional wildcard(/*) URL, the return from req.getSession(false) is a valid session even though timeout has occurred. Release fixed: WebLogic Server 7.0 SP5.
EJB Known Issues
Change Request Number
Description
Release Fixed
CR082058
If an EJB is deployed as part of an Enterprise Application, you cannot redeploy the EJB without redeploying the entire application.
8.1
CR096713
Some EJBCacheRuntime object IDs do not return results when you run the snmpwalk command against them because their RuntimeMBeans have been removed but their object IDs still exist in the Management Information Base: 150.x.x EJB Entity Home Runtime, 458.x.x EJB Stateful Home Runtime, 170.x.x EJB Stateless Home Runtime, 137.x.x EJBCache Runtime, 136.x.x EJB Cache Monitor Runtime, 150.x.x EJB Entity Home Runtime, 160.x.x EJB Message Driven Runtime, 161.x.x EJB Pool Runtime, 458.x.x EJB Stateful Home Runtime, 170.x.x EJB Stateless Home Runtime, 455.x.x Connector Connection Pool Runtime, and 312.x.x JTA Statistics Runtime.
Tools Known Issues
Change Request Number
Description
Release Fixed
CR092278
In order to redeploy a Web Application using the weblogic.Deployer utility, you must specify both the -source and -target options on the command line. If the -source and -target options are not specified, the tool indicates success but does not redeploy the Web Application.
Web Services Known Issues
Change Request Number
Description
Release Fixed
CR101160
Complex data types in service-specific exceptions are not handled in strict accordance with the Java API for XML-Based RPC (JAX-RPC) 1.0 specification, as follows:
Section 4.3.6 WSDL Fault, Service Specific Exception: When the clientgen Ant task generates the JAX-RPC stubs from a WSDL that contains a wsdl:fault element whose message part is an xsd:complexType, the generated stubs incorrectly map the xsd:complexType to a simple Java type. This means that when a client application uses the stubs to invoke the Web Service, and the service throws the service-specific exception (rather than the a javax.xml.rpc.SOAPFaultException), the client application cannot access the full complex data from the exception.
There is no workaround to this problem.
Section 5.5.5 Methods, Exceptions, fourth bullet: The WebLogic Web Service runtime incorrectly maps multiple fields in a service-specific Java exception class to a simple XML data type, rather than to an xsd:complexType.
Workaround: Always throw a javax.xml.rpc.SOAPFaultException,
rather than a service-specific exception, when implementing a WebLogic Web
Service.
Known Issues in WebLogic Server 7.0 Service Pack 2
WebLogic Server 7.0 SP2 contains the following known issues.
HPUX 11i Users Must Apply a Patch
An incorrect version of the hpux11/libweblogicunix1.sl library was bundled with the WebLogic Server 7.0 SP2 download. To obtain the correct library, HPUX 11i users must download a patch from the following location, and apply it:
If you use the alternative method of placing custom help files in console.war, be sure to add console.war to WL_HOME/server/lib/weblogic.jar. Otherwise the custom files will be wiped out when console.war is regenerated at server startup.
N/A
CR066112
Deployment procedures using the Administration Console have changed since the 6.x release. For more information, see WebLogic Server Application Deployment.
N/A
CR069828
You can no longer edit the Web Services deployment descriptor using the Administration Console.
N/A
CR069927
Selecting Server --> Monitoring --> Process Output and selecting any of the view options does not display the output. If you select the "View Node Manager Output" while Node Manager is running, Node Manager will crash.
7.0 SP3
CR073164
You cannot use the Administration Console to edit a domain other than the current domain of the Administration Server.
CR074339
Explanatory text for creating configuration objects is not displayed when using Netscape 4.7 to access the console.
8.1
CR094174
The Administration Console gives a RuntimeError with Internet Explorer version 5 when you select JDBC->MultiPool in the left panel of the Console.
Core Server Known Issues
Change Request Number
Description
Release Fixed
CR048834
On Solaris, if you are using JDK 1.3.1, and if the timestamp for WebLogic log messages is in Greenwich Mean Time (GMT) regardless of your local time settings, you need to update jre/lib/i18n.jar.
In some cases, this JAR file is missing the resources that the JRE uses to localize time stamps.
Workarounds:
Fix the JRE install with a proper i18n.jar.
If the platform does not support the i18n.jar, then a custom ResourceBundle implementation can be placed in the CLASSPATH from where it will be loaded.
Ensure that the TimeZone is set properly for the install and it supports DST if applicable to the Locale.
CR059543
If you use the Administration Console to update an XML Registry by setting the DocumentBuilderFactory text field to NULL, then subsequently view the same XML Registry, the DocumentBuilderFactory text field is empty. It should contain WebLogic Server's default DocumentBuilderFactory, weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl.
CR063799
Calling getLogFileName on VirtualHostMBean returns an incorrect path.
8.1
CR065299, CR067642
The Java HotSpot(TM) Server VM is not yet supported on WebLogic Server 7.0. Use the certified client version of this VM.
CR066581
The WebLogic Server version of javax.management.timer.Timer, called weblogic.management.timer.Timer, was incompatible with the JMX timer.
If you use the WebLogic class and instantiate it, you will have timers that use the WebLogic thread pools and honor the user identity when executing their listeners.
CR066723
Managed Server discovery is off by default when you are in development mode. To turn it on, add -Dweblogic.manager.discover=false to your command line argument that starts WebLogic Server.
CR067087
WebLogic Server currently does not provide a means to set security permissions within a weblogic-applications.xml file.
CR067814
If you wish to use an LDAP browser to view the embedded LDAP server on WebLogic Server, try using the following input:
host: localhost port: 7003 Anonymousbind LDAP Version 3
CR067868
When using the HotSpot JVM the server can hang when running large deployments.
Workaround: Try setting your -XX:MaxPermSize to a higher figure.
CR068186
If you install WebLogic Server version 7.0 on a multi-homed, Windows 2000 system, configured servers will incorrectly resolve each IP address to the common DNS name for the system itself. For example, consider a multi-homed Windows 2000 machine named "MyWin2KMachine" and having IP addresses:
192.168.1.105 192.168.1.106 192.168.1.107
If you install multiple WebLogic Server instances on the system using IP addresses 192.168.105, 192.168.1.106, and 192.168.1.107 for the servers' Listen Address attributes, all servers will yield the common DNS name, "MyWin2KMachine," when resolving their IP addresses. This can lead to conflicts when accessing resources on remote servers.
Workarounds:
Edit the c:/winnt/system32/drivers/hosts file with a text editor to explicitly name each IP address. For example:
If the machine's IP addresses have names registered with a DNS server, use those externally-available DNS names instead of IP addresses when configuring servers' Listen Address attributes. For example, configure servers using MyWin2KMachine1, MyWin2KMachine2, and MyWin2KMachine3 rather than using 192.168.105, 192.168.106, and 192.168.107. Note that this problem does not affect other software platforms, including Windows NT.
CR068228
When you are not running in compatibility mode and you use the command line Administration tool, you may be prompted for a `guest' password. The default password for "guest" is "guest".
CR068247
The JSPs included with WebLogic Server 7.0 are not being pre-compiled before they are accessed for the first time. If you are deploying precompiled JSPs, WebLogic Server may recompile them to the /wlnotdelete/ directory.
CR068361
If you are migrating a 1.1 EJB from Bean Managed Persistence to Container Managed Persistence, selecting the bean and checking "Container-managed persistence" should generate Advanced and Automatic Key Generation options, but does not.
CR069278
When using the command line to create a connection pool, in the properties string you can only escape the double quotes on platforms where the shell removes one set of quotes.
Workaround: On platforms where the quotes are not removed during this process, you should use only one set of double quotes. You can also repeat the property argument for each connection property, which eliminates the need for quoting a string of properties. For example:
The JTA implementation in WebLogic Server was updated to comply with the JTA specification version 1.0.1a, including minor changes to the Transaction.commit() and TransactionManager.setTransactionTimeout(int) methods.
CR072646
When using Netscape version 4.75 or older on Windows 2000, file associations may not be converted correctly from the same used for Internet Explorer. This results in the following behavior when opening About WebLogic Server 7.0, About Examples, and About Pet Store from the Windows Start menu:
An error message is displayed indicating failure to find target URI (even though the page opens in a browser).
If the browser is already running, the HTML page fails to display in the browser.
CR072940
If your config.xml file does not have the <SecurityConfiguration> element set, or is missing the credential and name attributes within that element, your server tries to create this attribute. If your config.xml file is writeable, your java client caches the value of this credential in its local JVM memory space. Then, for the lifetime of the JVM, the java client uses this credential. However, once the JVM gets re-started, it is denied access because it does not have the credential.
Workaround: save your config.xml file once, when it has the credential already set.
CR073395
There is a problem with Sun's Pet Store application when you try to run it with more than one client and use an Oracle database.
CR073647
Currently only users in an Administration role can use the AdministrationPort.
8.1
CR073737
If you restart an Administration Server for an active domain, the Administration Server can fail to discover its Managed Servers. This occurs with the following configuration:
A multihomed machine running a Windows operating system, in which the Administration Server and one or more processes use the same listen ports (but on different IP addresses). It is caused by a limitation of the Windows operating system. If a restarted Administration Server does not discover its Managed Server, commands that you issue to a domain via the Administration Server will fail. For example, a Managed Server that starts in Managed Server Independence (MSI) mode can fail to respond to shutdown commands after the Administration Server regains control.
CR073793
You cannot deploy an application with untargeted modules if you have not set URIs for the untargeted modules in your config.xml.
8.1
CR074296
In some situations, the Administration Console allows users to create more than one WebLogic Tuxedo Connector WTCResources MBean. Only one WTCResources MBean is allowed for a given WTCServer MBean configuration. Users may need to remove the extra configuration and restart the WebLogic Tuxedo Connector.
8.1
CR074452
If your JVM is throwing errors and WebLogic Server is under heavy load, try increasing your java memory heap.For example, modify the command that starts WebLogic Server by adding the following: MEM_ARGS="-XX:MaxPermSize=128m -Xms512m -Xmx512m"
CR074969
You may encounter problems deploying EJBs without JNDI names. BEA recommends that users continue to deploy their EJBs with JNDI names as was done in earlier releases of WebLogic Server.
CR085169
When using Iplanet 4.1SP9, the Java client can not read post data from a plug-in due to read_timeout from the java client using socket.getInputStream().readLine()' caused by a problem in netbuf_getbytes().
Workaround: Using Iplanet 6.0SP2 with WebLogic Server eliminates this problem.
The nohup command starts failing; the WebLogic Server process exits when the parent shell exits, regardless of the invocation of nohup. The problem was confirmed for ksh (the default Solaris 8 shell), but may exist for other shells. The problem does not occur with the bash shell.
Use "(startWeblogic >output 2>&1 &)" instead of "nohup startWeblogic &".
CR110028, CR120181
Stuck thread detection in WebLogic Server 7.0 is limited to threads in the default execute queue.
Stuck thread detection is done by checkStuckThreads method of weblogic.t3.srvr.CoreHealthService, and a private variable, policyName, which corresponds to the queue name for checking stuck threads, is statically set to "default."
EJB Known Issues
Change Request Number
Description
Release Fixed
CR089847
Many WebLogic Server EJB deployment properties have default values that are optimized for performance. In some cases, these default values are not compliant with the EJB specification.
Workaround: To make WebLogic Server compliant with the EJB specification, set the following properties:
In weblogic-ejb-jar.xml set enable-call-by-reference to False.
In weblogic-cmp-jar.xml, set include-updates to True.
In weblogic-cmp-jar.xml, set check-exists-on-method to True.
N/A
CR089630
When a table contains both BLOB and LONG RAW columns, OracleThinDriver requires that the LONG RAW column be read first from the stream even if BLOB occurs before LONG RAW in the select list.
The EJB container currently does not handle this case and throws a java.sql.SQLException "Stream already closed".
Workaround: Use JDriver.
CR097323
There is a known issue with deploying or redeploying EJBs to a single server instance in a cluster—referred to as pinned deployment—if the .jar file contains contain uncompiled classes and interfaces.
During deployment, the uncompiled EJB is copied to each server instance in the cluster, but it is compiled only on the server instance to which it is deployed. As a result, the server instances in the cluster to which the EJB is not targeted lack the classes generated during compilation that are necessary to invoke the EJB. When a client on another server instance tries to invoke the pinned EJB, it fails, and an Assertion error is thrown in the RMI layer.
Workaround: If you are deploying or redeploying an EJB to a single server instance in a cluster, compile the EJB before deploying it to ensure that the generated classes are copied to all server instances and available to all nodes in the cluster.
N/A
Examples and Pet Store Known Issues
Change Request Number
Description
Release Fixed
CR055626
The login.jsp file for the webapp security sample does not allow for URL encoding when a user logs in. The login.jsp file is in this location:
SAMPLES_HOME\server\src\examples\webapp\security
The login.jsp file has this code:
<form method="POST" action="j_security_check">
Here is an example of code that could be used to allow for URL encoding:
Due to Microsoft VB Scripting Versioning, Excel 2000 or later is required to run the ZeroClient jCom example.
CR071260
The password and username for the examples and Pet Store has been changed since WebLogic Server 7.0 Beta. Using installadministrator/installadministrator no longer works, use weblogic and weblogic instead.
N/A
CR073395
Pet Store has problems when multiple clients are using the same resources. Sun is working to address this problem.
CR074004
In the package-summary.html file in the SAMPLES_HOME\server\src\examples\security directory, the Security Examples Summary table makes references to the audit and cert samples. These samples have been removed from the WebLogic Server distribution because they used APIs that are being deprecated in WebLogic Server 7.0.
Also, the descriptions of the SSLClient, JAAS, and Net samples should read as follows:
SSLClient: Demonstrates how to make outbound SSL connections and two-way SSL connections from a WebLogic Server that is acting as a client to another WebLogic Server or application server.
JAAS: Demonstrates use of the Java Authentication and Authorization Service by validating username and password, and then, if valid, executing the stateless session Trader EJB.
Net: Demonstrates writing connection filters that implement the weblogic.security.net.ConnectionFilter and ConnectionFilterRulesListener interfaces. Connection filters allow you to reject or accept client connections to the WebLogic Server environment based on the client's IP address and protocol and the local and remote port numbers.
N/A
CR080288
There are problems with the RMI cluster example when using ant run to execute the client. The java call to the client includes incorrect quotation marks.
Installation Known Issues
Change Request Number
Description
Release Fixed
CR085531
After successful upgrades and downgrades of a WebLogic Server via SmartUpdate, a subsequent upgrade results in the following error:
Installer is not compatible with the installed product. Your product directory contains installed components that are not available in the current installer. Please check your installer to ensure it matches the product distribution on your system.
Workaround: Contact your customer support representative for assistance.
Interoperability Known Issues
Change Request Number
Description
Release Fixed
CR093343 and CR093347
When a Java client running on Java 2 SDK 1.4.1 accesses a server running on Java 2 SDK 1.3.1, the following errors occur:
The getDate() and setDate() methods return inconsistent results.
When calling getTimeStamp() or setTimeStamp() from the client, the client gets the "class not found" error.
These are known issues with the Sun Java 2 SDK (Ticket #808980). Sun plans to fix these errors in Java 2 SDK 1.5.
Workaround: Run the client application on SDK 1.3.1.
CR092507, CR095479
Remote methods throwing MarshalException/UnmarshalException when interoperating between 7.0 SP1 and 7.0 SP2 servers may result in unmarshalling problems. This occurs because MarshalException and UnmarshalException map to the correct completion statuses in SP2 but the incorrect completion statuses in SP1.
CR095804
When a WebLogic Server 7.0 SP2 client attempts to get the Coordinator remote object from a WebLogic 8.1 server instance, a ClassCastException is thrown while casting the remote stub to the CoordinatorOneway interface. This prevents commit handoff to the 8.1 coordinating server.
7.0 SP3
jDriver Known Issues
Change Request Number
Description
Release Fixed
CR094209
Using WebLogic Server applications with distributed transactions with Oracle Server 9.2.0.x causes problems with the Oracle thin driver 9.2.0.x.
Workaround: Use the Oracle 9.2.0.3 driver with patch 2717235. Check the Oracle Web site and apply any necessary patches.
In addition to the workaround, the following tuning technique may help alleviate the problem:
Set the number of connections in the JDBC configured connection pools to equal the number of default execute threads, so that WebLogic Server does not have to wait for a connection to complete an activity on an XA resource.
JMS Known Issues
Change Request Number
Description
Release Fixed
CR075438
A message-driven bean (MDB) that is deployed on a distributed topic, and which is targeted to a server instance that is hosting two members of the distributed topic, is also deployed on all the members of the distributed topic.
This is the expected behavior because the MDB is pinned to the member destination name. Therefore, if a JMS server contains two members, there will be two MDBs deployed, one for each member.
JRockit Known Issues
Change Request Number
Description
Release Fixed
CR093270
When running WebLogic Server 7.0 SP2 server on the JRockit JVM, in UDDI, publishing a new Web service to the private registry fails with this error message: "An error has occurred E_fatalError(10500): a serious technical error has occurred while processing the request."
This is due to a bug in the UDDI implementation (AUDDI 1.0).
JTA Known Issues
Change Request Number
Description
Release Fixed
CR089804
In a transaction, you cannot use connections from two Tx Data Sources that point to the same connection pool. When you attempt to get a connection from the second Tx Data Source, you will get an XA_PROTO error.
Internally, WebLogic Server uses the connection pool name to identify the resource, not the data source name. When you get two separate connections from the same connection pool using different Tx Data Sources, they are treated as the same resource. In a transaction, start/enlist is called on the first Tx Data Source, then start/enlist is attempted on the second Tx Data Source. Because the server considers the resources to be the same, an XA_PROTO error is thrown because end/delist was not called before starting a new transaction.
Workarounds:
Use a connection from only one Tx Data Source during the transaction.
Use two Tx Data Sources that point to different connection pools.
There should be no performance degradation from either of these workarounds.
Node Manager Known Issues
Change Request Number
Description
Release Fixed
CR074230
Applications deployed to WebLogic Server should perform file lookups relative to the Root Directory obtained with the ServerMBean.getRootDirectory() method (this defaults to the "." directory). For example, to perform a file lookup, use code similar to:
File f = new File(rootDir + File.separator + "foo.in");
rather than simply:
File f = new File("foo.in");
If an application is deployed to a server that is started using Node Manager, use the following method calls instead:
String rootDir //application root directory
if ((rootDir = ServerMBean.getRootDirectory()) == null) rootDir = ServerStartMBean.getRootDirectory(); File f = new File(rootDir + File.separator + "foo.in");
The ServerStartMBean.getRootDirectory() method obtains the Root Directory value that you specified when configuring the server for startup using Node Manager. (This corresponds to the Root Directory attribute specified the Configuration->Remote Start page of the Administration Console.)
A Managed Server started remotely by Node Manager does not recognize the weblogic.RootDirectory set on the Remote Start tab.
To avoid this problem, enter an absolute path for Staging Directory on the Domain—>Servers—>Configuration—>Deployment tab. Do not enter a relative path. Enter the full path, including the WebLogic Server root directory.
CR073078
When the Administration Server attempts to set up an SSL connection to Node Manager, it does not automatically search for certificate files in the Administration Server's root directory. If you store SSL certificate files in the Administration Server's root directory, make sure you configure the absolute path to the certificate files using the Connections->SSL tab in the Administration Console.
8.1
CR075142
The Administration Server and Node Manager may simultaneously attempt to close a TCP socket, causing the following error message to appear in the Node Manager log file:
<Apr 18, 2002 5:32:55 PM EDT> <Error> <NodeManager@localhost:5555> <OutputHandler: done2 socket close failed, reason: java.net.SocketException: Connection reset by peer.>
This problem does not affect the operation of Node Manager or the Administration Server.
CR094722
When Managed Servers in a cluster are booted, a socketWrite error is thrown on the Administration Server.
Workaround: Ignore the problem or restart the managed node.
Plug-in Known Issues
Change Request Number
Description
Release Fixed
CR095161
Under load, an Apache plug-in may receive a CONNECTION REFUSED error from a back-end WebLogic Server instance. This error was observed with Apache Server version 1.3.22 with the Apache plug-in and WebLogic Server running on Solaris 8.
RMI Known Issues
Change Request Number
Description
Release Fixed
CR099693
A client accessing WebLogic Server through a firewall using the t3 protocol resulted in an error because the server expected to route a message over an uninitialized connection.
The server's ExternalDNSName was specified. Upon initial connection, the client addressed the request to the server instance's ExternalDNSName. The JVMID in the response from the server instance required the server's internal IP address and internal DNS name. Subsequent requests from the client were not recognized.
The problem occurs if clients are connecting over t3 through a firewall. The workaround is to add an entry to the external DNS servers that maps the server instance's internal DNS name to its external IP address.
7.0 SP03
Security Known Issues
For information about BEA security advisories, refer to the BEA Advisories & Notifications page on the dev2dev Web site. On this page, you can download security-related patches and register to receive notifications of newly available security advisories. You can access the Advisories & Notifications page with the following URL: http://dev2dev.bea.com/advisories.
BEA has established an e-mail address (security-report@bea.com) to which you can send reports of any possible security issues in BEA products.
The following table summarizes security-related known issues for this service pack release:
The proper syntax for a role name must be an XML_NMTOKEN as defined in the specification at:
http://www.w3.org/TR/REC-xml#NT-Nmtoken
CR093652
In order for clients built with JDK 1.4.1 to use SSL, the Java 2 SDK jsse.jar file must be removed from the JAVA_HOME\jre\lib directory.
CR094566
To use the nCipher JCE provider with this release of WebLogic Server, clients must be built using JDK 1.3.1.
CR096589
weblogic.servlet.security.ServletAuthentication.strong() is broken and fails with a class cast exception.
Workaround: Install the following patch: CR096589_70sp2.jar.
7.0 SP3
Third-Party Tools Known Issues
Change Request Number
Description
Release Fixed
CR071527
There is a problem persisting sessions with Resonate—a third-party load balancing tool that uses WebLogic Server as a backend server. Because Resonate does not handle case insensitivity, if URLEncoding sends a cookie as jsessionid instead of JSESSIONID, Resonate does not detect the cookie.
Tools Known Issues
Change Request Number
Description
Release Fixed
CR064893
The following deployment descriptor elements cannot be edited in WebLogic Builder:
WebLogic Builder may fail to access a database on a server if the driver classes for the database are not on the client.
CR066466
WebLogic Builder does not provide the option to cancel operations.
CR066668
On Linux, WebLogic Builder's file browser opens at root instead of current directory.
CR068152
The operations Add, Edit, and Delete can be slow in the EJB elements of WebLogic Builder.
8.1
CR068165
In the Add dialog in Resource Links, in the WebLogic Settings, J2EE Links, WebLogic Builder incorrectly offers a selection of application scoped data resources.
CR068620
Table columns may not resize properly in WebLogic Builder.
8.1
CR069568
WebLogic Builder cannot map multiple roles to a method in EJB method permission.
CR071833, CR072541
WebLogic Builder support for RARs does not include generation of deployment descriptors.
CR072700, CR074591
If you use WebLogic Builder's deployment dialog box to undeploy an application, the dialog will not show the undeployment. This dialog may also report that applications whose deployment has failed are deployed.
7.0 SP3
CR073975
WebLogic Builder incorrectly allows you to add a transaction without specifying a method or a transaction attribute.
7.0 SP3
CR074210
Optimistic concurrency strategy does not work in WebLogic Builder.
8.1
CR074322, CR074856
In WebLogic Builder, canceling an edit action may not work.
8.1
CR074566
Finders or container-managed persistence values modified through WebLogic Builder's BeanGrid/Edit (like include-update) may not be represented in the individual panels.
8.1
CR074622
In editing a container-managed persistence field using the WebLogic Builder's pop-up dialog, if you set column type to OracleCLOB and then click on the CMP tree node, the column type change does not show up on the CMP panel.
CR074728
WebLogic Builder does not allow changing a method to a local method.
CR074754
Editing some transaction attributes may cause WebLogic Builder to create duplicate descriptors.
CR074961
If you use WebLogic Builder to generate web.xml descriptors, it creates a security-role "guest" which pertains to the pre-7.0 security protocol.
CR075129
If you switch a stateless session bean to stateful, WebLogic Builder may not show that the module is dirty.
CR075228
WebLogic Builder may throw an assertion error if you delete a transaction or permission method.
8.1
CR075586
If you want to use WebLogic Builder with the WebLogic Server Examples Server or examples, you should run setExamplesEnv (located at %SAMPLES_HOME%\server\config\examples) before starting WebLogic Builder, so that files needed to run the PointBase database server will be added to the classpath. If you do not, you will get database error messages.
CR075753
Some descriptor elements may pass through WebLogic Builder validation and then be found to be in error by ejbc.
CR075924
In some cases, WebLogic Builder may not properly generate descriptor files for nested WAR files in EARs.
8.1
CR075936
WebLogic Builder may generate an illegal value for the element estimated-bean-size.
8.1
WebLogic Tuxedo Connector Known Issues
Change Request Number
Description
Release Fixed
CR067275
Load balancing and failover are not supported with WebLogic Tuxedo Connector in a cluster using RMI over IIOP.
CR079630
Most users expect to set the Correlation ID using the setJMSCorrelationID(String) method. This will take a 32 character string and turn it into a 64 byte array. JMS stores the string as UTF-16BE. When the tBridge receives the Correlation Id from Tuxedo it is 32 characters as 32 bytes. The tBridge then uses the setJMSCorrelationIDAsBytes(byte[]) method to set the message for JMS receiving queue. The characters may be the same in ASCII but the two will not compare due to the length difference.
When it is necessary to compare the Correlation ID with the ID returned from Tuxedo in the receiving JMS queue, create a byte array containing the hexadecimal values of the Correlation ID. Then use the setJMSCorrelationIDAsBytes() and getJMSCorrelationIDAsBytes()methods to create an ID to compare with the ID returned from Tuxedo in the receiving JMS queue.
For example, if the string Correlation ID is "1234567890ABCDEFGHIJKLMNOPQRSTUV":
The command line version of the clientgen Ant task doe not support the following options that correspond to the Ant task attributes:
-autotype -overwrite
8.1
CR073661
WebLogic Web services that are described with an invalid web-services.xml file incorrectly deploy on WebLogic Server, although they are not accessible by client applications trying to invoke them.
CR083493
The messages and multicomponent examples in the Web Services examples package do not contain the code needed to generate a downloadable client.jar file.This omission does not affect the functionality of the example which work with the provided client.
CR094688
Using the 7.0 WebServices Portable Stubs client .jar may result in a java.lang.NoClassDefFoundError.
Workaround: Run the client using the full CLASSPATH and provide the difference between the classes to the VersionMaker utility.
CR095629
When using the new weblogic.webservice.cachewsdl flag to optimize memory use, a bogus warning message displays in the server log:
This warning is bogus; in spite of this message, the flag takes effect.
CR101160
Complex data types in service-specific exceptions are not handled in strict accordance with the Java API for XML-Based RPC (JAX-RPC) 1.0 specification, as follows:
Section 4.3.6 WSDL Fault, Service Specific Exception: When the clientgen Ant task generates the JAX-RPC stubs from a WSDL that contains a wsdl:fault element whose message part is an xsd:complexType, the generated stubs incorrectly map the xsd:complexType to a simple Java type. This means that when a client application uses the stubs to invoke the Web Service, and the service throws the service-specific exception (rather than the a javax.xml.rpc.SOAPFaultException), the client application cannot access the full complex data from the exception.
There is no workaround to this problem.
Section 5.5.5 Methods, Exceptions, fourth bullet: The WebLogic Web Service runtime incorrectly maps multiple fields in a service-specific Java exception class to a simple XML data type, rather than to an xsd:complexType.
The workaround is to always throw a
javax.xml.rpc.SOAPFaultException, rather than a service-specific
exception, when implementing a WebLogic Web Service.
XML Known Issues
Change Request Number
Description
Release Fixed
CR070547
When the XML Streaming API is used on Solaris, some character references do not resolve to the same character as on NT.
Known Issues in WebLogic Server 7.0 Service Pack 1
This section covers known issues in WebLogic Server 7.0 Service Pack 1.
Administration Console Known Issues
Change Request Number
Description
Release Fixed
CR066112
Deployment procedures using the Administration Console have changed since the 6.x release. For more information, see WebLogic Server Application Deployment.
N/A
CR069828
You can no longer edit the Web Services deployment descriptor using the Administration Console.
N/A
CR069927
Selecting Server --> Monitoring --> Process Output and selecting any of the view options does not display the output. If you select the "View Node Manager Output" while Node Manager is running, Node Manager will crash.
CR073164
You cannot use the Administration Console to edit a domain other than the current domain of the Administration Server.
CR074339
Explanatory text for creating configuration objects is not displayed when you use Netscape 4.7 to access the console.
8.1
CR074677
When you upgrade a domain created under version 6.x of WebLogic Server, the user "system" no longer explicitly grants access to the Administration Console. To access the console, a user must be a member of the Administrators Group.
7.0 SP2
Core Server Known Issues
Change Request Number
Description
Release Fixed
CR110058
The MalformedURLException can result when the dynamic group attribute memberURL contains a string value with a reserved character such as a forward slash '/') in the filter portion of the LDAP URL. Such a URL can result when the filter portion resolves to an object in the LDAP Directory Server that contains the forward slash character.
Workaround: Avoid the use of reserved characters ':','?','/') in object names in your LDAP directory if your directory makes use of dynamic groups. The netscape.ldap.LDAPUrl utility class open source) cannot handle these characters.
CR030981
The JDBC t3 Driver, which was deprecated in WebLogic Server 6.0, was removed from this release.
N/A
CR048834
On Solaris, if you are using JDK 1.3.1, and if the timestamp for WebLogic log messages is in GMT regardless of your local time settings, you need to update jre/lib/i18n.jar.
In some cases, this JAR file is missing the resources that the JRE uses to localize time stamps.
Workaround: To fix this there are several alternatives.
Fix the JRE install with a proper i18n.jar.
If the platform does not support i18n.jar then a custom ResourceBundle implementation can be placed in the CLASSPATH from where it will be loaded.
Ensure that the TimeZone is set properly for the install and it supports DST if applicable to the Locale.
CR059543
If you use the Administration Console to update an XML Registry by setting the DocumentBuilderFactory text field to NULL, then subsequently view the same XML Registry, the DocumentBuilderFactory text field is empty. It should contain WebLogic Server's default DocumentBuilderFactory, weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl.
CR063799
Calling getLogFileName on VirtualHostMBean returns an incorrect path.
8.1
CR065299, CR067642
The Java HotSpot(TM) Server VM is not yet supported on WebLogic Server 7.0. Use the certified client version of this VM.
CR066581
WebLogic Server has its own version of javax.management.timer.Timer, called weblogic.management.timer.Timer. If you use the WebLogic class and instantiate it, you will have timers that use the WebLogic thread pools and honor the user identity when executing their listeners.
CR066723
Managed Server discovery is off by default when you are in development mode. To turn it on, add -Dweblogic.manager.discover=false to your command line argument that starts WebLogic Server.
CR067087
WebLogic Server currently does not provide a means to set security permissions within a weblogic-applications.xml file.
CR067814
If you wish to use an LDAP browser to view the embedded LDAP server on WebLogic Server, try using the following input:
host: localhost port: 7003 Anonymousbind LDAP Version 3
CR067868
When using the HotSpot JVM the server can hang when running large deployments. Workaround: Try setting your -XX:MaxPermSize to a higher figure.
CR068186
If you install WebLogic Server version 7.0 on a multi-homed, Windows 2000 system, configured servers will incorrectly resolve each IP address to the common DNS name for the system itself. For example, consider a multi-homed Windows 2000 machine named "MyWin2KMachine" and having IP addresses:
192.168.1.105 192.168.1.106 192.168.1.107
If you install multiple WebLogic Server instances on the system using IP addresses 192.168.105, 192.168.1.106, and 192.168.1.107 for the servers' Listen Address attributes, all servers will yield the common DNS name, "MyWin2KMachine," when resolving their IP addresses. This can lead to conflicts when accessing resources on remote servers.
Workaround: Do one of the following:
Edit the c:/winnt/system32/drivers/hosts file with a text editor to explicitly name each IP address. For example:
If the machine's IP addresses have names registered with a DNS server, use those externally-available DNS names instead of IP addresses when configuring servers' Listen Address attributes. For example, configure servers using MyWin2KMachine1, MyWin2KMachine2, and MyWin2KMachine3 rather than using 192.168.105, 192.168.106, and 192.168.107. Note that this problem does not affect other software platforms, including Windows NT.
CR068228
When you are not running in compatibility mode and you use the command line Administration tool, you may be prompted for a `guest' password. The default password for "guest" is "guest".
CR068247
The JSPs included with WebLogic Server 7.0 are not being pre-compiled before they are accessed for the first time. If you are deploying precompiled JSPs, WebLogic Server may recompile them to the /wlnotdelete/ directory.
CR068361
If you are migrating a 1.1 EJB from Bean Managed Persistence to Container Managed Persistence, selecting the bean and checking "Container-managed persistence" should generate Advanced and Automatic Key Generation options, but does not.
CR069278
When using the command line to create a connection pool, in the properties string you can only escape the double quotes on platforms where the shell removes one set of quotes. On platforms where the quotes are not removed during this process, you should use only one set of double quotes. You can also repeat the property argument for each connection property, which eliminates the need for quoting a string of properties. For example:
The JTA implementation in WebLogic Server was updated to comply with the JTA specification version 1.0.1a, including minor changes to the Transaction.commit() and TransactionManager.setTransactionTimeout(int) methods.
CR070429
There is currently no way to re-boot with the last known good COMMO configuration.
7.0 SP2
CR071954
In 6.x versions, the weblogic.management.Admin class had the static method, getActiveDomain(). In Weblogic Server 7.0, getActiveDomain() is no longer static. In its place, use Admin.getInstance().getAdminMBeanHome().getActiveDomain();
When you use Netscape version 4.75 or earlier on Windows 2000, file associations may not be converted correctly from the same used for Internet Explorer. This results in the following behavior when opening About WebLogic Server 7.0, About Examples, and About Pet Store from the Windows Start menu:
An error message is displayed indicating failure to find target URI (even though the page opens in a browser).
If the browser is already running, the HTML page fails to display in the browser.
CR072940
If your config.xml file does not have the <SecurityConfiguration> element set, or is missing the credential and name attributes within that element, your server tries to create this attribute. If your config.xml file is writeable, your java client caches the value of this credential in its local JVM memory space. Then, for the lifetime of the JVM, the java client uses this credential. However, once the JVM gets re-started, it is denied access because it does not have the credential.
Workaround: save your config.xml file once, when it has the credential already set.
CR073395
There is a problem with Sun's Pet Store application when you try to run it with more than one client and use an Oracle database.
CR073647
Currently only users in an Administration role can use the AdministrationPort.
8.1
CR073737
If you restart an Administration Server for an active domain, the Administration Server can fail to discover its Managed Servers. This occurs with the following configuration:
A multihomed machine running a Windows operating system, in which the Administration Server and one or more processes use the same listen ports (but on different IP addresses). It is caused by a limitation of the Windows operating system. If a restarted Administration Server does not discover its Managed Server, commands that you issue to a domain via the Administration Server will fail. For example, a Managed Server that starts in Managed Server Independence (MSI) mode can fail to respond to shutdown commands after the Administration Server regains control.
CR073793
You cannot deploy an application with untargeted modules if you have not set URIs for the untargeted modules in your config.xml.
8.1
CR074296
In some situations, the Administration Console allows users to create more than one WebLogic Tuxedo Connector WTCResources MBean. Only one WTCResources MBean is allowed for a given WTCServer MBean configuration. Users may need to remove the extra configuration and restart the WebLogic Tuxedo Connector.
8.1
CR074452
If your JVM is throwing errors and WebLogic Server is under heavy load, try increasing your java memory heap.For example, modify the command that starts WebLogic by adding the following: MEM_ARGS="-XX:MaxPermSize=128m -Xms512m -Xmx512m"
CR074969
You may encounter problems deploying EJBs without JNDI names. BEA recommends that users continue to deploy their EJBs with JNDI names as was done in earlier releases of WebLogic Server.
CR085169
When using Iplanet 4.1SP9, the Java client can not read post data from a plug-in due to read_timeout from the java client using socket.getInputStream().readLine()' caused by a problem in netbuf_getbytes().
Workaround: Use Iplanet 6.0SP2 with WebLogic Server.
CR086784
You can encounter problems with deadlocks when starting WebLogic Server 7.0 SP1 on Windows 2000 with Sun Microsystem's JVM 1.3.1_03. These problems occur when using the JVM's over-optimizations.
Workaround: use the JVM's -XX:-UseCompilerSafepoints option to turn off the over-optimizations.
EJB Known Issues
Change Request Number
Description
Release Fixed
CR124381
An EAR file generates an put-of-memory error during deployment. The exception begins:
<Sep 30, 2003 8:28:41 AM MDT> <Info> <Deployer> <BEA-149060> <Module ttri_depl.jar of application OSS_TTRI successfully transitioned from prepared to unprepared on server myserver.>
<Sep 30, 2003 8:28:41 AM MDT> <Info> <Deployer> <BEA-149033> <failed application OSS_TTRI on myserver>
<Sep 30, 2003 8:28:41 AM MDT> <Info> <Management> <BEA-140009> <Configuration changes for the domain have been saved to the repository.>
Workaround: reduce the quantity setting for max-beans-in-free-pool in weblogic-ejb-jar.xml, for instance from:
Many WebLogic Server EJB deployment properties have default values that are optimized for performance. In some cases, these default values are not compliant with the EJB specification.
To make WebLogic Server compliant with the EJB specification, you must set the following properties:
In weblogic-ejb-jar.xml set enable-call-by-reference to False.
In weblogic-cmp-jar.xml, set include-updates to True
In weblogic-cmp-jar.xml, set check-exists-on-method to True.
N/A
CR089630
In the case where a table contains both BLOB and LONG RAW columns, OracleThinDriver requires that the LONG RAW column be read first from the stream even if BLOB occurs before LONG RAW in the select list.
The EJB container currently does not handle this case and throws a java.sql.SQLException "Stream already closed".
Workaround: Use JDriver.
CR097323
There is a known issue with deploying or redeploying EJBs to a single server instance in a cluster—referred to as pinned deployment—if the .jar file contains contain uncompiled classes and interfaces.
During deployment, the uncompiled EJB is copied to each server instance in the cluster, but it is compiled only on the server instance to which it has been deployed. As a result, the server instances in the cluster to which the EJB was not targeted lack the classes generated during compilation that are necessary to invoke the EJB. When a client on another server instance tries to invoke the pinned EJB, it fails, and an Assertion error is thrown in the RMI layer.
Workaround: If you are deploying or redeploying an EJB to a single server instance in a cluster, compile the EJB with ejbc before deploying it, to ensure that the generated classes copied to all server instances available to all nodes in the cluster.
Examples and Pet Store Known Issues
Change Request Number
Description
Release Fixed
CR055626
The login.jsp file for the webapp security sample does not allow for URL encoding when a user logs in. The login.jsp file is in this location:
SAMPLES_HOME\server\src\examples\webapp\security
The login.jsp file has this code:
<form method="POST" action="j_security_check">
Here is an example of code that could be used to allow for URL encoding:
Due to Microsoft VB Scripting Versioning, Excel 2000 or later is required to run the ZeroClient jCom example.
CR071260
The password and username for the examples and Pet Store has been changed since WebLogic Server 7.0 Beta. Using installadministrator and installadministrator no longer works, use weblogic and weblogic instead.
N/A
CR073395
Pet Store has problems when multiple clients are using the same resources. Sun is working to address this problem.
CR074004
In the package-summary.html file in the SAMPLES_HOME\server\src\examples\security directory, the Security Examples Summary table makes references to the audit and cert samples. These samples have been removed from the WebLogic Server distribution because they used APIs that are being deprecated in WebLogic Server 7.0.
Also, the descriptions of the SSLClient, JAAS, and Net samples should read as follows:
SSLClient: Demonstrates how to make outbound SSL connections and two-way SSL connections from a WebLogic Server that is acting as a client to
another WebLogic Server or application server.
JAAS: Demonstrates use of the Java Authentication and Authorization Service by validating username and password, and then, if valid, executing the stateless session Trader EJB.
Net: Demonstrates writing connection filters that implement the weblogic.security.net.ConnectionFilter and ConnectionFilterRulesListener interfaces. Connection filters allow you to reject or accept client connections to the WebLogic Server environment based on the client's IP address and protocol and the local and remote port numbers.
N/A
CR080288
There are problems with the RMI cluster example when using ant run to execute the client. The java call to the client includes incorrect quotation marks.
CR085521
The package-summary.html file of the r3client Web service example is incomplete. This example is located in the SAMPLES_HOME\server\src\examples\webservices\r3client directory.
The example illustrates how to run the WebLogic Web service client to exercise the SOAPBuilders Interoperability Lab Round 3 suite of tests.
To build the example, follow these steps:
1. Set up your development shell as described in Quick Start.
2. Change to the SAMPLES_HOME\server\src\examples\webservices\r3client directory where SAMPLES_HOME refers to the examples WebLogic Server domain directory.
3. Assemble and compile the example by executing the Java ant utility at the command line:
prompt> ant
4. Compile the results into an HTML table by executing the following Ant task at the command line:
prompt> ant compileResults
Note: You do not need to start WebLogic Server because the application invokes Web services from the SOAPBuilders Web site rather than one running on WebLogic Server.
To check the output, open the following file in your browser to view the results of the tests in an HTML table:
After successfully upgrading and downgrading WebLogic Server via SmartUpdate, a subsequent upgrade results in the following error:
Installer is not compatible with the installed product. Your product directory contains installed components that are not available in the current installer. Please check your installer to ensure it matches the product distribution on your system.
Workaround: Contact your customer support representative for assistance.
JMS Known Issues
Change Request Number
Description
Release Fixed
CR066079
WebLogic JMS is now fully compliant with Sun Microsystems' JMS Specification version 1.0.b. Therefore, the message property name should not contain spaces.
CR075438
A message-driven bean (MDB) that is deployed on a distributed topic, and which is targeted to a server instance that is hosting two members of the distributed topic, is also deployed on all the members of the distributed topic.
This is the expected behavior because the MDB is pinned to the member destination name. Therefore, if a JMS server contains two members, there will be two MDBs deployed, one for each member.
Node Manager Known Issues
Change Request Number
Description
Release Fixed
CR071591
Node Manager detects Managed Server failures by trying to initiate an HTTP connection. If Node Manager receives a connection failure, the connection exception can be observed in Node Manager output:
<Mar 19, 2002 2:30:04 PM EST> <Warning> <net> <000900> <Could not open connection java.net.ConnectException: Connection refused: connect
7.0 SP2
CR073078
When the Administration Server attempts to set up an SSL connection to Node Manager, it does not automatically search for certificate files in the Administration Server's root directory.
Workaround: If you store SSL certificate files in the Administration Server's root directory, make sure you configure the absolute path to the certificate files using the Connections->SSL tab in the Administration Console.
8.1
CR099693
In 7.0 (G.A., SP01, and SP02), a client accessing WebLogic Server through a firewall using the t3 protocol, resulted in this error on the server:
####<Feb 17, 2003 10:15:59 AM EST> <Error> <RJVM> <ewibeasbx01.merck.com> <edmServer> <ExecuteThread: '14' for queue: 'default'> <kernel identity> <> <000506> <Closing: weblogic.rjvm.t3.T3JVMConnection@23730e because of Server expected to route a message received over an uninitialized connection:
The server's ExternalDNSName was specified. Upon initial connection, the client addressed the request to the server instance's ExternalDNSName. The JVMID in the response from the server instance required the server's internal IP address and internal DNS name. Subsequent requests from the client were not recognized.
This is a known problem in WebLogic Server 7.0 that is resolved in SP03. The problem occurs if clients are connecting over t3 through a firewall.
Workaround: Add an entry to the external DNS servers that maps the server instance's internal DNS name to its external IP address.
7.0 SP03
CR074230
Applications deployed to WebLogic Server should perform file lookups relative to the Root Directory obtained with the ServerMBean.getRootDirectory() method (this defaults to the "." directory). For example, to perform a file lookup, use code similar to:
String rootDir = ServerMBean.getRootDirectory(); //application root directory File f = new File(rootDir + File.separator + "foo.in");
rather than simply:
File f = new File("foo.in");
If an application is deployed to a server that is started using Node Manager, use the following method calls instead:
String rootDir //application root directory if ((rootDir = ServerMBean.getRootDirectory()) == null) rootDir = ServerStartMBean.getRootDirectory(); File f = new File(rootDir + File.separator + "foo.in");
The ServerStartMBean.getRootDirectory() method obtains the Root Directory value that you specified when configuring the server for startup using Node Manager. (This corresponds to the Root Directory attribute specified the Configuration->Remote Start page of the Administration Console.)
A Managed Server started remotely by Node Manager does not recognize the weblogic.RootDirectory set on the Remote Start tab.
To avoid this problem, enter an absolute path for Staging Directory on the Domain—>Servers—>Configuration—>Deployment tab. Do not enter a relative path. Enter the full path, including the WebLogic Server root directory.
CR075142
The Administration Server and Node Manager may simultaneously attempt to close a TCP socket, causing the following error message to appear in the Node Manager log file:
<Apr 18, 2002 5:32:55 PM EDT> <Error> <NodeManager@localhost:5555> <OutputHandler: done2 socket close failed, reason: java.net.SocketException: Connection reset by peer.>
This problem does not affect the operation of Node Manager or the Administration Server.
RMI Known Issues
Change Request Number
Description
Release Fixed
CR099693
In 7.0 (G.A., SP01, and SP02), a client accessing WebLogic Server through a firewall using the t3 protocol, resulted in this error on the server:
####<Feb 17, 2003 10:15:59 AM EST> <Error> <RJVM> <ewibeasbx01.merck.com> <edmServer> <ExecuteThread: '14' for queue: 'default'> <kernel identity> <> <000506> <Closing: weblogic.rjvm.t3.T3JVMConnection@23730e because of Server expected to route a message received over an uninitialized connection:
The server's ExternalDNSName was specified. Upon initial connection, the client addressed the request to the server instance's ExternalDNSName. The JVMID in the response from the server instance the server's internal IP address and internal DNS name. Subsequent requests from the client were not recognized.
This is a known problem in WebLogic Server 7.0 that is resolved in SP03. The problem occurs if clients are connecting over t3 through a firewall. The workaround is to add an entry to the external DNS servers that maps the server instance's internal DNS name to its external IP address.
7.0 SP03
Security Known Issues
For information about BEA security advisories, refer to the BEA Advisories & Notifications page on the dev2dev Web site. On this page, you can download security-related patches and register to receive notifications of newly available security advisories. You can access the Advisories & Notifications page with the following URL: http://dev2dev.bea.com/advisories.
BEA has established an e-mail address (security-report@bea.com) to which you can send reports of any possible security issues in BEA products.
The following table summarizes security-related known issues for this service pack release:
Change Request Number
Description
Release Fixed
CR135489
When configuring custom security providers, you put the MBean JAR file for the provider in the WL_HOME\lib\mbeantypes directory. Placing other files in this directory is not advisable, because WebLogic Server will try to load any files in this directory, possibly causing server start-up errors.
CR051215
There is a problem with the password prompt on Solaris. If you press the ctrl-c keys when prompted for the password, the shell window becomes unusable because everything will be written in invisible text.
CR061030
WebLogic parses the grant statements in deployment descriptors for EJBs, servlets, and resource adapters but does not expand system variables.
Workaround:
Do not use variables in the <security-permission> tag in EJB, servlet, and resource adapter deployment descriptors.
CR064593
The following command-line arguments used to control the SSL time-to-live and cache size are ignored in WebLogic Server 7.0:
Clients using SSL now must have a valid license. Please refer to the WebLogic Server security documentation for instructions on specifying the license's location.
Also, clients using SSL must perform trust checks on the certificates of servers that connect to it by default. Please refer to the documentation on how to specify trusted Certificate Authorities.
CR066782
Statically loading JCE providers, or using Sun's JSSE implementation can cause interaction problems with SSL and WebLogic Server. You may see these errors:
<<java.security.NoSuchAlgorithm> Exception: Algorithm XXXXXX not available>>
or
<Unable to initialize the server: Fatal initialization exception Throwable: java.lang.ExceptionInInitializerError java.lang.ExceptionInInitializerError: java.lang.SecurityException: class "com.rsa.asn1.b"'s signer information does not match signer information of other classes in the same package
Using Sun's JSSE implementation can cause conflicts with WebLogic's SSL implementation, which causes these errors.
Workarounds: Remove the jsse.jar (that Sun's JDK 1.4 provides by default) from your JDK directory to resolve the conflict.
You may also see these errors if you are using JCE providers. Loading the providers dynamically rather than statically defining them in the java.security file may resolve the problem. Here's an example of a java.security policy:
The sunJCE provider is specifically unloaded by WebLogic Server if it is found to be registered statically. If you require the sunJCE provider, load it dynamically.
CR067087
The security-permission-spec attribute cannot currently be added to your weblogic-application.xml, you are limited to using this attribute within weblogic-ejb-jar.xml and weblogic.xml.
CR067621
The TLS_NULL_WITH_NULL_NULL cipher suite is not supported and will be ignored. A warning message will be logged indicating that the cipher suite is not being used.
CR067814
If you wish to use an LDAP browser to view the embedded LDAP server in WebLogic Server, use the following information
host:localhost
port:listen port for WebLogic Server
User DN:cn=Admin
Password:the password defined for the embedded LDAP server on the Domain-->Security-->Embedded LDAP tab.
CR072154
The MyListener class is implemented in the SSLSocketClient.java file. In the Class Summary table in the SSLClient Package-Summary.html file, the class is listed as SSLSocketClient.MyListener.
There is a known issue with the TLS_RSA_WITH_DES_CBC_SHA cipher when your SSL license allows only export level cryptography. This situation causes a server that is configured to use that suite to fail to start SSL when you boot the server. An example of the error you will see upon failure is as follows:
<Apr 2, 2002 7:32:24 AM PST> <Emergency> <WebLogicServer> <000209><ListenThread.run() failed: java.lang.IllegalArgumentException: Export Restriction on suite: TLS_RSA_WITH_DES_CBC_SHA java.lang.IllegalArgumentException: Export Restriction on suite:TLS_RSA_WITH_DES_CBC_SHA at com.certicom.tls.TLSSystem.setEnabledCipherSuites(Unknown Source) at javax.net.ssl.impl.SSLServerSocketImpl.setEnabledCipherSuites(Unknown Source) at weblogic.t3.srvr.SSLListenThread.newServerSocket(SSLListenThread.java:667) at weblogic.t3.srvr.ListenThread.run
Workaround: If your server is configured to use specific cipher suites, to allow your WebLogic Server to start up remove the following from the cipher suites configuration setting:
TLS_RSA_WITH_DES_CBC_SHA SSL_RSA_WITH_DES_CBC_SHA
CR074716
The Administrator, Operator, Deployer and Monitor roles are only partially functional in this release. Adding someone to those roles will give them access to the appropriate administrative MBean operations but will not give them access to the Administration Console.
Workaround: To give a user access to both the MBean operations and the console add them to the Administrators, Operators, Deployers and Monitors groups. Furthermore, if you are running in compatibility mode you should make sure that the system user is in the Administrators group.
CR075658
There is a known issue regarding access control lists (ACLs) for JDBC connection pools when running in compatibility mode or when using File realm as the security realm. If your fileRealm.properties file includes an ACL that grants any permission on a connection pool, the shrink and reset actions will be disallowed for that connection pool, even if you include ACLs that explicitly grant shrink and reset permission.
CR081250
A disabled user account in the LDAP Active Directory Authentication provider still authenticates to WebLogic Server.
Workaround:
Modify the user filter to only return accounts that do not have the UF_ACCOUNTDISABLE bit set. For example:
Original Filter microsoft.user.filter=(&(sAMAccountName=%u)(objectclass=user))
If a user account becomes locked and you delete the user account and add another user account with the same name and password, the UserLockout attribute will not be reset.
CR082926
The SimpleConnectionFilter2 sample in the Security Network Connection Filter samples may cause WebLogic Server not to boot. This problem is known to occur on Solaris platforms only, but may occur on others.
The sample file is at this location:
SAMPLES_HOME\server\src\examples\security\net
For example, when running the SimpleConnectionFilter2 sample on node sunbird, the following filter rule may cause the server to not boot:
temple2 10.61.4.13 7001 deny
Workaround: If the following filter rule is used, the server may boot properly:
sunbird 172.18.130.72 7001 deny
CR083155
The array of Strings returned from the getValues() method in the weblogic.security.service.ResourceBase class does not support String array value types. Specifically, the JNDIResource "path" key and the EJBResource's "signature" key always return null. If you are using WebLogic 7.0 (without Service Pack1), you may also get a NullPointerException when there are no non-null values in the array.
CR083242
After you configure a Realm Adapter Authentication provider in a security realm, WebLogic Server will not boot.
Workaround: Before you configure the Realm Adapter Authentication provider, create an empty filerealm.properties file in the directory from which you boot WebLogic Server. When you configure the Realm Adapter Authentication provider, set the Control Flag to Optional. Reboot WebLogic Server.
CR083273
When the username/password combination for a domain is specified as weblogic/weblogic, the Administration Console pre-populates the username and password causing a potential security risk.
Workaround: Do not use the username/password combination of weblogic/weblogic in production.
CR085089
When creating a Custom Authorization provider, specifying EJB parameters of the same type in the getname() method of the ContextElement is broken. Only the first parameter of the type is retrieved. This known problem is fixed in WebLogic Server 7.0 SP02.
Tools Known Issues
Change Request Number
Description
Release Fixed
CR064893
The following deployment descriptor elements cannot be edited in WebLogic Builder:
WebLogic Builder may fail to access a database on a server if the driver classes for the database are not on the client.
CR066466
WebLogic Builder does not provide the option to cancel operations.
CR066668
On Linux, WebLogic Builder's file browser opens at root instead of current directory.
CR068152
The operations Add, Edit, and Delete can be slow in the EJB elements of WebLogic Builder.
8.1
CR068165
In the Add dialog in Resource Links, in the WebLogic Settings, J2EE Links, WebLogic Builder incorrectly offers a selection of application scoped data resources.
CR068620
Table columns may not resize properly in WebLogic Builder.
8.1
CR069568
WebLogic Builder cannot map multiple roles to a method in EJB method permission.
CR071833, CR072541
WebLogic Builder support for RARs does not include generation of deployment descriptors.
CR072700, CR074591
If you use WebLogic Builder's deployment dialog box to undeploy an application, application the dialog will not show the undeployment. This dialog may also report that applications whose deployment has failed are deployed.
CR073715
WebLogic Builder may not be able to display multiple RDBMS XML files.
7.0 SP2
CR073975
WebLogic Builder incorrectly allows you to add a transaction without specifying a method or a transaction attribute.
7.0 SP3
CR074210
Optimistic concurrency strategy does not work in WebLogic Builder.
8.1
CR074247
In WebLogic Builder, adding a finder with a duplicate method name may update the original finder instead of adding the new one.
7.0 SP2
CR074322, CR074856
In WebLogic Builder, cancelling an edit action may not work.
8.1
CR074566
Finders or CMP values modified through WebLogic Builder's BeanGrid/Edit (like include-update) may not be represented in the individual panels.
8.1
CR074622
In editing a CMP field using the WebLogic Builder's pop-up dialog, if you set column type to OracleCLOB and then click on the CMP tree node, the column type change doesn't show up on the CMP panel.
CR074634, CR074955, CR074972
Using WebLogic Builder's Relations wizard to edit the relations of a CMP with multiple relations already configured results in an exception.
7.0 SP2
CR074639
When you edit a Finder method name using WebLogic Builder's editing panel, the change doesn't propagate to XML. When you edit using the Finder pop-up dialog, the change does not propagate to XML or to the editing panel.
7.0 SP2
CR074728
WebLogic Builder does not allow changing a method to a local method.
CR074754
Editing some transaction attributes may cause WebLogic Builder to create duplicate descriptors.
CR074775
It is recommended that you set the enable-call-by-reference element explicitly in WebLogic Builder.
CR074961
If you use WebLogic Builder to generate web.xml descriptors, it creates a security-role "guest" which pertains to the pre-7.0 security protocol.
CR075005
Specifying an invalid drive when opening a component (type bogusDrive
in the textbox, press enter and select open) in WebLogic Builder causes a NullPointerException.
7.0SP2
CR075006
In some circumstances WebLogic Builder will not properly construct one-to-many relations.
7.0 SP2
CR075129
If you switch a stateless session bean to stateful, WebLogic Builder may not show that the module is dirty.
CR075228
WebLogic Builder may throw an assertion error if you delete a transaction or permission method.
8.1
CR075586
If you want to use WebLogic Builder with the WebLogic Server Examples Server or examples, you should run setExamplesEnv (located at%SAMPLES_HOME%\server\config\examples) before starting WebLogic Builder, so that files needed to run the PointBase database server will be added to the classpath. If you do not, you will get database error messages.
CR075753
Some descriptor elements may pass through WebLogic Builder validation and then be found to be in error by ejbc.
CR075924
In some cases, WebLogic Builder may not properly generate descriptor files for nested WAR files in EARs.
8.1
CR075936
WebLogic Builder may generate an illegal value for the element <estimated-bean-size>.
8.1
WebLogic Tuxedo Connector Known Issues
Change Request Number
Description
Release Fixed
CR067275
Load balancing and fail-over are not supported with WebLogic Tuxedo Connector in a cluster using RMI over IIOP.
CR079630
Most users will expect to set the Correlation ID using the setJMSCorrelationID(String) method. This will take a 32 character string and turn it into a 64 byte array. JMS stores the string as UTF-16BE. When the tBridge receives the Correlation Id from Tuxedo it is 32 characters as 32 bytes. The tBridge then uses the setJMSCorrelationIDAsBytes(byte[]) method to set the message for JMS receiving queue. The characters may be the same in ASCII but the two will not compare due to the length difference.
Workaround: When it is necessary to compare the Correlation ID with the ID returned from Tuxedo in the receiving JMS queue, create a byte array containing the hexadecimal values of the Correlation ID. Then use the setJMSCorrelationIDAsBytes() and getJMSCorrelationIDAsBytes()methods to create an ID to compare with the ID returned from Tuxedo in the receiving JMS queue.
For example, if the string Correlation ID is "1234567890ABCDEFGHIJKLMNOPQRSTUV":
The command line version of the clientgen Ant task doe not support the following options that correspond to the Ant task attributes:
-autotype -overwrite
8.1
CR073661
WebLogic Web services that are described with an invalid web-services.xml file deploy incorrectly on WebLogic Server, although they are not accessible by client applications trying to invoke them.
CR073899
When generating a SOAP fault, WebLogic Web services adds extra non-CDATA characters.
7.0 SP2
CR083493
The messages and multicomponent examples in the Web Services examples package do not contain the code needed to generate a downloadable client.jar file.This omission does not affect the functionality of the examples that work with the provided client.
CR101160
Complex data types in service-specific exceptions are not handled in strict accordance with the Java API for XML-Based RPC (JAX-RPC) 1.0 specification, as follows:
Section 4.3.6 WSDL Fault, Service Specific Exception: When the clientgen Ant task generates the JAX-RPC stubs from a WSDL that contains a wsdl:fault element whose message part is an xsd:complexType, the generated stubs incorrectly map the xsd:complexType to a simple Java type. This means that when a client application uses the stubs to invoke the Web Service, and the service throws the service-specific exception (rather than the a javax.xml.rpc.SOAPFaultException), the client application cannot access the full complex data from the exception.
There is no workaround to this problem.
Section 5.5.5 Methods, Exceptions, fourth bullet: The WebLogic Web Service runtime incorrectly maps multiple fields in a service-specific Java exception class to a simple XML data type, rather than to an xsd:complexType.
Workaround: always throw a javax.xml.rpc.SOAPFaultException,
rather than a service-specific exception, when implementing a WebLogic Web
Service.
XML Known Issues
Change Request Number
Description
Release Fixed
CR070547
When using the XML Streaming API on Solaris, some character references do not resolve to the same character as on NT.
Known Issues in WebLogic Server 7.0
This section lists problems in WebLogic Server 7.0 that are not associated with a specific Service Pack.
Connector Known Issues
Change Request Number
Description
Release Fixed
CR098342
The WebLogic Server 7.0 JCA implementation is not compatible with the IBM CICS resource adapter. BEA's implementation of the javax.resource.spi. ConnectionManager interface does not direct return the object returned by the getConnection() method of the resource adapter's implementation of the javax.resource.spi.ManagedConnection interface. It returns an instance of a class dynamically generated by the java.lang.reflect.Proxy class instead.
Core Server Known Issues
Change Request Number
Description
Release Fixed
CR106616
There is a problem in Netscape Version 4.79 running on Linux AS2.1 and HP-UX.
After several operations on the WebLogic Server Administration Console, the browser shuts down with a bus error, sometimes with a core dump.
EJB Known Issues
Change Request Number
Description
Release Fixed
CR061938
EJB QL queries can return spurious duplicates that are the results of SQL cross products. This can occur under the following conditions:
The EJB-QL query contains path expressions that navigate relationships; this generates multiple tables in the generated SQL SELECT clause.
The WHERE clause contains OR operands which navigate relationships, and not all of the path expression in the OR operands map to all of the tables in the generated SQL SELECT clause for the query; this may cause a cross product to show up in the results for that OR operand.
The following example illustrates the problem:
EJB QL:
SELECT OBJECT(c) FROM CustomerBean AS c, IN(c.accounts)accts WHERE c.name = '100' OR c.accts.bal = 300
CREATE TABLE thorick_accounts (acct_id INTEGER, bal FLOAT, PRIMARY KEY (acct_id));
INSERT INTO thorick_accounts VALUES (100, 100.0); INSERT INTO thorick_accounts VALUES (200, 200.0); INSERT INTO thorick_accounts VALUES (300, 300.0); INSERT INTO thorick_accounts VALUES (400, 400.0); INSERT INTO thorick_accounts VALUES (500, 500.0); INSERT INTO thorick_customers VALUES('100', 'jazz', 2, null); INSERT INTO thorick_customers VALUES('900', 'punk', 3, 400); SELECT WL0.cust_name, WL0.cust_interests, WL0.acct_id FROM thorick_Customers WL0, thorick_Accounts WL1 WHERE WL0.cust_name = '100' OR ( wl1.bal = 300 AND wl0.acct_id=wl1.acct_id );
CUST_NAME CUST_INTER ACCT_ID ---------- ---------- ---------- 100 jazz 100 jazz 100 jazz 100 jazz 100 jazz
JDBC Known Issues
Change Request Number
Description
Release Fixed
CR101419
Fail-over for DataSources and TxDataSources in a cluster is not working in this release.
8.1 SP1
RMI Known Issues
Change Request Number
Description
Release Fixed
CR099693
In 7.0 (G.A., SP01, and SP02), when a client accesses WebLogic Server through a firewall using the t3 protocol, this server error results:
####<Feb 17, 2003 10:15:59 AM EST> <Error> <RJVM> <ewibeasbx01.merck.com> <edmServer> <ExecuteThread: '14' for queue: 'default'> <kernel identity> <> <000506> <Closing: weblogic.rjvm.t3.T3JVMConnection@23730e because of Server expected to route a message received over an uninitialized connection:
The server's ExternalDNSName was specified. Upon initial connection, the client addressed the request to the server instance's ExternalDNSName. The JVMID in the response from the server instance required the server's internal IP address and internal DNS name. Subsequent requests from the client were not recognized.
This is a known problem in WebLogic Server 7.0 that is resolved in SP03. The problem occurs if clients are connecting over t3 through a firewall.
Workaround: add an entry to the external DNS servers that maps the server instance's internal DNS name to its external IP address.
7.0 SP03
Spaces in Directory Names
WebLogic Server will not start from a directory whose name or address includes a space. For example, the following directory names cause failures on startup:
D:\bea new\weblogic700 space\
D:\bea new\
Do not include spaces in directory names in WebLogic Server 7.0. This issue is represented in change request CR084568.
EJB Pass By Value J2EE Incompatibility
Many of the WebLogic Server EJB deployment properties have default values that are optimized for performance. In some cases, these default values are not compliant with the EJB specification. Should you wish to make WebLogic Server compliant with the EJB specification, you must set the following properties:
In weblogic-ejb-jar.xml set enable-call-by-reference to False.
In weblogic-cmp-jar.xml, set include-updates to True.
In weblogic-cmp-jar.xml, set check-exists-on-method to True.
HTML Pages and Netscape
If you already have a Netscape browser running when you start WebLogic Server, some HTML pages will not display. For example, if you select the About WebLogic Server page from the Start menu, and you have Netscape running and do not have Microsoft Internet Explorer, the screen may flash but the page will not display.
Clusters, DNS, and Multihoming on NT
Be aware of naming issues when using multihoming features on Windows NT in a cluster. For example, naming conflicts may occur if a cluster is running on a multihomed Windows NT machine and one of the servers in the cluster is bound to the same DNS name as the machine name. Attempts to contact that server using the DNS name in a URL may result in Windows NT converting that DNS name to any of the IP addresses of the multihomed Windows NT machine. In this case, the request may go to the wrong address. Avoid having DNS names that match your machine name.
WebLogic Keystore Provider Support
Only Java 2 Enterprise Edition (JKS) keystores can be used with the WebLogic Keystore provider. JKS keystores that are password-protected can now be used with the WebLogic Keystore provider.
Note: The WebLogic Keystore provider is deprecated in this release of WebLogic Server.
Transaction Limitations with a Non-XA JDBC Driver in a Multi-Server Environment
The Emulate Two-Phase Commit (or EnableTwoPhaseCommit=true) option on a TxDataSource is designed to allow a single non-XA resource to participate in a distributed transaction. You can use only one such TxDataSource in a distributed transaction.
In a multi-server environment (including clusters), if you configure a TxDataSource with a non-XA resource on more than one server, an application must access the resource on the server that acts as the transaction coordinator. If not, an error will occur during commit processing which will result in a heuristic completion.
In a clustered environment, there is a greater risk for this error to occur due to load balancing between multiple servers.
Workaround:
Use a JDBC driver that supports XA to access JDBC resources in distributed transactions.
