[
https://issues.apache.org/jira/browse/KARAF-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667119#comment-13667119
]
Ryan Moquin commented on KARAF-2340:
------------------------------------
Actually, I guess there is only one the karaf.bat, I could have swore when I
started karaf it told me the nio class wasn't found and I added it to
jre.properties, restarted and then it found it. I now don't see if in
jre.properties, I think I added it to the wrong version of karaf, which is
strange that 2.3.1 started up without complaint. Anyhow, so it looks like only
karaf.bat in 2.3.1 needs the property added. I'll check 2.3.2 which must be
where I saw the complaint, but had meant to try it on 2.3.1 first.
> Stock Karaf 2.3.1, Cellar 2.3.0, CPU go to constant 20%
> -------------------------------------------------------
>
> Key: KARAF-2340
> URL: https://issues.apache.org/jira/browse/KARAF-2340
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
> Affects Versions: 2.3.1
> Environment: Windows 7 JDK7_17
> Reporter: Ryan Moquin
> Assignee: Jean-Baptiste Onofré
> Attachments: console_screen.JPG,
> karaf-2.3.1-cellar-2.3.0-installing-eventadmin.JPG,
> karaf-2.3.1-cellar-2.3.0-profile.nps
>
>
> I've been working on a demo for several weeks to promote Karaf and Cellar.
> Even thought Karaf 3.0.0 seems to work great, the addition of Cellar just
> isn't ready yet. When I tried Karaf 2.3.2-SNASHOT with Cellar 2.3.0, my CPU
> went to 25% and hazelcase 5 seemed to be going a bit crazy. So I moved to
> Karaf 2.3.1 and Celler 2.3.0. I was able to install cellar but when I
> finally typed the correct comment to install the admin, my cpu utilization
> went to 25% and the features:install command never returned.
> Attached are some screenshots of sampling from jvisualvm (the profiler seems
> to through karaf into fits). I'm a little lost on how to get Karad and
> Cellar running correctly together.
--
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
