openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Curtis (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (OPENJPA-1886) Query trace may contain sensitive information and should not be logged by default.
Date Wed, 13 Jul 2011 16:13:00 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rick Curtis closed OPENJPA-1886.
--------------------------------


Closing resolved issues.

> Query trace may contain sensitive information and should not be logged by default.
> ----------------------------------------------------------------------------------
>
>                 Key: OPENJPA-1886
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1886
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: logging
>    Affects Versions: 2.0.2, 2.1.0
>            Reporter: Rick Curtis
>            Assignee: Rick Curtis
>             Fix For: 2.1.0
>
>
> This is the same problem as reported by OPENJPA-1678 except it is coming from openjpa.Query.
> To recreate this problem, run org.apache.openjpa.persistence.querycache.TestQueryCache
and enable "openjpa.Log","Query=trace". 
> 375  test  TRACE  [main] openjpa.Query - Executing query: [SELECT o FROM Entity1 o WHERE
o.pk = :pk] with parameters: {pk=2}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message