> Known and Resolved Issues > WebLogic Server Known and Resolved Issues

Known and Resolved Issues

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

WebLogic Server Known and Resolved Issues

The following sections describe known problems in WebLogic Server 10.0 and later Maintenance Packs, as well as problems that were resolved in version 10.0 and subsequent Maintenance Packs. Entries include a description of the problem, and a workaround or solution where appropriate. A notation in the Fixed In column indicates that the problem has been resolved.

For information about new and changed functionality in WebLogic Server 10.0, see What’s New in WebLogic Server 10.0.

Disclaimer

This section also provides information about issues planned to be resolved in WebLogic Server 10.0 Maintenance Pack 2 (10.0 MP2), in advance of the general availability of WebLogic Server 10.0 MP2. For final information about resolved issues see the Release Notes that will be published when 10.0 MP2 becomes generally available.

Note: WebLogic Server 10.0 MP2-specific information is subject to change, and patches for 10.0 MP2 CRs are currently neither integrated with the latest available version of WebLogic Server nor available for download.

 

Administration Console

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR063594
Information about cached JDBC statements is not displayed on the JDBC Monitoring pages.
9.0 Beta
Will not fix
CR200627
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 or Solution:
BEA 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.
9.0
 
CR269866
Some WebLogic Server Administration Console pages did not work correctly in a proxy server environment. In some circumstances, pages were constructed with incorrect URLs.
Workaround or Solution:
The URL construction method has been corrected and the WebLogic Server Administration Console now works correctly when accessed from a browser behind a proxy server.
9.1
10.0
CR284857
In the Administration Console Online Help, the Search button always returns “0 documents found.”
Workaround or Solution:
Search the Administration Console Online Help that is published at
http://edocs.bea.com/wls/docs92/ConsoleHelp/
Enter your search query in the text box that is in the upper right corner of the document. To search for text that appears only in the Online Help, include the following string with your query: docs92/ConsoleHelp
For example, the following query finds all instances of “SNMP” in the Administration Console Online Help:
SNMP docs92/ConsoleHelp
9.2
10.0
CR284747
To archive configuration files, the following two parameters need to be configured appropriately:

<archive-configuration-count>10</archive-configuration-count>

<config-backup-enabled>true</config-backup-enabled>

However, the Administration Console did not enable you to configure the parameter config-backup-enabled.
Workaround or Solution:
You can now configure these parameters in the Administration Console on the Domain: Configuration: General page, in the Advanced section.
9.1
10.0
CR284823
The WebLogic Server Administration Console did not provide the ability to monitor connection details for a Jolt Connection Pool. This feature was present in previous versions of WebLogic Server.
Workaround or Solution:
You can now use the Administration Console to view details for each Jolt Connection Pool connection. Click on a connection pool entry in the monitoring table to display a page with details for each connection.
9.1
10.0
CR284894
In the Administration Console Online Help, links to other WebLogic Server documents point to http://docs-stage/wls/docs92/, which is the wrong URL root.
Workaround or Solution:
After you click on a link to a WebLogic Server document, in your Web browser’s address field, change docs-stage to edocs.bea.com. For example, the following is the correct URL for the ServerMBean entry in the WebLogic Server MBean Reference:
http://edocs.bea.com/wls/docs92/wlsmbeanref/mbeans/ServerStartMBean.html
9.2
10.0
CR287765
The Deployment Control page in the WebLogic Server Administration Console supports navigating into the modules, Web Services, and EJBs within a deployment. When a deployment was expanded, the ability to navigate to previous or next pages in the deployment control table was disabled and the page number information was incorrect.
Workaround or Solution:
The Deployment Control page was updated to resolve these paging issues. Administrators are now able to navigate to other deployments regardless of whether any deployments on the current page are expanded.
9.2
10.0
CR303905
Clicking on the Release Configuration button while editing the settings for a Server/Cluster/Virtual Host whose name includes non-ASCII characters caused the console to display "The object that you were viewing has been deleted, ..." due to the name being garbled.
Solution:
This issue has been fixed.
9.2
10.0
CR306634
The WebLogic Server Administration Console includes pages which can be used to test web applications, resource connectors, Web Services, and other deployments. Test pages are include for EJBs, but the test points for these listed EJBs are never available.
The omission of these EJB test points does not imply that the EJBs are not reachable or working. Administrators can use the console’s EJB monitoring pages to monitor the activity and status of their deployments.
9.2
 
CR314311
There was no method to set the ShowArchivedRealPathEnabled attribute of WebAppContainerMBean in config.xml file from Administration Console.
This problem has been resolved by adding a check box named Archived Real Path Enabled on the Domain > Configuration > Web Applications page.
9.2
10.0 MP1
CR320020
The IdleTimeoutSeconds attribute of Stateful Session Bean was not working as expected.
This problem has been resolved.
9.1
10.0 MP1
CR320304
CR320841
When you export or import a large JMS queue using WebLogic Administration Console, the system used to raise OutofMemory error.
This problem has been resolved.
9.2 MP1
10.0 MP1
CR323690
WebLogic Administration Console was not allowing the user to create more than 100 WTC Import/Export services.
This problem has been resolved.
9.2
10.0 MP1
CR325644
It was not possible to set the WeblogicPluginEnabled attribute of ClusterMBean from Administration Console.
This problem has been resolved by providing a check box in Advanced Settings of the Cluster > Configuration > General tab that sets WeblogicPluginEnabled attribute of ClusterMBean.
10.0
10.0 MP1
CR336261
java.util.MissingResourceException used to occur when you change the log level using Administration Console.
Workaround:
Edit the config.xml file manually.
This problem has been resolved.
10.0
10.0 MP2
CR345091
Applications referring to J2EE libraries were not redeployed after J2EE library upgrade.
This problem has been resolved.
10.0
10.0 MP2
CR336816
Some of the links in the “Understanding JMS Resource Configuration” online help topic point to http://docs-stage/wls instead of http://edocs.bea.com/wls. This problem is causing a 404 error. To access the correct information, substitute edocs.bea.com for docs-stage in your web browser.
10.0
 
CR338409
Two invalid configuration options, true and false, are documented in the Administration Console Reference > Deployments > Resource Adapters > Resource Adapter: Configuration: General page of the Administration Console online help.
10.0
 

 

Apache Beehive Support

No issues at this time.

 

Cluster

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR357904
Unreachable server was not removed from the secondary server list and WebLogic Server was trying to replicate session to a server that has been disconnected from the network.
This problem has been resolved.
10.0
10.0 MP2

 

Connector (Resource Adapter)

No issues at this time.

 

Console Extensions

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR294969
Administration console extension writers who wished to use the ButtonBar or ButtonBarButton tags in a console extension were unable to specify a resource bundle to customize or localize labels for buttons, due to the absence of a bundle attribute in the tags.
Workaround or Solution:
The ButtonBar and ButtonBarButton tags in console extensions now support the bundle attribute.
9.2
10.0
CR308556
WebLogic Portal requires that any explicit Skeleton URI references be fully qualified relative to the webapp. The documentation and some of the console extension examples that we have provided have sometimes used relative references to these skeletons. For example:
<netuix:singleLevelMenu markupType="Menu" markupName="singleLevelMenu" skeletonUri="singlelevelmenu_children2.jsp"/>
should have been correctly specified as:
<netuix:singleLevelMenu markupType="Menu" markupName="singleLevelMenu" skeletonUri="/framework/skeletons/default/singlelevelmenu_children2.jsp"/>
Workaround or Solution:
The WebLogic Server Administration Console portal configuration has been updated to use fully qualified references. For this release, relative skeleton URI references will continue to work. Warnings will be logged for any console extensions that do not use fully qualified skeleton references in their look and feel files.
Any console extensions that you have written should be updated to use fully qualified skeleton URIs, as these relative references may no longer function correctly in a future release.
9.0
10.0

 

Core Server

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR283286
The default accept backlog value for the listen thread was too small.
Solution:
The default accept backlog value for the listen thread has been increased from 25 to 300.
9.0
10.0
CR298059
The cluster messaging receiver that receives and dispatches multicast messages was using the WebLogic Server thread pool. The receiver never released the thread and continued to use it forever. This is expected behavior but the thread was reported as hogging.
Solution:
The cluster messaging receiver has been moved to its own dedicated daemon thread outside of the thread pool to prevent the reporting of the hogging thread.
9.0
10.0
CR307041
Deploying a deprecated WebLogic Server 8.1 application scope startup or shutdown class on WebLogic Server 9.x resulted in a DeploymentException while activating after deployment. Startup and shutdown classes registered in the weblogic-application.xml descriptor were being required to extend the WebLogic-specific class weblogic.application.ApplicationLifecycleListener.
Solution:
Startup and shutdown classes registered in the weblogic-application.xml descriptor are no longer required to extend the WebLogic-specific class weblogic.application.ApplicationLifecycleListener.
9.2
10.0
CR283953
On Solaris 9 or later, with JDK 1.5, any set operation on a half-closed socket throws a SocketException. This delayed the server in accepting new connections on the same port and also caused the server socket to be recycled if the maximum backoff time between failures reaches its maximum.
Solution:
WebLogic Server no longer throws an exception in connection with a set operation on half-closed sockets.
9.1
10.0
CR317840
When using the -Dweblogic.iiop.useJavaSerialization flag in a call over IIOP, org.hibernate.LazyInitializationException used to occur.
This problem has been resolved.
9.2
10.0 MP2
CR362919
SSL connection used to fail when native I/O was enabled.
This problem has been resolved.
10.0
10.0 MP2
CR365419
Deleting and re-creating a work manager used to result in java.lang.IllegalArgumentException.
This problem has been resolved.
10.0 MP1
10.0 MP2
CR363797
When the <use81-style-execute-queues> element was set to true in config.xml, the HTTP URI request was not displayed properly on the Server > Monitoring > Threads page of the Administration Console.
This problem has been resolved.
10.0 MP1
10.0 MP2

 

Deployment

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR067087
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.
7.0
Will not fix
CR071138
The weblogic.Deployer tool interprets any extra 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.
7.0
 
CR091020
If you deploy an application to a cluster and one or more clustered servers are unavailable (for example, servers partitioned from the cluster due to a network outage), the deployment operation may appear to hang. In addition, the partitioned servers may not deploy the application even after they successfully rejoin the cluster.
Workaround or Solution:
Reboot the partitioned servers after they rejoin the cluster.
8.1
 
CR200754
If a deployment plan has overrides of non-configurable elements, WebLogic Server does not currently reject the elements or fail to parse them.
Workaround or Solution:
Use configurable elements that use these annotations:
@configurable
@dependency
@declaration
@dynamic
9.0
Will not fix
CR220968
If you deploy a web app with virtual hosts as targets, you cannot then change the targeting information unless you redeploy the entire web app with new target information.
Workaround or Solution:
Redeploy the web app with new targets information.
9.0
 
CR277341
ClassLoader.getResources() was only returning the first matching entry in an application.
Solution:
ClassLoader.getResources()now returns all the matching entries found in the application.
9.1
10.0
CR279281
Some OS and NFS combinations result in deployment failures or configuration updates with an exception like:

weblogic.management.DeploymentException: Attempt to operate 'distribute' on null BasicDeploymentMBean

Workaround or Solution:
  • Run statd() and lockd() processes on every NFS client that accesses a remote NFS volume.
  • If multiple servers that share the same domain root are started with different user Ids of same group, set the correct "umask" for the server processes so that a file created by one server can be opened for read/write by other servers without security exceptions.
9.1
 
CR280686
WebLogic Server 9.x encountered an error when deploying an application using a WebLogic Server 8.1 weblogic.Deployer client.
Solution:
This release of WebLogic Server can now handle deployments from a WebLogic Server 8.1 weblogic.Deployer client.
9.1
10.0
CR282367
While using the WebLogic 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 Administration Server in addition to any Managed Servers or clusters.
9.0
 
CR287774
WebLogic Server could not deploy more than two versions of an application library. Attempting to do so resulted in an error like:
Cannot deploy or redeploy application 'test-app-lib [LibSpecVersion=9.2.0,LibImplVersion=9.2.0.2]' because the maximum number of application versions (2) for application 'test-app-lib' is exceeded
Workaround or Solution:
The limit on the number of deployed versions has been removed. Now, more than two versions of an application library can be deployed.
9.2
10.0
CR292189
When you partially redeploy a single module from a set of inter-dependent modules, the deployment operation could throw an exception if any of the dependent modules (such as children) are not included in the partial redeploy list.
Workaround or Solution:
In development mode, WebLogic Server now traces the dependencies between various modules and, rather than throwing an exception, it automatically deploys any required modules.
9.2
10.0
CR294746
In some scenarios, redeployment failed with a CannotRedeployException. The exception was caused by the web app’s Module-URI being registered in the AppClassLoaderManager instead of its module-id (context-root). This occurred only during a classloader bounce in WebAppModule.
Solution:
WebLogic Server now registers a web app’s module-id with the AppClassLoaderManager.
9.2
10.0
CR299135
If you deploy a web app as an archive war file, then context.getRealPath() returns null. This behavior can lead to certain failures in cases where the web app is dependent on the path.
Solution:
Use the <show-archived-real-path-enabled> flag to specify that context.getRealPath() returns the path of the resource from the Server's internal webapp extraction directory for archived web applications. The flag can be configured in two ways:
  • At domain level in config.xml. For example:
<web-app-container>
<show-archived-real-path-enabled>true
</show-archived-real-path-enabled>
</web-app-container>
  • At the web app level in weblogic.xml. For example:
<container-descriptor>
<show-archived-real-path-enabled>true
</show-archived-real-path-enabled>
</container-descriptor>
The value of <show-archived-real-path-enabled> set in the web app has precedence over the value set at the domain level. The default value of this property is false.
Note that, if this path is used to dynamically copy some content to this directory location, the content will end up in the Server's internal web app extraction directory. When the web app is recompiled for any reason, the web app may be re-extracted and previously copied content will be lost.
9.2
10.0
CR299081
In the interest of faster server startup, a remote deployer EJB used only by WebLogic 9.0 or 9.1 weblogic.Deployer clients is no longer started by default. If you use 9.0 or 9.1 weblogic.Deployer with default settings, an error message will be displayed:

While trying to lookup 'weblogic.remote.Deployer' didn't find subcontext 'remote'. Resolved 'weblogic'

Workaround or Solution:
If you require deployment from a 9.0 or 9.1 weblogic.Deployer using the -remote option, you need to set the DeploymentConfigurationMBean.RemoteDeployerEJBEnabled attribute to true. To set this attribute using the WebLogic Server Administration Console, on the Domain: Configuration: General tab, click Advanced and check Enable Remote Deployer EJB.
10.0
 
CR301854
WebLogic Server was invoking weblogic.application.ApplicationLifecycleListener callbacks with an internal kernel identity instead of the anonymous user identity.
Workaround or Solution:
WebLogic Server now invokes these ApplicationLifecycleListener callbacks with the anonymous user identity. As part of this change, the user identity will be different for the execution of these callbacks.
If your implementation of these callbacks is depending upon the permissions of the internal kernel identity, then the callback implementation may encounter errors when run with the anonymous user identity. You should either modify the callback implementation to use a different identity or specify a deployment principal name on the application deployment MBean.
9.0
10.0
CR303462
An application deployed to an individual managed server in a cluster was not removed from the staging directory during undeployment. This could cause errors if the application was later targeted to a different individual server in the cluster. The deployment could fail with the following error:
An error occurred during activation of changes, please see the log for details. [Deployer:149257]Rejecting attempt to distribute application, 'webapp_900', while the application is running.
Solution:
WebLogic Server now ensures that the application and stage files are removed if the application is no longer targeted to any cluster members.
9.0
10.0
CR305769
WebLogic Server would fail to apply deployment plan overrides if a default namespace was not set in the weblogic.xml descriptor. This would result in a VALIDATION PROBLEMS WERE FOUND error.
Solution:
WebLogic Server was modified to inherit the namespace from the parent attribute when merging deployment plan overrides with the weblogic.xml descriptor.
9.0
10.0
CR308613
Performing a partial build through WebLogic Workshop could result in a deployment error, due to a partial redeploy.
Solution:
This has been fixed by reconciling WebLogic Server 8.1-style MBeans in the compatibility processor of the DynamicUpdateOperation.
9.2
10.0
CR308699
Changes made to the deployment plan while one managed server is down were not propagated to the managed server when it was brought back up. WebLogic Server was not using the file timestamps when determining whether to download the archive and plan files during startup of the managed server.
Workaround or Solution:
WebLogic Server’s startup has been modified to use the plan and archive timestamp. If the plan or archive are out of date, then WebLogic Server downloads new versions when the managed server starts up.
9.0
10.0
CR313531
WebLogic Server ignored the deployment order attribute when specified in a startup class element in config.xml. Since the deployment order was ignored, WebLogic Server ran startup classes based on the order of the startup class name and the load before app deployments property value.
Workaround or Solution:
If deployment order is specified, it will no longer be ignored and will be used to determine execution order for startup classes.
9.0
10.0
CR319718
In a multi-clustering ALSB domain, when you change a Business Service configuration (for example, Web Service URL modification), the managed servers which are not part of the ALSB cluster fall into the SUSPENDED state.
This problem has been resolved.
10.0
10.0 MP1
CR360777
The retirement operation which was executed when an Administration Server was restarted, used to fail with UnreachableHostException. As a result of this failure, both (old and new) versioned applications became active.
This problem has been resolved.
10.0
10.0 MP2

 

EJBs

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR232765
The primary key in an Oracle table is a CHAR but the query field in the SQL table is a VARCHAR2.
Change database schema from CHAR to VARCHAR2. Using CHAR as a primary key is not recommended for the Oracle database.
9.2
Will not fix
CR233275
A Messaging Proxy Service still receives and routes messages after it has been deleted if the user sends the messages to it.
Workaround:
Do not use the JMS destination to which the deleted Messaging Proxy Service was listening.
9.0
10.0
CR262032
In Ejbgen, there is no counterpart for the select-first-sequence-key-before-update tag that is found in weblogic-cmp-rdbms-jar.xml.
Solution:
The Ejbgen annotation @AutomaticKeyGeneration now includes a selectFirstSequenceKeyBeforeUpdate attribute (whose type is Constants.Bool). This attribute can be used to specify the behavior of automatic primary key generation.
If selectFirstSequenceKeyBeforeUpdate is set to Constants.Bool.TRUE, when the EJB container needs to fetch the sequence value from a database, it generates the primary key from the current value + 1 in the sequence table, and updates the value in the table with the current value + the key-cache-size. By default, select-first-sequence-key-before-update is set to false.
9.1
10.0
CR295394
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.
10.0
 
CR295746
When accessing a Stateful Session Bean, method invocation must acquire a lock first. When concurrent access occurs, the lock acquisition will fail first so that a LockTimedOutException wrapped in an EJBException will be thrown, rather than a ConcurrentAccessException.
10.0
 
CR297054
Creating EJB 3.0 stateful session beans is much more expensive in terms of performance than creating equivalent EJB 2.1 stateful session beans.
Workaround:
Most of the performance difference can be regained by setting the system property weblogic.ejb30.enableproxypool=true. This system property is set to false by default. Note that it is not safe to turn on this flag if the bean has interceptors associated with it that contain state.
10.0
 
CR305173
Kodo components send log messages by default to the .out file of the server the bean is deployed to, rather to a log file.
Workaround:
Configure the component can be configured to log to a particular file.
10.0
 
CR305208
EJBs with generic information fail when all of the following conditions are met:
  1. The business interface doesn't extend java.rmi.Remote.
  2. The invocation of method is via remote proxy through RMI remote call, and there is no generated stub on client side. The local invocation within one JVM will succeed.
  3. The remote call is via t3 protocol, not iiop protocol.
  4. The method in the business interface has generic information; that is, type parameters or a generic type like List<String> as a parameter type.
Workaround or Solution:
Make sure you fulfill any of the following conditions:
  1. Write your business interface to extend java.rmi.Remote.
  2. Put the generated stub on the client side when the invocation of method is via remote proxy through a RMI remote call. The local invocation within one JVM will succeed as well.
  3. Make the remote call via the iiop protocol, not the t3 protocol.
  4. Either do not use generic information in the business interface method, or use only generic information declared on the class level of the business interface with the type variable parameterized with raw type. For example:
Interface RootI<T> {
public void hello(T t);
public <S extends Comparable> S testComp(T t, S s);
}

//Business interface
Interface StatelessI extends RootI<String>{
}
Though the business interface doesn't extend Remote, whether through remote call or local call, the invocation on StatelessI.hello(String) will work. But remote invocation on StatelessI.testComp() will fail when there is no generated stub on the client side.
10.0
 
CR306237
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 or Solution:
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.
10.0
 
CR316709
When using the Sun VM, dynamic class enhancement sometimes does not occur.
Workaround:
Run the Kodo enhancer on your persistent classes after compilation but before deployment. You can do this with the kodoc script bundled with WebLogic Server, by using an ant task, or by running java org.apache.openjpa.enhance.PCEnhancer, passing your persistent classes as arguments to the process.
10.0
 
CR314742
CR341595
When using EJB QL with PreparedQuery method, FinderException used to occur.
This problem has been resolved.
9.2
10.0 MP1
CR333333
In Windows platform, the appc compiler used to fail on EJB 3.0 JAR file when the size of the resultant EJB class file was more than 40KB.
This problem has been resolved.
10.0
10.0 MP1
CR349202
A runtime exception used to raise when stateless EJB resource was injected into an interceptor by using the annotation @EJB.
This problem has been resolved.
10.0
10.0 MP2
CR354384
CR363304
A runtime exception used to raise when multiple interceptors are configured in ejb-jar.xml deployment descriptor using <interceptor-order>.
This problem has been resolved.
10.0
10.0 MP2
CR360531
Unnecessary application recompilation used to happen during deployment and it slowed down the deployment.
This problem has been resolved.
10.0
10.0 MP2
CR363501
If javax.ejb.EJBAccessException was raised while using SLSB (EJB3.0), the Beans In Use Count value in the Monitoring tab was not set to 0.
This problem has been resolved.
10.0
10.0 MP2
CR366048
EnvironmentBuilder used to take only the value of 'mappedName' in @Resource annotation as the JNDI name.
This problem has been resolved. Now the value of 'name' in @Resource annotation is taken as the JNDI name when 'mappedName' is not specified.
10.0 MP1
10.0 MP2
CR369556
EJB3 stateless session bean method load balancing was not working for round-robin algorithm if ‘mappedName’ was specified in @Stateless annotation of the stateless session bean.
This problem has been resolved.
10.0 MP1
10.0 MP2

 

Examples

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR191354
Medical Records does not yet use deployment plans.
9.0 Beta
 
CR208965
The medrec.wls.config target in SAMPLES_HOME/server/medrec/setup/build.xml has a known issue with respect to security configuration.
9.0 Beta
Will not fix
CR287762
The Web Services Reliable Messaging example uses an incorrect WS-Policy file. In particular, the file uses an incorrect wsrm namespace and lists the assertions in an incorrect order.
To workaround this problem, update the example WS-Policy file (called ReliableHelloWorldPolicy.xml) to look like the default reliable messaging WS-Policy file included in WebLogic Server, described in Use of WS-Policy Files for Web Service Reliable Messaging Configuration. Pay particular attention to the namespaces and assertion order.
The example described in this note is located in WL_HOME/samples/server/examples/src/examples/webservices/reliable, where WL_HOME refers to the main WebLogic Server installations, such as /bea/weblogic92.
9.2
10.0
CR226622
The ../xml/stax example contains two files with the same root but different extension: 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 or Solution:
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.
9.0
Will not fix
CR276963
When you start the medrec or samples domains, you may see a warning message like the following:
<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 out of the console while starting a WebLogic Server sample application with an asynchronous Web Service deployed.
Workaround or Solution:
The warning is harmless and can be ignored.
9.2
 
CR317037
The documentation for the WebLogic Server samples assumes that the default WebLogic Server installation directory is weblogic100; instead, the actual default WebLogic Server installation directory is wlserver_10.0.
10.0
 

 

Installation

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR233609
The Beehive documentation on the install CD does not contain Web Service Management information, which may result in broken links.
Workaround or Solution:
Use the Beehive documentation that is on the install CD rather than the documentation on the Apache website.
9.0
10.0
CR307273
On installation, the installer may incorrectly report "Insufficient disk space". This error is the result of using a version of the UNIX df tool that is incompatible with POSIX.
Workaround or Solution:
Use a version of df that is compatible with POSIX.
9.2
 
CR346002
An unexpected EOF error occurs when downgrading from WebLogic Server 10.0 MP1 to WebLogic Server 10.0
Product Uninstaller in console mode returns a harmless EOF error and does not return a confirmation message on the successful completion of the downgrade.
Platform: Red Hat Linux
Workaround or Solution:
None
10.0 MP1
 
CR346976
Uninstallation of WebLogic Server 10.0 is not properly completed
After downgrading from WebLogic Server 10.0 MP1 to WebLogic Server 10.0, when you uninstall the 10.0 installation, some files in the BEA_HOME directory are not automatically removed.
Platform: All
Workaround or Solution:
Clean up the directory manually.
10.0 MP1
 
CR347082
Product upgrade from WebLogic Server 10.0 to WebLogic Server 10.0 MP1 using Smart Update fails
When Smart Update is used to upgrade WebLogic Server 10.0 to 10.0 MP1, the upgrade fails with a fatal error on a HPUX 64-bit machine.
Platform: HPUX 64
Workaround or Solution:
Use the WebLogic Platform package upgrade installer to upgrade from a WebLogic Server 10.0 installation to 10.0 MP1
10.0 MP1
 

 

Java EE

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR306909
WebLogic Server did not preserve the precedence when merging bean properties between library and application descriptors (when no key is defined for the bean). This merge results in an array of entries from both the library and application descriptors. However, the order of the entries was incorrect. Array entries from the library descriptor occurred before entries from the application descriptor; the library descriptor entries should have occurred after those from the application.
Workaround or Solution:
WebLogic Server now applies precedence when merging beans from the library descriptor with those from the application descriptor.
9.0
10.0
CR269767
weblogic.utils.io.ObjectStreamClass did not check the superclass if the readResolve and writeReplace methods were defined in it.
Solution:
The readResolve and writeReplace methods are now inherited properly.
9.1
10.0

 

JDBC

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR188442
The Oracle Thin JDBC driver has not been certified with JDK 5.0. In internal testing, BEA has noted test failures with the DECIMAL data type (TAR 4019650.995).
9.0 Beta
10.0
CR272583
There is a performance degradation in the WebLogic Type 4 JDBC Driver for Oracle getAsciiStream() method call caused by fixes and enhancements to character set support in the driver. In general, the updated driver outperforms the previous version of the driver.
Workaround or Solution:
Use the getCharacterStream() method instead of getAsciiStream().
9.1
 
CR276977
The 3.5 version of the BEA-branded driver from DataDirect has failed in long-running tests when JDBC connection pools have the ShrinkingEnabled attribute set to true.
Workaround or Solution:
For optimal JDBC pool performance and stability, BEA recommends that you set the ShrinkingEnabled attribute to false.
8.1
10.0
CR292068
The utils.Schema -s option has been removed. The -s option was for the obsolete WebLogic OCI driver, which did not accept the server name in the URL. All supported drivers now take all needed properties in the URL, so the -s option is no longer needed. It was removed because setting the server name in both the -s option and the URL caused problems.
Workaround:
Using the -s option will result in a warning saying that the -s option is no longer functional. If your connection fails, make sure all DBMS properties are in the URL.
10.0
NA

 

JMS

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR270257
Using the JMS WLMessageProducer forward() API on a newly created message causes a JMSClientException.
The JMS WLMessageProducer forward() API can only be used on unmodified received messages.
9.2
 
CR274706
Deployment descriptor validation fails when descriptor validation is enabled, and an EAR file contains only JMS modules.
Workaround or Solution:
Make sure that there is at least one J2EE specification-compliant module in the EAR.
9.2
 
CR278644
Reconnecting transactedSession.commit() or transactedSession.rollback()calls may throw exceptions more than once when reconnecting.
When a transacted session allows reconnect — that is, when a WLConnection.getReconnectPolicy() is not none — the first call to session.commit() or session.rollback() will throw an exception after the server WLConnection has reconnected after a failure. This is expected behavior. Unfortunately, the second call to commit()or rollback() may also throw an exception.
Afterwards the reconnected transacted session will work normally.
9.2
 
CR278960
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 the WebLogic Server will not boot.
Workaround or solution:
Create WebLogic Servers without multi-byte characters in the path name and use that path name rather than the default store. Do not use multi-byte characters in the Weblogic Server name.
9.2
 
CR277493
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 or solution:
When using multiple JMS SAF client producers, try introducing a small delay between the creation of each new client.
9.2
 
CR280150
When the WLConnection.getReconnectPolicy() method is set to all, JMS CLIENT_ACKNOWLEDGE sessions do not always throw a LostServerException when session.acknowledge() is called and there are unacknowledged, non-persistent topic messages.
9.2
 
CR280041
When the WLConnection.getReconnectPolicy() method is set to all, JMS CLIENT_ACKNOWLEDGE sessions may sometimes throw an extra LostServerException when session.acknowledge() is called. This occurs after the JMS session has been reconnected to the server.
9.2
 
CR280064
When deploying a JMS module, the WebLogic Server Administration Console was not transparently creating the necessary subdeployment targets in the Install assistant with some configurations of JMS Servers for the selected targets. In these cases, some subdeployment targets were not included in the deployment and the console did not provide error messages or the opportunity for an administrator to correct this targeting.
Solution:
The console now correctly senses when the automatic, transparent targeting of subdeployments was not complete and sufficient for a JMS module. In those cases, the console now displays error messages to the Administrator, and allows them to chose to explicitly deploy each module and subdeployment manually to specific targets.
9.2
10.0
CR272776
When using the WebLogic Scripting Tool (WLST) offline to generate a JMS module descriptor, for certain JMS Connection Factory Boolean parameters you cannot set the value to false.
The following JMS Connection Factory attributes do not have their default value specified in the corresponding JMS Module descriptor schema definition.
<allow-close-in-onMessage>
<xa-connection-factory-enabled>
<flow-control-enabled>
<load-balancing-enabled>
<server-affinity-enabled>
<attach-jmsx-user-id>
Therefore, the Java default of false for these Booleans is used by WLST offline. So when they are manually set to false, WLST does not persist the values to the JMS module descriptor assuming that setting is redundant.
Workaround or solution:
After the JMS module descriptor is created using WLST offline, these Boolean attribute values can be edited either manually or modified using the Administration Console.
9.2
10.0
CR294494
In cases where two servers using JMS distributed topics in a cluster started simultaneously, each creates a new RJVM connection to the other server because it didn't detect an existing connection. WebLogic Server would detect the duplicate connections and close them. This caused JMS hangs.
Solution:
WebLogic Server now allows duplicate RJVM connections in this case when servers are started at the same instant and the RJVM between the two servers has transmitted and received more than just bootstrap messages.
9.1
10.0
CR298712
When using DB2 with WebLogic JMS, the JMS backing store table failed to create itself. This problem was caused by the fact that DB2 allows its connections to have a different default schema than that of the logged-in user
Solution:
This problem has been corrected.
9.2
10.0
CR306437
Expired messages were not getting redirected to error destinations during server startup.
Solution:
This problem has been corrected.
9.2
10.0
CR310002
The JMS Thin Client does not, and has never, supported automatic reconnect functionality. This functionality has been explicitly disabled in this release.
9.0
10.0
CR315044
The JMS 1.1 specification states in section 3.5, table 3-3, that the JMSXDeliveryCount property is set by the "provider on receive", but WebLogic JMS has included this property in the list of property names returned by the JMS API method javax.jms.Message.getPropertyNames().
Workaround or Solution:
WebLogic JMS now only returns the JMSXDeliveryCount property name from the JMS API method javax.jms.Message.getPropertyNames() when both the message was delivered via receivers, queue browsers, or the administrative API, and the application hasn't called javax.jms.Message.clearProperties().
Newly created messages, or delivered messages on which javax.jms.Message.clearProperties() has been called, no longer include the JMSXDeliveryCount property name in the list of properties returned by javax.jms.Message.getPropertyNames(). The behavior of standard JMS API message methods for obtaining the JMSXDeliveryCount property value remain unchanged: these methods continue to return a JMSXDeliveryCount value of zero or greater as appropriate (whether or not JMSXDeliveryCount is included in the property name list).
9.2
10.0
CR314778
A failure used to occur while performing Paging I/O if many threads were waiting for Paging I/O to complete and these threads were blocked.
This problem has been resolved.
9.1
10.0 MP1
CR314779
When messages were sent to a destination, which was configured with a JMS quota and if that quota was met then messages were inadvertently getting added to the list of Pageable messages. This used to result in a memory leakage because the messages were retained on the list of Pageable messages until the server was restarted.
This problem has been resolved.
9.1
10.0 MP1
CR314780
Any failure detected by a distributed topic used to stop the forwarder and would not resume until the JMSServer was restarted.
This problem has been resolved.
9.1
10.0 MP1
CR332983
CR326377
It was not possible to deploy an MDB while connecting to a foreign JMS provider through WLS foreign server resources configured in a JMS module.
This problem has been resolved.
10.0
10.0 MP1
CR353518
A multi-threaded JMS client using different connection protocols on different threads was failing with DispatcherException.
This problem has been resolved.
10.0 MP1
10.0 MP2
CR356418
JMS client occasionally used to hang on a late connection close if the auto-reconnect logic has already been activated for the connection.
This problem has been resolved.
10.0 MP1
10.0 MP2
CR364200
Message bridge was not working with SwiftMQ when message selector was not configured.
This problem has been resolved.
10.0
10.0 MP2

 

JNDI

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR264754
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 or Solution:
The application can refresh the consumer either in the exception handler or through onException.
9.2
Will not fix

 

JSP and Servlet

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR267128
The page-check-seconds parameter did not work in production mode when its value was specified in an application’s weblogic.xml deployment descriptor file. This value tells WebLogic Server how often it needs to check and recompile or reload changed JSP pages. However, modified JSP files were recompiled as appropriate when the server was started in development mode, but were not recompiled when the server was started