Support #4418

[SCP ID :##2267##] : Unable to receive SMS notification

Added by William Gozali Tan over 10 years ago. Updated about 10 years ago.

Status:Closed - End of life cycleStart date:May 28, 2014
Priority:NormalDue date:
Assignee:Wijaya Kartono% Done:

30%

Category:RIBSpent time:-
Target version:-

Description

Please attend to customer's enquiry below:

Customer transfer to Maybank on 23/05/2014 10:16:39 AM.
Transaction Accepted and have deduction in her account.
Customer inform did not get any SMS notification after do this transaction

Below are the customer details :

1. Customer Name: SITI SALMAH BINTI AHMAD SAFARI
2. CIF No. : 280179007
3. Account No. : 1007021000053978
4. Third Party account no. : 114011471380
5. Transaction Date/ Time : 23/05/2014 10:16:39 AM
6. Type of transaction: New Interbank GIRO Transfer
7. Transaction Status: Accepted
8. Error message displayed: could not insert: [net.penril.ibss.core.hibernate.SmsTable]

History

#1 Updated by William Gozali Tan over 10 years ago

  • Subject changed from [SCP ID :##2267##] : [Request ID :##39736##] : LIVE: Bill Payment Problem to [SCP ID :##2267##] : [Request ID :##39736##] : Interbank Transfer issue

#2 Updated by William Gozali Tan over 10 years ago

  • Subject changed from [SCP ID :##2267##] : [Request ID :##39736##] : Interbank Transfer issue to [SCP ID :##2267##] : Interbank Transfer issue

#3 Updated by Wijaya Kartono about 10 years ago

  • Status changed from New - Begin Life Cycle to Development / Work In Progress

Error log:
"Error details : org.hibernate.exception.SQLGrammarException: could not insert: [net.penril.ibss.core.hibernate.SmsTable]
...
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Lock request time out period exceeded."

Root cause:
- Lock request time out period exceeded.
"Microsoft SQL Server has a setting to define the amount of time to wait for a lock before timing out:
LOCK_TIMEOUT is set per transaction and its default value is '-1', which means the attempt to acquire a lock never times out."
-
http://www-01.ibm.com/support/docview.wss?uid=swg21458491

*Lock is used for concurrency control to prevent the user from update same data at the same time and seeing out-of-date data while another user is updating the same data.
- http://pic.dhe.ibm.com/infocenter/soliddb/v6r5/index.jsp?topic=%2Fcom.ibm.swg.im.soliddb.sql.doc%2Fdoc%2Fthe.purpose.of.concurrency.control.html

Will discuss the solution with Hazri Ahmad, William Gozali and Ngoh Chee Ping.

#4 Updated by Tan Lee Yong about 10 years ago

  • Project changed from RIB to Agrobank Support
  • Category set to RIB

#5 Avatar?id=1733&size=24 Updated by Ahmad Hazri about 10 years ago

Hi Ton

According to this blog - http://weblogs.asp.net/jeffwids/lock-request-time-out-period-exceeded, you can check which/who is holding the request to DB.
Based on that maybe you can fine tune the query to avoid being locked again.

Or

We can increase the LOCKTIMEOUT at WebSphere from 2000 ms to 2500 or more if the that particular query need more time.

#6 Updated by Lizahwati Basirun about 10 years ago

  • Subject changed from [SCP ID :##2267##] : Interbank Transfer issue to [SCP ID :##2267##] : Unable to receive SMS notification

#7 Updated by Wijaya Kartono about 10 years ago

  • % Done changed from 0 to 30

I already inform user to increase lockTimeout value and restart database.
Although, it only serve as temporary solution. Meanwhile, I am looking for better solution.

Actions taken to identify the root problem:
1. Identify any transaction to database that might take much time to perform.
2. Identify if any network connection issue (will liaise with the user).

Candidate solution:
1. Reduce amount of data retrieved from database per transaction to reduce transaction time. (e.g. Instead of pulling all data for user/trnx inquiry, now it will pull page by page.)
2. Apply indexing to transaction history table. It will reduce transaction time for transaction enquiry.

#8 Avatar?id=1733&size=24 Updated by Ahmad Hazri about 10 years ago

  • Status changed from Development / Work In Progress to Closed - End of life cycle

No update from customer.
case closed.

Also available in: Atom PDF