You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Xilai Dai (JIRA)" <ji...@apache.org> on 2012/10/16 10:43:03 UTC
[jira] [Created] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Xilai Dai created KARAF-1925:
--------------------------------
Summary: 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
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
[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476946#comment-13476946 ]
Jean-Baptiste Onofré commented on KARAF-1925:
---------------------------------------------
Thanks for the update, the respectStartLvlDuringFeatureStartup property is interesting. Let me try to reproduce like this.
> 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
[jira] [Updated] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Pavel Vasilchenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Vasilchenko updated KARAF-1925:
-------------------------------------
Attachment: NormalStartupThreadDump.txt
AfterFailThreadDump.txt
GracePeriodBeforeFailThreadDump.txt
FailLog.txt
Hi, I also have reproduced this issue even with respectStartLvlDuringFeatureStartup=false.
Also I have created thread dumps with jvisualvm and attached file to this issue.
Maybe it will help you.
> 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: 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
[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477789#comment-13477789 ]
Jean-Baptiste Onofré commented on KARAF-1925:
---------------------------------------------
It depends the "dependencies". So basically, it means that the issue could be in the feature descriptor itself (start level) and not in the FeaturesService directly.
> 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
[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479022#comment-13479022 ]
Jean-Baptiste Onofré commented on KARAF-1925:
---------------------------------------------
I try with:
Bundle-SymbolicName: foobar;
blueprint.graceperiod:=false
> 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
[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477664#comment-13477664 ]
Andreas Pieber commented on KARAF-1925:
---------------------------------------
OK, I know that I've tested this before pushing :-) At least I can confirm that it works perfectly on ...
{code}
➜ ~ uname -a
Linux prime 3.6.2-1-ARCH #1 SMP PREEMPT Fri Oct 12 23:58:58 CEST 2012 x86_64 GNU/Linux
{code}
...and...
{code}
➜ ~ java -version
java version "1.7.0_07"
OpenJDK Runtime Environment (IcedTea7 2.3.2) (ArchLinux build 7.u7_2.3.2-2-x86_64)
OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)
{code}
...or...
{code}
➜ ~ /opt/java6/bin/java -version
java version "1.6.0_35"
Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01, mixed mode)
{code}
I've no windows 7 at hand right now (limited space on ssd :-)) but I'll try on my XP VM with Java 7. Let's hope I can reproduce your problem there...
> 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
[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Hendy Irawan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479971#comment-13479971 ]
Hendy Irawan commented on KARAF-1925:
-------------------------------------
Please change the environment to All, as this is not specific to Windows 7 (see #KARAF-1931).
My environment is:
{code}
Karaf
Karaf version 2.3.0
Karaf home /home/rudi/git/bippo-commerce5/karaf
Karaf base /home/rudi/git/bippo-commerce5/karaf
OSGi Framework org.apache.felix.framework - 4.0.3
JVM
Java Virtual Machine OpenJDK 64-Bit Server VM version 23.2-b09
Version 1.7.0_07
Vendor Oracle Corporation
Uptime 15.401 seconds
Total compile time 27.499 seconds
Threads
Live threads 113
Daemon threads 98
Peak 115
Total started 136
Memory
Current heap size 75,670 kbytes
Maximum heap size 466,048 kbytes
Committed heap size 245,888 kbytes
Pending objects 0
Garbage collector Name = 'PS Scavenge', Collections = 22, Time = 0.221 seconds
Garbage collector Name = 'PS MarkSweep', Collections = 1, Time = 0.130 seconds
Classes
Current classes loaded 9,043
Total classes loaded 9,044
Total classes unloaded 1
Operating system
Name Linux version 3.2.0-32-generic
Architecture amd64
Processors 4
{code}
> 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
[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Xilai Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476856#comment-13476856 ]
Xilai Dai commented on KARAF-1925:
----------------------------------
the only thing I did change is set value of respectStartLvlDuringFeatureStartup property from false to true in the etc/org.apache.karaf.features.cfg, but not sure if this issue exists when respectStartLvlDuringFeatureStartup=false (default value)
> 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
[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Xilai Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477759#comment-13477759 ]
Xilai Dai commented on KARAF-1925:
----------------------------------
Hi, I'm using 2.3.0 release.
I've tried to increase the start-lv of ssh and management bundle from 30 to 40 in the standard-2.3.0-features.xml, like this:
<feature name="ssh" description="Provide a SSHd server on Karaf" version="2.3.0">
...
<bundle start-level="40">mvn:org.apache.karaf.shell/org.apache.karaf.shell.ssh/2.3.0</bundle>
</feature>
<feature name="management" description="Provide a JMX MBeanServer and a set of MBeans in Karaf" version="2.3.0">
<bundle start-level="40">mvn:org.apache.karaf.management/org.apache.karaf.management.server/2.3.0</bundle>
...
</feature>
with these changes, it's really easy to reproduce this problem :) after those bundles failed , you will got the blueprint timeout exceptions.
[ 47] [Active ] [Failure ] [ 30] Apache Karaf :: Management :: MBeans :: System (2.3.0)
[ 48] [Active ] [Failure ] [ 30] Apache Karaf :: Management :: MBeans :: Bundles (2.3.0)
[ 49] [Active ] [Failure ] [ 30] Apache Karaf :: Management :: MBeans :: Services (2.3.0)
[ 50] [Active ] [Failure ] [ 30] Apache Karaf :: Management :: MBeans :: Config (2.3.0)
[ 51] [Active ] [Failure ] [ 30] Apache Karaf :: Management :: MBeans :: Log (2.3.0)
> 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
[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Xilai Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477679#comment-13477679 ]
Xilai Dai commented on KARAF-1925:
----------------------------------
Hi, Andreas, I can't reproduce this issue with respectStartLvlDuringFeatureStartup=false after about 30 times restart container. but with respectStartLvlDuringFeatureStartup=true, the exceptions will be shown after about 10-20 times restart container.
> 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
[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Xilai Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478731#comment-13478731 ]
Xilai Dai commented on KARAF-1925:
----------------------------------
Also can't reproduce this issue in case you add :
org/apache/karaf/management/mbeans/org.apache.karaf.management.mbeans.system/2.3.0/org.apache.karaf.management.mbeans.system-2.3.0.jar=30
org/apache/karaf/management/mbeans/org.apache.karaf.management.mbeans.bundles/2.3.0/org.apache.karaf.management.mbeans.bundles-2.3.0.jar=30
org/apache/karaf/management/mbeans/org.apache.karaf.management.mbeans.services/2.3.0/org.apache.karaf.management.mbeans.services-2.3.0.jar=30
org/apache/karaf/management/mbeans/org.apache.karaf.management.mbeans.config/2.3.0/org.apache.karaf.management.mbeans.config-2.3.0.jar=30
org/apache/karaf/management/mbeans/org.apache.karaf.management.mbeans.log/2.3.0/org.apache.karaf.management.mbeans.log-2.3.0.jar=30
org/apache/karaf/management/mbeans/org.apache.karaf.management.mbeans.packages/2.3.0/org.apache.karaf.management.mbeans.packages-2.3.0.jar=30
org/apache/karaf/management/mbeans/org.apache.karaf.management.mbeans.dev/2.3.0/org.apache.karaf.management.mbeans.dev-2.3.0.jar=30
to the startup.properties (under the line of org/apache/aries/jmx/org.apache.aries.jmx.blueprint.core/1.0.1/org.apache.aries.jmx.blueprint.core-1.0.1.jar=30 )
> 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: 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
[jira] [Comment Edited] (KARAF-1925) Blueprint timeout exceptions
after karaf startup
Posted by "Hendy Irawan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479971#comment-13479971 ]
Hendy Irawan edited comment on KARAF-1925 at 10/19/12 12:22 PM:
----------------------------------------------------------------
Please change the environment to All, as this is not specific to Windows 7 (see #KARAF-1931).
Our environment is:
{code}
Karaf
Karaf version 2.3.0
Karaf home /home/rudi/git/bippo-commerce5/karaf
Karaf base /home/rudi/git/bippo-commerce5/karaf
OSGi Framework org.apache.felix.framework - 4.0.3
JVM
Java Virtual Machine OpenJDK 64-Bit Server VM version 23.2-b09
Version 1.7.0_07
Vendor Oracle Corporation
Uptime 15.401 seconds
Total compile time 27.499 seconds
Threads
Live threads 113
Daemon threads 98
Peak 115
Total started 136
Memory
Current heap size 75,670 kbytes
Maximum heap size 466,048 kbytes
Committed heap size 245,888 kbytes
Pending objects 0
Garbage collector Name = 'PS Scavenge', Collections = 22, Time = 0.221 seconds
Garbage collector Name = 'PS MarkSweep', Collections = 1, Time = 0.130 seconds
Classes
Current classes loaded 9,043
Total classes loaded 9,044
Total classes unloaded 1
Operating system
Name Linux version 3.2.0-32-generic
Architecture amd64
Processors 4
{code}
was (Author: ceefour):
Please change the environment to All, as this is not specific to Windows 7 (see #KARAF-1931).
My environment is:
{code}
Karaf
Karaf version 2.3.0
Karaf home /home/rudi/git/bippo-commerce5/karaf
Karaf base /home/rudi/git/bippo-commerce5/karaf
OSGi Framework org.apache.felix.framework - 4.0.3
JVM
Java Virtual Machine OpenJDK 64-Bit Server VM version 23.2-b09
Version 1.7.0_07
Vendor Oracle Corporation
Uptime 15.401 seconds
Total compile time 27.499 seconds
Threads
Live threads 113
Daemon threads 98
Peak 115
Total started 136
Memory
Current heap size 75,670 kbytes
Maximum heap size 466,048 kbytes
Committed heap size 245,888 kbytes
Pending objects 0
Garbage collector Name = 'PS Scavenge', Collections = 22, Time = 0.221 seconds
Garbage collector Name = 'PS MarkSweep', Collections = 1, Time = 0.130 seconds
Classes
Current classes loaded 9,043
Total classes loaded 9,044
Total classes unloaded 1
Operating system
Name Linux version 3.2.0-32-generic
Architecture amd64
Processors 4
{code}
> 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
[jira] [Assigned] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479946#comment-13479946 ]
Jean-Baptiste Onofré commented on KARAF-1925:
---------------------------------------------
blueprint.graceperiod:=false works.
I think it's an issue in Aries Blueprint 1.0.1. Let me create a Jira there.
> 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
[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Pavel Vasilchenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478873#comment-13478873 ]
Pavel Vasilchenko commented on KARAF-1925:
------------------------------------------
I reproduced bug with this configuration
> 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: 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
[jira] [Updated] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Xilai Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xilai Dai updated KARAF-1925:
-----------------------------
Attachment: karaf.log
> 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
[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479882#comment-13479882 ]
Jean-Baptiste Onofré commented on KARAF-1925:
---------------------------------------------
I also add timeout=0.
> 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
[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Xilai Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478626#comment-13478626 ]
Xilai Dai commented on KARAF-1925:
----------------------------------
FYI, can't reproduce this issue in case respectStartLvlDuringFeatureStartup=true, but add dependency="true" property to:
<bundle start-level="30" dependency="true">mvn:org.apache.karaf.management/org.apache.karaf.management.server/2.3.0</bundle>
in the management feature of feature descriptor.
> 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: 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
[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Xilai Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477760#comment-13477760 ]
Xilai Dai commented on KARAF-1925:
----------------------------------
so, maybe decrease start-lv of ssh/management from 30 to 25 will be a workaround with respectStartLvlDuringFeatureStartup=true case, need more test...
> 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
[jira] [Updated] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-1925:
----------------------------------------
Environment: (was: Win 7, Java 7)
> 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é
> 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
[jira] [Commented] (KARAF-1925) Blueprint timeout exceptions after
karaf startup
Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477682#comment-13477682 ]
Andreas Pieber commented on KARAF-1925:
---------------------------------------
maybe my computer is simply too fast... are you using 2.3.0 (FINAL) or the 2.3.1-SNAPSHOTs? If this is the case, can you try to increase the start-lvl of those two bundles a bit (or decrease it) and check if the error still occurs. I would do it myself if I could reproduce it, but so I woult really appreciate your help.
Thank you very much!
> 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