Support #8888
SCP ID :##4799##] : Production TAC Expiry
| Status: | Closed - End of life cycle | Start date: | November 28, 2018 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Zahir Abd Latif | % Done: | 100% | |
| Category: | MY RIB | Spent time: | - | |
| Target version: | - |
Description
Hi,
Kindly attend below request:
Please help to check on the TAC expiry period as it is not behaving as per defined in upass.cfg.
I've tried with one transaction and key in the TAC after 5 minutes, it still can be used and transaction was succesful.
However, this behaviour is not happend in UAT as it prompted 'TAC Invalid' key in the TAC after exceed the timeout specified in the upass.cfg.
Kindly confirm the expiry period is 5 minutes. Below is the setting taken from production.
#TAC timeout in Sec
TAC_LIFTSPAN_TIMEOUT=7200
TAC_DEFAULT_TIMEOUT=300
TAC_MAX_ERROR=3
TAC_REPEAT_TIMEOUT=180
History
#1
Updated by Zahir Abd Latif over 5 years ago
- Status changed from New - Begin Life Cycle to Closed - End of life cycle
- Assignee changed from Hafizudin MD to Zahir Abd Latif
- % Done changed from 0 to 100
Hafiz, Dec 18, 2018 04:58 PM:-
From our investigation. We found upass.cfg (framework 0 & 1) for parameter "TAC_DEFAULT_TIMEOUT=900" and "TAC_REPEAT_TIMEOUT=900". Please follow instruction below to update upass.cfg. Change step:- 1) Stop all server (framework 0,1,2,3) 2) Edit upass.cfg(Framework 0) 3) change parameter "TAC_DEFAULT_TIMEOUT=300" and "TAC_REPEAT_TIMEOUT=180" and save 4) please copy upass.cfg from framework 0 and paste to framework 1,2 and 3 5) Start Server ** Please make sure upass.cfg setting at DR server is follow Production server and database setting at upass.cfg(DR) remain same as DR database setting
Kah Yan, Jan 4, 2019 11:26 AM:-
Dear Shikin, As per yesterday, we have identify upass in all instances ib03 (bv0,bv1) and ib04 (bv2,bv3). Kindly implement the guide provided by Hafiz to change TAC timeout value in all framework and in DR.
Issue closed in SCP.