You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Raul Kripalani (Created) (JIRA)" <ji...@apache.org> on 2011/11/08 17:21:51 UTC

[jira] [Created] (KARAF-986) Synchronisation issue when rootLogger is DEBUG and Karaf is started afresh

Synchronisation issue when rootLogger is DEBUG and Karaf is started afresh
--------------------------------------------------------------------------

                 Key: KARAF-986
                 URL: https://issues.apache.org/jira/browse/KARAF-986
             Project: Karaf
          Issue Type: Bug
    Affects Versions: 2.2.4
            Reporter: Raul Kripalani


When working in development mode, you will many times set your rootLogger's level to DEBUG.

If you delete the $KARAF_HOME/data dir and start afresh while your rootLogger remains on DEBUG, Karaf will likely block during bundle startup if you have large number of boot features (e.g. ServiceMix) defined in the {{featuresBoot}} property under {{org.apache.karaf.features.cfg}}. 

Changing the log level back to INFO avoids the issue.

Looks like it only happens if a large number of threads is emitting log statements simultaneously, as seen in [1] & [2]. Thread dump looks exactly the same as the one submitted in [1].

Not sure if there's much we can do on the Karaf side of things, but I guess it's worth raising.

[1] https://issues.apache.org/bugzilla/show_bug.cgi?id=50213
[2] https://issues.apache.org/bugzilla/show_bug.cgi?id=51047

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (KARAF-986) Synchronisation issue when rootLogger is DEBUG and Karaf is started afresh

Posted by "Guillaume Nodet (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148140#comment-13148140 ] 

Guillaume Nodet commented on KARAF-986:
---------------------------------------

The reason for those questions is that those bugs have been ported into pax-logging a long time ago and have been included in karaf since a few releases afaik.  Although ServiceMix is using a slightly older version of Karaf, so I'd suggest upgrading your pax-logging bundles in your ServiceMix distribution to the latest releases and double-check if you still see those issues.
                
> Synchronisation issue when rootLogger is DEBUG and Karaf is started afresh
> --------------------------------------------------------------------------
>
>                 Key: KARAF-986
>                 URL: https://issues.apache.org/jira/browse/KARAF-986
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 2.2.4
>            Reporter: Raul Kripalani
>
> When working in development mode, you will many times set your rootLogger's level to DEBUG.
> If you delete the $KARAF_HOME/data dir and start afresh while your rootLogger remains on DEBUG, Karaf will likely block during bundle startup if you have large number of boot features (e.g. ServiceMix) defined in the {{featuresBoot}} property under {{org.apache.karaf.features.cfg}}. 
> Changing the log level back to INFO avoids the issue.
> Looks like it only happens if a large number of threads is emitting log statements simultaneously, as seen in [1] & [2]. Thread dump looks exactly the same as the one submitted in [1].
> Not sure if there's much we can do on the Karaf side of things, but I guess it's worth raising.
> [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=50213
> [2] https://issues.apache.org/bugzilla/show_bug.cgi?id=51047

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (KARAF-986) Synchronisation issue when rootLogger is DEBUG and Karaf is started afresh

Posted by "Jean-Baptiste Onofré (Commented JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148058#comment-13148058 ] 

Jean-Baptiste Onofré commented on KARAF-986:
--------------------------------------------

Are you sure that you use Karaf 2.2.4 ?
Could you check your Pax Logging version in use ?

Thanks
                
> Synchronisation issue when rootLogger is DEBUG and Karaf is started afresh
> --------------------------------------------------------------------------
>
>                 Key: KARAF-986
>                 URL: https://issues.apache.org/jira/browse/KARAF-986
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 2.2.4
>            Reporter: Raul Kripalani
>
> When working in development mode, you will many times set your rootLogger's level to DEBUG.
> If you delete the $KARAF_HOME/data dir and start afresh while your rootLogger remains on DEBUG, Karaf will likely block during bundle startup if you have large number of boot features (e.g. ServiceMix) defined in the {{featuresBoot}} property under {{org.apache.karaf.features.cfg}}. 
> Changing the log level back to INFO avoids the issue.
> Looks like it only happens if a large number of threads is emitting log statements simultaneously, as seen in [1] & [2]. Thread dump looks exactly the same as the one submitted in [1].
> Not sure if there's much we can do on the Karaf side of things, but I guess it's worth raising.
> [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=50213
> [2] https://issues.apache.org/bugzilla/show_bug.cgi?id=51047

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira