Known Issues

Micro Focus is aware of the following issues affecting the current GitCentric release.

24861 - Change package gaps

If you use change packages (CPKs) with GitCentric in AccuRev 5.7 or earlier, be aware that GitCentric does not currently span CPK gaps automatically. This is not an issue in AccuRev 6.0 owing to changes in CPK functionality.

27473 - email confirmation

GitCentric currently does not provide confirmation email for account verification. not currently support other authorization types such as LDAP, OpenID, etc.

28936 - kandoMaintain backup files

The kandoMaintain backupdbs command creates backup files in the same directory as the kandoMaintain.jar, not where kandoMaintain is run from.

29070 - Re-installs require Tomcat reboot

If you re-install GitCentric over an existing installation, sometimes you cannot log into GitCentric when the installation is done. To fix this, restart Tomcat

29564 - Register all IP addresses for a server

For security reasons, the GitCentric bridge accepts commands only from IP addresses that it

recognizes. If you have registered an AccuRev Server that has multiple IP addresses (for example, if the server has multiple Ethernet cards) you must add server entries for each IP address. In this case, you should perform GitCentric operations only against one of these servers entries - typically one where you have specified a host name rather than an IP address. If you have a situation where IP addresses can change over time (such as dynamic IP addresses assigned via DNS), you may need to consider setting AC_BRIDGEAPI_SECURITY_POLICY to AllowAnyHost. Note, however, that this workaround has a security impact that you need to carefully consider before implementing it.

Procedures for adding server entries and GitCentric configuration settings are documented in the GitCentric On-line Help.

29089 - Errors in catalina.out log file

You may see instances of SEVERE errors in catalina.out, relating to failure to unregister JDBC driver and remove threads on exit. These errors can be safely ignored in this release.

30954 - Some strings with special characters require quote marks

A known issue with Gerrit requires that you enclose certain values in gerrit.config and secure.config files in double quotes if they contain special characters, as summarized in the following table.

Config File Section Value
gerrit.config [gerrit] basepath
gerrit.config [httpd] listenURL
gerrit.config [kando] KANDOHOME
gerrit.config [kando] bridgeURL
secure.config [database] password

For example, if the password in your secure.config file is my!pass#ord, you would need to enclose it in double quotes, like this: password = "my!pass#ord". The gerrit.config and secure.config files are located in <gc_home>/site/etc.

31660 - Code Review

GitCentric Code Review submit/merge operations do not return issues that have been closed in change comments.

34757 - Problem displaying Online help in Internet Explorer

Clicking the help button does not open the GitCentric online help in these versions of Internet Explorer:

  • Internet Explorer 9, version 9.0.8112.16421.
  • Internet Explorer10, version 10.0.9200.16899.

For best results, use the latest version of Internet Explorer.

To work around this issue, add the following section to gerrit.config (in <gc_home>/site/etc/):

     checkReferencedObjectsAreReachable = false

Unable to negotiate with <GC host> port 29418: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1

User sees error "Unable to negotiate with <GC host> port 29418: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1" when trying to clone/pull/push or execute an ssh command against the GitCentric server.

This problem can either be solved with a workaround on each client that experiences the problem, or with one work-around on the GitCentric server.

Solution on client
  1. Create a file config:
    Run <text editor> ~/.ssh/config.
  2. Ensure that the line below are added in the file config:
    Host *
    KexAlgorithms diffie-hellman-group1-sha1
Note: This works for Linux client or Microsoft Windows client with Git for windows only, does not work for built - in Git, such as TortoiseGit, or Eclipse Git plug-in.
Solution on server
The solution is to add the 'bouncy castle' jars to the project. Bouncy Castle is an open source encryption library written in Australia.

The three jars to be added to the project are :

  • bcpg-jdk15on-155.jar
  • bcpkix-jdk15on-155.jar
  • bcprov-ext-jdk15on-155.jar
Note: -155 indicates the version number.

Download the bouncy castle jar files from

There are two ways to add them to the project.

  • Copy the three jar files to <tomcat install>/lib.
    Note: Installing the jar files in this location might require re -configuration of other Web applications supported by the same Tomcat server.
  • Alternative way:
    1. Copy the three jar files into just the gitcentric.war file using the command line jar command, see
    2. Save a copy of <gc install>/bin/gitcentric.war for a Roll Back.
    3. Create subdirectory <gc install>/bin/gitcentric.war WEB-INF/lib/ and copy the three jar files in it.
    4. Run:
      jar uvf <gc install>/bin/gitcentric.war WEB-INF/lib/bc*.jar
    5. Delete subdirectory WEB-INF/lib.
    6. Restart the Tomcat server.
The steps taken above affects the gitcentric.war application only.