FUJ00225940
FUJ00225940
Peak Incident Management System
Call Reference PC0204310 Call Logger _Customer Call_ -- EDSC
Release Targeted At -- HNG-X 03.20 Top Ref PC0206867
HNG-X Data Centre Raised an
Call Type Incidents/Defects Priority B -- Progress Stopped
Contact EDSC Call Status Closed -- Programme approved - No fix
required
Effort (Man
Target Date 16/09/2010 Days) 0
Summary Duplicate JSN detected
All References Type Value
Product Baseline BAL_SRV_OSR_ROUTING_0320_V239
BAL_SRV_OSR_0320_V238 &
Product Baseline BAL_SRV_OSR_ROUTING_0320_V238
Product Baseline BAL_SRV_OSR_0320_D239
TRIOLE for Service 2858551
_ Release PEAK PC0206867
Product Baseline BAL_SRV_OSR_0320_V239
SSCKEL KEL MithyanthaJ1937S
DevIntRel-Director Live Supp.Test
Product Baseline BAL_SRV_OSR_ROUTING_0320_D239
Impact
S cteat User Date
Unknown 02-Nov-2010 16:22:59
Support overhead currently 30 incidents in 5 days. Resoluton will mean that any future occurrences will
have a different root cause and require investigation. Such incidents are currently getting masked by the
volume associated with this Peak with consequential risk to the integrity of the audit trail used for litigation
support.
Progress Narrative
fdate:13-Sep-2010 18:56:56 User: Customer Call_
cALL PC0204310 opened
Details entered are:-
lsummary:As per Catherine Obeng Reopen: OSR A0063 : [20560] : [112136-1-PP-0809-9] - Exception raised while p
call Type
call Priori
lfarget Rele.
INCIDENT MANAGEMENT
Date/Time Raised: Sep 13 2010 6:51PM
priority: B
contact Name:
contact. Phone
originator: XX
riginator's referen
product Serial No:
Product Site: HNG SMC
: 2858551
serve critical alert @ 8/9/2010 10:07 on I.
critical alert in text:
SR AO063 : [20560] : [112136-1-PP-0809-9] - Exception raised while processing message event - Serious system error:[ Duplicate JSN
letected - failed to insert journal record ] Caught Exception inclass com. fujitsu.poa-bal.osr.event .RequestEvent :Thread def
dent History:
2010-09-13 18 © [ Jayendrappa, Sunil Kumar]
HINT : AHDO5439: Copied from Incident 2835511
FUJ00225940
FUJ00225940
2010-09-13 18:51:39 [ Jayendrappa, Sunil Kumar)
Jzneun_en_rmg : Open Notification
2010-09-13 18:51:39 [ Jayendrappa, Sunil Kumar]
eneut_en_rmg : Transfer Notification
2010-09-13 18:52:44 [ Jayendrappa, Sunil Kumar]
fb : FIELD="summary' OLD="OSR A0063 : [20560] : [112136-1-PP-0809-9] - Exception raised while processing message event - Serious
system error:[ Duplicate JSN detected ~ failed to insert journal record ' NEW='As per Catherine Obeng Reopen: OSR A0063 : [20560] =
[112136-1-PP-0809-9] - Exception raised while processing message event - Serious system error:{ Duplicate JSN detected - failed to
insert journal record *
2010-09-13 18:53:30 [ Jayendray
L0G : Node name /Server name
service Detail:
SR AO0G3 : [20560] : {112136-1-PP-0809-9] - Exception raised while processing message event - Serious system error: [ Duplicate JSN
lletected - failed to insert journal record I Caught Exception inclass com. fujitsu.poa-bal.osr.event .RequestEvent:Thread def
pate + 8/9/2010
[time of accourrence : 10:07
KEL : MithyanthaJ1937s
2010-09-13 18:53:58 [ Jayendrappa, Sunil Kumar]
oc : Old Peak Provider Ref: PC0204088
Kumar]
\ionnalagadda, Naresh 08/09/2010 17:03 00:00:41 Field Update
IFIELD='zCloseCategory’ OLD='* NEW-'RMGA.O Operational.OP02 Central Systems Software failure'FIELD='zinclocode' OLD="' NEI
Admin’
Wonnalagadda, Naresh 08/09/2010 17:03 Transfer Notification - RMGA
transfer Notification
Wonnalagadda, Naresh 08/09/2010 17:03 Notify End User C
losure Notification
osed EN RMG
\ionnalagadda, Naresh 08/09/2010 17:03 Close
KEL : MithyanthaJ1937S - issue resloved hence closing this call
PoWebService, 01 08/09/2010 17:01 Notify End User Resolve EN RMG
Resolution Notification
PoWebService, 01 08/09/2010 17:01 00:00:00 Resolved
status changed from ‘Open’ to ‘Resolved’
PoWebService, 01 08/09/2010 17:01 00:00:00 Delay Service Type
the Service Type(s) on a ticket were delayed
PI 08/09/2010 17:01 00:00:00 OTI Resolved
Provider Ref: Pc0204088
kesolution Details: Update by Catherine Obeng:Category 67 -- Final -- Solicited Known Error:This is a known problem where a request
times out in the meantime, a retry with the same request Id success. As per above mentioned KEL, because the 1st message was
Irejected as a duplicate, there are no implications on the integrity of the data and therefore no issues of concern. Please close
this call as KEL.
PI 08/09/2010 10:20 00:00:00 OTT Provider Status Update
Update by John Charlton:Call routed to Team:EDSC Member:Catherine Obeng
2010-09-13 18:55:16 [ Jayendrappa, Sunil Kumar]
IR : Please investigate.
2010-09-13 18:55:48 [ Jayendrappa, Sunil Kumar]
Jzneut_en_tmg : Transfer Notification
Jbate:14-Sep-2010 08:10:50 Uscr:Lorraine Guiblin
Reference Added: SSCKEL Mithyanthadi937S
jbate:14-Sep-2010 08:12:06 User:Lorraine Guiblin
Product. HNG-X Platforms -~ BAL Server (BAL) (version unspecified) added.
IDaté:14-Sep-2010 08:12:28 Uscr:Lorraine Guiblin
[the Call record has been assigned to the Teait Member: Catherine Obeng
Progress was delivered to Consumer
bate:14-Sep-2010 1
[Start of Response]
Below is the output from the BRSS when I run the query described in the KEL:
9:47 Uscr:Catherine Obeng
ISoL> select journal _header
2 from ops$brdb.brdb_rx_message_journal
3 where FAD HASH = 13
Ja and BRANCH ACCOUNTING CODE = 112136
ls and JOURNAL SEQ NUMBER = 2454507
a
FUJ00225940
FUJ00225940
POURNAT_HEADER
Post: LabelEventServi
uthorization-Signature:
loi HgVopuxxYwvsqft25FDzerSpdaj rpbky+kmk j vVKMEXrEkg5PeF ggoBMZAF04z/SDDISFYmOhdp1 IwCgsF11Pki PLuunvojTUupzKLGYXix1Ai FUti /AJTAUL
yIyB2VAio¥c/Rqu9Sd99Pw9Y lwwcpad I kpKXq6vA=
lcontent-Length: 864
Retry: true
lReqMessageID: 112136-1-PP-0809-10
content-Encoding: gzip
isn: 2454507
in discussion with Andy Thomas this morning, I will gather evidence from the OSR/BAL logs before forward to 4GDC.
[End of Response]
Response code to call type J as Category 40 -- Pending -- Incident Under Investigation
lresponse was delivered to Consumer
[Date:14-Sep-2010 12:34:30 Uscr:Catherine Obeng
idence Added - 01 mes - File will be Obfuscated and made available to download soon.
jbate:14-Sep-2010 12:35:08 Uscr:Catherine Obeng
evidence Added - 01 poc ~ File will be Obfuscated and made available to download soon.
[Date:14-Sep-2010 12:36:56 User:Catherine Obeng
Invidence Obfuscated File (CTRMSG) Added - Node01 Mes
jDate:14-Sep-2010 12:37:39 Uscr:Catherine Obeng
lsvidence Obfuscated File (CTRPOC) Added - N.
jbate:14-Sep-2010 14:36:51 Uscr:Catherine Obeng
[Start of Response]
currently awaiting evidence gathering from the ACE Blade, platform Id is
Juthorisation messages etc.
[End of Response]
Response code to call type J as Category 40 -- Pending -- Incident Under Investigation
kesponse was delivered to Consumer
2 in order to determine message queues,
jbate:14-Sep-2010 17:02:58 Uscr:Catherine Obeng
lsvidence Added =
lbate:14-Sep-2010 1
[Start of Response]
Requested evidence is now attached. QFP please route onto to 4LS/GDC.
[End of Response]
esponse code to call type J as Category 40 -- Pending -- Incident Under Investigation
Response was delivered to Consumer
4:26 User:Catherine Obeng
jbate:14-Sep-2010 17:04:33 User:Catherine Obeng
[fhe Call record has been transferred to the team: QFP
Progress was delivered to Consumer
joaté:15-Sep-2010 08:11:21 User:Lionel Higman
fhe Call record has been transferred to the team: xCtr_GDC
User:Lionel Higman Confirmed that this Incident may be passed to the external company with the attached eviden
progress was delivered to Consumer
a
3
Jbate:15-Sep-2010 08:19:17 User:Ravindra Kumar
[the Call record has been transferred to the team: xOSR_GDC
fhe Call record has been assigned to the Team Member: Jeevan Mithyantha
Progress was delivered to Consumer
Date:46-Sep-2010 12:24:02 User:Jeevan Mithyantha
this peak has been raised due to “Duplicate JSN” issue occured in BAL/OSR while processing "
abelEventService" request.
from the DB record, its been clear that JSN "2454507" was inserted due to request id "12136-1-PP-0809-10".
From the counter message logs, we could see that "12136-1-PP-0809-9" and "12136-1-PP-0809-10" both had same JSN, since "12136-1-PP-
jos09-9" was timed out.
I think this is the issue with late arrival of the request in BAL/OSR (not sure thogh).
landy has suggested to look into ACE blade logs, to check whether the OSR instances for which these requests had gone to were
histening/working normally.
{fo investigate further on this, I would like to have OSR message.log & osr-log extract for request ids "12136-1-PP-0809-9" & "12136-
i-PP-0809-10".
FUJ00225940
FUJ00225940
"12136-1-PP-0809-10" has gone to . Not sure about the other one.
Jbate:16-Sep-2010 12:27:56 User:Jeevan Mithyantha
[the Call record has been transferred to the team: EDSC
lUser:Jeevan Mithyantha Confirmed that this Incident may be passed to the external company with the attached evidence.
Progress was delivered to Consumer
[Date:16-Sep-2010 12:28:40 User:Lorraine Guiblin
[the Call record has been assigned to the Team Member:
Progress was delivered to Consumer
atherine Obeng
jDate:20-Sep-2010 09:52:38 Us
evidence Added - 112136-10 me
sr:Catherine Obeng
ad. txt = File will be Obfuscated and made available to download soon.
jDate:20-Sep-2010 09:53:44 Uscr:Catherine Obeng
evidence Added - 12136-1- 09-10
Date:20-Sep-2010 09:59:25 User:Catherine Obeng
Jnvidence Obfuscated File (BALMSG) Added ~ 12136
bate: 20-Sep-2010 i
[Start of Response]
BAL. osr/message logs for MesgRqstID 12136-1-PP-0809-10 are now attached. Returning call to 41S.
{End of Response]
lkesponse code to call type J as Category 40 -- Pending -- Incident Under Investigation
lkesponse was delivered to Consumer
7:17 User:Catherine Obeng
JDate:20-Sep-2010 10:08:29 Uscr:Catherine Obeng
the Call record has been transferred to the team: x0SR_GDC
lUser:Catherine Obeng Confirmed that this Incident may be passed to the external company with the attached evidence.
Progr s delivered to Consumer
[Date:21-Sep-2010 08:46:39 Uscr:deevan Mithyantha
It have requested OSR logs (both osr.log & OSR message log) for request ids "12136-1-PP-0809-9" & "12136-1-PP-0a09-10"
tached logs contains the extract for request ID "12136-1-PP-0809-10", but missed the logs for "12136-1-PP-0809-9".
Please extract the same for request id "12136-1-PP-0809-9"
[Date:21-Sep-2010 08:46:54 Uscr:Jeevan Mithyantha
Action placed on Team:xOSR GDC, User:Jeevan Mithyantha
jDate:21-Sep-2010 08:47:11 Uscr:Jeevan Mithyantha
[the Call record has been transferred to the team:
User: Jeevan Mithyantha Confirmed that this Incident may be passed to the external company with the attached evidence.
Progress was delivered to Consumer
JDate:21-Sep-2010 09:01:12 Uscr:Lorraine Guiblin
[the Call record has been assigned to the Team Member: Catherine Obeng
Progress was delivered to Consumer:
Date:21-Sep-2010 10:39:05 Use::Catherine Obeng
[fhe call summary has been changed from:-
las per Catherine Obeng Reopen: OSR A0063 : [20560] : [112136-1-PP-0809-9] - Exception raised while p
[fhe call summary is now:-
Branch 112136 Duplicate JSN 112136-1-PP-0809-9 Exception raised
jDate:21-Sep-2010 15:52:37 Us
evidence Added - 112136 9 M
SriCatherine Obeng
sLogbk - File will be Obfuscated and made available to download soon.
Date:2i1-Sep-2010 15:54:25 User:Catherine Obeng
Evidence Added ~ RequestMesId 112136-1-
809-9
Dat c:21-Sep-2010 15:55:04 Uscr:Catherine Obeng
evidence Deleted - RequestMesId 112136-1-PP-0809-9
lDate:21-Sep-2010 5:50 User:Catherine Obeng
bvidence Added -
FUJ00225940
FUJ00225940
[bate:21-Sep-2010 16:01:01 User:catherine Obeng
lnvidence Obfuscated File (BALMSG) Added - Reques
bate:21-Sep-2010 1
[Start of Response]
jore evidence has been gathered and attached here. Returning call to $LS
{End of Response]
esponse code to call type J as Category 40 -- Pending -- Incident Under Investigation
Response was delivered to Consumer
5:14 User:Catherine Obeng
Date:21-Sep-2010 16:06:19 User:Catherine Obeng
the Call record has been transferred to the team: x0SR_GDC
User:Catherine Obeng Confirmed that this Incident may be passed to the external company with the attached evidence.
Progress was delivered to Consumer
Date:22-Sep-2010 09:32:12 User:Venu Anamalla
the Call record has been assigned to the Team Member: Jeevan Mithyantha
Progress was delivered to Consumer
[Dat e:22-Sep-2010 1.
Analysis
2:18 Uscr:Jeevan Mithyantha
rrom the OSR logs, I found that retried "LabelEventService" request with request id "112136-1-PP-0809-10" executed before the
original request with request id "112136-1-PP-0809-9
ain this has happened due to some network glitch. And hence the arrival of the messages in BAL/OSR got delayed.
probable solution
in order to get rid of these kind of errors/exceptions due to delayed arrivals, we could modify the code in BAL/OSR side.
In MessageJournalDAO, if SQLException occurs (i.e. if a JSN already exists in BRDB, then system will check the journal xml contents
jonly if its a retried request.
instead, we could check the journal xml contents irrespective of retry or original request. If the contents are same, then we could
lavoid throwing exception from OSR side and could be ending up in a warning message.
nyhow, from counter side this won't affect anything, since original request would have timed out and retried one will be
successful.
JDate:22-Sep-2010 14:24:51 User:Jeevan Mithyantha
Routing to Venu for review.
[Date:22-Sep-2010 14:25:00 User:Jeevan Mithyantha
[fhe Call record has been assigned to the Team Member: Venu Anamalla
Progress was delivered to Consumer
pate:23-Sep-2010 08:49:35 User:Venu Anamalla
tlooks like the root cause could be similar to peak PC0203208 (OSR paused for some time).
rs in similar manner to the one mentioned in
But, this peak could be used to address how to avoid Duplicate JSN issue, when it oc
this peak.
lanyhow, we are addressing the OSR imbalance/pause problem in peak PC0203208.
Please go ahead with the Fix Impact.
jbate:23-Sep-2010 08:50:07 Uscr:Venu Anamalla
[the Call record has been assigned to the Team Member: Jeevan Mithyantha
Progress was delivered to Consumer
Dat ¢:23-Sep-2010 09:19:22 User:deevan Mithyantha
[DEVELOPMENT IMPACT OF FIX:
SPECIFY THE HNG-X PLATFORMS IMPACTE!
ts Platforms details updated? - YES
TECHNICAL SUMMARY:
technical details explained above. This fix would affect 1 java file.
IuIST OF KNOWN DIMENSIONS DESIGN PARTS AFFECTED BY THE CHANGE:
ANY OF THESE DESIGN PARTS AFF
CTED BY APPROVED CPs/PEAKS in HNGX Release 2:
FUJ00225940
FUJ00225940
RELEASE 2 IMPACT:
DEPENDENCIES:
jone
JOOS THE FIX REQUIRE ANY MANUAL DEPLOYMENT BASELINES:
No
[DEV EFFORT IN MANDAYS:
0.5 day including development and testing
HMPACT ON USER:
[there isn't any direct impact on the user.
IMPACT ON OPERATIONS:
[Benefit of fix that may not visible to end user
[journal message contents.
larrival of the message in BAL side. $0, during this time to avoid Duplicate JSN issue, this fix would
]ZAVE RELEVANT KELS BEEN CREATED OR UPDATED?
ves.
IMPACT ON HORIZON TO HNGX BRANCH MIGRATIONS
jone
IMPACT ON TEST:
at independent test coverage/scenarios does development recommend?
I We could recreate the scenario mentioned in this peak, by starting OSR in DEBUG mode.
I Do a settlement transaction with any product in the basket, say 1st class stamp.
I Put a breakpoint in OSR, where the settlement request thread will suspend for some time
I Settlement will time out in counter side and retry request will be sent to OSR.
I Execute the retry request normally in OSR.
I: Counter will get response and settlement will be completed normally.
I Now, execute the original settlement request in OSR. Will get SQLException for duplicate JSN entry,
should log a warning message and will stop executing in filter stage itself.
hat CIT test coverage does development recommend?
I In CCIT, this particular scenario can't be tested, since we can't reproduce the late arrival of the
InISKS (of releasing and of not releasing proposed fix):
Fix is of low risk.
even though there won't be any direct impact on the end user, RISK of not releasing this fix would be
LIS? OF LIKELY DELIVERABLES:
essageJournalDAO. java
I With this fix, we could avoid throwing Duplicate JSN exception, in case if the JSN was inserted by s
imilar request i.e. with same
le have observed many scenarios in LIVE, where the retried request executed before the original request in BAL/OSR, due to delay in
be important.
but with the ew fix, it
request in OSR side.
medium.
JDate:23-Sep-2010 09:20:03 Uscr:Jeevan Mithyantha
kouting to Venu for review.
IDate:23-Sep-2010 09:20:11 User:Jeevan Mithyantha
[fhe Call record has been assigned to the Team Member: Venu Anamalla
Progress was delivered to Consumer
bate: 23-Sep-2010 09:49:04 User:Venu Anamalla
[Start of Response]
Fix Impact looks ok.
[End of Response]
Response code to call type J as Category 41 ~
lkesponse was delivered to Consumer
Pending -- Product Error Diagnosed
Date:23-Sep-2010 11:30:14 User:Jeevan Mithyantha
[the Call record has been assigned to the Team Member: Jeevan Mithyantha
progress was delivered to Consumer
jDate:24-Sep-2010 13:09:13 User:Jeevan Mithyantha
INGX CODE FIX
FIX DESCRIPTION
Described Above.
PROPOSED BRANCH
rap
COUNTER JAVA FILES CHANGED
lone.
FUJ00225940
FUJ00225940
[COUNTER PDL FILES CHANGED
nist changed files indicting if each file was added, updated or deleted. If no files changed, state None.
COUNTER REFDATA FILES CHANGED
jone.
SHARED CODE FILES CHANG!
jone.
BAL JAVA CODE FILES CHANGED
h) MessageJournalFilter. java
2) MessageJournalDAO. java
sql, FILES CHANGED
lone.
THER FILES CHANGED.
PPROPRIATE CODE COMMENTS
re
[DEPENDENCIES
lone.
RELATED PROBLEMS
jone.
UNIT TESTING EVIDENCE
screen shot of successful execution test cases has been attached.
lAlso, did manual testing as described above in the fix impact. Attached log extracts.
TESTCCLASS.
fessagedournalFilterTest java
IBACKWARDS COMPATIBILITY
/A ~ Framework change.
DEVELOPMENT. DOCUMENTATION
jone.
REQUIREMENTS DOCUMENTATION
jone.
HELE
None.
[Date:24-Sep-2010 13:12:17 User:Jeevan Mithyantha
3 part of regression test, we had alread a test class named MessageJournalFilterTest. To the same, I have included a new test case
Jramed "testDuplicateJSN_PC0204310" to test the scenario in this peak.
Joate:24-Sep-2010 13:12:45 User:Jeevan Michranehe
evidence Added - Code changes - Patch
jDate:24-Sep-2010
lsvidence Added - 1%
712:59 User:Jeevan Mithyantha
Date: 24-Sep-2010
evidence Added -—
Date:24-Sep-2010 13:13:42 Uscr:Jeevan Mithyantha
Routing to Venu for review.
jbate:24-Sep-2010 13:13:51 Uscr:Jeevan Mithyantha
fhe Call record has been assigned to the Team Member: Venu Anamalla
Progress was delivered to Consumer
Joate:04-Oct-2010 12:09:33 User:Venu Anamalla
code fix template looks plausible.
code patches and test details are OK.
Jbate:04-Oct-2010 12:09:45 User:Venu Anamalla
[the Call record has been assigned to the Team Member: Jeevan Mithyantha
Progress was delivered to Consumer
FUJ00225940
FUJ00225940
Date:08-Oct-2010 10:
[Start of Response]
3:01 User:deevan Mithyantha
{End of Response]
lkesponse code to call type J as Category 46 -- Pending -- Product Error Fixed
Response was delivered to Consumer
JDatc:19-Oct-2010 15:11:52 User:Martin Tonge
new Business Impact has been added:
[this Peak will reduce the support overhead because it will reduce the number of alerts associated with duplicate JSN's. It will
jalso mean that any future occurrences will have occurred for a different reason and would require investigation, Such incidents are
currently getting masked by the occurrences associated with this Peak.
[there is no immediate benefit to the customer other than support engineers no longer need to worry about these types of alert and
can focus on other alerts.
currently this type of error generates a relatively high frequency of Alerts on a daily basis, masking other types of error.
Date: 20-Oct-2010 15:52:02 User:_Customer Call_
Severity Count
OSR AQ063 : [20559] : [318518-3-10-2014-26] - [ Duplicate JSN detected - failed to insert
journal record ] Caught Exception inclass com. fujitsu.poa-bal.osr.event .RequestEvent :Thread generic brdb queue pool-12-thread-12
service URI: GenericBRDBModification Critical 1
Jat ¢:22-Oct-2010 12:20:11 User:Prashanth Pamidimukkala
product HING-X Platforms -- BAL Server (BAL) (version unspecified) added,
jDate:22-Oct-2010 12:20:32 User:Prashanth Pamidimukkala
fhe call Target Release has been moved to Proposed For -- HNG-X 03.20
jDate:25-Oct-2010 12:27:05 Uscr:Prashanth Pamidimukkala
ction has been removed from the call
bate:25-Oct-2010 12:28:00 User:Prashanth Pamidimukkala
ction placed on Team:RelMngmntForum
JDate:27-Oct-2010 14:11:41 User:John Boston
{the call Target Release has been moved to Targeted At -~ HNG-X 03.20
[Date :27-Oct-2010 14:11:53 User:John Boston
MF 26/10/10 Agreed - Targeted for 03.20.
Date: 27-Oct-2010 14:11:56 User:John Boston
ction has been removed from the call
0ate:02-Nov-2010 16:17:18 User:Steve Parker
[fhe call summary has been changed from:~
Branch 112136 Duplicate JSN 112136-1-PP-0809-9 Exception raised
[fhe call summary is now
jbuplicate JSN detected
Date:02-Nov-2010 16:22:59 Uscr:Steve Parker
[the Business Impact has been update
support overhead currently 30 incidents in 5 days. Resoluton will mean that any future occurrences will have a different root cause
land require investigation. Such incidents are currently getting masked by the volume associated with this Peak with consequential
risk to the integrity of the audit trail used for litigation support.
Jbate:02-Nov-2010 16:26:34 Uscr:Steve Parker
Jo3.20 is not due until early next year. Given an average of 30 calls / week this will result in approx 300 support incidents before
resolution representing 100 MD effort at 3rd line.
JDate:5-Nov-2010 15:07:17 Uscr:deevan Mithyantha
jpplied patches to CTRO3 20 00 RELEASE and smoke tested successfully.
Following file has been committed to CTRO3_20 00 RELEASE branch.
Hh) MessageJournalFilter.java -- 1.28.14.1
2) MessageJournalDAO. java -- 1.7.48.1
8) BranchAccessFilters/junittest /MessageJournalFilterTest.java -- 1.15.164.1
FUJ00225940
FUJ00225940
fa) BranchAccessFilters/junittest/beantactory-aml == Te
Jbate:16-Nov-2010 08:09:00 User:Jeevan Mithyantha
lAction placed on Team:xCtr_GDC
lbate:16-Nov-2010 08:09:13 User:Jeevan Mithyantha
[fhe Call record has been transferred to the team: xCtr_REL GDC
Progress was delivered to Consumer
jDate:22-Nov-2010 10:57:22 Usecr:Kishor GaneshRao
[this peak has not been verified in 4LS CCIT due to the fact that it is not reproducible.
tn CCIT, this particular scenario can't be tested, as we can't reproduce the late arrival of the request in OSR side.
ut note that this has been successfully tested in the GDC DEV rig by using the Debug option.
lDate:22-Nov-2010 10:57:46 User:Kishor GaneshRao
Reference Added: Product Baseline BAL SRV OSR 0320 V238 @ BAL SRV_OSR ROUTING 0320 v238
Jate:22-Nov-2010 10:57:48 User:Kishor GaneshRao
TOP Reference set to: Product Baseline BAL_SRV_O:
0320 _V238 & BAL_SRV_OSR_ ROUTING 0320 _v238
JDate:22-Nov-2010 1
FIX RELEASE CHECKLIST
9:21 User:Kishor GaneshRao
lrIX IMPACT TEMPLATE FULLY COMPLI
ves
IMF APPROVAL GRANTED?
ves
CODE REVIEW TEMPLATE FULLY COMPLETED?
ves
CODE REVIEW PASSED?
ves
CODE CHECK-IN BRANCH SPECIFIED?
ves
JALIL, CHECKED-IN FILES HAVE PEAK REFERENCE IN CVS COMMENT?
ves
TX PASSED CIT AND REGRESSION TESTING?
No, this fix has not been verified in CIT due to the fact that we are not able to reproduce the same, but note that this has been
verified successfully in GDC DEV rig by the developer.
KEI, UPDATED TO REFLECT PEAK FIX?
ves
cIT TEST SCRIPT UPDATED TO REFLECT PEAK?
INo, due to the fact that the change cannot be tested in CIT.
cI TEST RESULTS PUBLISHED?
ves
bate: 22-Nov-2010 11:18:12 User:Kishor GaneshRao
[the Call record has been assigned to the Team Member: Kishor GaneshRao
progress was delivered to Consumer
Date:01-Dec-2010 15:20:03 Uscr:PIT Automated User
Reference Added: Product Baseline BAL SRV _OSR_0320_V239
Reference Added: Product Baseline BAL SRV_OSR ROUTING 0320 V239
jbate:02-Dec-2010 15:15:04 Uscr:PIT Automated User
Reference Added: Product Baseline BAL SRV_OSR ROUTING 0320 D239
FUJ00225940
FUJ00225940
bate:02-Dee-2010 15:20:03 Uscr: Pit Automated User
Reference Added: Product Baseline BAL _SRV_OSR 0320 D239
Date:03-Dec-2010 09:39:46 User:Kishor GaneshRao
[Start of Response]
loving the Peaks to INT
[End of Response]
esponse code to call type J as Category 48
Date:03-Dec-2010 09:42:22 User:Kishor GaneshRao
the Call record has been transferred to the team: Development calls ready for Integration
the Call record has been assigned to the Team Member: Unassigned_
Date: 06-Dec-2010 14:3)
Reference Added: Relea
21 User:Tyrone Cozens
EAK PCO206867
JDate:30-Dec-2010 11:32:02 User:Sheila Bamber
lfested in LST - Please close
jbate:30-Dec-2010 11:32:18 User:Sheila Bamber
[the Call record has been transferred to the team: Live Supp.Test
the Call record has been assigned to the Team Member: Release to Live
Progress was delivered to Consumer
jate:16-Mar-2011 17:20:54 User:Mark Ascott
[the Call record has been transferred to the team: RM-x
Progress was delivered to Consumer
Jate:22-Nov-2011 13:34:57 Uscr:John Simpkins
[Start of Response]
identified for closure following review of open un-targeted peaks in October 2011. Closure requested by Saheed Salawu
[End of Response]
Response code to call type J as Category 63
service Response was delivered to Consumer
Joate:22-Nov-2011 13:34:59 User:John Simpkins
caLL Pc0204310 closed: Category 63 Type J
Root Cause General - Unknown
Logger _Customer Call_ -- EDSC
Subject Product HNG-X Platforms -- BAL Server (BAL) (version unspecified)
Assignee _ Customer Call_ -- EDSC
Last Progress 22-Nov-2011 13:34 -- John Simpkins