Description of problem: When you push "Flush" button on JMS Destinations runtime tab (both of queues and topics), a confirmation dialog box brings up. "Cancel" button in the dialog box is always ignored and destination flushing is inevitably executed. Steps to Reproduce: 1. Launch a standalone-full.xml instance. 2. Create a queue, helloworld-jms quickstart is sufficient. 3. In the management console, go to "Runtime > JMS Destinations > Queues" tab. 4. Select the queue and push "Flush". 5. Push "Cancel" in the dialog. 6. "Cancel" is ignored and messages are flushed. Additional info: "remove-messages" operation in CLI is the equivalent one. So possible workaround will be something like as follows. /subsystem=messaging/hornetq-server=default/jms-queue=testQueue:remove-messages()
Osamu Nagano <onagano> made a comment on jira WFLY-1921 {{isConfirmed}} is ignored in the {{onConfirmation()}} method. The same in {{TopicMetrics.java}}. [https://github.com/jbossas/console/blob/develop/gui/src/main/java/org/jboss/as/console/client/shared/runtime/jms/QueueMetrics.java#L180] {code:java} 176 Feedback.confirm("Flush Queue", "Do you really want to flush queue "+queue.getName(), 177 new Feedback.ConfirmationHandler(){ 178 @Override 179 public void onConfirmation(boolean isConfirmed) { 180 presenter.onFlushQueue(queue); 181 } 182 }); {code}
This bug can be critical, a message lost, but easy to fix. Shouldn't we rush this into EAP 6.1.1?
I seriously doubt that lack of confirmation dialog is critical. It is certainly confusing and thus should be properly documented. 6.1.1 is in ER8 should go straight to GA. I will propose this fix to 6.2.0 If you would have decided to perform this operation from let's say CLI, you would have to do so without confirmation message. Another workaround would bo to close configrmation dialog with the X button in upport right corner.
I agree with Jakub, I would consider this to be a critical bug.
meant to say: ... would not
Confirmation dialog is still broken. This is an important usability issue promised to be addressed in 6.2.0. Thus setting higher severity and proposing a blocker.
I apologize for last comment. The verification was done against ER2. The issue as described in this report is fixed in ER3 (hal 2.0.0.Final) Verified 6.2.0.ER3
Harald Pehl <hpehl> updated the status of jira WFLY-1921 to Resolved
Harald Pehl <hpehl> made a comment on jira WFLY-1921 Fixed in upstream. Will be part of WF 8 and EAP 6.2.CP0a.
Was this functionality removed in EAP 6.3.0 from webconsole? There is no such option in Configuraion > Messaging > Destinations > Queues.
Verified for EAP 6.3.0.ER9 (messages are flushed only when Flush is Confirmed).
Making public for inclusion in 6.3.0 Release Notes.