Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

If I click Portfolio > View Portfolio, I get an error

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/JiraDatabaseProviderBridge74, 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

  at com.atlassian.rm.common.bridges.jira.persistence.JiraDatabaseProviderBridge74.execute:52
  at com.atlassian.rm.common.persistence.env.JiraDatabaseProvider.execute:36
  at com.atlassian.rm.common.persistence.DefaultDatabaseProvider.run:26
  at com.atlassian.rm.jpo.core.plan.sql.QueryDslPlanPersistence.getAllPlans:275
  at com.atlassian.rm.jpo.core.plan.api.DefaultPlanListingService.getAllPlans:62
  at com.atlassian.rm.jpo.rest.service.program.ProgramRestEndpoint.getProgramList:118
  at sun.reflect.NativeMethodAccessorImpl.invoke0:-2
  at sun.reflect.NativeMethodAccessorImpl.invoke:62
  at sun.reflect.DelegatingMethodAccessorImpl.invoke:43
  at java.lang.reflect.Method.invoke:498
  at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke:192
  at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$1.intercept:83
  at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke:53
  at com.atlassian.plugins.rest.common.expand.interceptor.ExpandInterceptor.intercept:41
  at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke:53
  at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper.invokeMethodWithInterceptors:110
  at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker._dispatch:190
  at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch:75
  at com.atlassian.rm.common.rest.scope.RequestOperationScopeDispatcher.dispatch:25
  at

 

[...], Removed, Ticket Description was too long.

 

===============
=== Request ===
===============

URL: /rest/jpo/1.0/programs/list?_=1564270211181
Type: GET
Status: 500
Data: undefined

===================
=== Client Info ===
===================

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Firefox/68.0
Local time: Sun Jul 28 2019 01:30:24 GMT+0200 (Mitteleuropäische Sommerzeit)

===================
=== Plugin Info ===
===================

Plugin build: 3.6.0

===================
=== System Info ===
===================

Jira Title: ILCAI Jira
Jira Version: 8.0.2
Agile Version: 8.0.0-DAILY20190215023029

1 answer

1 accepted

1 vote
Answer accepted

Hi there Philip, I did some scouring around and found this bug which matches the error message you are seeing almost exactly : JPOSERVER-2511.

The report states that this happens if a Timetracker add-on was installed before installing Portfolio. Is this what happened in your instance as well?

If it is, you may want to try out the workaround that was provided in the bug ticket (there are some jar file downloads involved, so I can't just paste it here). Let me know how it goes!

Yes, that was exactly the case.

What helped me was:

- Stop Jira

- Remove the corrupt dependency plugin

- Restart Jira

 

Thank you very much!

Like Luis Vila likes this

Suggest an answer

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

☕️ Monday coffee with Jexo: Weekly Atlassian news roundup | 21st June 2021

Hi community 👋, as every Monday we're bringing you a quick update on what happened in the Atlassian ecosystem last week. There were a few interesting events like for example the announcement of th...

36 views 0 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