-
Bug
-
Resolution: Done
-
Major
-
7.2.6.GA
Currently, the web console is highly affected by the write lock acquisition. Most of the read operations done by the web console are translated into composite operations, that under some circumstances (target to a single host, non-wildcards..), require the DC write lock. This write lock acquisition has a huge impact on the web console since each operation is queued until the lock is released.
As an example, if we have a deployment that takes some minutes in the middle the user is clicking to see the server status, soon the web console gets unresponsible.
This issue tries to reduce the write lock acquisition in these cases and allow read operations.
See WFCORE-4809(https://issues.redhat.com/browse/WFCORE-4809)
- is blocked by
-
JBEAP-18655 (7.2.z) [HAL-1663] Two error dialog messages when DC is starting and user executes lifecycle operations on slave servers
- Closed
-
JBEAP-18657 (7.2.z) [HAL-1653] Topology is not refreshed automatically after restart the domain
- Closed
- is caused by
-
WFCORE-4809 Allow composite operation to read the model without need to acquired the write lock in domain mode
- Closed
- is cloned by
-
JBEAP-18651 [GSS](7.3.z) Allow composite operation to read the model without need to acquired the write lock in domain mode
- Closed
- is incorporated by
-
JBEAP-18607 [GSS](7.2.z) Upgrade WildFly Core from 6.0.24 to 6.0.26
- Closed