Skip to main content
Sitecore

Return to Answer

Fixed grammar and improved formatting.
Source Link
Sumit Helaiya
Sumit Helaiya
  • 3.2k
  • 2
  • 12
  • 23

Seems the connectivity between your CD servers and the xConnect server was not stablystable. Maybe when a website was running and sending the information to xConnect from which CD servers didn't receive the response in a timely manner.

It doesn't mean the xConnect getting any problems or errors.

If your xConnect is hosted under IIS in a separatedseparate application, you can try to look at its App Pool settingsApp Pool settings. Try to change the "Start Mode"Start Mode to "AlwaysRunning"AlwaysRunning and "Idle-timeout Action"Idle-timeout Action to "Suspend"Suspend. This can prevent IIS from terminating the xConnect when it reaches the "Idle-timeout"Idle-timeout (20 minutes as default).

Seems the connectivity between your CD servers and xConnect server was not stably. Maybe when website was running and sending the information to xConnect from which CD servers didn't receive the response in a timely manner.

It doesn't mean the xConnect getting any problems or errors.

If your xConnect is hosted under IIS in a separated application, you can try to look at its App Pool settings. Try to change the "Start Mode" to "AlwaysRunning" and "Idle-timeout Action" to "Suspend". This can prevent IIS terminating the xConnect when it reaches the "Idle-timeout" (20 minutes as default).

Seems the connectivity between your CD servers and the xConnect server was not stable. Maybe when a website was running and sending the information to xConnect from which CD servers didn't receive the response in a timely manner.

It doesn't mean the xConnect getting any problems or errors.

If your xConnect is hosted under IIS in a separate application, you can try to look at its App Pool settings. Try to change the Start Mode to AlwaysRunning and Idle-timeout Action to Suspend. This can prevent IIS from terminating the xConnect when it reaches the Idle-timeout (20 minutes as default).

Source Link
Jonathan
Jonathan
  • 131
  • 4

Seems the connectivity between your CD servers and xConnect server was not stably. Maybe when website was running and sending the information to xConnect from which CD servers didn't receive the response in a timely manner.

It doesn't mean the xConnect getting any problems or errors.

If your xConnect is hosted under IIS in a separated application, you can try to look at its App Pool settings. Try to change the "Start Mode" to "AlwaysRunning" and "Idle-timeout Action" to "Suspend". This can prevent IIS terminating the xConnect when it reaches the "Idle-timeout" (20 minutes as default).