View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006196 | SymmetricDS Pro | Bug | public | 2024-01-22 13:52 | 2024-01-22 15:54 |
| Reporter | elong | Assigned To | elong | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.14.0 | ||||
| Target Version | 3.14.12 | Fixed in Version | 3.14.12 | ||
| Summary | 0006196: Failed to queue work because the background refresher service has been shut down | ||||
| Description | Background refresher job is shut down even though user is still logged in. The user may attempt certain operations that will not perform, like taking a support snapshot. WARN [gui] [ServerRpcHandler] [qtp1893063019-121] Resynchronizing UI by client's request. A network message was lost before reaching the client and the client is reloading the full UI state. This typically happens because of a bad network connection with packet loss or because of some part of the network infrastructure (load balancer, proxy) terminating a push (websocket or long-polling) connection. If you are using push with a proxy, make sure the push timeout is set to be smaller than the proxy connection timeout INFO [gui] [ConsoleEventService] [qtp1893063019-121] Event "Console User Logout" from user "no_user" at node "server" [ 127.0.0.1 ] ERROR [gui] [BackgroundRefresherService] [qtp1893063019-121] Failed to queue work because the background refresher service has been shut down | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-01-22 13:52 | elong | New Issue | |
| 2024-01-22 13:52 | elong | Status | new => assigned |
| 2024-01-22 13:52 | elong | Assigned To | => elong |
| 2024-01-22 13:57 | elong | Status | assigned => resolved |
| 2024-01-22 13:57 | elong | Resolution | open => fixed |
| 2024-01-22 13:57 | elong | Fixed in Version | => 3.14.12 |
| 2024-01-22 13:57 | elong | Issue cloned: 0006197 | |
| 2024-01-22 13:57 | elong | Relationship added | related to 0006197 |
| 2024-01-22 15:54 | elong | Relationship added | related to 0006033 |
| 2024-02-05 18:57 | admin | Status | resolved => closed |