View Issue Details

IDProjectCategoryView StatusLast Update
0006197SymmetricDS ProBugpublic2024-01-22 15:54
Reporterelong Assigned Toelong  
Prioritynormal 
Status closedResolutionfixed 
Product Version3.15.0 
Target Version3.15.3Fixed in Version3.15.3 
Summary0006197: Failed to queue work because the background refresher service has been shut down
DescriptionBackground 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
TagsNo tags attached.

Relationships

related to 0006196 closedelong Failed to queue work because the background refresher service has been shut down 
related to 0006030 closedelong Work queued via BackgroundRefresherService sometimes does not get done 

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2024-01-22 13:57 elong New Issue
2024-01-22 13:57 elong Status new => assigned
2024-01-22 13:57 elong Assigned To => elong
2024-01-22 13:57 elong Issue generated from: 0006196
2024-01-22 13:57 elong Relationship added related to 0006196
2024-01-22 13:59 elong Status assigned => resolved
2024-01-22 13:59 elong Resolution open => fixed
2024-01-22 13:59 elong Fixed in Version => 3.15.3
2024-01-22 15:54 elong Relationship added related to 0006030
2024-02-05 18:58 admin Status resolved => closed