Project

General

Profile

Bug #6767

GMN crashes if the replication target is not responding

Added by Dave Vieglais over 7 years ago. Updated over 6 years ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
Start date:
2015-01-22
Due date:
% Done:

0%

Story Points:
Sprint:

Description

Hays reports that his GMN instance was hanging due to a large number of attempted connections to a replication target that was not responding.

GMN should be defensive when connecting to external services, either queuing requests or failing them.

GMN should also be terminating connections if the action does not complete within "a reasonable period of time"

History

#1 Updated by Mark Servilla over 6 years ago

  • Assignee changed from Mark Flynn to Roger Dahl

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)