Change Request Number
|
Description
|
CR106432
|
To avoid incorrect configuration, if the config.xml file has multiple entries with the same name for the same MBean type, WebLogic Server no longer boots up and the parser displays an appropriate error message.
|
CR107552
|
WebLogic Server now throws a MalformedObjectNameException if ObjectNames specified on the command line are not correctly separated by the designated delimiter.
For example, the following ObjectName contains the illegal delimiter, | , and therefore, would result in a MalformedObjectNameException :
SET -mbean mydomain:Name=sqlpool,Type=JDBCConnectionPool -property Targets mydomain:Name=OtherServer,Type=Server|mydomain:Name=myserver,Type=Server
|
CR108485
|
The new implementation now strictly enforces restrictions on attribute values. As a result, it is no longer possible to set a COMMO MBean attribute to a value that is lower than its minimum value and higher than the specified maximum.
If you set invalid values for attributes on any of the security providers, these values will now fail.
|
CR108714
|
Wlconfig no longer fails when queries return multiple object names and the return value is assigned to a property.
In addition, WebLogic Server now throws an InvalidWebLogicObjectNameException if the MBean parameter passed in resolves to multiple MBeans.
|
CR109300
|
The wl.Admin tool now accounts for the CommoMBeans and properly converts them to displayable Strings.
|
CR109386
|
weblogic.Admin VALIDATECLUSTERCONFIG no longer fails in cases where the cluster has no cluster address (default) or the server has no listen address (default).
|
CR109680
|
weblogic.Admin validateClusterConfig was output an error message even when the cluster was correctly configured.
Now, validateClusterConfig does not throw an error if the cluster name is an empty string for the server.
|
CR109743
|
When a shutdown is issued on a server through JMX, WebLogic Server no longer throws the following exception:
weblogic.rjvm.PeerGoneException: ; nested exception is: java.io.EOFException
As a result, it is no longer necessary to capture and ignore RemoteRuntimeException s when shutting down the server.
|
CR110861
|
You can no longer use weblogic as the domain name.
WebLogic Server now throws a clear configuration exception rather than a NullPointerException under the following circumstances:
|
CR110865
|
Now, WebLogic Server throws a ConfigurationException when two or more Configuration MBeans have the same name.
|
CR120270
|
The conversion utility now treats JoltConnectionPool as an MBean rather than as a startup class so that JoltConnectionPool is now converted properly.
|
CR120684
|
Now, the weblogic.Admin validateclusterconfig command can be executed without a username, password, or server URL.
|
CR122793
|
Because deprecated APIs are dependent on the Administration Server, it was necessary that the Administration Server be up to ensure a smooth shutdown of the Managed Server.
Administration Server no longer needs to be up to perform a shutdown.
|
CR124003
|
It is now possible to set the HTTP Message Timeout to "-1" in the Administration Console.
|
CR124169
|
WebLogic Server no longer throws an Assertion error when shutting down or undeploying the WebLogic Messaging Bridge using JMX.
|
CR125202
|
The chmod command is no longer used on Windows. Now, wlserver generateconfig no longer fails on Windows if the chmod command is not used.
|
CR129262
|
ServerDebugMBean interface debug attributes were not dynamic. Therefore, when the value was set on the Admin MBean, it was not propagated to the Config MBean on the Managed Server.
Now, ServerDebugMBean attributes can be dynamically be set and un-set.
|
CR132602
|
The weblogic.Admin utility now allows access over the IIOP protocol when accessed through -adminurl.
|
CR133869
|
Now, ServerMBean.getClusterRuntime returns true for a server that is part of a cluster.
|
CR137128
|
Because increasing the array size and adding elements into an array are two different steps, the Array list was not synchronized. As a result, an ArrayIndexOutOfBoundsException was thrown when elements were added to Array list in two different threads.
This exception is no longer thrown.
|
CR175671
|
You no longer get a NullPointerException when you use the clz.getPackage() method.
|
CR175945
|
Because the running-managed-server.xml file was being used to monitor the status of a Managed Server, the status was being displayed inconsistently and often incorrectly when viewed either from the Administration Console or from the command line.
Now, when the Administration Server has discovery mode enabled, for each Managed Server entry in the running-managed-server.xml file, WebLogic Server attempts to determine if that server is running regardless of its status in the running-managed-server.xml file. As a result, Managed Servers are now being correctly discovered.
|
CR177737
|
The Administration Server failed to start if two JMS queues using the same JNDI name were in a cluster and if "Replicate JNDI Name In Cluster" was enabled.
Now, JNDI name validation is done against tree destinations of all the concerned servers so that any conflict is detected before actual server startup.
As a result, it is not possible to configure a destination that can restrain the server from starting, and an attempt at such configuration causes an error to be thrown.
|
CR189644
|
If logs had been rotated, the output of View Server Log in the Administration Console was not legible, and the order of the logs displayed was not correct because of the order in which file names were stored. There was also an inconsistency in the logs seen in Reverse chronological order and Forward chronological order. The output of View Server Log displayed the messages of the current log file as well as rotated log files, instead of just the current log file, for both reverse and forward orders.
Now, the Console shows log messages only from the current log file and the contents shown in both forward and reverse chronological orders are the same.
|
CR189763
|
When a staged application was deployed to a server running in MSI mode, the server incorrectly created a staging directory.
Now, when a staged application is deployed on a server running in MSI mode, WebLogic Server determines whether to use an existing staging directory or create a new one. As a result, there is no InvalidAttributeValueException when deploying to a server running in MSI mode where the server process does not have write access to the directory structure.
|
CR191317
|
If the Managed Server listen address was null and the Managed Server port was the same as the Administration Server port, WebLogic Server threw an error while starting the Managed Server if the Managed Server was started on a remote machine.
Now, the Managed Server can be started on a machine other than the Administration Server machine in case its port is the same as the Administration Server port, even if its listen address is specified as null.
|
CR199214
CR193887
CR211395
|
Whenever the log was rotated, the next log rotation was calculated using the file time span and the rotation time set in the LogMBean which was always returning the time between the rotation time and 24:00. As a result, the logs were not getting rotated between 24:00 and the rotation time.
Now, the next log rotation time is calculated by adding the file span to the previously set next log rotation time. After the server has been started, the next log rotation time is dependent only on the file time span.
|
CR201967
|
MBeanHomeImpl.getActiveDomain() returned the Administration DomainMBean, which caused problems when the Administration server was down.
MBeanHomeImpl.getActiveDomain() now returns Admin.getInstance().getActiveDomain(), which is the local Configuration DomainMBean and does not rely on the Administration Server's availability.
|
CR202036
|
On a Windows platform, the server log in the Administration Console now displays the last 2 characters of the line.
|
CR202059
|
WebLogic Server incorrectly persisted certain attributes of type java.util.Properties for COMMO MBeans. Upon retrieval, the values were incorrect. This issue has now been resolved by proper serialization and de-serialization.
|
CR203963
|
When trying to validate whether a user is locked out by using either the ServerSecurityRuntimeMBean or the UserLockManagerMBean on a Managed Server, the isLockedOut method and the getUserLockoutTotalCount method are now returning the correct results on the Managed Server.
|
CR205146 CR209670
|
When a Web Application is undeployed, the memory used in Permanent Generation is now freed upon a full garbage collection. As a result, the server no longer runs out of memory when the Web Application is repeatedly undeployed and redeployed.
|
CR208029
|
WebLogic Server now throws an exception during bootup if both the old and new style attributes co-exist in the config.xml file.
For example:
<JoltConnectionPool ApplicationPasswordEncrypted="{3DES}pPCVe/Lp17dc5WG18Ot3wg=="Name="MyJoltConnectionPool" Targets="cgServer" UserPassword="userpassword"/>
is legal but
<JoltConnectionPool ApplicationPassword="appPassword"ApplicationPasswordEncrypted="{3DES}pPCVe/Lp17dc5WG18Ot3wg=="Name="MyJoltConnectionPool" Targets="cgServer" UserPassword="userpassword"/>
is illegal because it contains both ApplicationPassword(old) and ApplicationPasswordEncypted(new) attributes specified that really represent the same entity.
|
CR209218
|
The CounterMonitor.stop() method is no longer synchronized and there is no more deadlock.
|
CR209592
|
Security MBeans returned by the JMX query are no longer filtered out by the MBeanServer; they are returned to the client.
|
CR209771
|
The TaskRuntimeMBean.printLog(pw) function got a NotSerializableException when the method was invoked on a T3 client.
The method was excluded from the public documentation, and the TaskRuntimeMBean.printLog(pw) method is no longer documented or available for public use.
|
CR210425
|
Now, the <wlserver> tag throws an exception when you try to stop the server without providing the username and password.
|
CR211069
CR218084
|
The Administration Server now makes adjustments to the encyrpted attribute values when the Managed Server is on WebLogic Server 8.1 Service Pack 3 or earlier.
As a result, when you upgrade an Administration Server to WebLogic Server 8.1 Service Pack 4 or later, you can start a Managed Server that is running on WebLogic Server Service Pack 3 or earlier.
|
CR212225
|
During a JMS stress test, WebLogic Server no longer throws the following exception:
NotSerializableException: weblogic.t3.srvr.T3Srvr
|
CR213168 CR214825
|
Certain private methods that accessed shared data have been synchronized to prevent inconsistent states during server bootup.
As a result, ModelMBeanTypeMBean.operationCategory() no longer throws a NullPointerException when starting multiple Managed Servers at the same time.
|
CR214170 CR208509 CR221784
|
The Console application javascript code was rewritten to work on all known versions of all browsers.
|
CR214241
|
When the weblogic.Admin tool BATCHUPDATE option was used, quotes were stripped from the file before processing.
The logic on stripping quotes from batch files was changed to allow empty quotes to be passed. As a result, wl.admin now works the same in batch mode as in interactive mode.
|
CR214288
CR236570
|
Application deployment on a large cluster of nodes threw a NullPointerException on the Administration Server, of a synchronization problem in updating the configuration MBean list.
This problem has now been fixed.
|
CR214301
CR230260
|
During the validation check of setting the ErrorDestination to a valid JMSQueue , the JMSLegalHelper code failed with an NullPointerException because the parent attribute had not been set.
Now, if the parent attribute is not set, WebLogic Server tries to obtain the parent from the WeblogicObjectName for comparison and legal checks.
As a result, WebLogic Server no longer throws a NullPointerException and still does the validation check.
|
CR215114
|
The JDBC pool commands usage strings have been updated to be consistent with code.
RESET, ENABLE, DISABLE, EXISTS, TEST, REMOVE, SUSPEND, SHUTDOWN, RESUME, and DELETE use -poolName <poolName> to obtain the JDBC connection pool name for the specified operation. CREATE and DESTROY pool commands obtain the poolName through a positional parameter to the command line.
|
CR216453
|
The Monitor role could not see the deployment status on the Console because the required access permissions were not given.
Now, monitor role can access the deployment status page.
|
CR216513
|
When authorization errors occur, the Administration Console now shows a complete error message that explains the reason for the remote failure.
|
CR219192
|
When setting the ErrorDestination of the JMSQueue , a NullPointerException no longer occurs in the Administration Server.
|
CR220015
|
The weblogic.Admin utility returned an exit code of 0 when the START and RESUME commands failed.
This problem has been fixed and now weblogic.Admin returns 1 as the exit code.
|
CR221970
|
WebLogic Server logger formats the log record before publishing it. When formatting bad records, any exception that occurred was not handled, which resulted in the log record not being published. After a certain number of such bad records, the logger deleted the handler, no records were published, and logging stopped.
Now, WebLogic Server handles all exceptions during formatting and publishes the records. As a result, logging continues despite bad log records.
|
CR223944
|
The weblogic.Admin BATCHUPDATE command now returns accurate results when executed from the command prompt or as a batch file.
|
CR227566
|
When generating custom providers, WebLogic Server generates <MBeanInterfaceName>MBI.java files that are used to generate the MBeanInfo files for the compiled MBeans.
WebLogic Server now puts these source files in the same package as the MBean interface for which this class was generated. WebLogic Server no longer bundles these *MBI.class files in the provider's JAR file. As a result, the JAR files are much lighter.
|
CR228265
|
A timestamp formatted log file is now displayed in the Administration Console.
|
CR232488
|
The WebLogic Server command line tool displayed junk attribute values when it encountered encrypted data.
This problem has been resolved.
|