The first problem troubleshooting process of re disk

Problem description

A contract cannot be signed successfully

The screening process

First, there is no problem in signing other contracts , The only problem is the contract for the new project

See if the log request returns read time out abnormal

Possible causes of this problem

1. Someone in a certain place changed the relevant overtime for him , Is unlikely to

2. There's something wrong with this file

（ The final confirmation is that the file is too large , The timeout in the process of sending it to a third party for processing and then taking it back leads to problems ）

Link grooming

The request link of the whole service is combed

app Of react-native Request method ② -> Native request methods ->nginx ->springMVC A back-end framework made by the company

-> Another self-made middleware -> Total services tomcat End initiator （cfca client ）->（ Intermediate gateway ①）->cfca Server side

Response link sorting  

cfca Server side ->（ Intermediate gateway ①）->  Total services tomcat End initiator （cfca client ）-> Another self-made middleware ->springMVC A back-end framework made by the company -> Native accept response ->app Of react-native Received results ②

Through the time analysis of logs and subsequent cooperation tests

Confirmation is cfca The processing time of our signature service contract documents is too long

He will cause problems in two places

One is marked red Intermediate gateway   There will be a limitation on the session time , It will cause the conversation not to be maintained for more than a little time , Directly return to session expiration

One is blue app Of react-native Request and response ②  There will be timeout settings , After the time has expired, return to the disconnected session first

Problem solving

Finally, the solution discussed by all involved parties is that the process and result of contract generation are asynchronous

take app After the signing request of is sent to the backend , Is to store its relevant data in the table , Save successfully and return to the user “ The contract is being generated ”, Then a schedule will be created , Run once per second , There is no related data generated in the traversal table , In the end update, The files are stored on the server , Finally, update the contract status from “ The contract is being generated ” To “ Check the contract ” when insert go in