Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-11985

javax.net.ssl.SSLException: Received fatal alert: bad_record_mac with subversion-plugin 1.37

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • None
    • Centos 5.6
      java version "1.6.0_20"
      OpenJDK Runtime Environment (IcedTea6 1.9.8) (rhel-1.22.1.9.8.el5_6-i386)
      OpenJDK Server VM (build 19.0-b09, mixed mode)

      SVN repo is on beanstalkapp platform

      SVN stopped working with the following issue:

      Caused by: org.tmatesoft.svn.core.SVNException: svn: OPTIONS request failed on '/XXXXX/trunk/XXXXXXXXX'
      svn: Received fatal alert: bad_record_mac
      at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
      at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
      at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:662)
      at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:292)
      ... 67 more
      Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: OPTIONS request failed on '/XXXX/trunk/XXXXXXX'
      at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200)
      at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:660)
      ... 68 more
      Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: Received fatal alert: bad_record_mac
      at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:101)
      at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:424)
      ... 68 more
      Caused by: javax.net.ssl.SSLException: Received fatal alert: bad_record_mac
      at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
      at sun.security.ssl.Alerts.getSSLException(Alerts.java:154)

      run back to version subversion 1.35 and it seen to work fine.

          [JENKINS-11985] javax.net.ssl.SSLException: Received fatal alert: bad_record_mac with subversion-plugin 1.37

          kutzi added a comment - Note to myself (or whoever is going to fix this): see http://teamcity.tmatesoft.com/viewModification.html?modId=4977&personal=false&init=1&buildTypeId=bt31&tab=vcsModificationFiles and compare http://svn.svnkit.com/repos/svnkit/branches/1.3.x/svnkit/src/main/java/org/tmatesoft/svn/core/internal/util/SVNSocketFactory.java against https://github.com/jenkinsci/svnkit/blob/master/svnkit/src/main/java/org/tmatesoft/svn/core/internal/util/SVNSocketFactory.java for the changes done to fix this in vanilla SVNKit

          Will try to test these options.

          Currently I only have our production ci to test against, which will cause issues.

          John-Paul Drawneek added a comment - Will try to test these options. Currently I only have our production ci to test against, which will cause issues.

          I see the same error with 1.443.

          Konstantin Burov added a comment - I see the same error with 1.443.

          kutzi added a comment -

          This got nothing to do with the Jenkins version, but simply with the subversion-plugin 1.37. Updating issue title to reflect this.

          kutzi added a comment - This got nothing to do with the Jenkins version, but simply with the subversion-plugin 1.37. Updating issue title to reflect this.

          Scott Oster added a comment -

          I have this problem with 1.37 and 1.443. I'm not really clear what the workaround is, could someone clarify? I tried reverting to 1.34 but got a different NoClassDef error

          Scott Oster added a comment - I have this problem with 1.37 and 1.443. I'm not really clear what the workaround is, could someone clarify? I tried reverting to 1.34 but got a different NoClassDef error

          Peter Carr added a comment -

          I have the same exact problem. Are there any workarounds?

          Peter Carr added a comment - I have the same exact problem. Are there any workarounds?

          tq rst added a comment - - edited

          Same problem here. Adding -Dsvnkit.http.sslProtocols=SSLv3 didn't help. This is with Jenkins 1.443 + svn 1.40 and 1.42, and also with 1.483 + svn 1.43. This is a showstopper for us. Reverting back to 1.34 used to work for us, but the latest version only allows to downgrade to 1.42, so we're pretty much stuck.

          Update: -Dsvnkit.http.sslProtocols=SSLv3 does work after all. It has to be done on every node, though.

          tq rst added a comment - - edited Same problem here. Adding -Dsvnkit.http.sslProtocols=SSLv3 didn't help. This is with Jenkins 1.443 + svn 1.40 and 1.42, and also with 1.483 + svn 1.43. This is a showstopper for us. Reverting back to 1.34 used to work for us, but the latest version only allows to downgrade to 1.42, so we're pretty much stuck. Update: -Dsvnkit.http.sslProtocols=SSLv3 does work after all. It has to be done on every node, though.

          uma prasath added a comment -

          Hi,
          I resolved both bad_record_mac and No Crendential to try error by doing the below steps. I am writing mail so that it may be of help to some one.

          For bad_record_mack:
          1. Check your proxy setting in the Manage Jenkins --> Manage plugin --> advance
          2. Remove .subversion folder
          3. Enter the svn url you are trying to access

          ERROR: svn: authentication cancelled
          org.tmatesoft.svn.core.SVNCancelException: svn: authentication cancelled.

          1. Login to the server in which the jenkin is running through putty or any tool
          2. Execute svn checkout <<svn repo url>> --username <<username>> --password <<password>>
          3. When it attempts to store the password, save it.

          You can see the below four files getting created under .subversion/auth folder
          svn.simple
          svn.ssl.client-passphrase
          svn.ssl.server
          svn.username

          After which go to the job in jenkins. It will work fine.

          Thanks
          uma

          uma prasath added a comment - Hi, I resolved both bad_record_mac and No Crendential to try error by doing the below steps. I am writing mail so that it may be of help to some one. For bad_record_mack: 1. Check your proxy setting in the Manage Jenkins --> Manage plugin --> advance 2. Remove .subversion folder 3. Enter the svn url you are trying to access ERROR: svn: authentication cancelled org.tmatesoft.svn.core.SVNCancelException: svn: authentication cancelled. 1. Login to the server in which the jenkin is running through putty or any tool 2. Execute svn checkout <<svn repo url>> --username <<username>> --password <<password>> 3. When it attempts to store the password, save it. You can see the below four files getting created under .subversion/auth folder svn.simple svn.ssl.client-passphrase svn.ssl.server svn.username After which go to the job in jenkins. It will work fine. Thanks uma

          I made it work with JDK 7 on Tomcat. Only trouble were the Tomcat Windows Service configuration: http://jespertejlgaard.blogspot.dk/2013/01/solved-badrecordmac-error-for.html

          Jesper Tejlgaard added a comment - I made it work with JDK 7 on Tomcat. Only trouble were the Tomcat Windows Service configuration: http://jespertejlgaard.blogspot.dk/2013/01/solved-badrecordmac-error-for.html

          kutzi added a comment -

          See http://issues.tmatesoft.com/issue/SVNKIT-176 for the underlying issue in the SVNKit project

          kutzi added a comment - See http://issues.tmatesoft.com/issue/SVNKIT-176 for the underlying issue in the SVNKit project

            Unassigned Unassigned
            jpd4classiek2 John-Paul Drawneek
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: