You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/10/15 10:39:44 UTC

[jira] Created: (JCR-1812) WorkspaceUpdateChannel.updateCommitted logs too much

WorkspaceUpdateChannel.updateCommitted logs too much
----------------------------------------------------

                 Key: JCR-1812
                 URL: https://issues.apache.org/jira/browse/JCR-1812
             Project: Jackrabbit
          Issue Type: Improvement
          Components: clustering
    Affects Versions: core 1.4.2
            Reporter: Felix Meschberger


On each cluster record update, an info message is logged.

I think this is too much and logging should be reduced to the DEBUG level.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (JCR-1812) WorkspaceUpdateChannel.updateCommitted logs too much

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger updated JCR-1812:
-----------------------------------

    Attachment: JCR-cluster-update-log.patch

Proposed patch, which also includes making use of SLF4Js log call optimization for not concatenating strings if not needed.

> WorkspaceUpdateChannel.updateCommitted logs too much
> ----------------------------------------------------
>
>                 Key: JCR-1812
>                 URL: https://issues.apache.org/jira/browse/JCR-1812
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: clustering
>    Affects Versions: core 1.4.2
>            Reporter: Felix Meschberger
>         Attachments: JCR-cluster-update-log.patch
>
>
> On each cluster record update, an info message is logged.
> I think this is too much and logging should be reduced to the DEBUG level.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (JCR-1812) WorkspaceUpdateChannel.updateCommitted logs too much

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-1812:
-------------------------------

          Component/s: jackrabbit-core
             Priority: Trivial  (was: Major)
    Affects Version/s:     (was: core 1.4.2)
        Fix Version/s: 1.5.0

Looks good. Commit it soon and I'll get this included in 1.5. :-)

> WorkspaceUpdateChannel.updateCommitted logs too much
> ----------------------------------------------------
>
>                 Key: JCR-1812
>                 URL: https://issues.apache.org/jira/browse/JCR-1812
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: clustering, jackrabbit-core
>            Reporter: Felix Meschberger
>            Priority: Trivial
>             Fix For: 1.5.0
>
>         Attachments: JCR-cluster-update-log.patch
>
>
> On each cluster record update, an info message is logged.
> I think this is too much and logging should be reduced to the DEBUG level.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (JCR-1812) WorkspaceUpdateChannel.updateCommitted logs too much

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger updated JCR-1812:
-----------------------------------

    Fix Version/s: 1.6.0

> WorkspaceUpdateChannel.updateCommitted logs too much
> ----------------------------------------------------
>
>                 Key: JCR-1812
>                 URL: https://issues.apache.org/jira/browse/JCR-1812
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: clustering, jackrabbit-core
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>            Priority: Trivial
>             Fix For: 1.5.0, 1.6.0
>
>         Attachments: JCR-cluster-update-log.patch
>
>
> On each cluster record update, an info message is logged.
> I think this is too much and logging should be reduced to the DEBUG level.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (JCR-1812) WorkspaceUpdateChannel.updateCommitted logs too much

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-1812:
-------------------------------

    Fix Version/s:     (was: 1.6.0)

> WorkspaceUpdateChannel.updateCommitted logs too much
> ----------------------------------------------------
>
>                 Key: JCR-1812
>                 URL: https://issues.apache.org/jira/browse/JCR-1812
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: clustering, jackrabbit-core
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>            Priority: Trivial
>             Fix For: 1.5.0
>
>         Attachments: JCR-cluster-update-log.patch
>
>
> On each cluster record update, an info message is logged.
> I think this is too much and logging should be reduced to the DEBUG level.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (JCR-1812) WorkspaceUpdateChannel.updateCommitted logs too much

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger closed JCR-1812.
----------------------------------

    Resolution: Fixed

Applied patch to 1.5 branch in Rev. 704863 and to trunk in Rev. 704864.

> WorkspaceUpdateChannel.updateCommitted logs too much
> ----------------------------------------------------
>
>                 Key: JCR-1812
>                 URL: https://issues.apache.org/jira/browse/JCR-1812
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: clustering, jackrabbit-core
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>            Priority: Trivial
>             Fix For: 1.5.0
>
>         Attachments: JCR-cluster-update-log.patch
>
>
> On each cluster record update, an info message is logged.
> I think this is too much and logging should be reduced to the DEBUG level.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (JCR-1812) WorkspaceUpdateChannel.updateCommitted logs too much

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger reassigned JCR-1812:
--------------------------------------

    Assignee: Felix Meschberger

> WorkspaceUpdateChannel.updateCommitted logs too much
> ----------------------------------------------------
>
>                 Key: JCR-1812
>                 URL: https://issues.apache.org/jira/browse/JCR-1812
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: clustering, jackrabbit-core
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>            Priority: Trivial
>             Fix For: 1.5.0
>
>         Attachments: JCR-cluster-update-log.patch
>
>
> On each cluster record update, an info message is logged.
> I think this is too much and logging should be reduced to the DEBUG level.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.