Oracle® Fusion Middleware Release Notes 11g Release 1 (11.1.1) for Oracle Solaris on SPARC (64-Bit) E14772-21 |
|
![]() Previous |
![]() Next |
This chapter describes issues associated with Oracle WebLogic Server. It includes the following topics:
Section 11.2, "Administration Console Issues and Workarounds"
Section 11.3, "Apache Beehive Support Issues and Workarounds"
Section 11.6, "Connector (Resource Adapter) Issues and Workarounds"
Section 11.8, "Core Server and Core Work Manager Issues and Workarounds"
Section 11.12, "HTTP Publish/Subscribe Server Issues and Workarounds"
Section 11.21, "Java Virtual Machine (JVM) Issues and Workarounds"
Section 11.24, "Operations, Administration, and Management Issues and Workarounds"
Section 11.31, "Spring Framework on WebLogic Server Issues and Workarounds"
Section 11.32, "System Component Architecture (SCA) Issues and Workarounds"
Section 11.35, "WebLogic Server Scripting Tool (WLST) Issues and Workarounds"
Section 11.37, "Web Services and XML Issues and Workarounds"
Section 11.38, "WebLogic Tuxedo Connector Issues and Workarounds"
Note: For a list of bugs that are fixed in WebLogic Server 11g Release 1 (10.3.3), enter the following document ID in the Search Knowledge Base field. You must enter the entire document ID.1080299.1 The 10.3.3 list includes bugs that were fixed in the WebLogic Server 10.3.1, 10.3.2, and 10.3.3 releases. The same list is also stored in your WebLogic Server installation in the following location:
|
This section describes the following issues and workarounds:
Section 11.1.2, "Oracle ojdbc14.jar File Has Been Changed to ojdbc6.jar"
Section 11.1.3, "Strong Password Enforcement May Cause Issues With WLST Offline Scripts"
Section 11.1.4, "In Turkish Locale, MDS Initialization Fails"
Section 11.1.5, "Administration Server Reports a 'Too Many Open Files' Message on the EM Console"
Oracle Fusion Middleware 11g contains Oracle WebLogic Server 11g. The version number of Oracle WebLogic Server is 10.3.3.
The Oracle ojdbc14.jar
file has been changed to ojdbc6.jar
, for use with JDK 5 or 6. As a result, any explicit references you make to ojdbc14.jar
must be changed to ojdbc6.jar
.
With the implementation of strong password enforcement (8 character minimum with one numeric or special character) in this release of WebLogic Server, existing scripts could potentially encounter issues.
Workaround
Use either of the following workarounds to bypass the new password restrictions.
Set the BACKWARD_COMPAT_PW_CHECK
environment variable to true
.
Include the -Dbackward.compat.pw.check=true
option when invoking WLST.
Oracle recommends that you change passwords to comply with the new password requirements, as this variable and option will be removed in a future release of WebLogic Server.
Any applications that use an MDS repository cannot be deployed or run with the JAXB version bundled with WebLogic Server as null values are returned for attributes named id
.
Workaround
Start the server in English locale.
The WebLogic Server Administration Server reports a Too Many Open Files
message on the Enterprise Manager (EM) console when the maximum number of file descriptors configured for the Administration Server is less than 65535.
Workaround
Increase the number of file descriptors within the shell and restart the WLS Administration Server within that shell. The command to increase the number of file descriptors (nofiles) differs across Operating Systems and shells but it's usually done with the ulimit command on UNIX platforms so consult the man pages for ulimit.
For example:
$ ulimit -n 65535
This section describes the following issues and workarounds:
Section 11.2.2, "Pressing Browser Back Button Discards Context"
Section 11.2.3, "Unsupported Work Manager Configurations Can Be Created"
Section 11.2.4, "Server Status Table Reflects Inconsistent Information"
Section 11.2.5, "Exceptions When Defining a Security Policy for an EJB"
Section 11.2.9, "Data Takes a Long Time to Display on the Metric Browser Tab"
Information about cached JDBC statements is not displayed on the JDBC Monitoring pages.
After a page flow completes in the Administration Console, it forwards to a different page, typically a table.
Pressing the browser Back button at this point results in an attempt to load the last JSP file in the completed assistant. At this point, all of the context for this assistant is discarded.
Workaround
Oracle recommends that you do not use the browser Back button to step back into an assistant once changes are cancelled or finished, and that you do not go back to a previous step in an assistant. Instead, use the navigation links and buttons in the Administration Console.
The Administration Console permits the creation of Work Manager configurations that are not supported and do not function as intended. Incorrect Work Manager configurations may result in a number of exceptions being recorded in the server logs, most commonly 'Validation problems were found'
exceptions while parsing deployment descriptors.
Workaround
Follow the guidelines described in the online help for Work Manager configurations. Specifically, you can only assign one request class to any given Work Manager, and that request class must be of the same or a broader scope than the Work Manager. You should not assign an application-scoped request class to a global Work Manager, and you should not create more than one application-scoped request class for an application-scoped Work Manager.
Correcting the Work Manager configurations to match the documented constraints resolves these issues.
The Server Status table on the Cluster: Monitoring: Summary page includes two default columns: Primary and Secondary Distribution Names. These fields do not always reflect all of the replication statistics that are collected and displayed on the Cluster: Monitoring: Failover page, depending on the replication scenario.
Please refer to the Cluster: Monitoring: Failover page for definitive information.
When defining security policies in the Administration Console for an EJB deployment that references types defined in a separate library deployment, exceptions can be observed if that library deployment is not available to the Console.
Workaround
All library deployments should be targeted at the WebLogic Server Administration Server as well as any Managed Servers needed to support referencing applications. This will ensure that when defining policies, the Console will have access to those library deployments so that referenced types can be class-loaded as needed.
The Administration Console does not always reflect external changes made in a deployment plan. If a change is made in a deployment plan outside of the Console (for example, using Workshop, editing the plan text files directly, or updating a deployment with a new plan using WLST or webLogic.Deployer) while a Console user is also viewing that deployment plan, the Console user will not see those changes.
Workaround
Navigate to a configuration page for a different deployment, then navigate back to the original deployment again.
The Oracle OCI driver is no longer explicitly listed as a preconfigured driver type in the Administration Console.
Workaround
The Oracle OCI driver remains a supported driver for application data connectivity, consistent with prior releases of Oracle WebLogic Server. However, users must now specify all required configuration properties manually, including the data base username.
Prior to WebLogic Server 10.3.3, you could view the WSDL for the current Web service by selecting the Configuration > WSDL tab. The WSDL tab has been removed as of WebLogic Server 10.3.3. To view the WSDL for the current Web service, select the Testing tab, expand the name of the Web service to view its test points, and click WSDL.
When using Internet Explorer 7 (IE 7) to display data on the Metric Browser tab of the Monitoring Dashboard, it takes an unusually long time for the data to display, and during this time, the page is unresponsive. The amount of time it takes to display data on this tab depends on the size of the domain.
Workaround
If you need to display data on the Monitoring Dashboard > Metric Browser tab, open the Administration Console in a supported web browser other than IE 7, such as Internet Explorer 8 or greater, Firefox 3 or greater, or Safari 4 or greater.
There are no known Apache Beehive Support issues in this release of WebLogic Server.
This section describes the following issue and workaround:
When using Unicast mode for cluster communication, many threads are blocked on cluster messaging. Some cluster members drop out from the cluster and may take some time to rejoin the cluster.
Workaround
Set the following system property to resolve this issue:
-Dweblogic.unicast.HttpPing=true
This section describes the following issues and workarounds:
Section 11.5.1, "Directory For a Non-Existent Server Name Is Created"
Section 11.5.2, "Abnormal Behavior in Terminal Window After Entering WebLogic Password"
If you attempt to connect to the WebLogic Server Administration Server with a non-existent server name, a directory for the non-existent server name is created under the domain_name
/servers
directory.
Workaround
Specify a valid server name when connecting to the Administration Server.
After pressing Ctrl-C to terminate the startManagedWebLogic.sh
process immediately after entering the WebLogic password, abnormal behavior may be experienced in the terminal window. For example, when pressing Return, the prompt is tabbed instead of going to the next line, and any characters that are entered at the prompt are not displayed in the terminal.
Workaround
Either close the current xterm and start a new one, or enter stty echo
into the xterm.
This section describes the following issue and workaround:
When trying to connect to the WebLogic Server Administration Server from WLST using localhost
as the host name, the following message may be displayed if the listen-address attribute of the Administration Server has been restricted to certain IP addresses:
javax.naming.CommunicationException [Root exception is java.net.ConnectException : <t3://HOST:PORT> : Destination unreachable; nested exception is: java.net.ConnectException: Connection refused; No available router to destination
Workaround
Use either of the following workarounds:
Check that the listen-address attribute of the Administration Server has been set correctly in the domain configuration file. You can either remove the listen-address
line or simply comment it out. Oracle recommends that you comment it out in case you need to know the value at a later time. For example, in the domain configuration file:
<server> <name>AdminServer</name> <ssl> . . . </ssl> <machine>machine_name</machine> <!-- listen-address>machine_ip_address</listen-address --> </server>
Use the host name of the Administration Server, instead of localhost
, in the WLST connect
command.
There are no known Extensions issues in this release of WebLogic Server.
This section describes the following issues and workarounds:
Section 11.8.1, "Threads Become Stuck While Waiting to Get a Connection"
Section 11.8.3, "Server Cannot Be Started After a Whole Server Migration"
Section 11.8.4, "Object State is not Retained After Renaming Field"
Section 11.8.5, "Forcing Unicast Messages To Be Processed in Order"
Section 11.8.7, "Administration Server or Node Manager Cannot Track the Status of a Managed Server"
Section 11.8.8, "Multicast Traffic Observed to be Unreliable During or After a Network Partition"
When a machine that is hosting one of the Managed Servers is abruptly shut down, a network cable is pulled, or its network interface card has issues, and any server attempts communication with that managed server, threads become stuck waiting to get a connection.
Workaround
This can currently be resolved by using a private flag:
-Dweblogic.client.SocketConnectTimeoutInSecs
and setting an appropriate timeout value that will release the thread attempting to make the connection and allow the request to fail quickly.
When using an IPv6-formatted address for WebLogic Server, the URL should include square brackets ('[' and ']') for the host address. Otherwise, WLST may fail to connect to the running server.
Workaround
Add square brackets to the host address. For example:
t3://[fe80:0:0:0:203:baff:fe2f:59e5]:9991
If the WebLogic Server Administration Server is down when a Whole Server Migration occurs for a clustered server, and the server migrates to a machine on which it was never run before, the server cannot be started on the new machine.
Workaround
Use one of the following workarounds for this issue:
Ensure that the Administration Server is up when the server migration is being performed.
Use a shared disk/NFS for all the migratable servers in the cluster.
When FastSwap is enabled in a J2EE application, you can make certain types of changes to Java classes during development and expect to see the change without re-deploying, with all instance states of the Java object being retained.
One type of change that does NOT retain the object state is that when a field name is changed, it is treated as follows:
the field with old name is deleted
the field with new name is added
Thus, in this case, any state in the old field is not carried over to the renamed field.
Using the Workshop or FastSwap ant task, you may see a FastSwap operation completed successfully
message, even when an instance field name change causes a value reset.
Workaround
You should expect an instance value to be reset when you change a field name.
The following conditions can cause very frequent JNDI updates, and as a result, JMS subscribers may encounter a java.naming.NameNotFoundException
:
Unicast messaging is being used for cluster communication.
The JMS topic connection is set with setReconnectPolicy("all")
.
JMS durable subscribers on topic are created and removed very frequently.
Workaround
To fix this issue, a new property, MessageOrderingEnabled
, has been added to the ClusterMBean
. This property forces unicast messages to be processed in strict order. By default, this property is not enabled. To enable the property, add the following line manually to the <cluster>
element in config.xml
.
<message-ordering-enabled>true</message-ordering-enabled>
When using a hostname to specify configuring the listen address on the WebLogic Server Administration Server or a Managed Server, machines that are configured with multiple Ethernet cards may listen on a different hostname after startup. For example:
The machine has 3 Ethernet cards
Card 1 is mapped to hostname1-s
(DNS registered hostname)
Card 2 is mapped to hostname1-i
(DNS registered hostname)
Card 3 is mapped to hostname1
(actual node's hostname)
You configure the server to listen on hostname1
After starting the server, it is listening on hostname1-s
because Windows resolves the actual node's hostname to the first enabled Ethernet card address
Workaround
Use one of the following three workarounds for this issue:
Use the IP address, instead of the hostname, as the listen address of the WebLogic Server Administration Server. On Managed Servers, use the IP address as the listen address, or configure the actual physical hostname to the first Ethernet card in the machine.
Add the following entry to the C:\Windows\system32\drivers\etc\hosts file on the machine:
<ip_address> <hostname>
Change the order of the network cards in the machine so that the card with the actual node's hostname is Card 1.
If you start a managed server by providing an incorrect WebLogic Server Administration Server URL from the command line (that is, the Administration Server cannot be reachable at the provided URL), the managed server will start in Managed Server Independence (MSI) mode.
In this case, neither the Administration Server nor Node Manager can track the status of the managed server. The Administration Console will show the status of the managed server as UNKNOWN, but the server will actually be RUNNING in MSI mode.
During or after a network partition that causes a server migration to take place, multicast traffic has been observed to be unreliable. For example, one node may be receiving multicast traffic, but traffic originating from this node is not received on other nodes in the network. As a result, the migrated servers are not added to the cluster because their heartbeats were not received.
Workaround
Currently, the only known workaround is to use unicast cluster messaging.
This section describes the following issues and workarounds:
Section 11.9.1, "security-permission Element is not Available in weblogic-application.xml"
Section 11.9.2, "Extraneous String Values Interpreted as File Specification"
Section 11.9.3, "java.lang.NoClassDefFoundError is Displayed"
Section 11.9.4, "The restore Method Does Not Update the DConfig Bean With Plan Overrides"
Section 11.9.5, "config-root <directory> not found Warning Is Displayed When Applying a Plan"
Section 11.9.6, "Application State Is Not Updated If the Server Starts in MSI Mode"
The security-permission
element is available in the weblogic.xml
and weblogic-ejb-jar.xml
deployment descriptors, but is not available in the weblogic-application.xml
descriptor. Therefore, in an Enterprise application, you can only apply security policies to JAR files that are EJBs or Web applications.
The weblogic.Deployer tool interprets any extraneous string values between command-line arguments as a file specification. For example, if you enter the command:
java weblogic.Deployer -activate -nostage true -name myname -source c:\myapp\mymodule
the tool attempts to activate a file specification named true, because the -nostage
option takes no arguments and true
is an extraneous string value.
While using the WebLogic Server Administration Console with applications or EJBs deployed on a Managed Server that depend on a deployed library, you may encounter a java.lang.NoClassDefFoundError
.
Workaround
The WebLogic Server Administration Console needs access to any shared library deployments so that Java data types and annotations can be processed. Therefore, all shared library deployments should always be targeted to the WebLogic Server Administration Server in addition to any Managed Servers or clusters.
The restore method does not correctly update the DConfig Bean with the plan overrides. For example, given the following steps:
DeployableObject dObject = WebLogicDeployableObject.createDeployableObject(new File(appName)); DeploymentConfiguration dConfig = WebLogicDeploymentManager.createConfiguration(dObject); dConfig.restore(new FileInputStream(new File(plan)));
the plan does not correctly override the DConfig Bean.
Workaround
Specify the plan when initializing the configuration for the application. For example:
helper = SessionHelper.getInstance( SessionHelper.getDisconnectedDeploymentManager()); helper.setApplication(app); helper.setPlan(new File(plan)); helper.initializeConfiguration();
If you use the Administration Console to make configuration changes to an application, a deployment plan will be generated. If external descriptors are generated as part of the deployment plan, they are placed in the config root plan directory. This directory will be set in the deployment plan 'config-root' attribute.
If no external descriptors are required, the config root directory will not be created, and a warning is displayed when you apply the deployment plan. This results in the following warning in the server output:
<Warning <WWebLogicDescriptorWL> <BEA-2156000><"config-root" C:\deployments\plan was not found>.
Workaround
Create the plan directory manually.
A managed server will start in MSI mode if the WebLogic Server Administration Server is not available when the managed server starts. If you start the Administration Server later, the managed server will connect to the Administration Server. However, the state of each application deployed to the managed server is not updated to reflect the state of the applications on the managed server. Each application's state is displayed as NEW or PREPARED in the WebLogic Server Administration Console.
Workaround
There are two workarounds for this issue:
Start the Administration Server before starting the managed server, or
Redeploy the application after starting the Administration Server.
If you initially deployed an application using one source file location, then attempt to redeploy the application using a new location for the source file, the deployment fails with the following exception:
New source location <new_source_file_path> cannot be configured deployed to
configured application, <application_name>. The application source is at
original_source_file_path. Changing the source location is not allowed for a
previously attempted deployment. Try deploying without specifying the source.
This is due to a WebLogic Server deployment restriction. Once you specify the source file for a deployment, you cannot change it on a redeployment.
Workaround
Undeploy the application before attempting to redeploy it using a new source file location.
This section describes the following issues and workarounds:
Section 11.10.2, "No Available Annotation That Enables Creation of a Clusterable Timer"
Section 11.10.3, "Kodo's MappingTool Cannot Generate Schemas"
Section 11.10.4, "Extensions to the JPA Metadata Model Can Only Be Specified Via Annotations"
Section 11.10.5, "Lookup Method Injection Not Supported by Spring"
Section 11.10.6, "Deserializing a JDO PersistenceManagerFactory in a Managed Environment May Fail"
Section 11.10.7, "Indexes Not Always Created During Schema Creation"
Section 11.10.8, "OpenJPA throws an exception when @Id fields are also annotated as @Unique"
Section 11.10.9, "Cache Hit and Miss Counts May Rise Unexpectedly"
Section 11.10.10, "Open JPA Tries to Create a Table Even if the Table Exists"
Section 11.10.11, "EJB Applications Fail During Serialization"
The primary key in an Oracle table is a CHAR but the query field in the SQL table is a VARCHAR2.
Workaround
Change the database schema from CHAR to VARCHAR2. Using CHAR as a primary key is not recommended for the Oracle database.
There is no annotation for EJB3 beans or Ejbgen
that enables creation of a clusterable timer.
Workaround
Create a weblogic-ejb-jar.xml file and put the <timer-implementation>
element and corresponding values into the file.
Kodo's MappingTool cannot generate schemas for classes that use BLOBs in their primary key. BLOBs can be used in a primary key, but the schema must be defined manually. Note that support for BLOB columns in primary keys is not mandated by either the JDO or JPA specifications.
Extensions to the JPA metadata model can only be specified via annotations, and not via a structure similar to the orm.xml file defined by the specification.
Workaround
To specify Kodo-specific metadata for your object model, either:
use the Kodo-specific annotations, or
convert your XML-based metadata to the JDO metadata format, which does support XML specification of extensions.
The Weblogic Spring injection extension model doesn't support lookup method injection.
Deserializing a JDO PersistenceManagerFactory
in a managed environment may fail. The exception states that the javax.jdo.PersistenceManagerFactoryClass
property is missing. Note that serializing a PersistenceManagerFactory
should not generally be necessary in a managed environment.
Indexes declared at the class level are not always created during schema creation.
Workaround
Create the indexes manually after running the schema generation tools.
OpenJPA throws an exception when @Id
fields are also annotated as @Unique
in some databases. Database primary keys are unique by definition. Some databases implement this by creating a unique index on the column.
Workaround
Do not specify both @Id
and @Unique
on a single field.
The cache hit and miss counts may rise unexpectedly when manipulating entities without version data. The extra cache access occurs when the EntityManager closes and all contained entities are detached. Entities without version fields appear to the system to be missing their version data, and the system responds by checking their version in the cache before detachment.
Workaround
Entities with version fields or other version strategies do not cause extra cache access.
When using the MySQL database, and OpenJPA is configured to automatically run the mapping tool at runtime and create tables within the default schema (for example):
<property name='openjpa.jdbc.SynchronizeMappings' value='buildSchema'/>
<property name='openjpa.jdbc.Schema' value='MySQL database name' />
OpenJPA will try to create the table even if the table already exists in the database. A PersistenceException will be thrown to indicate that the table already exists and the table creation statement fails.
Workaround
To avoid this problem, if you are using the MySQL database, don't configure OpenJPA to automatically run the mapping tool at runtime and specify the default schema at the same time.
EJB applications that use IIOP and send JPA entities from the server to the client will fail during deserialization if the entities are Serializable (but not Externalizable) and do not declare a writeObject()
method.
Workaround
Add a writeObject()
method to such entity classes. The write object can be trivial:
private void writeObject(java.io.ObjectOutputStream out) throws IOException { out.defaultWriteObject(); }
When using multi-threaded processing for non-transactional topic Message-Driven Beans (MDBs) that specify a foreign topic (non-WebLogic) JMS, the MDB container can fail to provide reproducible behavior. For example, if a runtimeException
is thrown in the onmessage()
method, the container may still acknowledge the message.
Workaround
Set the max-beans-in-free-pool
attribute to 1 in the deployment descriptor.
This section describes the following issues and workarounds:
Section 11.11.1, "Security Configuration in medrec.wls.config"
Section 11.11.2, "HTML File not Created for StreamParser.java File"
Section 11.11.3, "Warning Message Appears When Starting Medrec or Samples Domain"
The medrec.wls.config
target in SAMPLES_HOME/server/medrec/setup/build.xml
has a known issue with respect to security configuration.
The ../xml/stax
example contains two files with the same root but different extensions: StreamParser.java
and StreamParser.jsp
. The samples viewer build, however, creates just one corresponding HTML file, rather than two for each type of file. In this case only the StreamParser.jsp
file has an equivalent HTML file; the StreamParser.java
file does not.
The problem occurs because of a setting in the build.xml file that controls the behavior of java2html
to generate the files for the documentation.
When using java2html
, the useShortFileName="true"
parameter crops off the file extensions for the source files to create the file names for the HTML output files. If two files have the same name and different file extensions, whichever HTML file is generated last will overwrite previous ones.
Workaround
Set the useShortFileName
parameter to "false". This setting generates HTML files with the file extensions included in the name. The drawback to this solution is that every link that points to the HTML output file needs to be revised, regardless of whether the files in question were affected by the bug.
When you start the medrec or samples domains, you may see a warning message similar to this:
<Warning> <WorkManager> <BEA-002919> <Unable to find a WorkManager with name weblogic.wsee.mdb.DispatchPolicy. Dispatch policy weblogic.wsee.mdb.DispatchPolicy will map to the default WorkManager for the application bea_wls_async_response>
This warning message appears in the standard output of the Console while starting a WebLogic Server sample application with an asynchronous Web Service deployed.
Workaround
The warning is harmless and can be ignored.
This section describes the following issues and workarounds:
Section 11.12.1, "Authentication and Authorization of the Local Client is not Supported"
Section 11.12.2, "Event Messages Published by Local Clients Cannot Be Received"
Section 11.12.3, "Event Messages Published By Local Clients Do Not Go Through Filters"
The HTTP Publish/Subscribe server does not support authentication and authorization of the local client. The local client has full permissions to operate on channels of the HTTP Publish/Subscribe server, which means the local client can create/delete channels and publish/subscribe events from channels.
In a clustering environment, event messages published by a local client on a server can be received only by subscribed clients connected to the same server. These messages cannot be received by subscribed clients connected to other servers in the cluster.
Event messages published to a channel by a local client will not go through the Message Filters configured to that channel.
This section describes the following issues and workarounds:
The Oracle WebLogic Server 11g Release 1 installer does not download the Sybase JDBC drivers. When you try to upgrade an existing WebLogic Server 10.3 installation using the latest installer, it does not remove the Sybase JAR files from the original installation. The installer upgrades only the weblogic.jar file.
The Sybase JAR files (jconn2.jar, jconn3.jar, and jConnect.jar) in the /server/lib or /server/ext/jdbc/sybase directories are removed from the manifest classpath in the upgraded weblogic.jar file. Therefore, if the classpath of a WebLogic Server application does not include Sybase JAR files and only includes weblogic.jar then after the upgrade installation, the application will throw a ClassNotFoundException.
To work around this issue, explicitly add Sybase JAR files in the WebLogic Server application classpath.
When using an Upgrade installer or Smart Update to upgrade an existing WebLogic Server 10.3.x installation to WebLogic Server 10.3.3, if you abort the upgrade before completion, the installation should automatically roll back to the prior installation. This may not always occur, resulting in an unusable installation.
The installer does not verify whether sufficient disk space is available on the machine prior to completing the installation. As a result, if an installation cannot be completed due to insufficient space, the installer displays the following error message and exits:
Fatal error encountered during file installation. The installer will now cleanup and exit!
Workaround
If this problem occurs, restart the installer using the following command:
server103_linux32.bin -log=log.out -log_priority=debug
The preceding command generates a log of the installation procedure, providing details about the exact cause of the failure. If the cause is indeed insufficient space, the log file indicates it explicitly.
This section describes the following issues and workarounds:
Section 11.14.1, "FastSwap May Relax the Access Modifiers of Fields and Methods"
Section 11.14.2, "FastSwap Does Not Support Redefinition of the Entity Bean and ejbClass"
Section 11.14.3, "Classpath Order Is Not Guaranteed When There Are Multiple JARs in an EAR File"
FastSwap may relax the access modifiers of fields and methods. Private and protected members may be made public at runtime. This changes the behavior of reflection and may affect reflection-based frameworks such as Struts.
FastSwap does not support redefinition of the Entity bean and ejbClass (Session/MDB). Therefore, any updates to entity classes will cause redefinition errors.
Workaround
After updating an entity class, redeploy the application.
When you have an EAR file containing separate JAR files, and two or more of those JAR files have a class with the same name, it is not possible to predict from which of those JAR files WebLogic Server will instantiate the class. This is not an issue if the classes are the same, but if they are different implementations, the results are unpredictable.
Workaround
Currently there is no known workaround for this issue.
This section describes the following issues and workarounds:
Section 11.15.1, "Queries Can Take Longer When Using Data Direct 4.0 MSSQL Driver"
Section 11.15.3, "SQLException Occurs When Retrieving an NClob Object From an Oracle Database"
Section 11.15.4, "Issues When Using WLCachedRowSet to Update NClob Data or Get NClob Objects"
Section 11.15.5, "BLOB Data Is Not Updating in the Database"
In WebLogic Server Release 10.3.2, our OEM DataDirect drivers were upgraded to 4.0. In order for the SQLServer driver to fully handle new DBMS data types, when running in it's default configuration, queries will take longer. If application access to new data types can be limited to getString()
, the following configuration workarounds will restore the performance.
Workaround
Add the following driver property to the list of driver properties for the WebLogic data source's connection pool. From the Administration Console, select the Configuration>Connection Pool tab for the data source.
For a non-XA connection pool, add:
ReportDateTimeTypes=false
For an XA connection pool, add:
ExtendedOptions=ReportDateTimeTypes=false
Alternatively, you can accomplish the same result by adding the property to the data source's XML configuration file.
For non-XA:
<jdbc-driver-params> <properties> <property> <name>ReportDateTimeTypes</name> <value>false</value> </property>
For XA:
<jdbc-driver-params> <properties> <property> <name>ExtendedOptions</name> <value>ReportDateTimeTypes=false</value> </property>
A new system property, -Dweblogic.jdbc.remoteEnabled
, has been added to JDBC in Oracle WebLogic Server 10.3.2. For compatibility with prior releases of WebLogic Server, the default setting of this property is true
. When this property is set to false
, remote JDBC access is turned off, and such access via a remote client will result in an exception.
System Limitation
When the -Dweblogic.jdbc.remoteEnabled
option, which is available in WebLogic Server 10.3.2 or later, is set to false
, any attempt to access a non-XA data source with a transaction option of LLR, 1PC or Emulate XA on multiple WebLogic Server instances in a global transaction will fail.
Notes: A 1PC, Emulate XA, or LLR participant in a global transaction that is hosted locally on the transaction coordinating server will continue to work. This can sometimes be accomplished by optimizing your applications to use connection instances directly hosted on the coordinator as described in "Optimizing Performance with LLR" in Oracle Fusion Middleware Programming JTA for Oracle WebLogic Server.It may not be possible to optimize an application to use connection instances directly hosted on the coordinator. For example, an MDB that receives messages from a remote WebLogic JMS server will always use a remote coordinator. |
Workaround
Change the data source to use XA instead. This may lower performance.
When using a JdbcRowSet
object to retrieve an NClob
object from an Oracle database via the Oracle Thin driver, the following SQLException occurs:
Incorrect form of use to create NCLOB.
As a result, the NClob
object cannot be retrieved.
When using WLCachedRowSet, the following two issues have been seen:
An Object has been closed
SQL exception occurs when updating the NClob data in a Rowset
object.
A This column cannot be converted to a NClob
SQL exception occurs when getting NClob objects from WLCachedRowSet
objects.
When using MSSQL and using the updateBlob()
and updateBinaryStream()
methods to update BLOB data in RowSet
objects, the data is not being updated in the database.
This section describes the following issues and workarounds:
The WebLogic Server system password may appear in clear text while prompted for userid and password when using the stopWebLogic.sh
command.
Workaround
Do one of the following:
Include $JAVA_VM
in the java command of the stopWeblogic.sh script.
Include -d64
in the java command of the stopWeblogic.sh script if you are using a 64-bit Sun JVM.
This section describes the following issues and workarounds:
Section 11.17.2, "Exception When Multiple Producers Use the Same Client SAF Instance"
Section 11.17.3, "Multi-byte Characters are not Supported in Store File and Directory Names"
Section 11.17.4, "Generation of the Default UOO Name Has Changed"
Section 11.17.5, "Testing Abrupt Failures of WebLogic Server When Using File Stores on NFS"
Section 11.17.6, "JMS Message Consumers Will Not Always Reconnect After a Service Migration"
Deployment descriptor validation fails when descriptor validation is enabled, and an EAR file contains only JMS modules.
Workaround
Make sure that there is at least one J2EE specification-compliant module in the EAR.
When multiple JMS producers use the same JMS Client SAF instance (within a single JVM), depending on the timing of the JMS SAF client creation, you might receive the following exception:
Error getting GXA resource [Root exception is weblogic.jms.common.JMSException: weblogic.messaging.kernel.KernelException: Error getting GXA resource]
Workaround
When using multiple JMS SAF client producers, try introducing a small delay between the creation of each new client.
There is no support for multi-byte characters in WebLogic Store file and directory names. For instance, when the WebLogic Server name has multi-byte characters, the default store cannot be created, and WebLogic Server will not boot.
Workaround
Create WebLogic Server instances without multi-byte characters in the path name and use that path name for the default store configuration. Do not use multi-byte characters in the Weblogic Server name.
WebLogic Server 10.3.3 contains a fix for configurations that set a default unit-of-order (UOO) on a JMS regular destination, distributed destination, or template. This fix ensures that the default unit-of-order name stays the same even after a restart of the destination's host JMS server. The default UOO name is now based on the domain, JMS server, and destination names.
Oracle strongly recommends verifying the behavior of a server restart after abrupt machine failures when the JMS messages and transaction logs are stored on an NFS mounted directory. Depending on the NFS implementation, different issues can arise post failover/restart. For more information, see Section 6.3, "Testing Abrupt Failures of WebLogic Server When Using File Stores on NFS."
JMS message consumers will not always reconnect after a service migration when an application's WLConnection.getReconnectPolicy()
attribute is set to all
. If the consumers do not get migrated, either an exception is thrown or onException
will occur to inform the application that the consumer is no longer valid.
Workaround
The application can refresh the consumer either in the exception handler or through onException
.
Certain conditions can cause very frequent JNDI updates, and as a result, JMS subscribers may encounter a java.naming.NameNotFoundException
. For more information, see Section 11.8.5, "Forcing Unicast Messages To Be Processed in Order."
There are no known JNDI issues in this release of WebLogic Server.
This section describes the following issues and workarounds:
Section 11.19.1, "Deployment Plans Cannot Be Used To Override Two Descriptors"
Section 11.19.2, "Spring Dependency Injection Not Supported on JSP Tag Handlers"
Section 11.19.3, "503 Error When Accessing an Application With a Valid sessionid"
Deployment plans cannot be used to override the following two descriptors during deployment of a Web application or a Web module: WEB-INF/classes/META-INF/persistence.xml and WEB-INF/classes/META-INF/persistence-configuration.xml. Deployment plans can otherwise be used to override any descriptor.
Workaround
Package WEB-INF/classes/META-INF/persistence.xml and WEB-INF/classes/META-INF/persistence-configuration.xml (if present) along with related class files into a JAR file. The JAR file must then be placed in the WEB-INF/lib directory of the Web application or Web module. A deployment plan can be used to override the two descriptors in such a JAR file.
With the Spring extension model enabled, WebLogic Server 10.3 or later does not support Spring Dependency Injection (DI) on JSP tag handlers for performance reasons.
Currently, WebLogic Server supports Spring DI on most Web components, for example, servlets, filters and listeners. Spring DI is not, however, presently supported on JSP tag handlers for performance reasons.
When a session is persistent and an older version of a servlet context is retired, accessing the application with a valid sessionid
will cause a 503 error.
For example, the session-persistent type of a versioned Web application is 'file'. A user can access the application successfully. Later, version 2 of the application is redeployed and version 1 is retired. If the same user accesses the application, they will get a 503 error.
There are no known JTA issues in this release of WebLogic Server.
This section describes the following issues and workarounds:
Section 11.21.1, "1.4 Thin Client Applet Cannot Contact WebLogic Server"
Section 11.21.2, "JRockit JVM Appears to Freeze When Doing Long Array Copies"
Section 11.21.3, "Using AWT libraries May Cause a JVM Crash"
Due to a known Sun Microsystems VM bug (513552), a 1.4 Thin Client Applet cannot contact WebLogic Server 9.0 or later. This is because the VM does not distinguish correctly between a client and a server connection. The VM creates a server-type connection and caches it. It then attempts to make a client-type connection, finds the cached connection and tries to use that, but then encounters an error because clients are not allowed to use server connections.
Workaround
None. This issue must be resolved by Sun Microsystems.
The JRockit JVM appears to freeze when doing long array copies as part of unlimited forward rolling. This can happen when multiple server reboots occur due to Out Of Memory
conditions.
Workaround
When booting the servers, include the following JRockit JVM flag:
-XXrollforwardretrylimit:-1
export IBM_JAVA_OPTIONS="-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0"
This section describes the following issue and workaround:
The @unharvestable
tag is not being honored at the interface level. If MBean attributes are not explicitly marked as @unharvestable
, they are considered to be harvestable and will appear as harvestable in the WebLogic Administration Console.
Workaround
You can explicitly mark MBean attributes as @unharvestable
.
In an upcoming release of WebLogic Server, the current default prefix for catalog and non-catalog Message IDs will be changed from the current BEA prefix to WL.
Workaround
You should be prepared for this future change. In the interim, here are some guidelines to consider:
Avoid depending on BEA for Message ID prefixes in scripts, filter expressions, etc.
For log messages such as the following:
<Jan 30, 2009 12:51:49 AM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
it is better for you to filter on '000365' and not on the BEA prefix itself.
Your log parsing scripts should be updated to look for both BEA and WL, instead of filtering only on BEA.
There are no known Node Manager issues in this release of WebLogic Server.
There are no known Operations, Administration, and Management issues in this release of WebLogic Server.
There are no known Oracle Kodo issues in this release of WebLogic Server.
This section describes the following issue for various WebLogic Server plug-ins:
Under the following circumstances, the IIS plug-in may not work, resulting in an apr_socket_connection
error:
Both the IIS and Weblogic Server instances are on the same machine.
IPv6 is enabled on the machine, but the machine is not in an IPv6 environment (that is, the IPv6 interface is enabled but is not working).
The listen address of the WebLogic Server instance is set to the simple host name.
Either the directive WebLogicHost or WebLogicCluster is set to the simple host name for the IIS instance.
There are no known Protocols issues in this release of WebLogic Server.
This section describes the following issue and workaround:
Calls to the Ant version 1.7 rmic
task automatically add a -vcompat flag
, which is not compatible with rmic
for Oracle WebLogic Server.
Workaround
Use either of the following workarounds if your rmic call is of the form:
rmic classname="com.bea.crmsimulation.legacyra.LegacyAdapter" base="${module_location}/core-legacy-ra/classes" classpath="${core.classes}" compiler="weblogic" />
Add a stubversion
<rmic classname="com.bea.crmsimulation.legacyra.LegacyAdapter" base="${module_location}/core-legacy-ra/classes" classpath="${core.classes}" compiler="weblogic" stubversion="1.2"/>
Remove the compiler
flag
<rmic classname="com.bea.crmsimulation.legacyra.LegacyAdapter" base="${module_location}/core-legacy-ra/classes" classpath="${core.classes}"
This section describes the following issues and workarounds:
Section 11.29.1, "StoreBootIdentity Works Only if the Appropriate Server Security Directory Exists"
Section 11.29.3, "Boot Time Failure Occurs With SecurityServiceException"
Section 11.29.4, "Authentication Failure After Upgrading a Domain From WLS 6.1"
Section 11.29.5, "InvalidParameterException Message Generated and Displayed"
Section 11.29.7, "Authentication May Fail When Group Membership Caching Is Enabled"
Section 11.29.8, "Random Number Generator May Be Slow on Machines With Inadequate Entropy"
The option -Dweblogic.system.StoreBootIdentity
works only if the appropriate server security directory exists. This directory is usually created by the Configuration Wizard or upgrade tool.
However, the appropriate server security directory could be absent in domains checked into source-control systems.
WebLogic Server allows for a NULL cipher to be used with an SSL connection, which results in data not being encrypted.
In WebLogic Server 10.3 or greater, the use of the NULL cipher is now disabled by default. In order for a client to enable the NULL cipher, set the weblogic.ssl.AllowUnencryptedNullCipher
system property to true. For example:
-Dweblogic.ssl.AllowUnencryptedNullCipher=true
In WebLogic Server 10.3 or greater, client SSL connections requiring a NULL cipher will fail unless this system property explicitly enables the use of the NULL cipher. For NULL cipher to be used, you need to enable NULL cipher on both the server side and client side. If not enabled on both sides, the SSL handshake will fail.
A WebLogic Server instance can experience a boot time failure with a SecurityServiceException
when the RDBMS Security Data Store is configured for a DB2 database using the DB2 driver supplied with WebLogic Server.
Workaround
When RDBMS Security Data Store is using the AlternateId
connection property for a DB2 database, you must also set the additional property BatchPerformanceWorkaround
as true
when using the DB2 driver supplied with WebLogic Server.
After upgrading a domain from WLS 6.1, the WebLogic Server instance will not boot due to an authentication failure.
Workaround
A system user password must be set up in the WLS 6.1 domain before or after the upgrade process in order for the WebLogic Server instance to boot properly.
After you configure either the Identity Provider or Service Provider services for SAML 2.0 and attempt to publish the SAML 2.0 services metadata file, an InvalidParameterException
message may be generated and displayed in the Administration Console.
Workaround
When configuring the SAML 2.0 federation services for a WebLogic Server instance, be sure to enable all binding types that are available for the SAML role being configured. For example, when configuring SAML 2.0 Identity Provider services, you should enable the POST, Redirect, and Artifact bindings. When configuring SAML 2.0 Service Provider services, enable the POST and Artifact bindings. Optionally, you may choose a preferred binding.
When configuring SAML 2.0 Service Provider services, enabling both the Force Authentication and Passive attributes is an invalid configuration that WebLogic Server is unable to detect. If both these attributes are enabled, and an unauthenticated user attempts to access a resource that is hosted at the Service Provider site, an exception is generated and the single sign-on session fails.
Note that the Force Authentication attribute has no effect because SAML logout is not supported in WebLogic Server. So even if the user is already authenticated at the Identity Provider site and Force Authentication is enabled, the user is not forced to authenticate again at the Identity Provider site.
Avoid enabling both these attributes.
When configuring any of the authentication providers included in WebLogic Server, setting Group Membership Searching to "limited" may result in authentication failures if Enable Group Membership Lookup Hierarchy Caching is enabled. Authentication may succeed or fail depending on the current content of the group membership cache.
In the authentication provider configuration page of the WebLogic Server Administration Console, the Group Membership Searching attribute is available from the Provider Specific tab, and the Enable Group Membership Lookup Hierarchy Caching attribute is available from the Performance tab.
Note that the default settings for these attributes are as follows:
Group Membership Searching is set to "unlimited".
Enable Group Membership Lookup Hierarchy Caching is enabled.
Workaround
These two configuration settings should not be used together. When configuring an authentication provider, use either of the following methods to avoid this problem:
Avoid setting Group Membership Searching to "limited".
If you must use the "limited" setting, disable the Enable Group Membership Lookup Hierarchy Caching setting. Note that disabling the group membership cache typically results in slower system performance.
In order to generate random numbers that are not predictable, SSL security code relies upon "entropy" on a machine. Entropy is activity such as mouse movement, disk IO, or network traffic. If entropy is minimal or non-existent, then the random number generator will be slow, and security operations may time out. This may disrupt activities such as booting a Managed Server into a domain using a secure admin channel. This issue generally occurs for a period after startup. Once sufficient entropy has been achieved on a JVM, the random number generator should be satisfied for the lifetime of the machine.
For further information, see Sun bugs 6202721 and 6521844 at:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6202721
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6521844
Workaround
On low-entropy systems, you can use a non-blocking random number generator, providing your site can tolerate lessened security. To do this, add the -Djava.security.egd=file:///dev/urandom
switch or file:/dev/./urandom
to the command that starts the Java process. Note that this workaround should not be used in production environments because it uses pseudo-random numbers instead of genuine random numbers.
This section describes the following issue and workaround:
In WebLogic Server 10.3.3, an optimization has been included to conserve the initial memory usage by the SNMP Agent, by lazily loading the nodes for the MIB when the user accesses those nodes with a get
, getnext
or other SNMP request. While the nodes corresponding to the WebLogic Server Runtime and Configuration MBeans are loaded lazily, the nodes for custom MBeans are initially loaded at startup. Note that custom MBeans are not registered in the MIB by default. To register custom MBeans in the MIB, the SNMPAccessForUserMBeansEnabled
attribute on the SNMPAgentMBean
must be set to true
.
Workaround
There is no workaround for this issue. You see this issue only if the SNMPAccessForUserMBeansEnabled
attribute is enabled and the SNMP Agent is running.
This section describes the following issues and workarounds:
Section 11.31.1, "OpenJPA ClassFileTranformer Does Not Work When Running on JRockit"
Section 11.31.2, "petclinic.ear Does Not Deploy on WebLogic Server"
The OpenJPA ClassFileTranformer
does not work when running WebLogic Server on JRockit.
Workaround
Use an alternative method of applying enhancements at build time through an OpenJPA enhancer compiler; do not use the LoadTimeWeaver
.
For the SpringSource petclinic
sample, the petclinic.war
deploys without any problems. The petclinic.ear
will not deploy on WebLogic Server because it is not packaged correctly. A request has been sent to SpringSource to fix the petclinic.ear
packaging.
This section describes the following SCA issue:
In the System Component Architecture (SCA) Spring bean Web service, if a service bean is using SOAP 1.2 and swaRef(@XmlAttachmentRef)
in the response(return value)
, the Content-Type
is incorrectly set to "text/xml" when producing the response SOAP message. The incorrect Content-Type
causes the SAAJ MessageFactory to throw an Unable to internalize message
error, and the service then responds with a fault.
Workaround
Use SOAP 1.1 or Message Transmission Optimization Mechanism (MTOM) for the attachment.
This section describes the following issues:
Section 11.33.1, "Domains Created on WebLogic Server 10.3.1 Cannot Be Run on WebLogic Server 10.3"
Section 11.33.2, "Downgrade Option is Unavailable in Smart Update After Upgrade"
If you create a domain using WebLogic Server 10.3.1, then roll back to WebLogic Server 10.3, you will not be able to start the servers that you created in that domain. This is a known restriction, as the config.xml
file contains references to newer schema definitions (xmlns.oracle.com
) that did not exist in WebLogic Server 10.3.
If you have WebLogic Server 10.3.0 or 10.3.1 installed with the WorkShop for WebLogic component, and you use Smart Update to upgrade to WebLogic Server 10.3.2, there is no Downgrade Option available in Smart Update that will allow you to roll back from 10.3.2 to the prior release.
Note: This issue does not occur if your WebLogic Server installation does not include the Workshop for WebLogic component. |
Workaround
Run the WebLogic Server uninstaller and select the Rollback option to roll back to the original WebLogic Server 10.3.0 or 10.3.1 installation. For information on how to run the WebLogic Server uninstaller, see the Installation Guide for Oracle WebLogic Server.
This section describes the following issue and workaround:
Section 11.34.1, "Administration Console Fails to Implement session-timeout Changes"
Section 11.34.2, "Connection Pool Connection Reserve Timeout Seconds Value is Overridden"
Section 11.34.3, "Database Connections Become Unstable When a PoolLimitSQLException Occurs"
If the session-timeout
is configured in the web.xml
file, any changes made to change the session-timeout
using the Administration Console do not take effect.
Workaround
Use a deployment plan to override the session-timeout
setting.
When using a JDBC session, the value of Connection Reserve Timeout Seconds for a connection pool is changed to be one of the following:
the JDBC connection timeout seconds, which is defined in the session descriptor (either in weblogic.xml
or weblogic-application.xml
)
the default value of 120 seconds
Workaround
Configure jdbc-connection-timeout-secs
in the session descriptor.
When a PoolLimitSQLException occurs during a JDBC persistence session, connections to the database become unstable, and may fail with recovery or fail without recovery. This results in the loss of session data. Either an older session or null is returned.
This section describes the following issues and workarounds:
Section 11.35.1, "Property Names Containing '.' Characters Are Not Supported by loadProperties"
Section 11.35.2, "Invalid cachedir Created by Jython Causes WLST to Error Out"
Section 11.35.3, "WLST returnType='a' Option Returns Child Management Objects"
The WLST loadProperties
command does not support loading a property with a name that contains "." characters. For example, if the property myapp.db.default
is present in the property file, WLST throws a name exception:
Problem invoking WLST - Traceback (innermost last): File "<iostream>", line 7, in ? File "<iostream>", line 4, in readCustomProperty NameError: myapp
This is a system limitation of Python and the loadProperties
command. WLST reads the variable names and values and sets them as variables in the Python interpreter. The Python interpreter uses "." as a delimiter to indicate module scoping for the namespace, or package naming, or both. Therefore, the properties file fails because myapp.db.default.version=9i
is expected to be in the myapp.db.default
package. This package does not exist.
Workaround
Use variable names that do not have periods. This will allow you to load the variables from the property file and refer to them in WLST scripts. You could use another character such as "_" or lowercase/uppercase character to delimit the namespace.
As an alternative, you can set variables from a properties files. When you use the variables in your script, during execution, the variables are replaced with the actual values from the properties file. For example:
myapp.py var1=10 var2=20 import myapp print myapp.var1 10 print myapp.var2 20
This will work for one level of namespaces (myapp.var1
, myapp.var2
). It will not work for top level variables that share the same name as the namespace (for example, myapp=oracle
and myapp.var1=10
). Setting the myapp
variable will override the myapp
namespace.
If you need multiple levels, then you can define a package namespace using directories. Create a myapp/db/default directory with a vars.py
file as follows:
var1=10 var2=20
Then import:
import myapp.db.default.vars print myapp.db.default.vars.var1 10
You may need to add __init__.py
files to the subdirectories. Refer to the Python documentation for more information on packages:
The default cachedir
created by Jython 2.2 is not a valid directory. If you are using Jython directly from weblogic.jar
, this causes WLST to error out.
Workaround
There are two workarounds for this issue:
When invoking WLST, specify the -Dpython.cachedir=<
valid_directory
>
parameter, or
Install Jython 2.2.1 separately instead of using the partial Jython that is included in weblogic.jar
.
The WLST returnType='a'
option should only return attributes from the specified directory. Instead it also returns child management objects. For example:
ls('Server') drw- AdminServer drw- worker01 ls('Server', returnMap='true', returnType='a') drw- AdminServer drw- worker01 ls('Server', returnMap='true',returnType='c') drw- AdminServer drw- worker01
The ls
with returnType='a'
should not list any child management objects, but AdminServer
and worker01
are children.
Workaround
When processing the output from ls(returnType='a')
, check to see if the returned entry is a directory.
This section describes the following issue:
Currently, mod_wl
and mod_wl_ohs
only support container level failover and not application level failover. mod_wl_ohs
continues to route requests to a down application as long as the managed server is up and running. In the clustered case, requests continue to go to the container where the original session started even when the application is shutdown, typically resulting in the http error 404.
This section describes the following issues and workarounds:
Section 11.37.1, "Sparse Arrays and Partially Transmitted Arrays Are Not Supported"
Section 11.37.2, "WSDL Compiler Does Not Generate Serializable Data Types"
Section 11.37.4, "Cannot Use JMS Transport in an Environment That Also Uses a Proxy Server"
Section 11.37.6, "JAX RPC Handlers in Callback Web Services Are Not Supported"
Section 11.37.7, "Message-level Security in Callback Web Services Is Not Supported"
Section 11.37.10, "Using SoapElement[] Results in Empty Array"
Section 11.37.11, "FileNotFound Exception When a Web Service Invokes Another Web Service"
Section 11.37.12, "Client Side Fails to Validate the Signature on the Server Response Message"
Section 11.37.13, "INFO Messages in Log for Domains Created Without Web Services-Specific Resources"
Section 11.37.14, "xmlcatalog Element Entity Cannot Be a Remote File or a File in an Archive"
Section 11.37.15, "Catalog File's public Element Is Not Supported When Using XML Catalogs"
Section 11.37.16, "Local xmlcatalog Element Does Not Work Well"
Section 11.37.18, "External Catalog File Cannot Be Used in the xmlcatalog Element of clientgen"
Section 11.37.19, "Exceptions When Running Reliable Messaging Under Heavy Load"
Section 11.37.21, "ClassNotFound Exception Occurs When Using wseeclient.jar"
Section 11.37.23, "Exception Occurs During Invocation of Clientside Policy Applied to a Service"
Section 11.37.24, "WS-AT Interoperation Issues With WebSphere and WebLogic Server"
Section 11.37.25, "DBWS Invocation Fails When WebLogic Server Is Running JRockit JDK"
Section 11.37.26, "Server Enters a Warning State After Crash Recovery"
WebLogic Server does not support Sparse Arrays and Partially Transmitted Arrays as required by the JAX-RPC 1.1 Spec.
The Web Service Description Language (WSDL) compiler does not generate serializable data types, so data cannot be passed to remote EJBs or stored in a JMS destination.
WebLogic Server does not support using a custom exception on a callback that has a package that does not match the target namespace of the parent Web Service.
Workaround
Make sure that any custom exceptions that are used in callbacks are in a package that matches the target namespace of the parent Web service.
You cannot use JMS transport in an environment that also uses a proxy server. This is because, in the case of JMS transport, the Web Service client always uses the t3 protocol to connect to the Web Service, and proxy servers accept only HTTP/HTTPS.
clientgen
fails when processing a WSDL that uses the complex type http://www.w3.org/2001/XMLSchema{schema}
as a Web Service parameter.
WebLogic Server 9.2 and later does not support JAX RPC handlers in callback Web Services.
Workaround
If JAX RPC handlers were used with Web Services created with WebLogic Workshop 8.1, then such applications must be redesigned so that they do not use callback handler functionality.
WebLogic Server 9.2 and later does not support message-level security in callback Web Services.
Workaround
Web Services created with WebLogic Workshop 8.1 that used WS-Security must be redesigned to not use message-level security in callbacks.
WebLogic Server does not support handling of Java method arguments or return parameters that are JAX-RPC-style JavaBeans that contain an XmlBean
property. For example, applications cannot have a method with a signature like this:
void myMethod(myJavaBean bean);
where myJavaBean
class is like:
public class MyJavaBean { private String stringProperty; private XmlObject xmlObjectProperty; public MyJavaBean() {} String getStringProperty() { return stringProperty; } void setStringProperty(String s) { stringProperty = s; } XmlObject getXmlObjectProperty() { return xmlObjectProperty; } void getXmlObjectProperty(XmlObject x) { xmlObjectProperty = x; } }
Workaround
Currently there is no known workaround for this issue.
Using a two dimensional XmlObject
parameter (XmlObject[][]
) in a JWS callback produces an IllegalArgumentException
.
Workaround
Currently there is no known workaround for this issue.
Using SoapElement[]
as a Web Service parameter with @WildcardBinding(className="javax.xml.soap.SOAPElement[]", binding=WildcardParticle.ANYTYPE)
will always result in an empty array on the client.
Workaround
Do not use the @WildcardBinding
annotation to change the default binding of SOAPElement[]
to WildcardParticle.ANYTYPE
. The SOAPElement[]
default binding is set to WildcardParticle.ANY
.
When Web Service A wants to invoke Web Service B, Web Service A should use the @ServiceClient
annotation to do this. If Web Service B needs a custom policy file that is not attached to the WSDL for Web Service B, then Web Service A will fail to run. Web Service A will look for the policy file at /Web-Inf/classes/policies/
filename
.xml
. Since no policy file exists at that location, WebLogic Server will throw a 'file not found' exception.
Workaround
Attach the custom policy file to Web Service B, as in this example:
@Policy(uri="CustomPolicy.xml", attachToWsdl=true) public class B { ... }
When the security policy has one of these Token Assertions, the client side may fail to validate the signature on the server response message.
<sp:WssX509PkiPathV1Token11/> <sp:WssX509Pkcs7Token11/> <sp:WssX509PkiPathV1Token10/> <sp:WssX509Pkcs7Token10/>
In addition, when there are more than two certifications in the chain for X509 certification for <sp:WssX509Pkcs7Token11/> or <sp:WssX509Pkcs7Token10/> Token Assertion, the server side may fail to validate the signature on the incoming message.
A policy such as the following policy is not supported, unless the entire certificate chain remains on the client side.
<sp:AsymmetricBinding> <wsp:Policy> <sp:InitiatorToken> <wsp:Policy> <sp:X509Token sp:IncludeToken='. . ./IncludeToken/AlwaysToRecipient'> <wsp:Policy> <sp:WssX509Pkcs7Token11/> </wsp:Policy> </sp:X509Token> </wsp:Policy> </sp:InitiatorToken> <sp:RecipientToken> <wsp:Policy> <sp:X509Token sp:IncludeToken='. . ./IncludeToken/Never'> <wsp:Policy> <sp:WssX509Pkcs7Token11/> </wsp:Policy> </sp:X509Token> </wsp:Policy> </sp:RecipientToken> . . . </wsp:Policy> </sp:AsymmetricBinding>
Workaround
Use either of the following two solutions:
Configure the response with the <sp:WssX509V3Token10/>
Token Assertion, instead of WssX509PkiPathV1Token11/>
. The policy will look like this:
<sp:AsymmetricBinding> <wsp:Policy> <sp:InitiatorToken> <wsp:Policy> <sp:X509Token sp:IncludeToken='. . ./IncludeToken/AlwaysToRecipient'> <wsp:Policy> WssX509PkiPathV1Token11/> </wsp:Policy> </sp:X509Token> </wsp:Policy> </sp:InitiatorToken> <sp:RecipientToken> <wsp:Policy> sp:IncludeToken='. . ./IncludeToken/Never'> <sp:X509Token <wsp:Policy> <sp:WssX509V3Token10/> </wsp:Policy> </sp:X509Token> </wsp:Policy> </sp:RecipientToken> . . . </wsp:Policy> </sp:AsymmetricBinding>
Configure the response with the WssX509PkiPathV1Token11/>
token assertion, but include it in the message. The policy will look like this:
<sp:AsymmetricBinding> <wsp:Policy> <sp:InitiatorToken> <wsp:Policy> <sp:X509Token sp:IncludeToken='. . ./IncludeToken/AlwaysToRecipient'> <wsp:Policy> WssX509PkiPathV1Token11/> </wsp:Policy> </sp:X509Token> </wsp:Policy> </sp:InitiatorToken> <sp:RecipientToken> <wsp:Policy> <sp:X509Token sp:IncludeToken='. . ./IncludeToken/AlwaysToInitiator'> <wsp:Policy> WssX509PkiPathV1Token11/> </wsp:Policy> </sp:X509Token> </wsp:Policy> </sp:RecipientToken> . . . </wsp:Policy> </sp:AsymmetricBinding>
When there are multiple certifications in the X509 Certificate chain, WssX509PkiPathV1Token11/>
or <sp:WssX509PkiPathV1Token10/>
should be used, instead of <sp:WssX509Pkcs7Token11/>
or <sp:WssX509Pkcs7Token10/>
.
WebLogic Web Services expects that each WebLogic Server domain will contain specific resources needed to support Web services. Some domains, however, are not created with these resources.
For example, creating a default WebLogic Server domain in the configuration wizard (without applying any other templates) will not create the needed Web Services resources.
A domain that doesn't contain Web Services resources will still boot and operate correctly for non-Web services scenarios, and any Web Services scenario that doesn't involve asynchronous request/response. You will, however, see INFO messages in the server log indicating that async resources have not been configured and that the async response service for web services has not been completely deployed.
Workaround
Web Services that use async request/response will not function properly in a domain that doesn't have Web Services resources configured in it. To configure these resources, there are two approaches:
Use the configuration wizard and apply the wls_webservice.jar
template to your domain.
Manually configure these resources according to the rules given in the online documentation under domain configuration for Web services.
Note: The configuration wizard approach mentioned above is not advised for domains that already have JMS servers configured and that enable JMS resource 'default targeting' on JMS resources such as destinations. The wizard automatically creates additional JMS servers, and the default targeted resources can automatically appear on the newly created JMS servers, yielding, for example, distributed destinations that suddenly span many more JMS servers than intended. |
For the xmlcatalog
element in build.xml
, the location of an entity must be a file on the local file system. It cannot be a remote file (for example, http:
) or a file in an archive (for example, jar:
).
Workaround
If necessary, define the remote element as an entity in a catalog file instead.
The public
element in a catalog file is not supported when using the XML Catalogs feature. It is not supported to be consistent with JAX-WS EntityResolver implementation. WebLogic Server only supports defining the system
element in a catalog file.
The local xmlcatalog
element does not work well due to an Ant limitation.
Workaround
In the ant build.xml
file, you have to define a local element above a clientgen(wsdlc)
task when you are in the same target, or define the element out of any targets.
The WebLogic Server Web Service JAXRPC client doesn't encode the HTTP SOAPAction header with multi-byte characters, but WebLogic Server only supports ASCII for HTTP headers.
Workaround
Change the SOAP action to ASCII in the WSDL.
An external catalog file cannot be used in the xmlcatalog
element of a clientgen
task. For example, this snippet of an ant build file will not work:
<clientgen ... <xmlcatalog> <catalogpath> <pathelement location='wsdlcatalog.xml'/> </catalogpath> </xmlcatalog>
This is a limitation of the Ant XML Catalog.
Workaround
Resource locations can be specified either in-line or in an external catalog file(s), or both. In order to use an external catalog file, the xml-commons
resolver library (resolver.jar
) must be in your classpath. External catalog files may be either plain text format or XML format. If the xml-commons
resolver library is not found in the classpath, external catalog files, specified in <catalogpath>
paths, will be ignored and a warning will be logged. In this case, however, processing of inline entries will proceed normally.
Currently, only <dtd>
and <entity>
elements may be specified inline. These correspond to the OASIS catalog entry types PUBLIC and URI respectively.
When running a Web services reliable messaging scenario under heavy load with file based storage that has the Direct-Write
synchronous write policy setting, you may encounter IO exceptions similar to the following in the WebLogic Server log:
weblogic.store.PersistentStoreRuntimeException: [Store:280029]The persistent store record <number> could not be found
or
Could not load conversation with id uuid:<some ID> -> Conversation read failed: ... weblogic.wsee.jws.conversation.StoreException: Conversation read failed: id=uuid:<some ID> weblogic.store.PersistentStoreException: [Store:280052]The persistent store was not able to read a record. java.io.OptionalDataException
These exceptions are known to occur only when using Web Services reliable messaging. They indicate a failure to read a record from the file store and are considered 'fatal' data access errors.
The underlying issue causing these errors will be addressed in a future release.
Workaround
The following workarounds are available for this issue:
Change the file store synchronous write policy to Direct-Write-With-Cache
or
Change the file store synchronous write policy to Cache-Flush
.
or
Keep the Direct-Write synchronous write policy and add the following Java system property to your WebLogic server startup scripts:
-Dweblogic.store.AvoidDirectIO=true
Note: The-Dweblogic.store.AvoidDirectIO system property has been deprecated in WebLogic Server 10.3.3. Oracle recommends configuring the store synchronous write policy to Direct-Write-With-Cache instead. |
The Direct-Write-With-Cache
option may improve performance; it creates additional files in the operating system's temporary directory by default.
The Cache-Flush
and AvoidDirectIO
workarounds may lead to some performance degradation; it may be possible to reduce or eliminate the degradation by configuring a different block-size for the file store.
For important information about these settings and additional options, see "Tuning File Stores" in Oracle Fusion Middleware Performance and Tuning for Oracle WebLogic Server.
Prior to 11g Release 1 (WebLogic Server version 10.3.1), a JAX-WS JWS that allowed its service endpoint interface to be inferred from the implementation (that is, no explicit service endpoint interface class was declared) would have the implicit service endpoint interface include only those methods that included an @WebMethod
annotation (and that annotation did not specify exclude=true
). This behavior is incorrect according to the JAX-WS 2.1 specification. JAX-WS 2.1 specifies that the service endpoint interface inferred from the JWS should include all public non-static methods on the JWS, as long as those methods do not have @WebMethod(exclude=true)
attached to them.
In WebLogic Server 10.3.1, jwsc
(and the Web services runtime) have been modified to properly generate the implicit service endpoint interface (and resulting WSDL for the service) according to the JAX-WS 2.1 specification. As a result, the implicitly derived service endpoint interface will include all non-excluded public non-static methods on the JWS. In some cases, you may have written JWS implementations that relied on the prior jwsc
behavior, assuming that methods with no @WebMethod
annotation would not be included in the service endpoint interface and resulting WSDL for the service. With the new jwsc
behavior, such methods will be included in the service endpoint interface and resulting WSDL for the service.
Workaround
After installing WebLogic Server 10.3.1 or greater, Oracle recommends that you evaluate your existing services for the following possible errors:
Public non-static methods that are not legal Web method declarations (these can cause jwsc
to fail when building a service).
Public non-static methods that are legal Web methods, but were never intended to be exposed publicly on the service.
The two cases are described in detail here:
Case 1: It is possible that some JWS classes will fail to compile in jwsc
if a previously excluded method is an invalid Web method. The new implicit inclusion of such methods will cause the jwsc
task to fail. There are many possible reasons for jwsc
to fail compiling of a newly included Web method. The most common reason is if a method includes parameter types that are incompatible with JAXB (for example, an interface instead of a concrete class with a default no-arg constructor).
Case 2: Any public non-static methods that are not explicitly excluded will now be represented in the service endpoint interface. These methods may be perfectly legal Web method declarations (for example, they compile correctly in jwsc
), but may never have been intended as public operations on the service.
Oracle recommends that you inspect any implicitly defined service endpoint interface (and dynamically generated WSDL) for their existing services, and ensure that only the intended methods are exposed.
In either of these cases, simply add the following annotation to the method that you want to exclude from the service's endpoint interface and WSDL:
@WebMethod(exclude=true)
In some circumstances, when executing a standalone JAX-WS client application using wseeclient.jar
(as described in "Using a Stand-Alone Client JAR File When Invoking Web Services" in Oracle Fusion Middleware Getting Started With JAX-WS Web Services for Oracle WebLogic Server), the application may fail with a ClassNotFound exception. For example:
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: com/oracle/xml /ws/transport/http/client/HttpTransportPipe at weblogic.wsee.jaxws.WLSTransportTubeFactory.createHttpTransport(WLSTransportTube Factory.java:30
Workaround
Use the client-side JAX-WS 2.1 that is integrated with the Java Standard Edition Release 6 (JDK 1.6), Update 4 and later. This requires using the JAX-WS API instead of any WebLogic Server specific APIS.
Current releases of JDK 1.6 are available for download at http://java.sun.com/javase/downloads/index.jsp
. For information about writing a standalone JAX WS 2.1 client application, see the JAX-WS Users Guide on the JAX-WS 2.1 Reference Implementation Web site at https://jax-ws.dev.java.net/
.
An incomplete configuration can result when you use the Configuration Wizard to add the WebLogic Server Advanced Web Services component to a newly created SOA domain. If you create a cluster that contains only the default 'out-of-the-box' soa_server1 server definition, the resulting cluster does not include the resources needed to run WebLogic Server Web Services in that cluster.
Workaround
Use either of the following workarounds for this issue:
While running Configuration Wizard, create a second server in the cluster:
On the Select Optional Configuration screen, select Managed Servers, Clusters, and Machines.
On the Configure Managed Servers screen, add a managed server.
On the Assign Servers to Clusters screen, add this server to the cluster in which the default soa_server1 server resides.
On the Configuration Wizard Target Services to Servers or Clusters screen, target Web Services resources (for example, WseeJmsServer, WseeJmsModule) to the cluster.
Either of these workarounds will cause the Configuration Wizard to apply the resources for the WebLogic Server Advanced Web Services component to the cluster.
After upgrading from WebLogic Server 10.3.1 to WebLogic Server 10.3.2 or 10.3.3, if the value of the name attribute of @WebParam(header=true)
is different from the Java parameter name in the JWS method, a WSDL part name exception may occur.
Workaround
Run clientgen
against the service to rebuild the client artifacts.
Web Services Atomic Transactions (WS-AT) 1.1 interoperation using WebSphere as the client and either WebLogic Server or JRF as the service does not work.
WS-AT 1.1 interoperation does work when WebSphere is the service and either WebLogic Server or JRF is the client. In this case, interoperation works only if you have WebSphere 7 with Fix/Feature Pack 7.
When a WebLogic Server instance is running the JRockit JDK, invocation of Database Web Services (DBWS) based on either EclipseLink or TopLink fails.
This issue is not seen when running the application server in a Sun JVM environment.
For a workaround for TopLink, see the Oracle Toplink Release Notes.
For a workaround for EclipseLink, see http://wiki.eclipse.org/EclipseLink/Release
.
In certain scenarios, when a server instance in a WebLogic cluster crashes, Web Services-Atomic Transaction (WS-AT) recovery results can result in timeouts during the commit processing of current transactions or stuck threads that cause the server to enter a Warning state. WS-AT data recovery is successful in these cases. The log files, however, contain 'failed state' messages due to the fact that commit acknowledgements for transactions are not being processed properly in this situation. Although the server may continue to function while in the Warning state, the threads continue to be stuck until the transaction abandonment timeout is reached (the default is 24 hours).
Workaround
Restart the server, which removes the stuck threads and clears the Warning state.
The Sun JDK (1.6.0 U18) that is supported with WebLogic Server 10.3.3 includes StAX 1.2 APIs. The JRockit JDK (1.6.0 U17) that is supported with WebLogic Server 10.3.3 includes StAX 1.0 APIs. As a result, an application that was developed on the Sun JDK and which uses StAX 1.2-specific APIs cannot be deployed on the JRockit JDK.
This section describes the following issue and workaround:
View classes are not set on a per connection basis.
A shared WebLogic Tuxedo Connector hash table can cause unexpected behavior in the server if two applications point to the same VIEW name with different definitions. There should be a hash table for the view classes on the connection as well as for the Resource section.
Workaround
Ensure that all VIEW classes defined across all your WebLogic Workshop applications are consistent, meaning that you have the same VIEW name representing the same VIEW class.
This section describes documentation errata:
Section 11.39.1, "Issues With Search Function in the Samples Viewer"
Section 11.39.2, "Japanese Text Displays in Some Search Results Topics Avitek Medical Records"
Section 11.39.3, "Some Interfaces to SAML2 Are Not Documented in the MBean Reference"
Section 11.39.4, "WS-AT Code Example Is Not Listed on the Examples Page"
The Search function in the Samples viewer does not work when accessing the Examples documentation by selecting Oracle Weblogic > Weblogic Server > Examples > Documentation from the Windows Start menu.
Workaround
To search the Sample Applications and Code Examples, you must start the Examples server and navigate to http://localhost:7001/examplesWebApp/docs/core/index.html
. Click Instructions and then Search.
The samples viewer Search function may sometimes return topics that display the Japanese and English versions of some Avitek Medical Records topics simultaneously.
The WebLogic Server 10.3.1 MBean Reference does not document the interfaces to the SAML 2.0 Identity Asserter and SAML 2.0 Credential Mapping provider. Instead, Javadoc for these MBean interfaces is provided in the WebLogic Server 10.3.1 MBean API Reference Guide.
When displaying the WebLogic Server Code Examples web page, the topic "Using Web Services Atomic Transaction" is not listed in the Web Services section of the Table of Contents (under WebLogic Server Examples > Examples > API > Web Services).
Workaround
To display this topic, enter the following URL in your web browser:
WL_HOME\samples\server\examples\src\examples\webservices\jaxws\wsat\
instructions.html
where WL_HOME
is the WebLogic Server installation directory (the default is C:\Oracle\Middleware\wlserver_10.3
).
There is a typographical error in the last line of Example 6-3, "Sample manifest.mf File" in Oracle Fusion Middleware Using ActiveCache. The example should be as follows:
Extension-List: active-cache active-cache-Extension-Name: active-cache active-cache-Specification-Version: 1.0 active-cache-Implementation-Version: 1.0