Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

QueryDSL conflict between Advanced Roadmaps and RESTful Worklog Query plugins

Nick James
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 17, 2020

Hi,

 

I've been using the Advanced Roadmaps (Portfolio) plugin for a number of years, and recently I installed the RESTful Worklog Query plugin. Things seemed to be working fine, however once my Jira instance restarted I started seeing a number of issues, for example being unable to open any of the plans within Advanced Roadmaps.

The error I was seeing is below which is due to Java being unable to determine which QueryDSL library to link to. Advanced Roadmaps provides querydsl-4.0.7-provider-plugin-1.2.jar and RESTful Worklog Query plugin provides jira-querydsl-support-2.0.0.jar.

java.lang.LinkageError: loader constraint violation: when resolving method "com.querydsl.sql.SQLQueryFactory.<init>(Lcom/querydsl/sql/Configuration;Ljavax/inject/Provider;)V" the class loader (instance of org/apache/felix/framework/BundleWiringImpl$BundleClassLoader) of the current class, com/atlassian/rm/common/bridges/jira/persistence/JiraDatabaseProviderBridge76, and the class loader (instance of org/apache/felix/framework/BundleWiringImpl$BundleClassLoader) for the method's defining class, com/querydsl/sql/SQLQueryFactory, have different Class objects for the type javax/inject/Provider used in the signature java.lang.RuntimeException: java.lang.LinkageError: loader constraint violation: when resolving method "com.querydsl.sql.SQLQueryFactory.<init>(Lcom/querydsl/sql/Configuration;Ljavax/inject/Provider;)V" the class loader (instance of org/apache/felix/framework/BundleWiringImpl$BundleClassLoader) of the current class, com/atlassian/rm/common/bridges/jira/persistence/JiraDatabaseProviderBridge76, and the class loader (instance of org/apache/felix/framework/BundleWiringImpl$BundleClassLoader) for the method's defining class, com/querydsl/sql/SQLQueryFactory, have different Class objects for the type javax/inject/Provider used in the signature

In order to get Jira back to a working state, I have to perform the following steps.

  1. Shut down Jira.
  2. Delete the file JIRA_HOME\plugins\installed-plugins\jira-querydsl-support-2.0.0.jar
  3. Start up Jira.
  4. Re-install the RESTful Worklog Query plugin (so it no longer shows as disabled).

Does anyone know of a more permanent solution to the problem? I am running the following versions:

  • Jira v8.5.3
  • Advanced Roadmaps v3.9.1
  • RESTful Worklog Query v3.0.2

Thanks.

1 answer

1 vote
Attila Bordás _Everit_
Atlassian Partner
April 27, 2021

Hello there,

Thank you for your feedback!

I’m sorry that you encounter this issue. Please note, that RESTful Worklog Query Plugin is a free, open source app, and due to the lack of activity in the community, we have decided not to support it further, as it is indicated on the marketplace. This means, that we may, or may not fix this issue in the future.

Sorry again for your inconvenience.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events