Why would you have a single Logger being used by a class that logs with JUL and 
another class that doesn’t?  That is the only way I can see this happening. The 
formatter used is specific to the Logger.

Ralph


> On Oct 26, 2015, at 8:52 AM, Mikael Ståldal <[email protected]> wrote:
> 
> Ah, that explains it.
> 
> But how are you supposed to use Log4j 2 if you both use the JUL adapter and 
> does logging directly through the Log4j 2 API in the same application?
> 
> On Mon, Oct 26, 2015 at 2:09 PM, Ralph Goers <[email protected] 
> <mailto:[email protected]>> wrote:
> The JUL logger does.
> 
> Ralph
> 
> On Oct 26, 2015, at 3:07 AM, Mikael Ståldal <[email protected] 
> <mailto:[email protected]>> wrote:
> 
>> The strange thing is that I have not called LogManager.getLogger() with any 
>> MessageFormat anywhere in my app.
>> 
>> I am using the JUL adapter, the Log4j 1.2 adapter and the SLF4j impl. Can 
>> any of those do it?
>> 
>> On Sat, Oct 24, 2015 at 1:49 AM, Remko Popma <[email protected] 
>> <mailto:[email protected]>> wrote:
>> You called LogManager.getLogger(name) twice with the same name, once 
>> specifying a MessageFormat, once with just the name. 
>> 
>> When you specified just the name, you may expect to get a Logger with the 
>> default ParameterizedMessageFormat, but you're getting the cached instance 
>> with MessageFormat, so things may not work as expected. 
>> 
>> (At least I think that 's what it means.)
>> 
>> Sent from my iPhone
>> 
>> On 2015/10/23, at 22:36, Mikael Ståldal <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>>> I get this warning with Log4j 2.4.1:
>>> 
>>> was 2015-10-23 13:32:36,181 main WARN The Logger 
>>> com.magine.contenturl.ContentUrlServer$ was created with the message 
>>> factory 
>>> org.apache.logging.log4j.message.MessageFormatMessageFactory@29bf34bb and 
>>> is now requested with a null message factory (defaults to 
>>> org.apache.logging.log4j.message.ParameterizedMessageFactory), which may 
>>> create log events with unexpected formatting.
>>> 
>>> It seems to work properly though. What does it mean?
>>> 
>>> -- 
>>>  
>>> 
>>> Mikael Ståldal
>>> Senior software developer 
>>> 
>>> Magine TV
>>> [email protected] <mailto:[email protected]>    
>>> Regeringsgatan 25  | 111 53 Stockholm, Sweden  |   www.magine.com  
>>> <http://www.magine.com/>
>>> 
>>> Privileged and/or Confidential Information may be contained in this 
>>> message. If you are not the addressee indicated in this message
>>> (or responsible for delivery of the message to such a person), you may not 
>>> copy or deliver this message to anyone. In such case, 
>>> you should destroy this message and kindly notify the sender by reply 
>>> email.   
>> 
>> 
>> 
>> -- 
>>  
>> 
>> Mikael Ståldal
>> Senior software developer 
>> 
>> Magine TV
>> [email protected] <mailto:[email protected]>    
>> Regeringsgatan 25  | 111 53 Stockholm, Sweden  |   www.magine.com  
>> <http://www.magine.com/>
>> 
>> Privileged and/or Confidential Information may be contained in this message. 
>> If you are not the addressee indicated in this message
>> (or responsible for delivery of the message to such a person), you may not 
>> copy or deliver this message to anyone. In such case, 
>> you should destroy this message and kindly notify the sender by reply email. 
>>   
> 
> 
> 
> -- 
>  
> 
> Mikael Ståldal
> Senior software developer 
> 
> Magine TV
> [email protected] <mailto:[email protected]>    
> Regeringsgatan 25  | 111 53 Stockholm, Sweden  |   www.magine.com  
> <http://www.magine.com/>
> 
> Privileged and/or Confidential Information may be contained in this message. 
> If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not 
> copy or deliver this message to anyone. In such case, 
> you should destroy this message and kindly notify the sender by reply email.  
>  

Reply via email to