Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NoClassDefFoundError when starting Kamon without slf4j-api in classpath #32

Closed
ivantopo opened this issue May 12, 2014 · 0 comments
Closed

NoClassDefFoundError when starting Kamon without slf4j-api in classpath #32

ivantopo opened this issue May 12, 2014 · 0 comments
Labels
Bug

Comments

@ivantopo
Copy link
Contributor

The exception bellow is fired when no slf4j-api is available in the classpath.. we should either declare the dependency explicitly to make sure it is always there or eliminate the dependency.

[AppClassLoader@138297fe] error Cannot instantiate message handler kamon.weaver.logging.KamonWeaverMessageHandler -- (NoClassDefFoundError) org/slf4j/LoggerFactory
12:54:33 web.1   | org/slf4j/LoggerFactory
12:54:33 web.1   | java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
12:54:33 web.1   | at kamon.weaver.logging.KamonWeaverMessageHandler.<init>(KamonWeaverMessageHandler.scala:29)
@ivantopo ivantopo added the Bug label May 12, 2014
@dpsoft dpsoft closed this as completed in b758b4d May 12, 2014
dpsoft added a commit that referenced this issue Dec 4, 2016
@dpsoft
! core: added java.logging.Logger instead of slf4j in KamonWeaverMess…
94766ff 
…ageHandler and fixes #32
ivantopo added a commit that referenced this issue Mar 9, 2020
@ivantopo
Merge pull request #32 from danischroeter/patch-1
fc6cd00 
Update HostMetricsCollector.scala
ivantopo added a commit that referenced this issue Mar 29, 2020
@ivantopo
Merge pull request #32 from kamon-io/issue#29/handling-4xx-status-codes
c277ea3 
only replace http server operation names on 404 responses, fixes #29
ivantopo added a commit that referenced this issue Mar 29, 2020
@ivantopo
run WSClient instrumentation only once when filters are applied, fixes …
b0cbef1 
…#28 (#32)

* run WSClient instrumentation only once when filters are applied, fixes #28
* instrument WSClient.url(..) instead of WSRequestExecutor
* instrument WSRequest instead of the ning-specific implementation
* fix compilation error for 2.6/Scala 2.11
ivantopo pushed a commit that referenced this issue Mar 31, 2020
@rb3ckers @ivantopo
Replace default argument value with a no-args constructor (#32)
1a0d57b 
Loading reporters from the configuration file uses Java reflection to instatiate the reporter with its no-args constructor. No such constructor was generated for `InfluxDBReporter` (the default argument value doesn’t generate one).
ivantopo added a commit that referenced this issue Mar 31, 2020
@ivantopo
Merge pull request #32 from codacy/fix/build-failing
5c1d2c9 
Force conversion toSeq in config
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ivantopo