To mitigate "Did not get a response from the MID server" error

soham_dutta
Kilo Explorer

‎12-22-2019 07:00 AM

Our scheduled job runs daily to fetch records from another system. Recently, the data source is facing the issue of "Did not get a response from the MID server" or "Did not get a response from the MID server after 305 seconds", though the same midserver being used in other jobs/data sources are working fine. So we are planning to extend the 305 seconds limit by implementing the system properties 'glide.jdbcprobeloader.retry' and 'glide.jdbcprobeloader.retry_millis'.

It would be great to have some insight on the impacts of this on global scale, if anyone has implemented the same before. Many thanks.

Labels:
0 Helpfuls
  • 2,395 Views
2 REPLIES 2

Ashutosh Munot1
Kilo Patron
Kilo Patron

‎12-22-2019 09:45 AM

Hi,

Before doing this, did you check why it is not getting response in specified time. It should get response in this 305 seconds. Is there anything blocking from another system. Check that and then decide to increase this time.


Thanks,
Ashutosh

0 Helpfuls

soham_dutta
Kilo Explorer
In response to Ashutosh Munot1

‎12-23-2019 11:24 PM

Hi Ashutosh, 

 

I am yet to determine the cause actually. While doing a low level validation, in the mid server logs, I can see that error has occurred while executing the sql query on the other system. So could it be that the midserver trying to fetch the records is working fine, but probably theres some issue with the system at the other end? Thanks.

 

Regards,

Soham

0 Helpfuls