You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@openjpa.apache.org by Chris <cw...@gmail.com> on 2013/09/26 16:05:52 UTC

Is there any way to get OpenJPA to not log to stderr?

I am running OpenJPA in JBoss and would like it's trace and logging to 
go to the JBoss log, rather then standard error, which JBoss captures 
and then redirects to the log at priority "ERROR", causing many 
false-positive errors for tools that search the log.


Here are my current settings:

       <property name="openjpa.ConnectionFactoryProperties"
                value="QueryTimeout=50000, printParameters=true, 
PrettyPrint=true, PrettyPrintLineLength=72"/>
       <property name="openjpa.Log" value="openjpa.jdbc.MetaData=TRACE"/>
       <property name="openjpa.Log" value="openjpa.jdbc.JDBC=TRACE"/>
       <property name="openjpa.Log" value="slf4j"/>
       <property name="openjpa.Log" value="SQL=TRACE"/>


Thanks,

Chris

Re: Is there any way to get OpenJPA to not log to stderr?

Posted by Chris <cw...@gmail.com>.
Yes, and the implementation jar is slf4j-log4j12.jar and log4j-12.jar is 
also included.  I have a log4j.properties in the "classes" directory of 
the WAR, but no specific category for OpenJPA classes, but that should 
only control what gets logged, not whether logging is totally by-passed 
(as it is now)

Thanks,

Chris

On 9/26/2013 10:17 AM, Harald Wellmann wrote:
> Does your application include slf4j-api.jar?
>
> Regards,
> Harald
>
> 2013/9/26 Chris <cw...@gmail.com>:
>> I am running OpenJPA in JBoss and would like it's trace and logging to go to
>> the JBoss log, rather then standard error, which JBoss captures and then
>> redirects to the log at priority "ERROR", causing many false-positive errors
>> for tools that search the log.
>>
>>
>> Here are my current settings:
>>
>>        <property name="openjpa.ConnectionFactoryProperties"
>>                 value="QueryTimeout=50000, printParameters=true,
>> PrettyPrint=true, PrettyPrintLineLength=72"/>
>>        <property name="openjpa.Log" value="openjpa.jdbc.MetaData=TRACE"/>
>>        <property name="openjpa.Log" value="openjpa.jdbc.JDBC=TRACE"/>
>>        <property name="openjpa.Log" value="slf4j"/>
>>        <property name="openjpa.Log" value="SQL=TRACE"/>
>>
>>
>> Thanks,
>>
>> Chris

Re: Is there any way to get OpenJPA to not log to stderr?

Posted by Harald Wellmann <hw...@gmail.com>.
Does your application include slf4j-api.jar?

Regards,
Harald

2013/9/26 Chris <cw...@gmail.com>:
> I am running OpenJPA in JBoss and would like it's trace and logging to go to
> the JBoss log, rather then standard error, which JBoss captures and then
> redirects to the log at priority "ERROR", causing many false-positive errors
> for tools that search the log.
>
>
> Here are my current settings:
>
>       <property name="openjpa.ConnectionFactoryProperties"
>                value="QueryTimeout=50000, printParameters=true,
> PrettyPrint=true, PrettyPrintLineLength=72"/>
>       <property name="openjpa.Log" value="openjpa.jdbc.MetaData=TRACE"/>
>       <property name="openjpa.Log" value="openjpa.jdbc.JDBC=TRACE"/>
>       <property name="openjpa.Log" value="slf4j"/>
>       <property name="openjpa.Log" value="SQL=TRACE"/>
>
>
> Thanks,
>
> Chris