This commit improves the "Browse Queues" view in the following ways:
1. Remove unused column "Queue Count"
1. When clicking on an address in the "address" column the respective address is selected in the navigation tree
1. Make "name" cell in each row clickable so it selects the respective queue in the navigation tree and sets the queue filter.
1. Make "message count" cell in each row clickable so it navigates to the message queue browser.
This reverts commit 42e31e0494ebcf7e2005cfc28ffb680c8e56d4a3.
I am doing the revert just apply the correct JIRA, as I used the wrong JIRA ID by accident
This commit improves the "Browse Queues" view in the following ways:
1. Remove unused column "Queue Count"
1. When clicking on an address in the "address" column the respective address is selected in the navigation tree
1. Make "name" cell in each row clickable so it selects the respective queue in the navigation tree and sets the queue filter.
1. Make "message count" cell in each row clickable so it navigates to the message queue browser.
When deleting a durable scheduled message via the management API the
message would be removed from memory but it wouldn't be removed from
storage so when the broker restarted the message would reappear.
This commit fixes that by acking the message during the delete
operation.
Using a ThreadLocal for the audit user information works in most cases,
but it can fail when dispatching messages to consumers because threads
are taken out of a pool to do the dispatching and those threads may not
be associated with the proper credentials. This commit fixes that
problem with the following changes:
- Passes the Subject explicitly when logging audit info during dispatch
- Relocates security audit logging from the SecurityManager
implementation(s) to the SecurityStore implementation
- Associates the Subject with the connection properly with the new
security caching
