Menu ▾ ▴

#2973 ntf: NTFD send the response the client (MDS DEST) fail because the MDS dest disconnected

5.19.03
fixed
nobody
None
defect
ntf
d
major
False
2019-02-07
2018-11-23
Canh Truong
No

When the sending notification request come to NTFD , they are put in the mbx to wait for being processed. if client of these request is down, MDS thread receive the event down and also put to mbx.

The priority of event down and send request are the same. So NTFD will process the send request before the event down. NTFD send the response will be timeout because the last client that already was finalized (mds dest was disconnected).

Related

Wiki: ChangeLog-5.19.03

Discussion

  • Canh Truong

    Canh Truong - 2018-11-28
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,3 +1,3 @@
 When the sending notification request come to NTFD , they are put  in the mbx to wait for being processed.  if client of these request is down, MDS thread receive the event down and also put to mbx. 

-The priority of event down and send request are the same. So NTF will process the send request before the event down.
+The priority of event down and send request are the same. So NTFD will process the send request before the event down. NTFD send the response will be timeout because the client that already was finalized.
     

  • Canh Truong

    Canh Truong - 2018-11-28
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,3 +1,3 @@
 When the sending notification request come to NTFD , they are put  in the mbx to wait for being processed.  if client of these request is down, MDS thread receive the event down and also put to mbx. 

-The priority of event down and send request are the same. So NTFD will process the send request before the event down. NTFD send the response will be timeout because the client that already was finalized.
+The priority of event down and send request are the same. So NTFD will process the send request before the event down. NTFD send the response will be timeout because the last client that already was finalized.
     

  • Canh Truong

    Canh Truong - 2018-12-05
    • summary: ntf: NCSMDS_DOWN event is delayed to send to main thread --> ntf: NTFD send the response the client (MDS DEST) fail because the MDS dest disconnected
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,3 +1,3 @@
 When the sending notification request come to NTFD , they are put  in the mbx to wait for being processed.  if client of these request is down, MDS thread receive the event down and also put to mbx. 

-The priority of event down and send request are the same. So NTFD will process the send request before the event down. NTFD send the response will be timeout because the last client that already was finalized.
+The priority of event down and send request are the same. So NTFD will process the send request before the event down. NTFD send the response will be timeout because the last client that already was finalized (mds dest was disconnected).
     

  • Canh Truong

    Canh Truong - 2018-12-06
    • status: accepted --> review
     

  • Gary Lee

    Gary Lee - 2019-01-09
    • Milestone: 5.19.01 --> 5.19.03
     

  • Minh Hon Chau

    Minh Hon Chau - 2019-02-07
    • status: review --> fixed
    • assigned_to: Canh Truong --> nobody
     

  • Minh Hon Chau

    Minh Hon Chau - 2019-02-07

    commit ae78957e977d783cf053e86845ad7c34e51230a3
    Author: Canh Van Truong canh.v.truong@dektech.com.au
    Date: Fri Feb 8 10:55:54 2019 +1100

    ntf: Fix to NTFD doesn't send the response if MDS_DEST of client is disconnected [#2973]
     

Log in to post a comment.