-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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.
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
Receiver - Can't handle model of type ReceiverModel with tag: receiver #706
Comments
I would be happy to know if this should work. Does no one use this feature? |
I have the very same error and opened a ticket in the old Jira tracker: https://jira.qos.ch/browse/LOGBACK-1743 PR #699 has a fix for this. |
Thank you for the information. |
I ran into the same issue, thanks for the PR. Would be great to get an update on whether that's considered for merging into an upcoming release. Was there a reason not to support the receiver tag or just an oversight/bug? |
Also encountered this issue. Until a new release is available, would I have to build the logback-classic.jar myself to fix this behaviour? |
@ceki Any chances of addressing the issue in the near future? The bug basically makes the receiver functionality unusable but the PR posted above is a straightforward fix. |
Signed-off-by: Volker Götz <[email protected]>
Attempting Logback receiver feature I get this error:
ERROR in ch.qos.logback.core.model.processor.DefaultProcessor@76b10754 - Can't handle model of type class ch.qos.logback.classic.model.ReceiverModel with tag: receiver at line 11
My setup:
To reproduce:
Structure:
Main.java:
logback.xml:
(I also tried the canonical style with same result)
pom.xml:
To build and run:
Following the guide here: https://logback.qos.ch/manual/receivers.html
I also cloned code from github (various versions here too) and run the example codes. Everything give me the same problem.
I tried various versions of Logback (3.x and 4.x). I tried Java 8,11,17
I would prefer to make Logback 3.x to work since I am stuck with Java 8 in prod.
I even tried run it in a Docker-container to rule out problems in my environment.
Complete log:
The text was updated successfully, but these errors were encountered: