[
https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479900#comment-13479900
]
Christian Schneider commented on KARAF-1925:
--------------------------------------------
I can reproduce the issue on karaf 2.3.0 by doing the following:
download and extract fresh karaf 2.3.0
bin/karaf
^D
bin/karaf
la -s | grep ssh
[ 17] [Active ] [GracePeriod ] [ 30] org.apache.karaf.shell.ssh (2.3.0)
[ 24] [Active ] [ ] [ 30] org.apache.sshd.core (0.8.0)
I can not reproduce with current 2.3.x snapshot
> 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
