Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

cacheFileConnect may leak threads/sockets

Description

The way that Roxie attempts to ensure that dafilesrv sockets are not retained for the fileUpToDate checks doesn't work if the connect times out - the thread keeps running.

Conclusion

None

Activity

Show:

Richard Chapman May 10, 2016 at 11:09 AM

Also looks like the timeout CAN now be configured (via setRemoteFileTimeouts)

Richard Chapman May 10, 2016 at 11:05 AM

I think the reason Roxie uses this mechanism is that the timeout on dafilesrv connects is not configurable. This is a hack to make sure it only delays 10 seconds rather than 15 minute when the dafilesrv is not available.

Richard Chapman September 9, 2015 at 2:56 PM

We discussed how we proposed to address this (I think just set the global timeout from Roxie and then delete the whole cacheFileConnect mechanism - can you confirm that is your recollection too?)

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Compatibility

Minor

Fix versions

Pull Request URL

https://github.com/hpcc-systems/HPCC-Platform/pull/8630

Created August 28, 2015 at 2:19 PM
Updated May 11, 2016 at 1:49 PM
Resolved May 11, 2016 at 1:49 PM