question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error Starting Tomee Plume 7.0.3, 7.1.0 with javamelody 1.68.0 through 1.75.0

See original GitHub issue

This gives me following exception

org.apache.openejb.OpenEJBException: Creating application failed: [xxxx redacted xxxx]: class net.bull.javamelody.internal.common.LogbackLogger cannot access its superinterface net.bull.javamelody.JavaMelodyLogger
	at org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:1042)
	at org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:718)
	at org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1298)
	at org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:1124)
        [xxx shortened xxx]
Caused by: java.lang.IllegalAccessError: class net.bull.javamelody.internal.common.LogbackLogger cannot access its superinterface net.bull.javamelody.JavaMelodyLogger
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
	at org.apache.catalina.loader.WebappClassLoaderBase.findClassInternal(WebappClassLoaderBase.java:2277)
	at org.apache.catalina.loader.WebappClassLoaderBase.findClass(WebappClassLoaderBase.java:811)
        [xxx shortened xxx]

Important part is that stating:

net.bull.javamelody.internal.common.LogbackLogger cannot access its superinterface net.bull.javamelody.JavaMelodyLogger

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
evernatcommented, Jan 28, 2019

you are welcome

1reaction
evernatcommented, Dec 24, 2018

I have removed from javamelody the automatic monitoring of @Asynchronous methods, because it was working in some application server(s) but it does not seem to be valid according to CDI spec (and according to TomEE plume). Note that you may continue to monitor CDI/EJB methods with a javamelody annotation or by configuration, see https://github.com/javamelody/javamelody/wiki/UserGuide#8-business-facades-ejb-jarxml-file-if-ejb3-or-cdi

The issue is fixed by 406639b and ready for the next release 1.76.

Meanwhile you may workaround the issue by adding a file WEB-INF\exclusions.list in your webapp with the following content:

# inherit from defaults, this is important to keep it
default-list
# ignore javamelody interceptors
javamelody-core-1.75.0.jar
Read more comments on GitHub >

github_iconTop Results From Across the Web

Downloads - Apache TomEE
Apache TomEE is a lightweight, yet powerful, JavaEE Application server with feature rich tooling.
Read more >
tomee won't start from within eclipse - Stack Overflow
Both version of TomEE, witch is Apache TomEE plume 8.0.0-M3 and Apache Tomee plume 7.1.0, it seems to run without error, both started...
Read more >
Apache TomEE 8.0.0 Installation on Windows 10 ... - YouTube
In this video we are going to see how to install Apache TomEE 8.0.0 Plume on Windows 10 using Oracle JDK 8. TomEE...
Read more >
tomee
Apache TomEE Plus delivers all that is in the Web Profile and JAX-RS (RESTfull Services), plus EJB Full, Java EE Connector Architecture, JMS...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found