No. Based on the error message, it looks like the network connection is lost. If it only happens on the large file, maybe it’s because the operation takes too long.
The fact that the native svn client works makes me think it’s a problem with SVNKit, which is the java svn library used by the SonarQube scanner, unless it can be configured differently by the scanner to resolve the problem. SonarQube is already using the latest version of SVNKit so there isn’t an update we can try out.
SVNKit’s bug tracker is down so I can’t see if a related bug has been reported.
From here, I think the next step would be for you to try to get debug logs out of SVNKit, to see if any more details about the error are given.