[
https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801955#comment-13801955
]
Marcos commented on KARAF-1925:
-------------------------------
Does this setting work on Karaf 2.3.1?
> 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 was sent by Atlassian JIRA
(v6.1#6144)
