SVN connection denied by too frequent request of password

I get the following errors:

1. Repository initialize error:

Unable to initialise repository TEAM due to com.cenqua.fisheye.config.ConfigException:Could not access https://svn.sdsc.edu/repo/TEAM/ : org.tigris.subversion.javahl.ClientException: svn: E200015: authentication cancelled

2. Error from Test Connection:

SVN is requesting password too often for realm '<https: svn.sdsc.edu:443=""> SDSC Subversion Repository' and user 'fisheye_ro'

Unable to get info for the repository root for TEAM

svn: E200015: authentication cancelled

at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37)

at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32)

at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getNextAuthentication(DefaultSVNAuthenticationManager.java:215)

at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:583)

at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:286)

SVN is requesting password too often for realm '<https: svn.sdsc.edu:443=""> SDSC Subversion Repository' and user 'fisheye_ro'

Unable to get Repository Root URL for TEAM:https://svn.sdsc.edu/repo/TEAM/

SVN is requesting password too often for realm '<https: svn.sdsc.edu:443=""> SDSC Subversion Repository' and user 'fisheye_ro'

Exception getting FishEye access control

svn: E200015: authentication cancelled

at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:60)

at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)

at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.findStartingProperties(DAVUtil.java:136)

at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getBaselineProperties(DAVUtil.java:226)

at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getBaselineInfo(DAVUtil.java:184)

Error testing connection.

svn: E200015: authentication cancelled

at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:60)

at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)

at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.findStartingProperties(DAVUtil.java:136)

at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getBaselineProperties(DAVUtil.java:226)

at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getBaselineInfo(DAVUtil.java:184)

Connection failed.

3 answers

Hi Michael.

I'm suspecting that you may be experiencing this problem:

https://confluence.atlassian.com/display/FISHKB/Login+Fails+after+Updating+Subversion+Credentials

Could you please try that KB out and let me know if it helps.

Cheers,
Douglas Fabretti
Atlassian Support

The mentioned KB is not accessible throws 403 error, can you please check and post the updated link here...

 

your help is highly appreciated..

Thanks,

This abobe knowledge base article was not the solution in our case for the error.

What we found was that in the wrapper.conf (<InstallDir>\wrapper\conf\wrapper.conf) the following lines were present

wrapper.java.additional.11=-Dfisheye.inst="D:/fisheye-2.8.2/database"

wrapper.java.additional.12=-XX:MaxPermSize=128m

wrapper.java.additional.13=-Xrs

...

wrapper.java.additional.11=-XX:PermSize=256m

As a result the service could not find the database and went off to try the to create its own.

The resolution in our case was to update the duplicate increment in the wrapper.conf to 14

wrapper.java.additional.14=-XX:PermSize=256m


Hey Jason,

We can help more if you file a support ticket over at support.atlassian.com, if you are still experiencing this problem.

This abobe knowledge base article was not the solution in our case for the error.

What we found was that in the wrapper.conf (<InstallDir>\wrapper\conf\wrapper.conf) the following lines were present

wrapper.java.additional.11=-Dfisheye.inst="D:/fisheye-2.8.2/database"

wrapper.java.additional.12=-XX:MaxPermSize=128m

wrapper.java.additional.13=-Xrs

...

wrapper.java.additional.11=-XX:PermSize=256m

As a result the service could not find the database and went off to try the to create its own.

The resolution in our case was to update the duplicate increment in the wrapper.conf to 14

wrapper.java.additional.14=-XX:PermSize=256m

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

1,769 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you