Bug #620
SL027 - successful prepaid not found in rpt
| Status: | Work Completed-End life cycle | Start date: | November 08, 2010 | |
|---|---|---|---|---|
| Priority: | Urgent | Due date: | ||
| Assignee: |  Sarinah Darsy | % Done: | 100% | |
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
5.11.10 - Successful tranx not found in Mobile Rpt, Recon File & Internet tranx
Pls regen recon file or provide the details necessary to regen recon file.
History
#1
Updated by Sarinah Darsy over 13 years ago
- Status changed from New - Begin Life Cycle to Pending Customer Feedback
- % Done changed from 0 to 100
Issue SL026 (failed prepaid not found in rpt) & SL027 refers.
I checked, that transaction on 2/11/2010, failed prepaid is not listed in the Internet Transaction Report because of the column inside IB_TRANSACTION_HISTORY for OTHER1 is not long enough.
2010/11/02 09:04:46:645 ERROR kfh.enterprise.services.GenericBVDataServicesImpl: Error details : SQL ErrorCode=0, State=null, Message=SQL ErrorCode=12899, State=72000, Message=ORA-12899: value too large for column "BVUSERPRD"."IB_TRANSACTION_HISTORY"."OTHER1" (actual: 58, maximum: 50)
For transaction dated 5/11/2010, checked at startManagedWebLogic.log and ALSBServer.log, there is errors stated for the 'IB Prepaid Top up' where it is caused by:
in startManagedWebLogic.log:
<Nov 5, 2010 12:09:36 PM MYT> <Error> <ALSB Kernel> <BEA-380001> <Exception on TransportManagerImpl.sendMessageToService, com.bea.wli.sb.transports.TransportException: Tried all: 1 addresses, but could not connect over HTTPS to server: 58.26.9.22 port: 33831
com.bea.wli.sb.transports.TransportException: Tried all: 1 addresses, but could not connect over HTTPS to server: 58.26.9.22 port: 33831
in ALSBServer.log:
<Nov 5, 2010 12:05:51 PM MYT> <Error> <ALSB Kernel> <kfhib05> <ALSBServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1288929951855> <BEA-380001> <Exception on TransportManagerImpl.sendMessageToService, com.bea.wli.sb.transports.TransportException: Tried all: 1 addresses, but could not connect over HTTPS to server: 124.82.136.30 port: 33831
com.bea.wli.sb.transports.TransportException: Tried all: 1 addresses, but could not connect over HTTPS to server: 124.82.136.30 port: 33831
All are pointing to that cause.
#2
Updated by Latipah Abdul Rashid almost 13 years ago
- Status changed from Pending Customer Feedback to Work Completed-End life cycle
Closed on 1/3/2011 and migrated to Production.