[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after karaf startup

["Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697967#comment-13697967 ] 

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

I close this issue as it should be fixed with blueprint.synchronous=true. Please, reopen the Jira if you see this issue again.
                
> Blueprint timeout exceptions after karaf startup
> ------------------------------------------------
>
>                 Key: KARAF-1925
>                 URL: https://issues.apache.org/jira/browse/KARAF-1925
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>    Affects Versions: 2.3.0
>            Reporter: Xilai Dai
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 2.3.2
>
>         Attachments: AfterFailThreadDump.txt, FailLog.txt, GracePeriodBeforeFailThreadDump.txt, karaf.log, NormalStartupThreadDump.txt
>
>
> the karaf management bundle (or the karaf ssh bundle) sometimes will be on the GracePeriod after start karaf container.
> [  17] [Active     ] [GracePeriod ] [       ] [   30] Apache Karaf :: Shell :: SSH (2.3.0)
> or
> [  18] [Active     ] [GracePeriod ] [       ] [   30] Apache Karaf :: Management (2.3.0)
> and got the blueprint timeout exceptions in the karaf.log (attached)
> if then refresh the bundles manually:
> karaf@root>refresh 18
> or
> karaf@root>refresh 17
> then, everything will be ok.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira