That’s good. Now have a look at the link that I posted twice. In " standalone application" section it proposes to create ‘logging.properties’ file.
I would suggest the following content for this file:
# Rename this file to logging.properties to enable SVNKit debug logging.
# Log file will reside in your working directory.
handlers = java.util.logging.FileHandler
java.util.logging.FileHandler.pattern = C:/path/to/svnkit.log
java.util.logging.FileHandler.limit = 0
java.util.logging.FileHandler.count = 1
java.util.logging.FileHandler.append = true
java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter
In my example replace C:/path/to/svnkit.log with some path suitable for you. Once you create such logging.properties file, edit ‘jsvn.bat’ file in the following way. Find a line looking like:
set EXTRA_JVM_ARGUMENTS=-Djava.util.logging.config.file="%BASEDIR%\conf\logging.properties" -Dsun.io.useCanonCaches=false
then replace “%BASEDIR%\conf\logging.properties” with path to logging.properties file (prefer direct slashes ‘/’, e.g. C:/path/to/logging.properties) you’ve created before.
Now run ‘jsvn’ (once) to reproduce the problem. This will create more logging in ‘svnkit.log’ file. Make sure you have ‘svnkit.log’ with network data logged. Do NOT run ‘jsvn’ several times, to minimize relevant ‘svnkit.log’ file.
Now this ‘svnkit.log’ to some backup. Edit ‘logging.properties’ to replace FINEST with FINER everywhere. This will tell ‘jsvn’ to have less verbose logging. Again, run ‘jsvn’ to reproduce the problem. Now you’ll also have less verbose version of ‘svnkit.log’ (make sure this is so).
Finally, send/attach both files to us. We will analyze the logs and try to find out what’s wrong.