search

saif-hmk / javamelody

Automatically exported from code.google.com/p/javamelody
0 stars 0 forks source link

RuntimeException converting item 'net.bull.javamelody:net.bull.javamelody.jira-web-item' to Simple link #342

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Login to JIRA as Admin & navigate to "Application Navigator"
2. Make a change.
3. Inspect logs... there will be two sets of two different errors (I see 6 of 
each):

2013-09-18 20:18:17,339 http-bio-8080-exec-17 ERROR marks 1218x3024x1 1341zh8 
111.222.111.222 /plugins/servlet/customize-application-navigator 
[jira.plugin.webfragment.DefaultSimpleLinkManager] RuntimeException converting 
item 'net.bull.javamelody:net.bull.javamelody.jira-web-item' to Simple link. 
This link will be skipped. null

2013-09-18 20:15:40,340 http-bio-8080-exec-8 ERROR marks 1215x2986x1 1341zh8 
111.222.111.222 /plugins/servlet/stp/view/ 
[jira.plugin.webfragment.DefaultSimpleLinkManager] RuntimeException converting 
item 'net.bull.javamelody:net.bull.javamelody.jira-web-item' to Simple link. 
This link will be skipped. null

What is the expected output? What do you see instead?

I expect no logged exception but get some.  

What version of the product are you using? On what application server, JDK, 
operating system?

JavaMelody 1.46.0
JIRA v6.0.8
Apache Tomcat/7.0.29
Java 1.7.0_25 (see with both JRA & JDK)

Please provide any additional information below.

Note that, despite the logged errors, all seems OK in the UI.

Issue #210 seems similar to this defect but with a different error message (and 
a defect that was fixed & closed).

Original issue reported on code.google.com by msymo...@gmail.com on 18 Sep 2013 at 7:40

GoogleCodeExporter commented 9 years ago 
Also seen with:

Javamelody 1.47.0
Java 1.7.0_40

Original comment by msymo...@gmail.com on 10 Oct 2013 at 11:12

GoogleCodeExporter commented 9 years ago 
Issue 348 has been merged into this issue.

Original comment by evernat@free.fr on 12 Oct 2013 at 9:19

GoogleCodeExporter commented 9 years ago 
I think that this is a bug in JIRA:
https://jira.atlassian.com/browse/JRA-34147
You can vote in the issue.

And this issue should probably be fixed in JIRA by Atlassian.

Original comment by evernat@free.fr on 12 Oct 2013 at 11:17

GoogleCodeExporter commented 9 years ago 
And so this is won't fix on our side.

Original comment by evernat@free.fr on 17 Oct 2013 at 12:43

GoogleCodeExporter commented 9 years ago 
Issue 357 has been merged into this issue.

Original comment by evernat@free.fr on 29 Oct 2013 at 5:39

GoogleCodeExporter commented 9 years ago 
The linked JIRA defect provides a workaround.  Could that not be used in 
JavaMelody?

I've now had 3000 occurrences of this ERROR event - it makes the logs hard to 
work with  (easier to miss something important).

Original comment by msymo...@gmail.com on 20 Feb 2014 at 11:38

GoogleCodeExporter commented 9 years ago 
No, if the workaround is used, the plugin will not be compatible anymore with 
older versions of JIRA.
I think that it is not difficult for Atlassians to be again compatible with 
"system.admin", at least much less than changing all concerned plugins.
This is still won't fix here.

Original comment by evernat@free.fr on 1 Mar 2014 at 7:15

GoogleCodeExporter commented 9 years ago 
This means that JavaMelody is incompatible with JIRA 6.x. It would be a good 
idea to state this on the download page :(

Original comment by sorin.sb...@gmail.com on 18 Mar 2014 at 7:51

GoogleCodeExporter commented 9 years ago 
See https://jira.atlassian.com/browse/JRA-34147

Original comment by sorin.sb...@gmail.com on 18 Mar 2014 at 7:53

GoogleCodeExporter commented 9 years ago 
@sorin.sbarnea
It seems to me that it causes many logs. That does not mean that JavaMelody is 
incompatible.
I know JRA-34147: I have commented in that issue about the documentation to fix 
that and that the said documentation does not seem to work.

I would be glad if you can try to add some class in the jira-javamelody.jar and 
to modify the atlassian-plugin.xml file in the jar, as said in the JIRA 
documentation.

https://developer.atlassian.com/display/JIRADEV/Administration+Area+Locations#Ad
ministrationAreaLocations-MaintainingAdministrationAreaLocationCompatibilityAcro
ssJIRAVersions

Everyone will thank you if you fix that.

Original comment by evernat@free.fr on 19 Mar 2014 at 10:37

GoogleCodeExporter commented 9 years ago 
Of course, you may otherwise say to Atlassians that you don't understand why 
they don't use an alias for "system.admin" for compatibility.

Original comment by evernat@free.fr on 19 Mar 2014 at 10:41

GoogleCodeExporter commented 9 years ago 
In issue 210, olaf.kaus has suggested to replace the "system.admin/system" 
web-item section in the atlassian-plugin.xml file by 
"admin_plugins_menu/monitoring_section".

Since the location change was made in JIRA some time ago, it may be time to be 
more compatible with recent JIRA versions (v6.0.8+), and less compatible with 
old JIRA versions.
What do you think?

For reference: https://jira.atlassian.com/browse/JRA-34147

Original comment by evernat@free.fr on 31 Aug 2014 at 2:01

GoogleCodeExporter commented 9 years ago 
I totally agree the aim should be to support the current versions of JIRA. If 
someone still uses an old version of JIRA he/she could also use an old version 
of the plugin.

Untill then I am considering removing javamelody from jira as I have thousands 
of these messages in the logs.

Original comment by f...@twigs.de on 6 Sep 2014 at 9:23

GoogleCodeExporter commented 9 years ago 
As suggested by flo, this will be fixed in the next release (1.53).
The "system.admin/system" web-item section in the atlassian-plugin.xml file has 
been replaced by "admin_plugins_menu/monitoring_section" (revision 3923).

Original comment by evernat@free.fr on 26 Sep 2014 at 11:35