[
https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477672#comment-13477672
]
Andreas Pieber commented on KARAF-1925:
---------------------------------------
Windows XP, SP2, all patches installed with...
{code}
C:\> java -version
java version "1.7.0_07"
Java(TM) SE Runtime Environment (build 1.7.0_07-b11)
Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode)
{code}
and it works like a charm too...
I give up. Any more information you can provide us with? Maybe it's a timing
issue? Can you try if you get the same result if you set
respectStartLvlDuringFeatureStartup=false (the default value)?
Thanks
> 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
> Attachments: karaf.log
>
>
> 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
