none
Request timeout error on Windows Azure in-role cache

    Question

  • We use dedicated role cache, it works fine when we deploy solution to azure, but after it run few days we got many exception suddenly:

    Microsoft.ApplicationServer.Caching.DataCacheExceptionErrorCode<ERRCA0018>:SubStatus<ES0001>:The request timed out.. Additional Information : The client was trying to communicate with the server: net.tcp://xxx.xxx.xxx.xxx:20004/.</Message>
      <Detail>   at Microsoft.ApplicationServer.Caching.DataCache.ThrowException(ErrStatus errStatus, Guid trackingId, Exception responseException, Byte[][] payload, EndpointID destination)
       at Microsoft.ApplicationServer.Caching.SocketClientProtocol.CreateRegion(String region, IMonitoringListener listener)

    ----------------------------------------------------------------------------------------------------------------------------

    Microsoft.ApplicationServer.Caching.DataCacheException: ErrorCode<ERRCA0018>:SubStatus<ES0001>:The request timed out.. Additional Information : The client was trying to communicate with the server: net.tcp://xxx.xxx.xxx.xxx:20004/.
       at Microsoft.ApplicationServer.Caching.DataCache.ThrowException(ErrStatus errStatus, Guid trackingId, Exception responseException, Byte[][] payload, EndpointID destination)
       at Microsoft.ApplicationServer.Caching.SocketClientProtocol.Get(String key, DataCacheItemVersion&amp; version, TimeSpan&amp; timeout, ErrStatus&amp; err, String region, IMonitoringListener listener)
       at Microsoft.ApplicationServer.Caching.DataCache.InternalGet(String key, DataCacheItemVersion&amp; version, String region, IMonitoringListener listener)

    it happens on one Web role, other web roles are works fine, so it is not cache server issue. I have to reboot the webrole, after reboot, this issue is gone.

    what's this error means? how should I avoid this error?

    Wednesday, March 05, 2014 9:50 AM

Answers

All replies

  • Hi,

    The error message "The request timed out.. Additional Information : The client was trying to communicate with the server: net.tcp://xxx.xxx.xxx.xxx:20004/" means there was some issue in communicate with the cache server, if you reboot the webrole, how long the normal state will last? when the error occurred, we need check the address was correct or not, the server was running well or was busy, etc.. Hope this helps, if not, please give further information to us.

    Best Regards


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Thursday, March 06, 2014 6:09 AM
    Moderator
  • I checked the server address, it is correct, and find out this error happens when available memory is very low. thanks for your help.
    Friday, March 07, 2014 3:48 AM
  • Dear Jason,

    I checked the server address, it is correct, and find out this error happens when available memory is very low. thanks for your help.

    It Seems you have found the issue, and I will mark your post as answer.

    If have any issues, welcome to our forum!

    Best Regards


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, March 10, 2014 1:43 AM
    Moderator