Daemon Controller: Wrong Details Displayed If A Filter Is Applied
Last updated on SEPTEMBER 15, 2017
Applies to:Oracle Agile Engineering Data Management - Version 18.104.22.168 to 22.214.171.124 [Release 6.1.0 to 6.2.0]
Information in this document applies to any platform.
The Daemon Controller Plugin is activated in the Java Client and displays several records (connections).
Find that if a user filters the list by adding a filter criteria (for example a user name) into the filter field and then selects one connection and clicks on 'Information' (from the Context menu) then the Information for a different Connection is displayed.
Also if the user clicks 'Shutdown Server' not the displayed connection is shut down but the one that was in that line before the filter was applied.
The details from the truly selected connection should be displayed and not from the one that was filtered out.
The issue can be reproduced at will with the following steps:
1. From the Java Client Preferences click Plugins.
2. In the list of Plugins click the checkbox 'Load' for Daemon Controller Plug-In
3. Start the Java Client
4. Click the Daemon Controller icon from the Java Client toolbar (next to the Java Client preferences icon)
5. In the Daemon Controller window click Start | Connect to daemon... and add the connection details for the Java Daemon
6. Connect with at least two Java Clients to that daemon that you see two connections (or more)
7. Click from the context menu 'Information' to double check that the correct information is displayed
8. In the filter field add a filter criteria that only the second connection is displayed (for example enter the port number)
9. Select that connection which is now in the first line (as it is the only one remaining displayed) and click 'Information' form the context menu
=> The displayed information is from the filtered Connection that was previously displayed in the first line.
10 If 'Shutdown Server' is clicked from the context menu not the selected connection is shut down but the one that was originally displayed in that line.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms