+++ This bug was initially created as a clone of Bug #710230 +++ Created attachment 502598 [details] Screen shot of admin-console showing confusion when invoking the Test Connection operation on a datasource In some cases, the result of invoking an operation can be confused with the result of the actual operation. For example: For a datasource resource, you can invoke the "Test Connection" operation. Once the operation has been submitted, the "Operation History" will indicate "Successful". This "Successful" message can easily be interrupted as the connection to the datasource was successful when in reality, the actual test of the datasource connection returned failed. This is confusing to operational admins looking at this UI to test a connection. In fact, this would mislead them to look at the wrong section and proceed thinking the connection has been obtained when it's not, and could possibly cause serious production ramifications. The UI should be re-worked and be more intuitive and clear.
Fixed in AdminConsole_EAP_5_1 branch (commit 12148f7) - improved the description of the 'testConnection' datasource/connFactory operation so it makes it clear that the operation always returns SUCCESS even if the connection test failed. The fix still needs to be committed to master.
discussed with ips: verification is to be performed by EAP QA
wasn't this fix meant to be applied to EAP admin-console? Yes, the fix is present in the descriptor of EAP5-plugin for RHQ (commit 12148f7), but from the name of this issue and also the screenshot, I thought the same change was meant to be done for EAP admin console, which it seems hasn't been done. At least in EAP 5.1.2 ER1 admin console, the description of "Test Connection" operation is still the same, the confusing one, so I really don't understand why this is already ON_QA. If I am missing something, please correct me.
Yes. The fix can be seen in the tag for EAP 5.1.2 ER1 admin-console - http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=blob;f=modules/plugins/jboss-as-5/src/main/resources/META-INF/rhq-plugin.xml;h=71cfccec533ba0b5c25a4b9ac924ebc24b6f859d;hb=0cf4f6b696f31e115165b826af14570a6b8a0b20 So if it isn't there then EAP has some build issue because https://issues.jboss.org/browse/JBPAPP-6766 indicates that the component upgrade was complete.for ER1.
Created attachment 527684 [details] actual EAP 5.1.2 ER1 console I attached a screenshot proving that in EAP 5.1.2 ER1 this is not fixed. The EMBJOPR version (in the bottom of the screen) correctly says 1.3.4.SP5, but the description is not changed. Can someone investigate why this happens?
Verified with EAP/EWP 5.1.2 ER2.
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE
marking VERIFIED BZs to CLOSED/CURRENTRELEASE