Subversion Repositories SmartDukaan

Last modification

• Rev 37360 – 51 d 5 h
• Author: amit

• Log message:

  ICICI policy issuance: stop losing policies to a proposal read timeout
  
  hitAfinityProposal called ICICI's gadget proposal endpoint on the default 10s socket
  timeout. That POST issues the policy, so a read timeout abandons a request ICICI is
  still completing. The exception then unwound through generateIciciLombardPolicy into
  the controller's @Transactional(rollbackFor = Throwable.class), rolling back the whole
  request - including the wallet debit - before the tracker row was ever touched. Result:
  policy possibly live at ICICI, no trace on our side, and the 'policy already exists'
  retry path dead-ends because its Redis cache is only written on a parsed success.
  
  - Proposal and policy-certificate calls move to a dedicated RestClient built on
  HttpClientFactory.insuranceIssuanceRequestConfig() (socket 45s). JWT and quote stay
  on the default client - fast, and no remote write.
  - Transport failures are classified via HttpTransportFailures and reported as 'outcome
  unknown', not as an ICICI rejection.
  - IciciPolicyTrackerBookkeeping writes the tracker in REQUIRES_NEW, so both the UNKNOWN
  outcome and the issued policy number survive the request rollback. Recovery from an
  UNKNOWN row is the existing recoverPolicyNumberByProposalNumber path.
  
  Code only, no DDL: status is varchar(20) and remarks is text on prod already.