You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2007/09/18 16:27:43 UTC
[jira] Created: (DERBY-3079) Database name is printed twice in
derby.log on rollbacks when logStatementText is enabled
Database name is printed twice in derby.log on rollbacks when logStatementText is enabled
------------------------------------------------------------------------------------------
Key: DERBY-3079
URL: https://issues.apache.org/jira/browse/DERBY-3079
Project: Derby
Issue Type: Bug
Components: Miscellaneous
Affects Versions: 10.3.1.4, 10.2.2.0, 10.1.3.1, 10.4.0.0
Reporter: Kristian Waagan
Assignee: Kristian Waagan
Priority: Trivial
Fix For: 10.4.0.0
When the property derby.language.logStatementText is set to true, the database name is written twice in the log entry for rollbacks.
Example:
2007-09-18 10:28:42.355 GMT Thread[thread 3] (XID = 4890252), (SESSIONID = 128), (DATABASE = MyDB), (DATABASE = MyDB), (DRDAID = null), Rolling back
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Updated: (DERBY-3079) Database name is printed twice in
derby.log on rollbacks when logStatementText is enabled
Posted by Kristian Waagan <Kr...@Sun.COM>.
Myrna van Lunteren wrote:
> On 9/19/07, Kristian Waagan (JIRA) <ji...@apache.org> wrote:
>
>> The only problem I can think about is people parsing the log for some reason, but it should be easy enough for them to fix their parsers/scripts.
>
> Then maybe this issue should get flagged as existing application impact?
Hi Myrna,
I just did that. Is there anything special one has to take care of for
such issues?
Or will they just be put on a list in the release notes or something?
thanks,
--
Kristian
>
> Myrna
Re: [jira] Updated: (DERBY-3079) Database name is printed twice in derby.log on rollbacks when logStatementText is enabled
Posted by Myrna van Lunteren <m....@gmail.com>.
On 9/19/07, Kristian Waagan (JIRA) <ji...@apache.org> wrote:
> The only problem I can think about is people parsing the log for some reason, but it should be easy enough for them to fix their parsers/scripts.
Then maybe this issue should get flagged as existing application impact?
Myrna
[jira] Commented: (DERBY-3079) Database name is printed twice in
derby.log on rollbacks when logStatementText is enabled
Posted by "Thomas Nielsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528747 ]
Thomas Nielsen commented on DERBY-3079:
---------------------------------------
The patch is OK, and suites.All ran without problems for me as well.
> Database name is printed twice in derby.log on rollbacks when logStatementText is enabled
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-3079
> URL: https://issues.apache.org/jira/browse/DERBY-3079
> Project: Derby
> Issue Type: Bug
> Components: Miscellaneous
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.1.4, 10.4.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Trivial
> Fix For: 10.4.0.0
>
> Attachments: derby-3079-1a.diff
>
>
> When the property derby.language.logStatementText is set to true, the database name is written twice in the log entry for rollbacks.
> Example:
> 2007-09-18 10:28:42.355 GMT Thread[thread 3] (XID = 4890252), (SESSIONID = 128), (DATABASE = MyDB), (DATABASE = MyDB), (DRDAID = null), Rolling back
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-3079) Database name is printed twice in
derby.log on rollbacks when logStatementText is enabled
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan closed DERBY-3079.
----------------------------------
> Database name is printed twice in derby.log on rollbacks when logStatementText is enabled
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-3079
> URL: https://issues.apache.org/jira/browse/DERBY-3079
> Project: Derby
> Issue Type: Bug
> Components: Miscellaneous
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.1.4, 10.4.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Trivial
> Fix For: 10.4.0.0
>
> Attachments: derby-3079-1a.diff
>
>
> When the property derby.language.logStatementText is set to true, the database name is written twice in the log entry for rollbacks.
> Example:
> 2007-09-18 10:28:42.355 GMT Thread[thread 3] (XID = 4890252), (SESSIONID = 128), (DATABASE = MyDB), (DATABASE = MyDB), (DRDAID = null), Rolling back
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3079) Database name is printed twice in
derby.log on rollbacks when logStatementText is enabled
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-3079:
-----------------------------------
Derby Info: [Patch Available, Existing Application Impact] (was: [Patch Available])
I'm marking this as having existing application impact.
I do plan to commit the patch shortly.
> Database name is printed twice in derby.log on rollbacks when logStatementText is enabled
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-3079
> URL: https://issues.apache.org/jira/browse/DERBY-3079
> Project: Derby
> Issue Type: Bug
> Components: Miscellaneous
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.1.4, 10.4.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Trivial
> Fix For: 10.4.0.0
>
> Attachments: derby-3079-1a.diff
>
>
> When the property derby.language.logStatementText is set to true, the database name is written twice in the log entry for rollbacks.
> Example:
> 2007-09-18 10:28:42.355 GMT Thread[thread 3] (XID = 4890252), (SESSIONID = 128), (DATABASE = MyDB), (DATABASE = MyDB), (DRDAID = null), Rolling back
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3079) Database name is printed twice in
derby.log on rollbacks when logStatementText is enabled
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573743#action_12573743 ]
Kristian Waagan commented on DERBY-3079:
----------------------------------------
I'm wondering if the existing application impact can be unchecked and the issue closed?
> Database name is printed twice in derby.log on rollbacks when logStatementText is enabled
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-3079
> URL: https://issues.apache.org/jira/browse/DERBY-3079
> Project: Derby
> Issue Type: Bug
> Components: Miscellaneous
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.1.4, 10.4.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Trivial
> Fix For: 10.4.0.0
>
> Attachments: derby-3079-1a.diff
>
>
> When the property derby.language.logStatementText is set to true, the database name is written twice in the log entry for rollbacks.
> Example:
> 2007-09-18 10:28:42.355 GMT Thread[thread 3] (XID = 4890252), (SESSIONID = 128), (DATABASE = MyDB), (DATABASE = MyDB), (DRDAID = null), Rolling back
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3079) Database name is printed twice in
derby.log on rollbacks when logStatementText is enabled
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-3079:
-----------------------------------
Derby Info: (was: [Existing Application Impact])
Unset "Existing Application Impact ".
> Database name is printed twice in derby.log on rollbacks when logStatementText is enabled
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-3079
> URL: https://issues.apache.org/jira/browse/DERBY-3079
> Project: Derby
> Issue Type: Bug
> Components: Miscellaneous
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.1.4, 10.4.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Trivial
> Fix For: 10.4.0.0
>
> Attachments: derby-3079-1a.diff
>
>
> When the property derby.language.logStatementText is set to true, the database name is written twice in the log entry for rollbacks.
> Example:
> 2007-09-18 10:28:42.355 GMT Thread[thread 3] (XID = 4890252), (SESSIONID = 128), (DATABASE = MyDB), (DATABASE = MyDB), (DRDAID = null), Rolling back
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3079) Database name is printed twice in
derby.log on rollbacks when logStatementText is enabled
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-3079:
-----------------------------------
Derby Info: [Patch Available]
> Database name is printed twice in derby.log on rollbacks when logStatementText is enabled
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-3079
> URL: https://issues.apache.org/jira/browse/DERBY-3079
> Project: Derby
> Issue Type: Bug
> Components: Miscellaneous
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.1.4, 10.4.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Trivial
> Fix For: 10.4.0.0
>
> Attachments: derby-3079-1a.diff
>
>
> When the property derby.language.logStatementText is set to true, the database name is written twice in the log entry for rollbacks.
> Example:
> 2007-09-18 10:28:42.355 GMT Thread[thread 3] (XID = 4890252), (SESSIONID = 128), (DATABASE = MyDB), (DATABASE = MyDB), (DRDAID = null), Rolling back
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3079) Database name is printed twice in
derby.log on rollbacks when logStatementText is enabled
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-3079:
-----------------------------------
Attachment: derby-3079-1a.diff
'derby-3079-1a.diff' removes one of the printouts of the database name.
I ran suites.All and derbyall without failures.
I'll commit in a few days. The only problem I can think about is people parsing the log for some reason, but it should be easy enough for them to fix their parsers/scripts.
> Database name is printed twice in derby.log on rollbacks when logStatementText is enabled
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-3079
> URL: https://issues.apache.org/jira/browse/DERBY-3079
> Project: Derby
> Issue Type: Bug
> Components: Miscellaneous
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.1.4, 10.4.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Trivial
> Fix For: 10.4.0.0
>
> Attachments: derby-3079-1a.diff
>
>
> When the property derby.language.logStatementText is set to true, the database name is written twice in the log entry for rollbacks.
> Example:
> 2007-09-18 10:28:42.355 GMT Thread[thread 3] (XID = 4890252), (SESSIONID = 128), (DATABASE = MyDB), (DATABASE = MyDB), (DRDAID = null), Rolling back
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-3079) Database name is printed twice in
derby.log on rollbacks when logStatementText is enabled
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan resolved DERBY-3079.
------------------------------------
Resolution: Fixed
Derby Info: [Existing Application Impact] (was: [Existing Application Impact, Patch Available])
Committed 'derby-3079-1a.diff' to trunk with revision 584051.
Thanks Thomas for looking at the patch :)
> Database name is printed twice in derby.log on rollbacks when logStatementText is enabled
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-3079
> URL: https://issues.apache.org/jira/browse/DERBY-3079
> Project: Derby
> Issue Type: Bug
> Components: Miscellaneous
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.1.4, 10.4.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Trivial
> Fix For: 10.4.0.0
>
> Attachments: derby-3079-1a.diff
>
>
> When the property derby.language.logStatementText is set to true, the database name is written twice in the log entry for rollbacks.
> Example:
> 2007-09-18 10:28:42.355 GMT Thread[thread 3] (XID = 4890252), (SESSIONID = 128), (DATABASE = MyDB), (DATABASE = MyDB), (DRDAID = null), Rolling back
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.