You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
Does anyone know of a more permanent solution to the problem? I am running the following versions:
Thanks.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.