FUJ00171954
FUJ00171954
Peak Incident Management System
Call Reference PC0074043 Call Logger POA Deleted User -- Deleted Team
Release Targeted At -- BL 3 Top Ref FSTK 2 0 WP14566-69,71-73
Call Type System Testing Incidents/Defects _ Priority B -- Progress stopped
Contact Deleted Contact Call Status Closed -- S/W Fix Available to Call Logger
Target Date 25/02/2002 Effort (Man Days) 0
Summary Riposte6210: Time synch does not work
All References Type Value
Fast track fix FSTK_2_0_WP14566-69,71-73
Work Package PWY_WP_14566-69; 14571-74
Work Package PWY_WP_ 14566-14574
Test reference TCTIMO1
' Supplier reference 1017
Progress Narrative
fbate:20-Feb-2002 11:44:00 User:Madhu Karia
CALL PC0074043 opened
leferences entered are:-
If Test reference ; TCTIMO1
product Infrastructure RIPOSTE messaging sw added
lfarget Release entered: Unknown
Riposte6210: Time synch doe not work
lA Client only synchronises on riposte start up but not thereafter.
scenari
set up a Client (7261,1) to neighbor a LAN-connected peer client (7261,2) and
lan ISDN-connected Virtual Correspondence Server (0,42) made up of 2
correspondence Servers, CSA (0,32) and CSB (0,33).
set the following riposte parameters on the Clients
1261,1 1261,2
f'imeSynchDriftLimit 5000 5000
[fimeSynchLevel 2 2
[timeSynchNodeId 42 1
start riposte on CSA, then 7261,1 and then 7261,2 and check riposte is in
synch on all 3 platforms.
Display clocks on all 3 above platforms and check the clocks are in synch.
ISA: Advance the clock by 15 minutes.
SA: riposteprioritymessage 30000 1 25 7261
the clocks on 7261,1 and 7261,2 should advance by 15 minutes but they do not.
[?261,1: riposteprioritymessage 30000 1 25 0
the clocks on 7261,1 and 7261,2 still do not advance by 15 minutes
[7261,1: Stop and restart riposte
7261,1: When riposte goes online the clock synchronises with CSA
1261,1: riposteprioritymessage 30000 1 25 0 followed by riposteputmessage 5
fhe clock on 7261,2 does not synchronise with 7261,1
[)261,2: Stop and restart riposte
[7261,2: When riposte goes online the clock synchronises with 7261,1
the last time Time Synch worked OK was on Riposte 6.2.8.
Please route this call to Escher-Dev.
CALL PC0074043:Priority B:CallType S - Target 25/02/02 11:44:03
the Call record has been assigned to the Team Member: Chris Rayner
Defect cause updated to 42:Gen - Outside Pathway Control
Hours spent since call received: 3.0 hours
bate: 20-Feb-2002 11:48:00 User:Chris Rayner
the call summary has been changed from:
Riposte6210: Time synch doe not work
[the call summary is now:
Riposte6210: Time synch does not work
lf} Response :
Please route this call to Escher-Dev for investigation.
[END OF REFERENCE 28935003]
lkesponded to call type $ as Category 30 -TL confirmed
{fhe response was delivered on the system
[the Call record has been transferred to the Team: QFP
Hours spent since call received: 0 hours
0-Feb-2002 11:50:00 User:Tarig Arain
lthe Call record has been transferred to the Team: Escher-Dev
iours spent since call received: 0 hours
[Date:20-Feb-2002 16:10:00 User:Del (04/03 Brian Orzel)
FUJ00171954
FUJ00171954
ff confirmed, this bug could possibly be an urgent show stopper, but is more
likely to be something we can live with for a while. I am asking Escher for
ldvice at this stage rather than an immediate fix. We have missed normal BI2
liclivery deadlines.
[the Call record has been assigned to the Team Member: At-E
Hours spent since call received: 0 hours
cher
IDate:21-Feb-2002 0
Escher Respons:
he interim time synch fix was provided to handle the delay of the marker
arrival that caused time drift. This fix also handles a situation of the
clock of the client being changed. In Pathway's test case, the clock of
the source machine was changed, and it was not handled properly by the new
code. This is a new error on our end and the fix is not trivial.
[the nature of this problem should not have a significant impact on the
Hive environment, unless it can be anticipated that the clock at the
servers ave to be changed/adjusted reqularly.
5:00 User:Del (04/03 Brian Orzel)
JDate:21-Feb-2002 07:46:00 Uscr:Del (04/03 Brian Orzel)
fhe Call record has been assigned to the Team Member:
Hours spent since call received: 0 hours
cher recreated
[Dats:22-Feb-2002 1
717:00 User:De1 (04/03 Brian Orzel)
the call references have been updated. They are now:-
est reference : TCTIMO1
Supplier reference : 1017
jDate:11-Jun-2002 1
Fixed at WR2.1.2
3:00 User:Del (04/03 Brian Orzel)
[Date:49-dun-2002 08:42:00 User:Del (04/03 Brian Orzel)
[the Call record has been assigned to the Team Member: Brian Orzel
ours spent since call received: 0 hours
Jbate:15-gul-2002 15:02:00 User:Lionel Higman
target Release agreed outside QFP Forum
ffarget Release updated to BI_3
IDate:22-Aug-2002 12:29:00 User:Del (04/03 Brian Orzel)
lewy WP_14566; PWY WP 14567; PWY WP 14568; PWY WP 14569; PWY_WP 14571;
lpwy WP 14572; PWY WP 14573; PWY_WP_14574;
the Call record has been transferred to the Team: IP System Test
Hours spent since call received: 0 hours
bate:22-Aug-2002 15:28:00 User:Lionel Higman
[the call references have been updated. They are now:-
est reference : TCTIMO1
supplier reference : 1017
lt Work Package : PWY_WP_14566-69; 14571-74
the Call record has been transferred to the Team: Dev-Int-Rel
Hours spent since call received: 0 hours
Date: 27-Aug-2002 20:21:00 User:Lionel Higman
the call references have been updated. They are now:-
lest reference : TCTIMO1
supplier reference : 1017
jork Package : PWY_WP_14566-69; 14571-74
lt Work Package : PWY WP 14566-14574
JDate:29-Aug-2002 14:50:00 User:Miho Fujii
lewY WP_14566,14569 & 14570 Fast Tracked.
waiting for PWY WP 14567,14568,14571, 14572, 14573 @ 14574.
Date:03-Sep-2002 14:41:00 Uscr:Miho Fujii
fwe14571, 14572 & 14573 Fast Tracked.
JAwaiting for WP14567, 14568 & 14574,
JDate:04-Sep-2002 10:56:00 Uscr:Miho Fujii
P14567 & 14568 Fast tracked.
FUJ00171954
FUJ00171954
[Date:12-Sep-2002 15:53:00 Uscr:Miho Fujii
[the call references have been updated. They are now:-
Test reference : TCTIMO1
supplier reference : 1017
jork Package : PWY WP 14566-69; 14571-74
lork Package : PWY_WP 14566-14574
lt Fast track fix : FSTK 2 0 WP14566-69, 71-73
Ir} Response :
rast track availabel, please test.
[END OF REFERENCE 31242187]
lkesponded to call type S as Category 60 -S/W Fix Released to Call Logger
tours spent since call received: 0 hours
[the response was delivered on the system
Date: 26-Sep-2002 09:05:00 U
lrix tested OK in riposte 6.2.
CALL PC0074043 closed: Category 60, Type S
Root Cause Gen - Outside Program Control
Logger POA Deleted User -- Deleted Team
Subject Product Infrastructure -- RIPOSTE messaging sw (version unspecified)
Assignee Deleted User -- Deleted Team
Last Progress 26-Sep-2002 09:05 -- Madhu Karia