FUJ00081867
FUJ00081867
Peak Incident Management System
Call Reference PC0197409 Call Logger _ Customer Call_ -- EDSC
Release Released At -- HNG-X 01.22.00.40 Top Ref BAL _SRV_OSR_0122 D058-D057
Call Type Live Incidents/Defects Priority A -- Business stopped
Contact -EDSC Call Status Closed -- S/W Fix Available to Call Logger
Target Date 08/04/2010 Effort (Man Days) 0
Summary FADS519246 balancing and has Error Code: 0784 / 0783
All References Type Value
TRIOLE for Service 2211200 :
Product Baseline BAL_SRV_OSR_0122 D058-D057
DevintRel-Director ITU SV&I
Release PEAK PC0198579
Product Baseline CTR_APP_X0122_V050
SSCKEL IKEL cardc2043L.
Release PEAK ‘PC0198536
SSCKEL KEL cardc2043L
Progress Narrative
foate:07-Apr-2010 15:05:29 User: Customer Call_
ALL PCO197409 opened
etails entered are:~
ummary:Pm reported that she is balancing and has MSG 0784
call Type: L
call Priority:¢
flarget Release: 186
Routed to:EDSC - _Unassigned_
Priority: C
kontact Name:
contact Phone
riginator: XxX
riginator's reference
Product Serial No?
leroduct Site: 519246
Ibm reported that she is balancing and has MSG 0684
Incident History:
b010-04-07 14:37:24 [ Badenhorst, Jean Paul]
INIT : create a new request/incident /problem/change/issue
010-04-07 14:39:46 [ Badenhorst, Jean Paul]
neun_en_rmg : Open Notification
2010-04-07 14:39:46 [ Badenhorst, Jean Paul]
bneut en rmg : Transfer Notification
010-04-07 14:40:45 [ Badenhorst, Jean Paul]
0G : PM was doing her EOD stock balancing and this message has come up
lM is trying to go to
balance period-02
Htraining period-01
stock unit-AA
010-04-07 14:43:37 [ Badenhorst, Jean Paul]
FLD : FIELD-'zcbflag' OLD='NO' NEW='YES'
b010-04-07 14:54:37 [ Badenhorst, Jean Paul]
B : Called PO-advised pm to log out and back in.
Jom cant log out came up with “system error MSG 0783"
lspoke to Sean on HNG core team-checking events and KEL's- checked for Kels no relevant Kel's for this
FUJ00081867
FUJ00081867
mis unable to leg outs
010-04-07 14:56:27 [ Badenhorst, Jean Paul]
JfLD : FIELD='summary' OLD='Pm reported that she is balancing and has MSG 0684' NEW-'Pm reported that she is balancing and has MSG
e784"
010-04-07 14:56:32 [ Badenhorst, Jean Paul]
Loc : We have recieved a fair amount of calls with the same issue "MSG 0784" and "MSG 0783" and both state the same Error text
system error"
several sites have attemped Reboots and where able to log in but still coming up with the same error message.
010-04-07 14:59:00 [ Badenhorst, Jean Paul]
ftoG : This call is the master call for issue please insert all updates into this call.
fuink all other calls to this as parent.
2010-04-07 15:04:42 [ Badenhorst, Jean Paul}
ffR : Transfer assignee from ‘Badenhorst, Jean Paul' to
f'ransfer group from 'HSH2' to 'PEAK*
2010-04-07 15:04:42 [ Badenhorst, Jean Paul]
neut_en_rmg : Transfer Notification
te:07-Apr-2010 1
It have upgraded the call and v
7:04 User:_Customer Call_
ced PEAK.
[Date:07-Apr-2010 17:40:04 User:
d Mike Stewart of upgrade
‘Customer Call_
07-Apr-2010 17:40:35 User:_Customer Call_
je have had another PM ring in about this, hence the upgrade. Hamid from Frontline is adding the details now.
[pate:07-Apr-2010 17:
product HNG-X Counter
I User:John Simpkins
BUC-BranchAccounting (version unspecified) added.
jDate:07-Apr-2010 18:28:38 User:John Simpkins
fhe call Priority has been changed from C
fhe call Priority is now A
Date:07-Apr-2010 16:37:52 Uscr:John Simpkins
[Start of Response]
Itcoking at the PostOfficeCounter logs for a couple of sites this appears to be caused when the audit messages are not committed. The
next audit message is not allowed to be committed whilst an earlier one has not been comfirmed to have been committed.
IMAttempt made to send a second auditable message before the first one has returned"
[there are several other PEAK covering this
Ipco194805 - This problem is similar to the issue mentioned in the peak PC0194931. For whi
woposed a KEL. So I think we can mark this as duplicate of PC0194931
Vivek has provided the solution and also
Ic0194931 - This is a duplicate peak. This issue has already been raised as part of PC0193523.
PC0193523 - This relates just to the Change Password code section.
[End of Response]
eaponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
Response was delivered to Consumer
jbate:08-Apr-2010 08:04:57 User:Lorzaine El
fhe call summary has been changed from:
Pm reported that she is balancing and has MSG 0784
Ihe call summary is now:
rAD519246 balancing and has MSG 0684
[Date:08-Apr-2010 08:22:14 Uscr:_Customer Call_
If there is new diagnostic information available in an alternative KEL can you let HSD know the KEL reference is. We have searched
land can only find the Dave Seddon KEL that does not apply to these calls. We do not have the ability to look up PEAK references and
ro alternative Triole call reference is mentioned. We have had sites continue to call in this morning and a handful that logged OOH
oicemail calls reporting this issue.
jate?08-Apr-2010 08:44:06 User: Steve Parker
[fhe Call record has been assigned to the Team Member: Cheryl Card
rogress was delivered to ¢
FUJ00081867
FUJ00081867
[atcr08-Ape-2010 08:44:17 User! Steve Parker
[the Call record has been assigned to the Team Member: Cheryl Card
Progress was delivered to Consumer
Date:08-Apr-2010 09:02:44 User:Gheryl Card
he call summary has been changed from:—
IfAD519246 balancing and has MSG 0684
[he call summary is no
rADS19246 balancing and has Error Code: 0784 / 0783
Date:08-Apr-2010 11:24:12 Uscr:Anne Chambers
Laut i
Te:08-ApE-2010 11:37:13 User:gohn Simpkins
evidence Added - 353217 message. lou
~e:08-Apr-2010 11:37:33 User: John Simpkins
Evidence Deleted ~ 353217 message. log
e:08-Apr-2010 1:
[Start of Response]
Ihe clerk was rolling over stock unit AA. At 13.28 GM? she pressed the Confirm button and got a s
[the es log shows
ti:
IRRELEVANT
8:56 Uscr:Gheryl Cara
stem error with error code 0437.
ntime exception occurred while accessing service at URL:
After this the clerk got several system errors with error codes 0784 and 0783
counter had to be rebooted the clear the errors.
Please investigate the cause of the runtime exception and error 0437.
KEL cardc2043L raised to document the problem and workaround.
[End of Response]
sponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
esponse was delivered to Consumer
JDate:08-Apr-2010 11:51:21 Caer: GRAY Card
Isvidence Added = Lo! 08033 on_0
joate:08-Apr-2010 11:52:05 User:Gheryl card
he Call record has been transferred to the team: xCtr_GDC
Jser:Cheryl Card Confirmed that this Incident may be passed to the external company with the attacl
ogress was delivered to Consumer
ed evidence.
[ate:08-Apr-2010 12:30:39 Uscr:Ravindra Kumar
Ihe Call record has been transferred to the team: xCtr_CSM GDC
[fhe Call record has been assigned to the Team Member: Deepak Kumar
progres
was delivered to Consumer
[Date:08-Apr-2010 12:44:13 Uscr:Deepak Kumar
[the call summary has been changed from:-
IFAD519246 balancing and has Error Code: 0784 / 0783
[fhe call summary is nov
"AD519246 balancing and has Error Code: 0784 / 0783
[Date:08-Apr-2010 1.
evidence Added - Bran.
tJohn Simpkins
Mes gq ext
Date: 08-Apr-2010 13:16:11 User:gohn Simpkins
Evidence Added - Branch 353217 Postofriced
Jbate:08-Apr-2010 14:44:15 User:Deepak Kumar
[Start of Response]
his is a duplicate peak. The same issue has been addressed in PCO194931.
Ihe issue has been fixed by Steve CTRO25 09 HOTFIX addressing the peak PC0195238.
[End of Response]
esponse code to call type L as Category 40 -- Pending
esponse was delivered to Consumer
1
cident Under Investigation
~e:08-Apr-2010 14:45:16 User:Deepak Kumar
[fhe Call record has been transferred to the team: xCtr_Per GDC
Ihe Call record has been assigned to the Team Member: Ravindra Kumar
ogress was delivered to Consumer
FUJ00081867
FUJ00081867
[later08-Apr-2010 T!
[Start of Response]
fhe log contains the following:
10-04-07 13:33:34,535 UTC [AWT-EventQueue-0] com. fujitsu.poa.ctre.businesslogic.startup.Exc
Attempt made to send a second auditable message before the first one has returned.
204 User: Ravindra Kumar
ptionHandlerBLO ERROR - [] []- 0784:
his issue was fixed by peak PC0195238,
where if the immediate audit was not cleared, then the system will do a force logoff and
Kuring the force logoff,
the immediate audit stack will be flushed. And this fix was given in CTR025 09 HOTFIX.
[End of Response]
esponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
esponse was delivered to Consumer
ate: 08-Apr-2010 15:05:30 User:Ravindra Kumar
ction placed on Team:xCtr_OSR_SME, User:Steven Porter
‘bo? 08-ApE-2010 16:15:44 User: Steven Porter
[Start of Response]
ME Analysis Review:
ejected.
C0195238 simple changed the error handling for this situation so that the user experience was better.
It did not resolve the root
ause of this peak.
It have not looked at the evidence in any detail, but this particular peak has an interesting and a big hint from Chery] which
needs
to be looked at - see Cheryl's comment of 2010-04-08 11:48:56:
com. fujitsu.poa-nic.RequestExecutor WARN ~ {]
(J- Runtime exception occurred while accessing service at URL:
IRRELEVANT
his looks fairly fatal.
[End of Response]
esponse code to call type L as Category 40 -- Pending -~ Incident Under Investigation
esponse was delivered to Consumer
Te:08-Apr-2010 16:15:58 Uscr:Steven Porter
ction has been removed from the call
te:08-ApE-2010 1
[Start of Response]
SME Input = From looking at the code, it is fairly obvious that there's some kind of parsing problem.
9:33 User
Steven Porter
[this applies to evidence from both branch 353217 and branch 519246. This is a new issue that needs investigating.
i have to say I am very disappointed that this has not been picked up by GDC 4LS. It is very obviously where to start.
[End of Response]
fesponse code to call type Las Category 40 -~ Pending -- Incident Under Investigation
esponse was delivered to Consumer
[Date:08-Apr-2010 16:49:25 Uscr:Ravindra Kumar
[fhe Call record has been transferred to the team: xCtr CSM GDC
he Call record has been assigned to the Team Member: Deepak Kumar
rogress was delivered to Consumer
Te:08-Apr-2010 17:18:50 User: Steven Porter
[Start of Response]
jote, as taken from PostOfficeCounter.log (I've seen additional extracts)
branch 519246 = CTR 14 0 25 151 = CTRO25.07
ranch 353217 = CIR 14 0 25 151 = CTRO25.07
[End of Response]
Response code to call type L as Category 40 -- Pending -- Incident Under Investigation
lkesponse was delivered to Consumer
Jbate:09-Apr-2010 12:57:49 User:Deepak Kumar
[Start of Response]
[here are two issues that I can see:
h. Error : 0437
[his error happens when NIC gets exception executing the request.
FUJ00081867
FUJ00081867
P. Once the transaction, which is auditable, fails it starts giving error 0784/0783 becuase the previous auditable message had not
peen returned.
The issue #2 is being addressed in other peak i-e. PC0194931...
Ii think we should address only issue #1 in this peak.
Regarding issue #1 :
According to log reason is: "Error connecting to data centr
linputstream when it tries to access service.
", though it throws ClassCastException while parsing the supplied
equestExecutor WARN ~ [] []- Runtime exception occurred while
Bt Con fujitsu-poa. nie. shared. Communications .parseNormalResponse (Communications. jav.
bt com. fujiteu.poa.nic. Request Executor .makeHTTPRequest (Request Executor. java:373)
aused by: java.lang.ClassCastException
t com. fujitsu-poa-nic. shared. Communications .parseNormalResponse (Communications. javi
t com. fujitsu -poa.nic.RequestExecutor .makeHTTPRequest (RequestExecutor. java: 373)
--. 9 more
2010-04-07 13:28:56,784 UTC [AWT-EventQueue-0] Counter.ErrorMessages INFO - [] []- MSG90025: System Error - Error Code: 0437 has
pccurred
26)
leason: Error connecting to data centre-@@-
ut of course it does not look normal connection failure becuase normally it asks for retry instead of throwing exception.
[this PEAK belongs to NIC area
[End of Response]
esponse code to call type L as
kesponse was delivered to Consumer
ttegory 40 -~ Pending -~ Incident Under Investigation
jate:09-Apr-2010 13:01:45 Uscr:Deepak Kumar
ction placed on Team:xCtr_OSR_SME, User:Steven Porter
jDate:09-Apr-2010 14:13:50 User:Deepak Kumar
ction has been removed from the call
Te:09-Apr-2010 16:59:06 User: John Simpkins
evidence Added = 353217 Jog extract
[bate:09-Apr-2010 16:59:24 Uscr:gohn Simpkins
Wvidence Added ~ 519246 osr.log extract
joate:12-Apr-2010 11:59:41 User:Deepak Kumar
lhe Call record has been transferred to the team: xCtr_BAC_GDC
[the Call record has been assigned to the Team Member: Suresh Chitikela
Progress was delivered to Consumer
Te:i2-Apr-2010 16:34:03 User:Suresh Chitikela
[Start of Response]
analysis
joing through the postoffice counter log i can see there is problem occured in Communications. java while parsing the response from
the BAL.
It tried to reproduce the scenario in branch CTR_14_0 25 151 but not able to
reproduce
[End of Response]
kesponse code to call type L as Category 40 -- Pending
esponse was delivered to Consumer
Incident Under Investigation
jate:12-Apr-2010 16:34:31 User:Suresh Chitikela
ction placed on Team:xCtr_OSR_SME, User:Steven Porter
ateri2-Apr-2010 16:41:36 User
[Start of Response]
sz Guidance:
teven Porter
Ir suggest getting the osr message.log to see what response caused the Counter to blow up, Clearly the BAL could serialise the message
Iso why could the Counter not deserialise it.
Based on the evidence you should be able to guide SSC to locate the appropriate BAL message.
then you can investigate why the Counter could not parse it.
[End of Response]
FUJ00081867
FUJ00081867
sponse code to call type bas category 40 == Pending -= Incident Under Investigation
response was delivered to Consumer
[Date:12-Apr-2010 16:41:38 User:Steven Porter
Action has been removed from the call
Pori3-ApE-2010 1.
[Start of Response]
lfter going through the BAL message.log i can see the Response is received OK.
In Communications. java parseNormalResponse() method after receiving the reponse from BAL it is parsing the response xml string and
fenerating the root object of this xml using the dtotypemappings.
0:04 User:Suresh Chitikela
ror branch 353217 we got the message.log file and observed that after receiving the below response from the BAl we got the runtime
exception
3 OK, service url= [
‘com. fujitsu-poa.dto.reporting.GetReportDataResponseDI0 xmlns:direct ive="directive
ns: ref="ref"><BALProcessingTime>198</BALProcessingTime><Cutof fInfobist></CutoffInfolist><EarliestSURolloverDate>2010-03-
3100: 00:00.000Z</Earl iest SURO1loverDate><Of ficeF inancialYear>2009</OfficeF inancial Year><OfficeRol loverDate>2010-03-
31100: 00:00. 0002</OF FiceRol loverDate><OfficellP>12</OfficeTP><Report Data><Report Id><Report Id>2027</Report Id></Report Id><ResultSet><dir
lect ive:Entry Name='GetLocal Suspense ' ><Linkedhist><Dyno><di rect ive: Entry
jame=' prodId'><String>6295</String></direct ive:Entry><di rect ive:Entry
jame=' quant i ty'><OpeningBa lance . Quant it y><Va lue>1</Value></OpeningBa lance. Quant ity></di rect ive :Entry><di rect ive:Ent ry
* amount '><ProductFeeTotal . Amount><Amount>19.76</Amount></ProductFeeTotal Amount ></directive:Entry><di rect ive:Entry
jame=' Movement '><String>Y</String></di rect ive: Entry></Dyno><Dyno><di rect ive:fntry
lame=' prodid'><String>6297</string></directive:Entry><directive:Entry Name='quantity'><OpeningBalance.Quantity><Value>-
i</Value></OpeningBalance.Quantity></direct ive:Entry><directive:Entry Name="amount '><ProductFeeTot al .Amount ><Amount >=
9. 76</Amount></ProductFeeTotal .Amount></direct ive:Entry><directive:Entry
lame=' Movement '><St ring>Y</String></di rect ive: Entry></Dyno></LinkedList></directive:Entry></ResultSet><TimeStamp>2010-04—
1107:53:26.4212</TimeStamp></Report Data><Report Id><Report 1d>2027</Report 1d></Report Id><ServiceHandlerTimeTakenMi1lis>187</ServiceHan
HlerTimeTakenMi11is><SqlTimeTakenMi11is>182</SqlTimeTakenMi1lis><TradingDate>2010-04-
1707:53:26 .2352</TradingDate></com. fujitsu.poa.dto. report ing. GetReport DataResponseDTO>-@@-
[the above response looks fine to be parsed by the xml parser.
[End of Response]
Response code to call type L as Category 40 -- Pending —- Incident Under Investigation
lkesponse was delivered to Consumer
fe:13-Apr-2010 15:23:01 User:Suresh Chitikela
[Start of Response]
lin above reponse i can see the problem is the route object of the response xml (i.e)
com. fujitsu-poa.dto.report ing.GetReport DataResponseDTO>......</com. fujitsu.poa.dto. report ing.GetReport DataResponseDTO> which is
ausing the class cast exception
[End of Response]
esponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
esponse was delivered to Consumer
jDate:13-Apr-2010 16:10:08 User:Suresh Chitikela
ction placed on Team:xCtr_OSR_SME, User:Steven Porter
13-Apr-2010 16:55:01 User
[Start of Response]
jote that I have seen evidence of the same problem now in PC0197633, when relogon failed due to ClassCastException.
Steven Porter
[his peak seems to be fairly serious.
[End of Response]
esponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
esponse was delivered to Consumer
[Date:a3-Ape-2010 17:38:28 Uscr
[Start of Response]
IME Review:
iteven Porter
can you reproduce the issue? Your earlier statements are contraditory - in one place you say that the XML can be parsed, later that
setReportDataResponseDTO causes the problem.
fi don't think it is this, since I have seen similar issues in the peak I mentioned above, which is not report, but relogon
luthentication.
[End of Response]
esponse code to call type L as Category 40 -- Pending -~ Incident Under Investigation
esponse was delivered to Consumer
[Date:43-Apr-2010 17:38:30 Uscr:Steven Porter
ction has been removed from the call
FUJ00081867
FUJ00081867
[late:i4-Ape-2010 10:
[Start of Response]
analysis
234 User Suresh Chitikela
hH ) backoffice-->stockbalancing-->report
)after printing the final report counter asks for confirmation wheteher the print was successfull
)press confirm
4)At this point BAL sends a response and counter tries to parse this message
S)counter could not parse and blow up
benerally response comes like <GetReportDataResponseDTO>.......<GetReportDataResponseDTO> but in the message.log(we got it from the
SC for branches 353217 and 519246) file it is clear that response came like
com. fujitsu.poa.dto. report ing-GetReport DataResponseDTO>......</com. fujitsu-poa.dto. report ing.GetReportDataResponseDTO>
counter giving class cast exception because it is not able to cast com. fujitsu.poa.dto.reporting.GetReportDataResponseDTO to
bet Report DataResponseDTO
[End of Response]
esponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
esponse was delivered to Consumer
jbate:14-Apr-2010 10:39:12 User:Suresh Chitikela
ction placed on Team:xCtr_OSR SME, User:Steven Porter
Pori4-ApE-2010 11:45:57 User
[Start of Response]
SME Review
teven Porter
jot convinced. At Communications.java:126 the cast is to ResponseDTO. This should be a safe cast.
However, I have reproduced this using the first example I found in the logs, and it is indeed failing at this line.
lease investigate further. Root cause not yet understood.
[End of Response]
sponse code to call type L as Category 40 -- Pending
esponse was delivered to Consumer
Incident Under Investigation
jate:14-Apr-2010 11:46:08 Uscr:Steven Porter
Action has been removed from the call
[Date:14-Apr-2010 12:53:50 User
[Start of Response]
SME Guidance:
teven Porter
Hsing 519246 example. The message received at 010-04-07 13:28:56,573 UIC then fails parsing at 2010-04-07 13:28:56,593
Ihe message returned is a com.fujitsu-poa.domain.base.dyno.SimpleDynoImpl rather than a ResponseDTO.
It'd try to ascertain if this applies to older Counters and older OSRs.
so try to ascertain the OSR version that these peaks are being raised against.
[End of Response]
esponse code to call type L as Category 40 -- Pending
lkesponse was delivered to Consumer
Incident Under Investigation
5:08 User
[Date:4-Apr-2010 12:
[Start of Response]
For the above example, the actual message XML is
teven Porter
2010-04-07 13:28:56,573 UTC [Thread worker#:4] message_logger INFO - [] []- Response Received, Status OK, service url=
https: //vbal001: 9000/StockUnitRolloverBPService ] request id= [ 519246-1-V0-0713-37 ] content size= { 190 ]
com. fujitsu.poa.dto account ing.Rol1SUBPResponseDTO xmlns:directive="direct ive"
nins: ref="ref"><BALProcess ingT ime>99</BALProcessingTime></com. fujitsu.poa.dto.account ing. Roll SUBPResponseDTO>-@@-
shich is parsed to a Dyno, not a RollSUBPResponseDTO, hence why we get the class
exception.
leed to determine why this is the case.
[End of Response]
esponse code to call type Las Category 40 -- Pending -~ Incident Under Investigation
esponse was delivered to Consumer
Date:15-Apr-2010 08:50:27 User
[Start of Response]
(OTE: dtoTypeMappings supports XML element name of "
Steven Porter
01 1SUBPResponseDTO"
jit does NOT SUPPORT parsing com. fujitsu.poa.dto.accounting.Rol 1SUBPResponseDTO
FUJ00081867
FUJ00081867
fence I now think something has gone wrong In the serialisation on the BAL side.
[End of Response]
Response code to call type L as Category 40 -- Pending -- Incident Under Investigation
esponse was delivered to Consumer
[Date:46-Apr-2010 14:05:01 Uscr:Suresh Chitikela
[Start of Response]
frouting to BAl team for further investigation
[End of Response]
esponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
was delivered to Consume:
espons
Date:16-Apr-2010 14:05:26 Uscr:Suresh Chitakela
[fhe Call record has been transferred to the team: x0SR_GDC
he Call record has been assigned to the Team Member: Jeevan Mithyantha
Progress was delivered to Consumer
ater ?-ApE-2010 1
[Start of Response]
SME Guidance:
3:44 User: Steven Porter
It have now got to the root cause of this - a code fix to address the root cause will be required.
[End of Response]
Ikesponse code to call type L as Category 40 -- Pending —- Incident Under Investigation
esponse was delivered to Consumer
[Date:18-Apr-2010 14:43:40 User:Steven Porter
[Start of Response]
KEL PorterS199P raised.
[End of Response]
esponse code to call type L as Category 40 -- Pending
esponse was delivered to Consumer
cident Under Investigation
bate: 20-Apr-2010 1
[Start of Response]
see PC0196767 for details of the required fix.
6:04 User
teven Porter
[End of Response]
Response code to call type L as Category 40 -- Pending -~ Incident Under Investigation
esponse was delivered to Consumer
joate:2i-Apr-2010 14:02:37 User:_Customer call_
ebecca from POl rang for the latest position quoting Tfs 2238136.
ffs 2238136 call log refers to Tfs 2211200.
he asked what work was being carried out to identify what the problems were and what is being put in place so that it wouldn't
happen again.
[Date:21-Apr-2010 14:04:37 Uscr: Customer Call_
[ rang Steven Porter if he could further update this call with what the actual root cause of the problem was and what actions were
being put in place to prevent the problem happening again.
Steve confirmed that he would update this call.
jDate:21-Apr-2010 14:05:30 User:Steven Porter
[Start of Response]
root Cause: Code problem in the BAL. Threading issue.
reventative Measures: Code fix is planned for 01.22.00.00 release.
[End of Response]
esponse code to call type Las Category 40 -- Pending -~ Incident Under Investigation
lesponse was delivered to Consumer
jate:2i-ApE-2010 14:08:29 User: Steven Porter
[Start of Response]
SSC have been monitoring calls coming in which exhibit the evidence indicated in the KEL. This will alert us to potential isses; SSC
re not aware of “ClassCastExceptions" in any new calls this week, hence we are not anticipating the roll-over issue this Wednesday.
since it last occurred, the workarounds have been applied to reboot the BALs.
[End of Response]
esponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
esponse was delivered to Consumer
FUJ00081867
FUJ00081867
Date:22-Apy-2010 1.
[Start of Response]
Code changes for this peak is given as part of PC0196767.
2:03 User:deevan Mithyantha
code changes are reviewed and approved by Andy Thomas.
Following files have been committed to CVS branch "CTRO1 22 00_00_ RELEASE".
h) Parser. java -- 1.88.120.1
2) lypeMapper.java -- 1.25.226.1
b) Reflectutil.java ~~ 1,19.226.1
4) cutoffReport DAO. java ~~ 1.14.128.1
[End of Response]
esponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
Response was delivered to Consumer
pate: 22-Apr-2010 13:32:16 Uscr:Jeevan Mithyantha
Action placed on Team:xCtr GDC
joate:22-Apr-2010 13:32:27 User:deevan Mithyantha
he Call record has been transferred to the team: xCtr_REL GDC
rogress was delivered to Consumer
ate:22-Apr-2010 15:46:43 User: Tyrone Cozens
the call Target Release has been moved to Targeted At -- HNG-X 01.22.00
Date:22-Apr-2010 15:46:53 Uscr:Tyrone Cozens
(Start of Response]
Juthorised for 01.22.00.00 as agreed in RMF
[End of Response]
esponse code to call type L as Category 56 -- Pending -- Live Fix Authorised
esponse was delivered to Consumer
jbate:23-Apr-2010 11:54:02 User:Kishor GaneshRao
[Start of Response]
Iaseline: BAL SRV_OSR 0122 v058-v057
Release: BALO1.22.00.00
ig: 4LS$_CCIT
Nerified only the below mentioned scenario but couldn't observe any issues, Also please note that the inter dependent peak i.e.
PCO196767 is also updated with the further details in it,
cenario.
h) backof fice-->stockbalancing-~>report
b)after printing the final report counter asks for confirmation wheteher the print was successfull
b) press confirm
4) At this point BAL sends a response and counter tries to parse this message
Ib) Didn't observe any is
[End of Response]
response code to call type L as Category 56 -- Pending -- Live Fix Authorised
esponse was delivered to Consumer
Date:23-Apr-2010 11:54:09 User:Kishor GaneshRao
fhe Call record has been assigned to the Team Member: Kishor GaneshRao
Progress was delivered to Consumer
JDate:26-Apr-2010 16:22:38 Uscr:Kishor GaneshRao
[Start of Response]
Adding the counter baseline information also
[this peak is tested with the CTR APP xX0122_V050 at 4LS CCIT as part of CTRO1.22.00.00 release
[End of Response]
esponse code to call type L as Category 56 -- Pending -- Live Fix Authorised
esponse was delivered to Consumer
jDate:26-Apr-2010 16:30:26 User:Kishor GaneshRao
[the call Target Release has been moved to:Targeted At -- HNG-X 01.22
eference Added: Product Baseline CTR _APP_X0122 v050
[Start of Response]
joving to integration
[End of Response]
FUJ00081867
FUJ00081867
sponse code to call type b as category 48
[fhe Call re
gned
the Call record has been transferred to the team: Development calls ready for Integration
rd has been assigned to the Team Member: _Una:
728-Apr-2010 17:04:32 User:PIT Automated Usex
[Start of Response]
ssigning to Integrator
[End of Response]
fhe incident has been assigned to the Team Member: Rick
rogress was delivered to Consumer
jesponse code to call type Las Category 48 (Fix Released to PIT)
fhe incident has been transferred to the Team: Dev-Int-Rel
carter
abe:29-ApE-2010 1.
eferen
4:16 Uscr:Pat Automated User
Added: Product Baseline BAL SRV_OSR_0122 D058-D057 (TOP Reference)
jbate:29-Apr-2010 15:34:17 User: PIT Automated User
[Start of Response]
[End of Respot
se]
he incident has been transferred to the Team: Int-Rel
rogress delivered to Consumer
e@sponse code to call type L as Category 47 (Fix Processed by PIT)
eak has been test installed in Integration. Moving to holding stack awaiting release
Te:04-May-2010 1
2:47 User:Lionel Higman
[Start of Response]
"ix in LST release 01.22.00.40
[End of Response]
esponse code to call type L as Category 49
esponse was delivered to Consumer
[the call Target Release has been moved to:Released At -- HNG-X 01.22.00.40
Date:04-May-2010 17:13:18 Uscr:Lionel Higman
[fhe Call record has been transferred to the team: Live Support Team
[fhe Call record has been assigned to the Team Member: Una
gned
jate:06-May-2010 0!
ference Added: Rel
jate:06-May-2010 11:41:17 User:
eference Added:
[Date:d?-May-2010 11:13:42 User:Sheila Bamber
Passed test in LST - Please see release peak for details
[pate:47-May-2010 11:
3:50 User:Sheila Bamber
rogress was delivered to Consumer
Ihe Call record has been assigned to the Team Member: Release to Live
pate:07-Jul-2010 1.
[Start of Response]
plied 16/05/10
[End of Response]
0:08 User: Tyrone Cozens
esponse code to call type L as Category 60 -- Final -- 8/W Fix Released to Call
routing to Call Logger following Final Progress update.
jervice Response was delivered to Consumer
Logger
outing to Call Logger following Final Progress update.
Ikesponse was delivered to Consumer
Defect cause updated to 41 -- General - in Procedure
jate:07-Jul-2010 13:06:51 User:Lorraine Elliott
the Call record has been assigned to the Team Member: Cheryl Card
Progress was delivered to Consumer
Date:08-Jul-2010 11:55:16 User:Gheryl Card
[Start of Response]
low fixed in release BAL SRV_OSR_0122 V058-V057. Closing call.
[End of Response]
esponse code to call type L as Category 60 -- Final -- S/W Fix Released to Call Logger
jate:08-Sul-2010 11:55:16 Uscr:Cheryl Card
FUJ00081867
FUJ00081867
CALL POOISTAOS closed: Category G0 Type b
ate:08-Jul-2010 12:01:37 User:_Customer Call_
Consumer XXXXXX@TFS01 has acknowledged the call closure
Root Cause General - in Procedure
Logger _Customer Call_ -- EDSC
Subject Product HNG-X Counter -- BUC-BranchAccounting (version unspecified)
Assignee _ Customer Call_ -- EDSC
Last Progress 08-Jul-2010 12:01 -- Customer Call_