Change Request Number
|
Description
|
CR102753
|
The Network Channel Configuration page on the WebLogic Server Administration Console did not have a link to go back to the Channel lists page.
This problem has been resolved. You can now access the Network Channel Configuration page by clicking on the link in the bread-crumb trail.
|
CR106558
|
The WebLogic Server Administration Console displayed Type values only after the DefaultIdentityAsserter MBean was created.
The problem has been resolved. The WebLogic Server Administration Console now displays the Type values at the time the DefaultIdentityAsserter MBean is being created. In addition, the Available and Chosen columns have been widened to improve usability.
|
CR109929
|
The bread-crumb trail providing information about the resource to which a scoped role is associated is not displayed in the Title tag. Also, to view defined roles, users and groups after creating or editing them, you have to right-click the node in the nav-applet. This information should be made available through the bread-crumb trail.
This problem has been resolved. The WebLogic Server Administration Console now displays the association between a scoped role and a resource in the bread-crumb trail. In addition, clicking on the appropriate link in the bread-crumb trail now provides information about roles, users and groups.
|
CR111253
|
WebLogic Server did not initialize the Console Extension if the user who logs-in for the first time belonged to the "Operator" group. Subsequent logins as "Administrator" also did not initialize the extension. The extension is initialized only when WebLogic Server was rebooted and the "Administrator" logs on at first instance itself.
This problem has been resolved. The console extension is now initialized for all groups with appropriate permissions.
|
CR122389
|
WebLogic Server ignored case sensitivity with respect to names of a node. As a result, it listed a node only once in the JNDI tree even if there were multiple nodes that had the same name, but different case.
This problem has been resolved.
|
CR130398
|
Redeploying one application caused another application to be deleted.
A slow refresh rate gave the user the impression that the click to delete the application was not recorded. When the user clicked Delete again, the next application was deleted. As a result, making the user believe that deploying one application caused another to be deleted.
This problem has been resolved.
|
CR133506
|
Policies inherited from the parent JNDI node that were defined for the lookup, modify and list JNDI methods were displayed incorrectly by the WebLogic Server Administration Console for JNDI sub-nodes.
This problem has been resolved. Policies inherited from the parent JNDI node that are defined for the lookup, modify and list JNDI methods are now displayed as inherited policies for the lookup, modify and list methods respectively, in the JNDI sub-nodes.
|
CR209803
|
Console Extension pages did not require user login and password even when the user session had expired.
This problem has been resolved.
|
CR212333
|
In the Administration Console, users belonging to the Monitors, Operators, or Deployers group could view (but not modify) security information using the Realms link in the right navigation pane, but the security node was not available in the left navigation pane.
This problem has been resolved.
|
CR225707
|
Users belonging to the "Monitor" group could not view the Pools List of JDBCMultiPool.
This problem has been resolved.
|
CR233559, CR256737
|
When the default load order was modified, the deployment path changed from absolute to relative (that is, the leading "/"before the deployment path was removed) and this caused the deployment to fail on restart. This problem occurred only when the path attribute value had more than 50 characters.
This problem has been resolved.
|
CR236810
|
Refer to the security advisory information available at:
http://dev2dev.bea.com/pub/advisory/196
|
CR238260
|
Refer to the security advisory information available at:
http://dev2dev.bea.com/pub/advisory/190
|
CR238260
|
Refer to the security advisory information available at:
http://dev2dev.bea.com/pub/advisory/191
|
CR239145
|
When the Auto Deploy tab was clicked to assign the destination queue to the distributed destination, the JMS server list displayed in the target selection window was not properly formatted.
This problem has been resolved.
|
CR239403, CR265216
|
Due to insufficient permissions, users assigned to the Monitor role could not view the Deploy and Test page from the Administration Console.
This problem has been resolved.
|
CR241785
|
Administration Console did not prevent the setting of null values for MBean Attributes with @legalNull annotation.
This problem has now been resolved.
|
CR241816
|
From the Administration Console, switching between the tabs in the application page during application deployment was slow. In addition, after successful deployment, rendering the Deploy tab was slow.
This problem has been resolved.
|
CR241825
|
In the Administration Console, while configuring a custom security provider, the existing list of attribute values was not properly displayed in the drop-down list in this page.
This problem has been resolved.
|
CR243415
|
The Administration Console Login page was accessible through the administration port even after the domain-wide administration port was configured in the Administration Console.
This problem has now been resolved.
|
CR243427
|
Calls to assertIdentity() could only be made when the user belonged to the "Admin" role.
Now, the security policy to call the assertIdentity method can be defined through the Administration Console.
|
CR246438
|
When WebLogic Server was run as a Windows Service, applications located in remote mapped drives could not been deployed from the Console.
The set new Location option has been added in the Locate Application or Component to configure page to enable you to deploy applications from a mapped network drive on Windows, using the UNC path.
|
CR246599
|
Session monitoring of archived Web applications was disabled on Administration Console even when session monitoring was enabled in weblogic.xml .
Now, Administration Console displays the statistics of the currently active sessions of Web applications for which session monitoring has been enabled in weblogic.xml .
|
CR247206
|
Administration Console displayed the users of only the first authentication provider in a list of multiple configured authentication providers.
Now, Administration Console displays the users of all configured authentication providers.
|
CR248303
|
A cloned connection pool was deployed even when the connection parameter was wrong.
Now, the cloned connection pool is not deployed and appropriate error messages are shown in the Target and Deploy screens.
|
CR251390
|
On Compatibility Security domain, javax.management.ServiceNotFoundException occurred when resources like Web Application, EJB, JDBCConnectionPool, and so on were deleted from the Administration Console.
This problem has been resolved.
|
CR252286
|
When an EJB was deployed to a domain that had a Managed Server running on a remote machine, the EJB test on the Administration Console incorrectly displayed a failure message when the test was successful.
This problem has been resolved.
|
CR255268
|
The AuthCookieEnabled attribute associated with a Web Server MBean can now be set via the Administration Console.
|
CR256101
|
When users clicked the Embedded LDAP tab, a dialog that prompts them to save changes was displayed even when no changes were made.
This problem has been resolved.
|
CR264010
|
The Administration Console used to hang when a large application that contained many modules was deployed.
This problem has been resolved.
|
CR264965
|
Due to the value of MaxPageSize set in the LDAP Server configuration, only an incomplete list of users of all configured authentication providers was displayed on Administration Console.
This problem has been resolved.
|
CR267540
|
An application was not properly deployed when the Target Each Module button was used to deploy the EAR file that contained one or more Web modules.
This problem has been resolved.
|
CR269934
|
NullPointerException occurred when an EJB with an invalid deployment descriptor was deleted from Administration Console.
This problem has been resolved.
|
CR270210
|
Servlet session replication over SSL could not be disabled from Administration Console.
You can now disable secured replication from the Cluster —> Configuration —> General tab page.
|