Support #6303
[SCP ID :##3163##] : eCustody - client did not receive the SMS - Urgent
| Status: | Closed - End of life cycle | Start date: | June 02, 2016 | |
|---|---|---|---|---|
| Priority: | Urgent | Due date: | ||
| Assignee: |  Zahir Abd Latif | % Done: | 100% | |
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
Hi,
Kindly attend below request:
There are customer that not receive sms when bank admin create user or reset password. From last 7 days logs,
I found that there are error when sending the sms.
Can you assist us to identify why sms failed to send to customer.
History
#1
Updated by Zahir Abd Latif over 8 years ago
- Project changed from Maybank RCAS Support to Maybank CAS Support
#2
Updated by Ong Wei Kuan over 8 years ago
Summary :
1. Get the response and app server log file from bank on 13-06-2016
2. Replied on 13-06-2016, ask to check at SMS DB log, to confirm if there is any login error from user 'bzbackends' being caught at time around 2016/06/09 09:35:12:389 and 2016/06/09 19:22:38:983.
Summary of investigation :
1. Suspect invalid of login credentials to SMS DB
Based on the log file, system captured SQL error indicates that there is login issue to SMS DB
Log snippet :
2016/06/01 14:52:01:837 ERROR com.upass.integration.SMSmgc: Login failed for user 'bzbackends'.
Exception class : com.microsoft.sqlserver.jdbc.SQLServerException, class method : makeFromDatabaseError, line number : 156
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:156)
com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:240)
com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:78)
com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:2636)
Feedback :
However, Based on bank's reply, able to connect to SMS DB using the same login credential.
2. Suspect SQL Server DB upgraded to version 2012.
Suspect this issue might due to the restrict of database name in sql server 2012, where database name need to be specified to connect to DB. We suggested to add databaseName into the config parameter as below
jdbc.sqlserver://172.31.36.84:1433;databaseName=?
*? = database name
FeedBack :
However, as confirmed from bank side, the DB in use is not SQL Server 2012.
3. Suspect network connection issue
Suspect there might be network connection issue to SMS DB. After Checked from SystemOut.log, there is no connection error caught and captured. Request bank assistance to check at DB log, to check the requests sent from CAS.
Log snippet :
2016/06/09 09:35:12:389 ERROR com.upass.integration.SMSmgc: Login failed for user 'bzbackends'.
2016/06/09 19:22:38:983 ERROR com.upass.integration.SMSmgc: Login failed for user 'bzbackends'.
Remarks :
Pending feedback from bank on the checking in db log.
#3
Updated by Ong Wei Kuan about 8 years ago
- Assignee changed from Ong Wei Kuan to Zahir Abd Latif
Hi Zahir,
This issue occurred after WAS upgraded. It has been resolved after Bank added additional jvm argument to enable the sslv3.
Since the issue is not from application side, we can close this case at our end. TQ
#4
Updated by Zahir Abd Latif about 8 years ago
- Status changed from New - Begin Life Cycle to Closed - End of life cycle
- % Done changed from 0 to 100
Issue closed in SCP.