[ 
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

Reply via email to