You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Rick Curtis (JIRA)" <ji...@apache.org> on 2010/11/16 20:32:14 UTC

[jira] Assigned: (OPENJPA-1886) Query trace may contain sensitive information and should not be logged by default.

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

Rick Curtis reassigned OPENJPA-1886:
------------------------------------

    Assignee: Rick Curtis

> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.