[
https://issues.jboss.org/browse/JGRP-1966?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1966:
--------------------------------
Not sure I understand what the issue is. Also, I've never used either JDK logging or
sl4j.
Can you submit a pull request to fix what you perceive to be the issue? Meanwhile, I'm
closing this one, feel free to reopen once you have a PR.
Specify logger name for LogRecord in JDKLogImpl
-----------------------------------------------
Key: JGRP-1966
URL:
https://issues.jboss.org/browse/JGRP-1966
Project: JGroups
Issue Type: Enhancement
Affects Versions: 3.6.6
Reporter: George Zalizko
Assignee: Bela Ban
Priority: Minor
Fix For: 3.6.7
I use Spring Boot with logback.
For logging I have pattern:
{code}%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} %C{30}:%L - %msg%n{code}
And in console I see:
{code}
16:19:32.062 [OOB-1,yphis-cluster-web,George-THINKPAD-35404] WARN unknown.jul.logger
org.jgroups.logging.JDKLogImpl:49 - JGRP000010: packet from 192.168.50.123:45588 has
different version (3.2.8) than ours (3.6.6); packet is discarded{code}
This happens because LogRecord created in org.jgroups.logging.JDKLogImpl doesn't have
loggerName and when org.slf4j.bridge.SLF4JBridgeHandler make org.slf4j.Logger from
java.util.logging.LogRecord he sets logger name as
org.slf4j.bridge.SLF4JBridgeHandler#UNKNOWN_LOGGER_NAME that's
"unknown.jul.logger"
Actually I don't know is it done specially or not, but I can't find any
comments/solutions for that.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)