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 16 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.


Some functionality stopped to work after upgrading the app

The soft way (standard)

  • Remove the SQL+JQL Driver app
  • Install it again from the Marketplace
  • Enable Subversion ALM app

The hard way (manual)

Sometimes an app cand get stuck forever in Jira avoiding upgrades in a proper way. Under some circumstances removing the app in a manual way might be required.

Steps:

Figure out the OSGi Id assigned to the app during the installation process. The OSGi console must  be opened in Jira (administrator privileges are required)

${JIRA_BASE_URL}/plugins/servlet/upm/osgi 

and search for the app:

In the example above, SUbversion ALM was installed as the 223 OSGi plugin.

Open the

${JIRA_HOME}/plugins/installed-plugins

directory and delete the app file from there:


Open the

${JIRA_HOME}/plugins/.osgi-plugins/transformed-plugins

and search for the app plugin jar and delete all of them:

You will be able to delete all of them.. except one. This is the library being used by Jira:


Uninstall the app from Jira and wait for a couple of minutes to let Jira enough free time to remove all the Java classes and resources from the memory.  Then delete the last binary library above. If it cannot be deleted, Jira must be shut down to remove the app jar. 

Open the 

${JIRA_HOME}/plugins/.osgi-plugins/.osgi-plugins/felix/felix-cache

folder, search for the bundle with the OSGi ide figured out from the console and delete the entire folder.


Your app has been completely removed now. Please keep in mind that the app's data remains unmodified elsewhere the app stored them (file system, database, etc), so any previous configuration will still be there until those data are explicitly removed. This is not required by this process as we want to delete the app binary files and not its data.


Startup Jira again and install the latest version of the app from the Marketplace:



The 404 Error

The Atlassian's JIRA Subversion plugin must be uninstalled and Subversion 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)
,,,,



  • No labels