|
|
Description and Workaround or Solution
|
|
|
Depending on the complexity of the user’s inventory, the Interactive topology view (Tree) diagram in the Inventory pane may overlap nodes, making them difficult to read.
Collapse nodes to reduce the complexity of the diagram and minimize overlap.
|
|
|
When viewing the interactive view of the Inventory pane, in some rare circumstances the interactive topology view may appear twice, as if two copies of the tree are rooted at the same point.
|
|
|
When viewing the interactive view of the Inventory pane, if a JVM or service life cycle change occurs (for example, the service gets undeployed) the topology diagram does not dynamically update to reflect the life cycle change.
|
|
|
If you attempt to log in to the WLOC Administration Console using a user account that is not assigned to any roles and subsequently receive a 403 error, you must open a new browser before attempting to log in again.
|
|
|
When an Agent is restarted, the WLOC Administration Console may show the state of JVMs managed by that Agent as unreachable even after the Agent is fully running. In addition, when the Controller is restarted, the JVMs that it manages may not show up in the Inventory pane.
Refresh the browser window.
|
|
|
You may experience problems viewing configuration information in the following situations:
- When a JVM is added to the Inventory pane initially, the full association of the JVM instance to its service and process group may not be known. Consequently, when you click the name of the JVM instance, the complete details of the JVM instance may not display on the JVM instance page.
Workaround or solution:
Refresh the browser page.
- If one or more spaces are used in the service, process group, or JVM instance name, the complete details of the JVM instance may not display on the JVM instance page.
Workaround or solution:
Delete and recreate the service, process group, or JVM instance without using spaces in the name.
|
|
|
If you manually start a JVM instance using the Run Action method, the JVM instance may not appear dynamically or its performance chart may not appear correctly in the WLOC Administration Console.
|
|
|
While viewing the Inventory pane in a Mozilla Firefox Web browser, in some rare circumstances a console notification may not take effect immediately.
|
|
|
WLOC does not support nested groups. If you use nested groups, you may encounter the following issues:
- Users that are members of a nested group do not get the permissions that they should.
- Deleting a group that is a member of a second group does not remove the group name from the second group.
BEA recommends that you do not create nested groups in WLOC 1.0.
|
|
|
When viewing a chart with a large Y-axis values, the values may overlap with the Y-axis label.
Position the mouse pointer over a data point to view the current value. You can hide the axis labels using the chart preferences, if necessary.
|
|
|
While viewing the Inventory pane, in certain circumstances a node labeled loc may appear. This node represents internal state that the WLOC Administration Console uses to contain inventory nodes and can be ignored.
|
|
|
While viewing the Inventory pane, you may experience a problem with the Agents and resource pools if the lists are expanded and there are life cycle changes to the Agents or resource pools. In this case, you may be unable to expand the nodes.
Refresh the browser window.
|
|
|
When defining a process group, if you are importing from another service, running WebLogic domain, or WebLogic domain configuration, if you select the following flags:
- Allow me to choose instances to import
- Show me a summary of uncollectable metadata from config.xml
and then click the Back button, you are returned to the Service Properties page (the first page of the service assistant).
|
|
|
When defining a new process group, after you select the Process Requirements option and click Next, if you go back to the initial screen using the Back button, the Process Requirements value returns to the default value (Start from Scratch).
Reselect the process requirement option and proceed.
|
|
|
When viewing the Inventory pane, entries do not appear in alphabetical order.
|
|
|
When changing the Agent state, the page may refresh before the state change has been processed.
Refresh the browser window if you do not see the updated state.
|
|
|
When viewing the interactive view of the Inventory pane, when a service life cycle change occurs, for example, a service gets added or deleted, the change may not be reflected in the currently viewed diagram.
|
|
|
Deleting the JVM file copy operations from the File Management page using the WLOC Administration Console has no effect. The entries are not removed.
Delete the file copy operations directly from the metadata-config.xml file located in the config directory of the Controller installation.
|
|
|
In some high availability circumstances, the Inventory pane and service table may not reflect the correct number of processes.
Refresh the browser window.
|
|
|
In some high availability circumstances, the performance graphs for a service may not reflect a problem condition. For example, when the chart is plotting a negative value (-1). Under normal circumstances, the message Problem Detected would be displayed next to the data series in the chart legend.
Check the Tasks and Event viewer, Events tab, or log files for potential error conditions.
|
|
|
The File Management tab for managing the file copies of an LVM-based constraint only appears when the constraint is bound at the process group level. If you bind the rule at the service level you will not be able to directly manage those file copy operations through the WLOC Administration Console.
Re-bind the rule at the process group level.
|
|
|
When creating a file copy operation for an ISO constraint, the Copy Type drop-down list includes the At Shutdown option. This option is not valid for an ISO constraint file copy operation.
Do not select this option for an ISO constraint file copy operation.
|
|
|
In some cases, when a service is undeployed, the tabular performance data on the Resource Pool page may show negative values in the Used column. This has been observed primarily in ESX Agent-based resource pools, but may occur with Plain Agent-based resource pools, as well.
|
|
|
If you do not have the appropriate permissions to view the Agent configuration (for example, if your user account is assigned to the ServiceAdmin role only), you will not be able to view the configured software when you click the Available Software tab for the associated resource pool. The Available Software table will appear empty even if there is software configured for the Agent.
|
|
|
When creating a new constraint, after you select a type and click Next, if you go back to the initial screen using the Back button, the Type value returns to the default value.
Reselect the type and proceed.
|
|
|
When importing service metadata from a running WebLogic domain, the host parameter may include the DNS and IP address form of the host address. This may occur when connecting to the Administration server in some environments.
Edit the address, as required.
|
|
|
In some circumstances, you may receive a Javascript error in Microsoft Internet Explorer 6.0 when attempting to save a JVM instance configuration.
Try the operation using the Mozilla Firefox (or another) browser.
|
|
|
When using Mozilla Firefox 1.5 or above, you may experience repaint problems on smaller or laptop monitors when scrolling pages with tab controls at the top.
Resize the browser window by dragging its edges or maximizing it.
|
|
|
When deleting connection or connection factory entries, the Connections page may refresh too quickly causing the entries to reappear as if they were not deleted.
Refresh the browser window.
|
|
|
When you configure a console notification to add an icon to an element in the user interface (for example, the Services table), upon subsequent visits to the Service table, Monitoring tab, or Inventory pane, the icon is not present.
The icon should appear the next time the constraint is triggered and the console notification is executed.
|
|
|
When defining a process group, if you are importing from another service, running WebLogic domain, or WebLogic domain configuration, if you select the following flags:
- Allow me to choose instances to import
- Show me a summary of uncollectable metadata from config.xml
and you select to import from a service or configuration that was recently used (at the bottom of the screen), the recently used links may become corrupt, as follows:
- Import from Running Domain: The host/port may be missing.
- Import from Service: The service name may be missing.
- Import from domain configuration: The path to the configuration may be missing.
If the labels for the most recently used links are incomplete, you should not use them. Instead, you should enter data using the fields provided on the import page.
|
|
|
When viewing a constraint in the Constraints table that was configured with an event status of succeeded, the configured status appears as failed.
Clicking on the rule definition shows the correct status.
|
|
|
When navigating a table with more than 10 entries, the to value (shown below) in the table page navigation located above the table may reflect an incorrect value.
|
|
|
The Tasks and Events viewer displays the most current entries at the top of the viewer by default. If you refresh the browser window the order is reversed and the most current entries are displayed at the bottom.
|
|
|
When adding a process group to a service, if you select Import from another service, you may experience an error on the service selection screen.
Try importing from a different service or from another source, such as a running WebLogic domain, creating the process group from scratch, or cloning another process group or JVM instance from the Service page.
|
|
|
You may encounter an error when importing a process group from a service if you rename the process group during the import process.
Try importing the process group from a service without changing its name.
|
|
|
When adding two process groups or JVM instances to a service back-to-back (without refresh), both items may not be registered as being added.
Refresh the page between each add operation to ensure all process groups and JVM instances are added.
|
|
|
In some cases, following a Controller restart the Inventory pane may appear empty on initial display because of problems reading the user inventory.
Refresh the browser window.
|
|
|
When creating a policy, if you select Based on the value of an attribute or function, click Define Custom to define a custom metric, and you modify the instance portion of the generated metric prior to clicking the Finish button to create the policy, the change is not recognized.
|
|
|
If you attempt to log in to the WLOC Administration Console using a user account that is not assigned to any roles, you will see entries in the Inventory pane including resource pools and JVMs representing runtime data. However, when you click on the entries, you will not see any data because you are not authorized.
|
|
|
When you create a LiquidVM (LVM) instance initially in WLOC, it is placed within a resource pool for an ESX compute resource (single host or cluster). Later, the LVM instance may be migrated to a different resource pool or different compute resource (host or cluster) or a combination of both. This can be done using the VMware VirtualCenter client or VirtualCenter. Note that when a live VM is migrated to a different ESX host, VMware VMotion is used in the migration process.
If migration occurs within the resource pool: Typically, the VM is migrated to another physical ESX host within the cluster (to which the resource pool belongs) by the VMware DRS or HA features. In this case, there will be no impact to the lifecycle management and monitoring operations and the WLOC Administration Console will function as expected.
If the migration occurs across resource pools: Typically, the migration is performed manually by the user using the VMware VirtualCenter client. In this case, there will be no impact to the lifecycle management and monitoring operations. However, the WLOC ESX Agent will not detect the resource pool migration. As a result, the WLOC Administration Console will continue to show the VM as being associated with the original resource pool and all management and monitoring operations will be directed at the same ESX Agent assigned for the original resource pool.
Migrating an LVM instance to a new resource pool, as described above, is not supported.
|
|
|
If you save a blank password when configuring a JVM instance, when viewing the configuration you may see a string with the value of null in the JVM password field.
Clear the password field and save the JVM configuration.
|
|
|
The Filter tool that appears at the top of some pages in the WLOC Administration Console only sorts information on the current page.
|
|
|
If you attempt to delete a monitoring view that has charts associated with it, you may encounter an error.
Delete all charts associated with the view before deleting it.
|
|
|
Use of multi-byte character sets for the display and update of data may cause problems with the WLOC Administration Console.
Whenever possible, use English Locale when using the WLOC Administration Console.
|
