You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Albert Lee (JIRA)" <ji...@apache.org> on 2010/06/25 17:48:49 UTC
[jira] Created: (OPENJPA-1708) Excessive Info message on locking
row in optimistic transaction
Excessive Info message on locking row in optimistic transaction
---------------------------------------------------------------
Key: OPENJPA-1708
URL: https://issues.apache.org/jira/browse/OPENJPA-1708
Project: OpenJPA
Issue Type: Improvement
Components: kernel
Affects Versions: 1.1.0
Reporter: Albert Lee
Assignee: Albert Lee
Priority: Minor
Fix For: 2.1.0
The following info message is logged repeatedly by default (INFO log level)
2532162 **** INFO openjpa.Runtime - Though you are using optimistic transactions, OpenJPA is now beginning a datastore transaction because you have
requested a lock on some data.
Should turn this message into a TRACE entry and only log when need/request.
Also, the manual has documented the incorrect log levels supported by OpenJPA:
* DefaultLevel: The default logging level of unconfigured channels. Recognized values are TRACE, DEBUG, INFO, WARN, and ERROR. Defaults to INFO.
DEBUG is deprecated and FATAL level is missing.
Albert Lee.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (OPENJPA-1708) Excessive Info message on locking row
in optimistic transaction
Posted by "Albert Lee (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Lee closed OPENJPA-1708.
-------------------------------
> Excessive Info message on locking row in optimistic transaction
> ---------------------------------------------------------------
>
> Key: OPENJPA-1708
> URL: https://issues.apache.org/jira/browse/OPENJPA-1708
> Project: OpenJPA
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 1.1.0
> Reporter: Albert Lee
> Assignee: Albert Lee
> Priority: Minor
> Fix For: 2.1.0
>
>
> The following info message is logged repeatedly by default (INFO log level)
> 2532162 **** INFO openjpa.Runtime - Though you are using optimistic transactions, OpenJPA is now beginning a datastore transaction because you have
> requested a lock on some data.
> Should turn this message into a TRACE entry and only log when need/request.
> Also, the manual has documented the incorrect log levels supported by OpenJPA:
> * DefaultLevel: The default logging level of unconfigured channels. Recognized values are TRACE, DEBUG, INFO, WARN, and ERROR. Defaults to INFO.
> DEBUG is deprecated and FATAL level is missing.
> Albert Lee.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (OPENJPA-1708) Excessive Info message on locking
row in optimistic transaction
Posted by "Albert Lee (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Lee resolved OPENJPA-1708.
---------------------------------
Resolution: Fixed
> Excessive Info message on locking row in optimistic transaction
> ---------------------------------------------------------------
>
> Key: OPENJPA-1708
> URL: https://issues.apache.org/jira/browse/OPENJPA-1708
> Project: OpenJPA
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 1.1.0
> Reporter: Albert Lee
> Assignee: Albert Lee
> Priority: Minor
> Fix For: 2.1.0
>
>
> The following info message is logged repeatedly by default (INFO log level)
> 2532162 **** INFO openjpa.Runtime - Though you are using optimistic transactions, OpenJPA is now beginning a datastore transaction because you have
> requested a lock on some data.
> Should turn this message into a TRACE entry and only log when need/request.
> Also, the manual has documented the incorrect log levels supported by OpenJPA:
> * DefaultLevel: The default logging level of unconfigured channels. Recognized values are TRACE, DEBUG, INFO, WARN, and ERROR. Defaults to INFO.
> DEBUG is deprecated and FATAL level is missing.
> Albert Lee.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.