Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

Recognition

  • Give kudos
  • My kudos

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

QueryDSL conflict between Advanced Roadmaps and RESTful Worklog Query plugins

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.

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

5 mobile apps for Jira Cloud to boost productivity

  It’s very important to have access to the workflow process from anywhere. Especially if you manage the work of others. There is no difference whether you’re out of office, or drive a ca...

265 views 2 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you