Subversion Repositories SmartDukaan

Last modification

• Rev 37452 2026-08-29 07:24:31
• Author: amit

• Log message:

  Fix e-invoice IRN failure when the NIC auth token is about to expire
  
  NIC reissues the same auth token until it genuinely expires, so evicting the cache
  inside the 5 minute leeway hands back the identical near-dead token. getAuthenticatedHeaders
  checked the leeway once, before that re-fetch, and never inspected what came back.
  NSUPHR1770 filed with a token that had 12 seconds of life left and the gateway answered
  412/GSP752 'eInvoice AuthToken not found or expired'; the invoice filed a minute later,
  past the expiry and so on a genuinely new token, succeeded.
  
  getUsableAuthToken re-checks the refetched token and, when it is still inside a 60s
  floor, waits out the remainder before minting again. The wait is bounded by that floor
  and every caller on this path is a cron/async thread already running against a 60s NIC
  timeout with no transaction held open.
  
  Also make the gateway's own failures legible. NIC rejections arrive as
  {Status, ErrorDetails}, but failures the ASP raises in front of NIC use
  {status_cd, error{error_cd, message}}, which shares no field name with RespPl: Gson
  produced an all-null object and the stored reason degraded to the literal
  'RespPl{Status=0, Data=null, ErrorDetails=null, InfoDtls=null}', indistinguishable from
  NIC rejecting the document. RespGSPErr already modelled that envelope but was a
  non-static inner class and so could not be instantiated by Gson; made it static and
  copy the code and message into ErrorDetails, which every caller already reads.