Issue

Impacted Platforms: All

When using the Safari browser to download content, if a filename contains multi-byte characters, the characters are displayed as '------' in the filename.

Workaround

Set UseHeaderEncoding to true on the Managed Server. Use the following WLST commands to do so:

connect("admin_name", "admin_password", "t3://localhost:port")
edit()
startEdit()
cd("Servers/server_name/WebServer/server_name")
set("UseHeaderEncoding", "true")
save()
activate()
exit()

Issue

Impacted Platforms: All

Any applications that use an MDS repository cannot be deployed or run with the JAXB version bundled with Oracle WebLogic Server as null values are returned for attributes named id

Workaround

Start the server in English locale.

Issue

Impacted Platforms: Linux

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

Execute the following command to determine the maximum number of file descriptors currently configured:

cat /proc/sys/fs/file-max

If the value is less than 65535, perform the following steps:

Issue

Impacted Platforms: N/A

Coherence users who do not have a dependency on Oracle WebLogic Server and want to use Maven should use the standalone Coherence installer.

Coherence users who do have a dependency on Oracle WebLogic Server and want to use Maven must choose the WebLogic Server or Complete with Examples installation options. Do not choose the Coherence Installation option.

Workaround

N/A

Issue

Impacted Platforms: All

The default WebLogic Server message prefix will change from BEA to WL in a future release of WebLogic Server.

Workaround

N/A

Issue

Impacted Platforms: Linux

When using Unicast mode for cluster communication, many threads are blocked on cluster messaging, which may result in cluster members having difficulty sending heartbeat messages. In this situation, some cluster members drop out from the cluster and may take some time to rejoin the cluster.

Workaround

N/A

Issue

Impacted Platforms: All

To support elasticity, Oracle WebLogic Server 12.2.1 introduced the following configurable constraints on the minimum and maximum size of a dynamic cluster:

• MinDynamicClusterSize (default=1)
• MaxDynamicClusterSize (default=8)

Additionally, the MaximumDynamicServerCount attribute is deprecated and replaced with the DynamicClusterSize attribute. The value of this attribute is validated against the previously mentioned minimum and maximum constraints. As a result, some existing user configurations and/or scripts may fail. If this occurs, you need to update the MaxDynamicClusterSize setting appropriately so that the DynamicClusterSize value is within the limits.

Workaround

N/A

Issue

After upgrading Oracle WebLogic Server to 14c (14.1.2.0), the slf4j framework is not initialized.

Workaround

In Oracle WebLogic Server 14c (14.1.2.0), the slf4j framework is located in $ORACLE_HOME\oracle_common\modules\thirdparty\apache-maven_bundle\3.9.4.0.0\apache-maven-3.9.4\lib. Initialize the slf4j framework from this location.

Issue

Impacted Platforms: All

In rare cases, if your installation environment contains existing JAVA_OPTIONS prior to starting a Fusion Middleware product installation, these may cause an ASProvWorkflowException, preventing the domain from being created.

Workaround

Prior to starting the Fusion Middleware product installation, clear the existing JAVA_OPTIONS. If you have an application in the environment that uses these JAVA_OPTIONS, the application may not work after clearing the options. In this case, save the existing JAVA_OPTIONS to a text file and investigate alternatives for running your application.

Issue

Impacted Platforms: MS Windows

WLST can be run with localized messages by setting the desired locale. You should be aware of the following issue when running WLST in a non-English locale.

On Windows operating systems, if a DOS command window's active code page is different from the system's local (ANSI) code page, you must add the -Dfile.encoding=<DOS window's active code page> property to the WLST process when starting WLST by using a DOS command window. This property changes the default character set for the Java process. For example:

• The active code page for a DOS window is 850. This value can be achieved by issuing the chcp command in the WLST command window.

• The system's local (ANSI) code page is 1250. You can determine the system's local code page by viewing the value of the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NLS\CodePage\ACP key in the Windows registry. Files that are created by standard Windows editing tools (such as Notepad or Wordpad) are encoded in this way.

Workaround

In this situation, you can start WLST as follows:

set WLST_PROPERTIES="-Dfile.encoding=cp850"

$WL_HOME%\common\bin\wlst.cmd

Issue

Impacted Platforms: MS Windows

On some Microsoft Windows platforms, the Oracle WebLogic Server configuration tool commands (including wlst, config, pack, and unpack) can fail if the Oracle WebLogic Server installation path contains a space. In this case, the command may fail with a java.lang.ClassNotFoundException error, where the class is derived from the portion of the installation path after the space. The commands fail if short file name generation is disabled in the Windows registry.

Workaround

You must enable short name generation in the Windows registry to ensure that spaces are handled properly by the configuration tools. To enable short name generation:

Issue

Impacted Platforms: All

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 starting the Managed Server.

Issue

Impacted Platforms: Linux

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.

Issue

Impacted Platforms: Linux

On Linux systems, when creating a new domain using the Oracle Fusion Middleware Configuration Wizard, the Password and Confirm Password fields are sometimes not editable, and you cannot enter a password to create a domain.

Workaround

There are two ways to work around this issue:

• To work around the issue each time it happens, click the Close Window X button in the upper right corner of the Configuration Wizard. In the confirmation dialog box, click No to return to the Configuration Wizard. You can then enter and confirm the password for the domain.

• To fix this issue permanently:

  1. Kill all scim processes. For example:

     kill `pgrep scim`

  2. Modify (or create) the ~/.scim/config file to include the following line (case-sensitive):

     /FrontEnd/X11/Dynamic = true

  3. If you are running VNC, restart the VNC server.

  4. Run the Configuration Wizard again.

Issue

Impacted Platforms: All

If the Oracle WebLogic Server Configuration Wizard (config.sh) is used to create a domain and the WebLogic Coherence Cluster Extension template is specified, then a Coherence cluster will be defined. The Coherence cluster will be associated with any Managed Server or Oracle WebLogic Server cluster that is also created by the Configuration Wizard. If no Managed Server or Oracle WebLogic Server cluster is created, then the Coherence cluster will be associated with the Administration Server. This association between the Coherence cluster and the servers is not completely defined using the Oracle WebLogic Server configuration tool, which results in the Coherence cache configuration override file not being detected by the Coherence cluster. Note that this issue only occurs if you are using the cache override feature.

This will perform a complete association between the Coherence cluster and the targeted servers, which is required to detect and utilize the specified Coherence cluster cache configuration override file.

Issue

Impacted Platforms: All

Specify -managed=true when creating a Managed Server domain directory from a template. If you do not specify -managed=true, the Managed Server will fail to boot because it does not have the correct set of files in the security directory.

Workaround

N/A

Issue

Impacted Platforms: All

When using an IPv6-formatted address for Oracle 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

Issue

Impacted Platforms: All

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 when you change a field name. The field name change is treated as follows:

• The field with the old name is deleted.

• The field with the new name is added.

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 to reset.

Workaround

You should expect an instance value to be reset when you change a field name.

Issue

Impacted Platforms: All

When using a host name 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 host name after startup. For example:

• The machine has 3 Ethernet cards

• Card 1 is mapped to hostname1-s (DNS registered host name)

• Card 2 is mapped to hostname1-i (DNS registered host name)

• Card 3 is mapped to hostname1 (actual node's host name)

• 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 host name to the first enabled Ethernet card address

Workaround

Use one of the following three workarounds for this issue:

Issue

Impacted Platforms: Linux

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.

Issue

Impacted Platforms: All

Oracle WebLogic Server does not support Java DB for migration. There is no leasing script available in the WL_HOME/server/db directory for Java DB.

Workaround

No workaround for this issue.

Issue

Impacted Platforms: All

If you have a cluster containing at least two Managed Servers, and the messaging mode of the cluster is set to multicast, then the Managed Servers in the cluster will fail to start.

Workaround

To workaround this issue, add the following property to JAVA_OPTIONS in the startup script startWebLogic.sh. For example:

export JAVA_OPTIONS="${JAVA_OPTIONS} –Djava.net.preferIPv4Stack=true"

Issue

Impacted Platforms: All

A server JVM appears to have stalled; and a thread dump of this JVM reveals that almost all weblogic.kernel.Default threads appear to be stalled in calls such as wait-for-data or wait-for-prepare-acks.

Workaround

Issue

Impacted Platforms: N/A

As per expected behavior, if the bean class is annotated with @Local (or neither with @Local nor @Remote), and if one of the implemented interfaces is extended with the java.rmi.Remote interface, then the interfaces should be accessed only by the local client, not by the remote client.

However, in 12.2.1, the interface can be accessed by the remote client when annotated with @Local.

Workaround

If you want access to an EJB to be restricted to local clients only, you should avoid both of the following in the EJB implementation:

• Using the @Local annotation

• Extending the java.rmi.Remote interface

Workaround

Update the JDBC descriptor file to set the allowPortWithNamedInstance property to true or remove the port number from the URL.

WLST scripts must be updated by the administrator to set the allowPortWithNamedInstance=true property to true. The following sample URLs are valid:

jdbc:weblogic:sqlserver://host\\INSTANCE:1433;DatabaseName=db;allowPortWithNamedInstance=true"
jdbc:weblogic:sqlserver://host:1433;DatabaseName=db"
jdbc:weblogic:sqlserver://host\\INSTANCE;DatabaseName=db"

Issue

Impacted Platforms: N/A

If a CDI extension is observing the lifecycle events AfterBeanDiscovery or AfterDeploymentValidation, an attempt to get a javax.validation.ValidatoryFactory bean instance will fail. For example:

public class MyExtension implements Extension {
     void checkValidatorFactoryBean(@Observes AfterBeanDiscovery abd, BeanManager bm) {
          Set<Bean<?>> validatorFactoryBeans
          = bm.getBeans(ValidatorFactory.class,
          new AnnotationLiteral<Default>() {});
     if (validatorFactoryBeans.isEmpty()) {
          throw new RuntimeException("Container provided BeanManager doesn't contain a bean of javax.validation.ValidationFactory");
          }
     }
}

The example code above will cause a RuntimeException because the BeanManager cannot get a ValidatorFactory bean instance. This occurs because the ValidatorFactory and Validator bean types were removed from the built-in beans starting in CDI 1.1. In CDI 1.1 and later, ValidatorFactory and Validator beans are defined by the following extension: org.hibernate.validator.internal.cdi.ValidationExtension.

Note that when called during invocation of an AfterBeanDiscovery event observer, this method will only return beans discovered by the container before the AfterBeanDiscovery event is fired.

Workaround

N/A

Issue

Impacted Platforms : N/A

If an application contains both a CDI enabled EJB module and a non-CDI enabled web module, events defined with the following qualifier are not sent:

@Initialized(ApplicationScoped.class) and @Destroyed(ApplicationScoped.class)

Workaround

Place an empty beans.xml file in the WEB-INF directory of the WAR file.

Issue

Impacted Platforms: N/A

For CDI 1.0 in Oracle WebLogic Server, RAR archives are treated as CDI bean archives if the beans.xml file is present in the META-INF directory, and the embedded library JAR classes are included as part of that bean archive. As of Oracle WebLogic Server 12.2.1, each archive, including embedded library JARs, is individually considered as a candidate bean archive based on the presence of the META-inf/beans.xml file or at least one class with a bean-defining annotation.

Therefore, to reproduce the previous behavior, the embedded library JARs must have either a META-INF/beans.xml entry or at least one class with a bean-defining annotation.

Workaround

N/A

Issue

Impacted Platforms: All

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 apply security policies only to JAR files that are EJBs or web applications.

Workaround

N/A

Issue

Impacted Platforms: All

The weblogic.Deployer tool interprets any extraneous string values between command-line arguments as a file specification. For example, consider the following command:

java weblogic.Deployer -activate -nostage true -name myname -source c:\myapp\mymodule

In this case, the tool attempts to activate a file specification named true because the -nostage option takes no arguments and true is an extraneous string value.

Workaround

N/A

Issue

Impacted Platforms: All

The restore method does not correctly update the DConfig Bean with the plan overrides. For example, consider the following steps:

  DeployableObject dObject =
     WebLogicDeployableObject.createDeployableObject(new File(appName));
  DeploymentConfiguration dConfig =
     WebLogicDeploymentManager.createConfiguration(dObject);
  dConfig.restore(new FileInputStream(new File(plan)));

In this case, the plan does not override the DConfig Bean correctly.

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

Issue

Impacted Platforms: All

When a large application file is deployed using the upload option, the deployment task fails with the following error:

java.lang.OutOfMemoryError: Java heap space

To resolve this issue, a new system property, weblogic.deploy.UploadLargeFile, has been added. If you see this issue, include this flag in the java command you use to launch a deployment client.

If you are using the Oracle WebLogic Server patch releases 9.2 MP2, 9.2 MP3,10.0 MP1, 10.0 M2, 10.3, 10.3.1, 10.3.2, or 10.3.3, this flag is not needed.

Workaround

N/A

Issue

Impacted Platforms: Linux

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

Issue

Impacted Platforms: All

If you create an application and deploy it to a target, and then try to deploy that same application to that same target, no relevant output message is displayed to inform you that your application is already deployed to that particular target. This occurs because when the application is deployed the second time it is considered to be the equivalent of a redeploy.

Workaround

N/A

Issue

Impacted Platforms: All

An error occurs when using the appc Maven plug-in after installing Oracle WebLogic Server Maven artifacts to the local repository using the Maven synchronization plug-in.

Workaround

Oracle WebLogic Server pub-sub libraries rely on the BEA_HOME system property to resolve compiler issues. Set the BEA_HOME system property while running appc on pub-sub applications for compilation to resolve these dependencies.

Issue

Impacted Platforms: All

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.

Issue

Impacted Platforms: All

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 add the <timer-implementation> element and corresponding values in the file.

Issue

Impacted Platforms: All

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.

Workaround

None.

Issue

Impacted Platforms: All

Extensions to the JPA metadata model can be specified only through annotations and not by using a structure similar to the orm.xml file defined by the specification.

Workaround

To specify Kodo-specific metadata for your object model, do one of the following:

• Use the Kodo-specific annotations.

• Convert the XML-based metadata to the JDO metadata format, which does support XML specification of extensions.

Issue

Impacted Platforms: All

The WebLogic Spring injection extension model doesn't support lookup method injection.

Workaround

N/A

Issue

Impacted Platforms: All

Deserializing a JDO PersistenceManagerFactory in a managed environment may fail. The exception states that the javax.jdo.PersistenceManagerFactoryClass property is missing. Note that serializing PersistenceManagerFactory should not generally be necessary in a managed environment.

Workaround

None.

Issue

Impacted Platforms: All

Indexes declared at the class level are not always created during schema creation.

Workaround

Create the indexes manually after running the schema generation tools.

Issue

Impacted Platforms: All

OpenJPA throws an exception when @Id fields are also annotated as @Unique in some databases. The 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.

Issue

Impacted Platforms: All

The cache hit and miss counts may rise unexpectedly when manipulating entities without the version data. The extra cache access occurs when 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.

Issue

Impacted Platforms: All

When using the MySQL database, if OpenJPA is configured to automatically run the mapping tool at runtime and create tables within the default schema, it will try to create the table even if the table exists in the database. For example:

<property name='openjpa.jdbc.SynchronizeMappings' value='buildSchema'/>
<property name='openjpa.jdbc.Schema' value='MySQL database name' />

A PersistenceException message 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, do not configure OpenJPA to automatically run the mapping tool at runtime and specify the default schema at the same time.

Issue

Impacted Platforms: All

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

Issue

Impacted Platforms: All

The HTTP Publish/Subscribe server does not support authentication and authorization of the local client. The local client has full permission to operate on channels of the HTTP Publish/Subscribe server, which means that the local client can create/delete channels and publish/subscribe events from channels.

Workaround

N/A

Issue

Impacted Platforms: All

Event messages published to a channel by a local client will not go through the message filters configured to that channel.

Workaround

N/A

Issue

Impacted Platforms: All UNIX

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.

Issue

Impacted Platforms: N/A

When installing Oracle WebLogic Server 12.2.1 on Mac OS X development systems, some recommended JDBC driver fixes for production environments are not included with the Oracle JDBC thin driver that is included with the installation.

Workaround

A patch or patch(es) will be made available on My Oracle Support for developers wishing to incorporate these fixes on development environments.

Issue

Impacted Platforms: All

During server shutdown when executing rollouts, if the server enters the FAILED state, you may encounter the following error:

Workflow wf0008 failed and the revert process was not initiated. The failure was: Failure performing execute of wf0008-3-1-0 (ShutdownServerResumeOnRevertCommand), caused by Failed to shut down server server1: java.lang.Exception: The process for the server server1 has not completely shut down. This problem should be reported and you may have to kill the process manually.

This error is encountered when using WLST.

Workaround

You must check the server logs carefully to determine the reason for the server failure which led to the shutdown failure. You can continue the rollout after resolving the issue and manually shutting down the server.

Issue

Impacted Platforms: All

Due to incompatibility between the ONS (Oracle Notification Services) and the UCP (Universal Connection Pool) JARs that are packaged with WebLogic Server 12.2.1.1, the Active GridLink data source deployments are affected as some data sources stop receiving database FAN events.

Workaround

The ONS JAR packaged with WebLogic Server 12.2.1.1 requires a patch. You can contact My Oracle Support for the patch.

Issue

Impacted Platforms: N/A

In the Zero Downtime (ZDT) patching scenario, when the rollout in progress involves JMS service migration with a case of failback, the JMS T3 standalone clients are unable to perform JNDI lookup for the connection factory and the destination objects on the JMS server.

Workaround

When the migrated service fails back to the original server, the JMS standalone clients must wait for a nondeterministic time until the JNDI lookup is successful.

Issue

Impacted Platforms: All

FastSwap may relax the access modifiers of fields and methods. Private and protected members may be made public at runtime. This change alters the behavior of reflection and may affect reflection-based frameworks such as Struts.

Workaround

N/A

Issue

Impacted Platforms: All

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.

Issue

Impacted Platforms: All

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

Issue

Impacted Platforms: All

FastSwap is not supported when using CDI. If you deploy an application in exploded format with FastSwap enabled, this deployment fails and errors related to CDI occur.

Workaround

N/A

Issue

Impacted Platforms: All

Oracle WebLogic Server 12.1.2 supports JDK 7 for running server applications, and JDK 6 and JDK 7 for WebLogic Server 12.1.2 clients connecting to WebLogic Server 12.1.2 servers. Oracle JRockit is not supported for running WebLogic Server 12.1.2 and later server applications. For more information, see Supported Configuration in What's New in Oracle WebLogic Server.

Workaround

N/A

Issue

Impacted Platforms: All

This issue may occur if you are using an EJB or servlet with resource reference to a JMS Connection Factory, that is, when a connection factory is obtained using an @Resource annotation or a context lookup of a resource defined in an application's XML descriptor, and if this resource reference does not explicitly specify a JNDI name via a lookup attribute, a mappedName attribute, or a jndi-name in a descriptor file.

In WebLogic Server 12.2.1 and later releases, the Java EE 7 Platform Specification mandates a change that can cause such resource references to unexpectedly return a Platform Default Connection Factory instead of either returning a connection factory from JNDI with a JNDI name that matches the resource name, or returning a javax.naming.NameNotFoundException. Following are some of the possible symptoms of this change in behavior of unmapped connection factory resources:

• An INFO level log message indicating that an application has been given a default connection factory though it might have required a custom connection factory instead. For example,

  BEA-169827> <The resource reference "jms/my_cf" of type JMS Connection Factory in application "my_module" does not specify a JNDI name. As of Java EE 7 and WebLogic version 12.2.1.1, such references return a "java:comp/DefaultJMSConnectionFactory" by default when no Connection Factory with a JNDI name that matches the resource name is found.>
  

• An application stops delivering customized behavior that is expected from a custom configured WL JMS connection factory, such as a default message expiration.

• Errors, such as Illegal Destination type, which may occur while attempting to use an AQ JMS destination with a WebLogic JMS connection factory.

• Exceptions such as Destination not found or Dispatcher not found.

• Temporary destination is created on a local JMS Server instead of a JMS Server that is hosted in the same cluster as the intended connection factory.

Workaround

To ensure that applications work as expected, we recommend one of the following workarounds:

• Explicitly configure the system to force old behavior by setting the WebLogic Server JMSConnectionFactoryUnmappedResRefMode configurable to the FailSafe mode. Note that this setting is compliant with the Java EE 7 specification although Java EE 7 mandates that this setting cannot default to the FailSafe mode. For more information, see Specifying the Unmapped Resource Reference Mode for Connection Factories in Administering JMS Resources for Oracle WebLogic Server.

• Examine and fix all unmapped resource reference in all servlets and EJB applications to make them explicitly specify their desired connection factory. If the desired connection factory is Java EE 7 default connection factory, then you can specify java:comp/DefaultJMSConnectionFactory as the JNDI name.

Issue

Impacted Platforms: All

Deployment descriptor validation fails when descriptor validation is enabled, and an EAR file contains only JMS modules.

Workaround

Ensure that there is at least one Java EE specification-compliant module in the EAR file.

Issue

Impacted Platforms: All

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, introduce a small delay between the creation of each new client.

Issue

Impacted Platforms: All

There is no support for multi-byte characters in the Oracle WebLogic Server Store file and directory names. For instance, if the Oracle WebLogic Server name has multi-byte characters, the default store is not created, and Oracle WebLogic Server fails to boot.

Workaround

Create the Oracle 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.

Issue

Impacted Platforms: All

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.

Workaround

None.

Issue

Workaround

Impacted Platforms: All

As of Oracle WebLogic Server 12.1.2, JMS server and WebLogic store targeting in the Configuration Wizard has changed.

In 12.1.2, the Configuration Wizard automatically targets JMS servers and WebLogic stores to migratable targets when these objects are not explicitly targeted to a Managed Server or a cluster in a domain template. Using migratable targets is a best practice that enables high availability for the JMS system.

If you use a custom domain template to create domains in Oracle WebLogic Server 12.1.2, and the template includes JMS servers and WebLogic stores that are not explicitly targeted to a Managed Server or a cluster, targeting results differ from previous releases.

This change in behavior also results in a change to durable topic subscriptions for message-driven beans (MDBs) that enable the generate-unique-client-id extension. When Oracle WebLogic Server creates durable topic subscriptions for such an MDB, it changes the subscription name to include the migratable target name. Messages stored under the original subscription names are not delivered to the MDB, and the original subscriptions continue to accumulate new messages.

When planning your upgrade, note the following important changes:

• Use the Reconfiguration Wizard to reconfigure your existing pre-12.1.2 domain for keeping the configuration and durable topic subscriptions intact. For instructions, see Reconfiguring a WebLogic Domain in Upgrading Oracle WebLogic Server.

• If you regenerate your domain using a custom template, as described above, the resulting configuration differs from previous releases and new durable topic subscriptions are created when the system is started. However, old durable topic subscriptions remain. Those subscriptions contain unprocessed messages that continue to accumulate messages, depleting the server memory.

Choose one of the following recommended workarounds:

• Use the Reconfiguration Wizard to perform an in-place upgrade of the the domain.

• Drain messages before upgrading or regenerating the domain configuration.

• Delete the JMS file store files or JMS JDBC store tables. All messages persisted in the file or table are deleted.

Issue

Impacted Platforms: All

To enable JMS .NET clients developed prior to WebLogic Server 12.1.3 to interoperate with WebLogic Server 12.1.3, set the following system property on your WebLogic Server 12.1.3 instances:

-Dweblogic.protocol.t3.login.replyWithRel10Content=true

The default value is false for interoperability with existing JMS .NET clients developed prior to WebLogic Server 12.1.3.

Workaround

None.

Issue

Impacted Platforms: All

After extending a domain using an extension template that was generated from a domain that contains JMS distributed destinations, the distributed destinations are not present in the domain. This impacts the following distributed destinations:

• distributed-queue

• distributed-topic

• uniform-distributed-queue

• uniform-distributed-topic

If any of these elements are contained in the JMS XML files in the source template, they are not processed and are not configured in the destination domain.

Workaround

To resolve this, use the following sequence of WLST commands, either interactively or in a script:

readDomain('domain_path')

addTemplate('extension_template_file') 

unassign('JmsSystemResource','resource_name','Target','destination_name') 
For example: unassign('JmsSystemResource','JMSModule','Target','C1')

assign('JmsSystemResource','resource_name','Target','destination_name')
For example: assign('JmsSystemResource','testModule','Target','Server-1')

unassign('JmsSystemResource','resource_name','Target','destination_name')
For example: unassign('JmsSystemResource','testModule','Target','Server-1')

assign('JmsSystemResource','resource_name','Target','destination_name')For example: assign('JmsSystemResource','testModule','Target','C1')

updateDomain()

closeDomain()

Issue

Impacted Platforms: All

When creating a JMS messaging bridge using JBoss 5 as a foreign provider, conflicting versions of the same class are loaded. This causes the bridge to fail during startup.

Workaround

Oracle recommends that you upgrade to JBoss 7 to avoid this issue.

Issue

Impacted Platforms: All

When the transaction protocol for a data source is changed, it is necessary to restart all targeted servers in order to avoid inconsistent transaction outcomes.

Workaround

N/A

Issue

Impacted Platforms: All

Due to a known Sun Microsystems VM bug (513552), a 1.4 Thin Client Applet cannot contact Oracle 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 encounters an error because clients are not allowed to use server connections.

Workaround

N/A

Issue

Impacted Platforms: RedHat Linux

Applications that run on RedHat (RH) Linux and that also directly or indirectly use system time calls may experience intermittent time issues if the ClockSource is set to tsc (the default). The standard POSIX C gettimeofday() call, and consequently also the Java System.currentTimeMillis() and java.util.Date() calls can intermittently return a value that is approximately 4400 seconds in the future, even in a single-threaded application.

This issue is not unique to WebLogic or Java, but applies to any application running on RH Linux. Issues can occur for applications that either explicitly make a time call using standard Java, or explicitly by using any time-based application server services.

Possible symptoms include, but are not limited to, premature transaction timeouts, unexpected expiration of JMS messages, and incorrectly scheduled timers.

This issue was fixed in RedHat 5.3.

Workaround

N/A

Issue

Impacted Platforms: Linux

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

Issue

Impacted Platforms: Linux

A Serial Version UID Mismatch issue is encountered if you deploy an application on a latest JVM, but compiled with previous Service Release of IBM Java 6 JDK.

Workaround

To be compatible with the serialization of previously compiled applications, modify the WL_HOME/common/bin/commEnv.sh file to include the following command:

JAVA_OPTIONS="$JAVA_OPTIONS 
-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0"

Alternatively, you can use the command line option:

export IBM_JAVA_OPTIONS=
"-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0"

If you intend to deploy new applications with previously compiled applications, they must be recompiled as necessary to have the same Serial Version UID.

Issue

Impacted Platforms: Linux

You might encounter a JVM stack overflow error or exception while running WebLogic Server. This issue applies to Oracle Enterprise Linux 4, 5, 5.1 on AMD64 and 64-bit Xeon platforms.

Workaround

Increase the stack size from the default 128k to 256k.

Issue

Impacted Platforms: Linux x86

You might encounter a JVM crash when using GUI libraries such as AWT or javax.swing (which often delegates to AWT).

Workaround

Start the server using the following flag:

-Djava.awt.headless=true

Issue

Impacted Platforms: All

When packing a domain that has been configured to use Lifecycle Manager in one environment using the pack command, and then unpacking it in another environment, the plug-in paths contained in the <Domain>/config/lifecycle-config.xml file may still reference the Oracle Home directory paths from the source environment.

Workaround

Rectify the file paths in the lifecycle-config.xml file to reflect the Oracle Home directory paths in the target environment.

Issue

Impacted Platforms: All

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

Workaround

You can explicitly mark MBean attributes as @unharvestable.

Issue

Impacted Platforms: All

When specifying a wildcard pattern in a variable for a watch rule expression that matches custom MBean ObjectName patterns, ensure that the pattern is sufficiently explicit. If you exclude an MBean type name and use an ambiguous instance pattern, the following may result:

• Only WebLogic Server runtime MBean instances are matched to the pattern.

• The desired custom MBean instances are ignored.

For example, the following ObjectName pattern does not explicitly declare a type and uses an ambiguous ObjectName pattern that can match a WebLogic Server runtime MBean instance:

${ServerRuntime//com.b*:Type=Server*,*}

Workaround

To avoid confusion, use a sufficiently explicit ObjectName pattern, or declare the MBean type in the variable expression.

Issue

Impacted Platforms: All

This issue is related to a change in how WebLogic Diagnostic Framework (WLDF) uses the module name for harvester records and watch rule notifications. The internal descriptor name is now overridden to use the name that is provided when the external WLDF descriptor is registered through the Runtime Control API or WLST functions. You will notice this if you have been using the Runtime Control feature to deploy external WLDF system resources to gather Harvester metrics, or listen for a Watch rule notification based on the deployed module.

For example, assume that the Harvester and Watch elements in your deployed descriptor resemble the following:

<harvester>
   <name>MyExternalResource</name>
...
<watch-notification>
   <name>MyExternalResource></name>
...

In addition, you register this descriptor with the runtime control as createSystemControl("resource1", ...). Then the previous harvester data would have been recorded using MyExternalResource as the WLDFMODULE column value for Harvester records in the archive for this resource. It would also be used for the module name in the Watch Notification payloads. Now, resource1 would be used for the WLDFMODULE name in the harvester records and the watch and notification payloads.

Workaround

Use the name the external WLDF resource was registered with when using the WLST command createSystemResourceControl(). Additionally, any notification listeners for Watch notifications from an external resource that are dependent on the WLDF module name in the notification payload should be looking for the name the control was registered with.

For example, if you register your control as createSystemResourceControl("resource1", ...), then the WLDF Accessor queries for this resource should include the module name as WLDFMODULE='resource1' in the query string.

Issue

Impacted Platforms: Linux

On some specific Linux platforms and versions, there is an issue removing a virtual interface/alias dynamically. Removing the virtual interface that is the primary address of the interface may result in other secondary virtual IP addresses being removed at the same time. This condition may lead to random exceptions occurring with Node Manager during server migration. If you encounter this issue, you may occasionally find exceptions in the Node Manager log file when shutting down a server after migration. For example, you may receive the following error:

java.io.IOException: Command '/<PATH to DOMAIN>/bin/server_migration/wlsifconfig.sh -removeif -IPv4 eth0 X.X.X.X returned an unsuccessful exit code '1'.

Here is an example of the issue:

First, add three virtual interfaces with the first one being the primary:

$ sudo /sbin/ifconfig eth0:4 X.X.X.178 netmask 255.255.248.0
$ sudo /sbin/ifconfig eth0:5 X.X.X.179 netmask 255.255.248.0
$ sudo /sbin/ifconfig eth0:6 X.X.X.180 netmask 255.255.248.0
$ sudo /sbin/ifconfig eth0:4 down

When removing the primary (the first interface in the list), the other two will be automatically removed at the same time.

Workaround

To fix this issue temporarily, use the following command to enable the promote_secondaries flag on your network interface. Replace eth0 with your actual interface name:

$ sudo /sbin/sysctl net.ipv4.conf.eth0.promote_secondaries=1

You can also use the following command to update the default setting for all interfaces:

$ sudo /sbin/sysctl net.ipv4.conf.all.promote_secondaries=1

If this flag is enabled and the primary address of an interface gets deleted, a secondary interface will be upgraded to become the primary interface. The default is to purge all the secondary interfaces when you delete the primary interface.

To permanently remedy this issue after server reboot, update the sysctl.conf file. For example:

$ echo "net.ipv4.conf.eth0.promote_secondaries=1" >> /etc/sysctl.conf

Issue

Impacted Platforms: All

In rare cases, the Oracle HTTP Server (OHS) instances that are managed by the Oracle WebLogic Server may start in the UNKNOWN state. This situation can occur if the Administration Server is unable to initialize the state of the OHS instance. For example, if Node Manager is not running when you create the OHS instance and you connect directly to the Node Manager and bypass the Administration Server when checking the state for the first time.

Workaround

Continue to use the Administration Server. The state of the OHS instance should be initialized properly.

Issue

Impacted Platforms: All

WLST offline, as well as the pack and unpack commands, do not support setting the following new Node Manager replacement properties that were introduced in WebLogic Server 12.1.3.

Workaround

If you configure Node Manager properties using WLST offline, or the pack and unpack commands, you must continue to use the preceding deprecated properties, which remain fully supported in WebLogic Server. For more information, see Node Manager Properties in Administering Node Manager for Oracle WebLogic Server.

Issue

Impacted Platforms: MS Windows 2000

When trying to persist an empty byte array field within an entity to a Sybase or Oracle database, the value gets stored as a NULL rather than as bytes. As a result, when retrieving the value, NULL is returned.

This is a limitation of the Sybase and Oracle drivers, which convert the empty byte array to a NULL while storing it in the database. The issue happens with WebLogic JDBC drivers as well as the proprietary Sybase and Oracle drivers.

Workaround

N/A

Issue

Impacted Platforms: All

The proxy plug-in for IIS does not work in the following conditions and results in an apr_socket_connection error:

1. Both the IIS and Oracle WebLogic Server instances are on the same machine.
2. 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).
3. The listen address of the Oracle WebLogic Server instance is set to the simple host name.
4. Either the directive WebLogicHost or WebLogicCluster is set to the simple host name for the IIS instance.

Workaround

N/A

Issue

Impacted Platforms: All

Introspection fails and users receive an error when they try to introspect a domain that they cannot write into.

Workaround

Change the permissions on the domain root directory to allow the user that executes the introspect.

Issue

Impacted Platforms: All

In Oracle Virtual Assembly Builder (OVAB) Studio, HTTP proxying is disabled. You can use a system property to enable HTTP proxy detection.

Workaround

You can set this system property for each execution of a Studio launch, or permanently by modifying the abstudio.sh file.

To set the property for a single execution of OVAB Studio:

1. Shut down OVAB Studio.

2. Remove the configuration directory:

   $AB_INSTANCE/state/gui/$USER/system.12.1.2.0.0 (or equivalent)

3. Restart the GUI with the property set to some value, for example 1:

   ./abstudio.sh -J-Dovab.studio.enableHttpProxy=1

To set the property to consistently enable HTTP proxying:

After setting enableHTTPProxy=1, you can set the proxy host, port, and exceptions using the standard Java properties http.proxyHost, http.proxyPort, and http.nonProxyHosts. If you are using a non-standard desktop environment on Linux, you may need to set the http_proxy property with the valuehost:port.

Issue

Impacted Platforms: All

When a client invokes an EJB that is hosted in a WebLogic 12.1.2 domain configured to run in production mode, any invocation failure results in a truncated Java exception stack trace returned to the client.

Workaround

In the Java command that starts WebLogic Server, specify the following option:

-Dweblogic.PrintStackTraceInProduction=true

Issue

Impacted Platforms: All

The -Dweblogic.system.StoreBootIdentity option works only if the appropriate server security directory exists. This directory is usually created by the Configuration Wizard or the upgrade tool.

However, the appropriate server security directory could be absent in domains checked into source-control systems.

Workaround

N/A

Issue

Impacted Platforms: All

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.

Issue

Impacted Platforms: All

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.

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.

Issue

Impacted Platforms: All

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.

Even if the user is already authenticated at the Identity Provider site and Force Authentication is enabled, the user is forced to authenticate again at the Identity Provider site.

Avoid enabling both these attributes.

Workaround

N/A

Issue

Impacted Platforms: Linux

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 administrator 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. To do this, add the -Djava.security.egd=file:///dev/urandom switch or file://dev/./urandom to the command that starts the Java process.

Issue

Impacted Platforms: All

The BEA-090402 message is a catalog message that explains what to do if a server instance fails to boot due to a problem with the boot.properties file.

However, the real issue is an authentication problem. BEA-090402 describes the most likely root cause: the customer has modified the boot.properties file or the boot user password. Therefore, the authentication fails.

There are other causes for this failure that are less obvious. For instance, there could be an LDAP corruption, a disk failure, or a Managed Server may fail to connect to the Administration Server and falls back to authenticating on its local LDAP that is out-of-date. These causes are not mentioned in BEA-090402. If you are positive that you are not having a credential issue, BEA-090402 may indicate one of these less common causes.

Workaround

N/A

Issue

Impacted Platforms: All

The Oracle WebLogic Server LDAP Authentication provider log messages show an incorrect URL for the LDAP connection returned by the getConnection method. The getConnection messages indicate that SSL is used, even if you did not specify SSL in the Oracle WebLogic Server provider configuration.

Workaround

The "Connecting to host" messages in the log file do correctly indicate whether SSL is used. For example,

• <Connecting to host=somehost, port=3060>

• <Connecting to host=somehost, ssl port=3060>

Issue

Impacted Platforms: All

When starting an ODI Managed Server, the identity used to start the Managed Server is not mapping properly to the WebLogic Sever Administrator role, causing security errors. If these warnings are seen while starting the Managed Server, the embedded LDAP files from the Managed Server are causing a resynchronization of the policy from the Administration Server.

Workaround

Issue

Impacted Platforms: All

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.

Issue

Impacted Platforms: All

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.

Workaround

N/A

Issue

Impacted Platforms: All

The following exception occurs when upgrading Oracle WebLogic Server using the Reconfiguration Wizard with log_priority=ALL:

Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (NM_OPSS.IDX_JPS_RDN_PDN) violated

Workaround

N/A

Issue

Impacted Platforms: All

Several WebLogic Server software features, such as Lifecycle Manager, RESTful Management Services, WebLogic Remote Console, and Fusion Middleware Control have dependencies on WebLogic Server security features which may not be present in an upgraded domain configuration.

Workaround

You must manually configure the following security features during domain upgrade:

• Create an LCMUser service account if not present. This service account must be present in the administrator group and should have a secure password.

• Update the DefaultIdentityAsserter configuration to include weblogic-jwt-token as an active type if not present.

Issue

Impacted Platforms:All

After upgrading an application from a WebLogic Server version prior to 12.1.2, a MaxPostSizeExceededException is reported in the web browser.

Workaround

Set the max-save-post-size session-descriptor to the maximum size (in bytes) of the POST that will be saved or buffered by the container during FORM authentication.

Issue

Impacted Platforms: All

When a PoolLimitSQLException error 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.

Workaround

No workaround available.

Issue

Impacted Platforms: All

When accessing a web page using the SSL port, the page fails to open and the following error is reported:

Secure Connection Failed 
 
An error occurred during a connection to <hostname>. 
 
You have received an invalid certificate. Please contact the server 
administrator or email correspondent and give them the following information: 
 
Your certificate contains the same serial number as another certificate 
issued by the certificate authority. Please get a new certificate containing a unique serial number.

Workaround

The following workaround can be used for Firefox.

If you have received this error and are trying to access a web page that has a self-signed certificate, perform the following steps in Firefox:

If you are using Internet Explorer or other web browsers, you can ignore the warning page that appears and continue to the web page.

Issue

Impacted Platforms: All

Deployment plans cannot be used to override the following two descriptors during the 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 the 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.

Issue

Impacted Platforms: All

With the Spring extension model enabled, Oracle WebLogic Server 10.3 or later does not support Spring Dependency Injection (DI) on JSP tag handlers for performance reasons.

Currently, Oracle WebLogic Server supports Spring DI on most web components. For example, servlets, filters, and listeners. However, Spring DI is not presently supported on JSP tag handlers for performance reasons.

Workaround

No workaround available.

Issue

Impacted Platforms: All

When a session is persistent and an older version of a servlet context is retired, accessing the application with a valid sessionid will result in a 503 error.

For example, assume that 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, a 503 error occurs.

Workaround

No workaround available.

Issue

Impacted Platforms: All

As of Oracle WebLogic Server 12.1.2, the jdbc-connection-timeout-secs element in the weblogic.xml deployment descriptor has been removed. Applications that configure jdbc-connection-timeout-secs will fail to deploy on Oracle WebLogic Server 12.1.2 server instances, resulting in the following error in the server log:

Unable to load descriptor /.../WEB-INF/weblogic.xml of module myweb. The error is weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND 
  <6:7> problem: cvc-complex-type.2.4a: Expected elements 'timeout-secs@http://xmlns.oracle.com/weblogic/weblogic-web-app ...' instead of 'jdbc-connection-timeout-secs@http://xmlns.oracle.com/weblogic/weblogic-web-app' here in element session-descriptor@http://xmlns.oracle.com/weblogic/weblogic-web-app

Workaround

Remove the jdbc-connection-timeout-secs element from the weblogic.xml deployment descriptor.

Issue

Impacted Platforms: All

In order to prevent incoming messages that are too large, Tyrus places a constraint on the message frame size. The default value is 4 MB.

Workaround

This value can be configured through the servlet context parameter. For WebLogic Server, this is the weblogic.websocket.tyrus.incoming-buffer-size parameter and it can be edited as follows:

<context-param>
   <param-name>weblogic.websocket.tyrus.incoming-buffer-size</param-name>
   <param-value>value_to_tune</param-value>
</context-param>

Issue

Impacted Platforms: All

As of 12.2.1.1, Oracle WebLogic Server does not support annotated custom tags for JSF-based web applications that have the version of the web application deployment descriptor, web.xml, set to 2.5 or later.

Workaround

For compatibility with your web application that has the version set to 2.5 or earlier, Oracle recommends that you upgrade the version of the web application deployment descriptor, web.xml, to 3.2.

For instance, if your existing web application has the version set to 2.3, you should upgrade it to 3.2 as shown in the following example:

<?xml version = '1.0' encoding = 'windows-1252'?>
<web-app xmlns="xmlns.jcp.org/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="xmlns.jcp.org/xml/ns/javaee
xmlns.jcp.org/xml/ns/javaee/web-app_3_2.xsd"
         version="3.2">
   ...
</web-app> 

Issue

Impacted Platforms: All

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:

https://docs.python.org/3/tutorial/index.html

Issue

Impacted Platforms: All

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.

Issue

Impacted Platforms: All

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.

Workaround

N/A

Issue

Impacted Platforms: All

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.

Workaround

N/A

Issue

Impacted Platforms: All

Oracle 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

Ensure that any custom exceptions that are used in callbacks are in a package that matches the target namespace of the parent web service.

Issue

Impacted Platforms: All

You cannot use JMS transport in an environment that also uses a proxy server. The reason is that 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.

Workaround

N/A

Issue

Impacted Platforms: All

clientgen fails when processing a WSDL that uses the complex type http://www.w3.org/2001/XMLSchema{schema} as a web service parameter.

Workaround

N/A

Issue

Impacted Platforms: All

Using a two dimensional XmlObject parameter (XmlObject[][]) in a JWS callback produces an IllegalArgumentException error.

Workaround

No workaround available.

Issue

Impacted Platforms: All

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.

Issue

Impacted Platforms: All

When web service 'A' wants to invoke web service 'B', web service 'A' should use the @ServiceClient annotation. 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, Oracle 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 {
  ...
}

Issue

Impacted Platforms: All

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

When there are multiple certifications in the X509 Certificate chain, <sp:WssX509PkiPathV1Token11/> or <sp:WssX509PkiPathV1Token10/> should be used, instead of <sp:WssX509Pkcs7Token11/> or <sp:WssX509Pkcs7Token10/>.

Issue

Impacted Platforms: All

For the xmlcatalog element in the build.xml file, 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.

Issue

Impacted Platforms: All

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 outside of a target.

Issue

Impacted Platforms: All

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 inline or in an external catalog file(s), or both. To use an external catalog file, the xml-commons resolver library (resolver.jar) must be in the 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. However, in this case, 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.

Issue

Impacted Platforms: All

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.

Workaround

N/A

Issue

Impacted Platforms: All

When shutting down an Oracle WebLogic Server instance that has a JAX-RS application running on it, you may observe the following error message in the server log:

<Error>
<org.glassfish.jersey.server.internal.monitoring.MonitoringStatisticsProcessor
> <BEA-000000> <Exception thrown when provider class 
org.glassfish.jersey.server.internal.monitoring.MonitoringFeature$StatisticsLi
stener was processing MonitoringStatistics. Removing provider from further
processing. ...

Workaround

This error message is benign and can be ignored.

Issue

Impacted Platforms: All

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.