![]() ![]() ![]() ![]() ![]() ![]() ![]() |
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.
After a page flow completes in the Administration Console, it forwards to a different page, typically a table.
|
|||
Search the Administration Console Online Help that is published at
http://download.oracle.com/docs/cd/E13222_01/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
|
|||
|
|||
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.
|
|||
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.
|
|||
Some of the links in the “Understanding JMS Resource Configuration” online help topic point to http://docs-stage/wls instead of
http://download.oracle.com/docs/cd/E13222_01/wls. This problem is causing a 404 error. To access the correct information, substitute http://download.oracle.com/docs/cd/E13222_01/wls for docs-stage in your web browser.
|
|||
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
../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.
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.
|
|||
<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>
|
|||
An unexpected EOF error occurs when downgrading from WebLogic Server 10.0 MP1 to WebLogic Server 10.0
|
|||
If non-dynamic changes are made to a domain configuration, then an application is added (e.g.,
MyApp ), and then the non-dynamic changes are activated, a Management Exception is thrown: [Deployer:149001] No application named 'MyApp' exists for operation start .
The error message occurs because when an edit is made to a non-dynamic configuration setting, no edits to dynamic configuration settings will take effect until after a server restart. This is to assure that a batch of updates having a combination of dynamic and non-dynamic attribute edits will not be partially activated. Since the application has not been added to the configuration, the application cannot be activated and the activate fails with the Management Exception.
For more information on dynamic versus non-dynamic changes, see
Managing Configuration Changes in Understanding Domain Configuration.
|
|||
Suspending or gracefully shutting down one managed server in a cluster could cause other servers in the cluster to hang. This problem was caused when ReplicationManager did not mark the suspended or gracefully shutting down server in the cluster as dead and would continuously try to replicate the sessions to that server. This would block all the execute threads in the ReplicationManager and the running server would hang.
|
|||
WebLogic Server fails with an
ImageSourceCreationException when capturing a diagnostic image on a managed server. The error is as follows:
<BEA-320127> <An error occurred while generating Image Source configuration as part of the diagnostic image zip file:
|
|||
WebLogic Server would require restart on changes to attributes that were actually dynamic. WLS uses annotations to determine if an attribute is dynamic. This affected the ServerStart, SNMPAgent, SNMPAttributeChange, SNMPCounterMonitor, SNMPGaugeMonitor, SNMPLogFilter, SNMPProxy, SNMPStringMonitor, SNMPTrapDestination, and SNMPTrapSource MBeans.
|
|||
An invocation on an MBean in the Domain Runtime MBeanserver failed with a
NoAccessRuntime exception as follows:
weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=[deployer, Deployers], on ResourceType: ServerRuntime Action: execute, Target: lookupApplicationRuntime
|
|||
WebLogic Server did not trim spaces in MDF legal values arguments. For example, the custom security provider MDF file had legal values defined as:
|
|||
JRockitRuntimeMBean exposes functionality from the JRockit MAPI ProfilingSystem API, which is being deprecated. Consequently, the following JRockitRuntimeMBean methods are deprecated:
public boolean isExceptionCountEnabled(Class throwableClass);
public long getMethodTiming(Method method); public long getConstructorTiming(Constructor constructor); public boolean isMethodInvocationCountEnabled(Method method); public boolean isConstructorInvocationCountEnabled(Constructor constructor); public boolean isMethodTimingEnabled(Method method); public boolean isConstructorTimingEnabled(Constructor constructor); public long getExceptionCount(Class throwableClass); public long getMethodInvocationCount(Method method); public long getConstructorInvocationCount(Constructor constructor); |
|||
Memory leak used to occur on the server side when using DeploymentManager from the client. The IIOPServerImpl$ConnectorLister object created during the call DeploymentManagerFactory.getDeploymentManager () was not getting removed on calling the DeploymentManager’s release() method.These objects used to remain until the client process stopped.
|
|||
The 2.0.2 version of the Spring Framework is certified for this release of WebLogic Server.
Prior to WebLogic Server 9.2, the viewj and viewj32 compilers did not handle any view definition file with a missing NULL value; instead they issued a warning message and stop processing. However, in WebLogic Server 9.2 this behavior changed. The compilers generate a Java file for the view, but the view class will not have field data and access methods for them. The result is that the viewj and viewj32 compilers generate an incorrect Java view class.
|
WebLogic Server now packages the standard Ant distribution in
WL_Home/modules/org.apache.ant_1.6.5 . If you use the standard WebLogic Server environment scripts created as a part of the installation, you will not need to make any changes to continue using Ant. If instead you directly referencing the Ant jars from the WebLogic Server installation, you will need to modify the classpath to point to the new location of the Ant distribution.
The
lib/ant-all.jar in that directory has a manifest classpath that refers to all of the other JARs in the lib directory. You should use ant-all.jar rather than ant.jar if you want to maintain the previous behavior, where the manifest classpath of ant.jar was modified to include all of the JARs in the lib directory.
|
|||
The manifest classpath for
weblogic.jar no longer contains ant-contrib.jar . As a result, if you use ant-contrib tasks and get an error message like "Could not load definitions from resource net/sf/antcontrib/antlib.xml. It could not be found ", this means that ant-contrib.jar is not on the classpath. If you use WebLogic Server’s setWLSEnv scripts, ant-contrib.jar is added to the classpath; however if you are using your own scripts that previously put weblogic.jar on the classpath, you need to update your scripts to put ant-contrib.jar on the classpath.
|
|||
This occurs because the resulting
wlfullclient.jar includes Ant classes that have a version number that is inconsistent with the Ant version you have in your classpath.
|
|||
![]() ![]() ![]() |