[
https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479019#comment-13479019
]
Jean-Baptiste Onofré commented on KARAF-1925:
---------------------------------------------
The following changes in etc/startup.properties look to provide good result:
org/apache/karaf/features/org.apache.karaf.features.core/2.3.0/org.apache.karaf.features.core-2.3.0.jar=25
org/apache/karaf/jaas/org.apache.karaf.jaas.config/2.3.0/org.apache.karaf.jaas.config-2.3.0.jar=25
org/apache/karaf/jaas/org.apache.karaf.jaas.modules/2.3.0/org.apache.karaf.jaas.modules-2.3.0.jar=25
org/apache/karaf/jaas/org.apache.karaf.jaas.command/2.3.0/org.apache.karaf.jaas.command-2.3.0.jar=25
In the mean time, as I suspect a "low" timeout in the Blueprint service
reference resolution, I try to increase this timeout.
> 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
