Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

Enabling the logs

Subversion ALM writes traces in the JIRA logs. However, this feature is disabled by default and you have to explicitly authorize the plugin for that:



JIRA > Administration > System > Logging and Profiling > Default Loggers > Configure:

  • Package Name: com.kintosoft.jira,  com.kintosoft.svnwebclient and, org.polarion.svnwebclient  (three packages)
  • Logging Level: DEBUG

Please repeat the test and send the relevant traces for supporting.

Keep in mind that the configuration above is automatically reset if JIRA is re-started so you have to grant the plugin to write in the JIRA logs again.

The 404 Error (or other unexpected errors on pages)

The Atlassian's JIRA Subversion plugin must be uninstalled and Subversion ALM re-installed again.


A lot of warnings in the logs: Dangerous use of multiple connections

Subversion ALM stores the Subversion index on the Jira database, therefore a database connection is required to read the data. It works perfectly with thousands of organizations running Subversion ALM with no issues and millions of records. However, it looks like Atlassian added a warning to notice this behavior as risky. None of the customers that reported this trace in the logs reported any other Jira issue (performance, reliability, etc). You might want to increase the database pool.


2020-06-14 13:01:33,619+0200 http-nio-2990-exec-5 WARN admin 781x2920x1 psmhc7 0:0:0:0:0:0:0:1 /projects/DEMO [c.a.jira.ofbiz.ConnectionPoolHealthSqlInterceptor] Dangerous use of multiple connections: taken => count=3; marks=[2-3]; pool=3/8
java.lang.AssertionError: Explicit stack trace requestedat com.atlassian.jira.util.log.RateLimitingLogger.warnWithTrace(RateLimitingLogger.java:124)
at com.atlassian.jira.ofbiz.ConnectionPoolHealthSqlInterceptor$CountHolder.logWarn(ConnectionPoolHealthSqlInterceptor.java:236)
at com.atlassian.jira.ofbiz.ConnectionPoolHealthSqlInterceptor$CountHolder.taken(ConnectionPoolHealthSqlInterceptor.java:252)
at com.atlassian.jira.ofbiz.ConnectionPoolHealthSqlInterceptor.onConnectionTaken(ConnectionPoolHealthSqlInterceptor.java:89)
at com.atlassian.jira.ofbiz.ChainedSQLInterceptor.lambda$onConnectionTaken$0(ChainedSQLInterceptor.java:64)
at com.atlassian.jira.ofbiz.ChainedSQLInterceptor.forEach(ChainedSQLInterceptor.java:93)
,,,,

A lot of errors in the Jira logs (caused by a service)

Subversion ALM does not use Jira services.

This error is caused by the discontinued Atlassian's plugin Subversion for Jira. It has a bug and the service is not removed along with the app and it remains active causing errors. It must be manually removed from the Jira administration services section and reboot Jira.



  • No labels