Some of the content described in this article is available in meshIQ Manage versions 11 and greater. See meshIQ Highlights v11 for an overview of feature changes.
If a viewlet you created is empty (displays the message, No data to display) or is missing objects, try the following troubleshooting suggestions:
- Refresh your viewlet
- Check display settings
- Are filters applied?
- Is there a limit in place?
- Is the node managed?
Refresh your viewlet
First try to refresh the viewlet by clicking the Refresh button.
Check display settings
Do you have any settings enabled that would prevent objects from appearing? Perform the following to check your settings:
- Click the Settings button located on the main toolbar.
- The Settings window opens. Enable/disable the following applicable settings:
- Click Save Changes. Go back to your viewlet and click Refresh
.
Are filters applied?
Is there a filter in place causing the object not to appear in the viewlet? Check the following filters:
- Confirm that the viewlet's Filter by field does not have an entry that would prevent the object from appearing.
- Is an Attribute filter being used? These filters affect which objects are displayed in viewlets. Check out Filtering objects displayed in a viewlet for more information.
- If a message filter is in place, objects will be filtered based on their messages' contents. If an object has at least one message containing the value within the Search Criteria field (see screenshot below), the object will display in the viewlet. Please note that this only applies for Local and Alias queues.
Is there a result limit in place?
Check to see if there is a Result limit specified for the viewlet. This value restricts the number of objects that can be displayed in a viewlet. By default, this value is controlled by a global setting set by your administrator (for example, 500), or by your user settings. But you can also change the Result Limit by editing the viewlet, or by adjusting the Result limit value in the viewlet header, if the Show advanced viewlet filtering user setting is enabled.
Check the Result limit. Confirm that its value is large enough.
In versions 10.5.x and earlier, if the value labeled Total at the lower left of the viewlet matches the Result Limit, then the Result Limit is almost certainly restricting the number of objects you are seeing. (For specific handling of local queues and channels, see the Version 10.4 and later section under Are you using Type 'All' for IBM MQ queues or channels? below.)
In versions 11 and later, the Total, Visible, and Selected labels become orange in this scenario. When this happens, increase the Result Limit to view additional objects that are not being included.
If the Visible number of objects is less than the Total, then the results are affected by a filter you've applied. In the example below, the "TEST" in the Filter by field is narrowing down results to only include the 12 records with the word "TEST".
When the Result Limit is too high (for example, 50,000), your browser may become overloaded. To narrow results, consider using an object pattern or selecting the node and manager instead of leaving "*" on the Edit Viewlet window's fields to include all nodes and managers.
In versions 10.5 and later, attribute filters are applied by the workgroup server before results are returned. If you consistently notice that the number of records in your viewlets matches the Result Limit (in versions 11 and later, the Total/Visible/Selected labels are orange in this case), then consider fine-tuning the viewlet’s attribute filters to return a more relevant set of results from the workgroup server.
Are you using Type 'All' for IBM MQ queues or channels?
Versions 10.3.x and earlier
To avoid returning too much data, the result limit is ignored for 'all' queues or channels, since multiple queries are done to fetch the objects to display. A hard coded limit of 1000 is used for each queue type. Thus, you might see a total of 1528 objects returned, of which 1000 are local queues and 528 are a combination of remote, alias and model queues. Use a more concise object or manager filter to return less than 1000 for any given type.
Version 10.4 and later
The functionality of the “All” selection in the type viewlet filter has been updated. The workgroup server limit of 1000 objects per type is no longer applicable. The number of objects returned is controlled by the Result Limit, which applies to each type of object.
The “total” (or maximum) number of items that can be returned is the Result Limit multiplied by the number of object types. If the number of objects of a given type exceeds your Result Limit, then you will not see all of them because the number of records that are "Visible" for that type is still subject to your Result Limit.
For both queues and channels, changing the Result Limit affects the total number of results returned, with these conditions:
- For queues: The Result Limit applies to each queue type. With a Result Limit of 1000, if you had 1000 of each queue type (local, remote, model, alias, and cluster), the maximum number of results would be 5000. Beginning in version 11, the Total/Visible/Selected labels become orange when the total results of at least one of these types matches the Result Limit.
- For channels: Since queries look for MQ channels, AMQP, MQTT, and client connections, then with a Result Limit of 1000, the maximum number of results would be 4000. Beginning in version 11, the Total/Visible/Selected labels become orange when the total results of at least one of these types matches the Result Limit.
Is the node managed?
If the viewlet is still empty, your administrator can check whether the object's node is managed. Please see, Viewlet displays "No data to display" (Re-manage the node), for more information.