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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,149
Community Members
 
Community Events
184
Community Groups

Portfolio does not work for my server jira

Edited

I'm getting exception on any portfolio page after installing free-trial version on my server version Jira.

Could you please help me undestand what's wrong?

 

Exception details
loader constraint violation: when resolving method "com.querydsl.sql.SQLQueryFactory.(Lcom/querydsl/sql/Configuration;Ljavax/inject/Provider;)V" the class loader (instance of org/apache/felix/framework/BundleWiringImpl$BundleClassLoaderJava5) of the current class, com/atlassian/rm/common/bridges/jira/persistence/JiraDatabaseProviderBridge63, and the class loader (instance of org/apache/felix/framework/BundleWiringImpl$BundleClassLoaderJava5) 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.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$BundleClassLoaderJava5) of the current class, com/atlassian/rm/common/bridges/jira/persistence/JiraDatabaseProviderBridge63, and the class loader (instance of org/apache/felix/framework/BundleWiringImpl$BundleClassLoaderJava5) 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.JiraDatabaseProviderBridge63.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:276
at com.atlassian.rm.jpo.core.plan.api.DefaultPlanListingService.getAllPlans:60
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
<...cut...>


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

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

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

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36
Local time: Fri Aug 24 2018 16:26:19 GMT-0700 (Pacific Daylight Time)

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

Plugin build: 2.15.0

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

Jira Title: Intermedia JIRA
Jira Version: 7.11.1
Agile Version: 7.11.0-DAILY20180712063948

 

 

2 answers

Anybody have a resolution for this issue?

0 votes
Deleted user Oct 19, 2018

Same problem here with jira 7.12.1.

Were you able so solve your issue?

Nope, they said they don't know the reason.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events