[
https://issues.jboss.org/browse/JGRP-1585?page=com.atlassian.jira.plugin....
]
David Lloyd commented on JGRP-1585:
-----------------------------------
The project is here:
https://github.com/jboss-logging/jboss-logging
There are no docs other than JavaDoc; just use the {{Logger}} class in the obvious way.
Methods that end in "f" or "v" are varargs; the "f" variants
use printf-style formatting and the "v" variants use MessageFormat-style
formatting.
Example:
{code}
static final Logger log = Logger.getLogger("org.myproject");
// ... later on ...
log.debugf("Flop the frob (%s)", frob); // or ...
log.debugv("Flop the frob ({0})", frob);
// ... etc ...
{code}
Upgrade log4j
-------------
Key: JGRP-1585
URL:
https://issues.jboss.org/browse/JGRP-1585
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.4
log4j has some heavy synchronization, which can sometimes lead to code blocking up to 30
seconds (see [1]).
Investigate whether we should switch to log42 [2]. Perhaps we can simply program against
the API (30K) and not even ship the implementation ?
[1]
https://issues.apache.org/bugzilla/show_bug.cgi?id=51047
[2]
http://logging.apache.org/log4j/2.x/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira