You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2012/10/18 15:36:03 UTC
[jira] [Assigned] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-1925:
-------------------------------------------
Assignee: Jean-Baptiste Onofré
> 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
> Environment: Win 7, Java 7
> Reporter: Xilai Dai
> Assignee: Jean-Baptiste Onofré
> 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