[
https://issues.apache.org/jira/browse/FELIX-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753024#action_12753024
]
Guillaume Nodet commented on FELIX-1574:
----------------------------------------
Committing to https://svn.apache.org/repos/asf/felix/trunk ...
M karaf/assembly/src/main/filtered-resources/bin/admin
M karaf/assembly/src/main/filtered-resources/bin/admin.bat
M
karaf/gshell/gshell-admin/src/main/java/org/apache/felix/karaf/gshell/admin/internal/AdminServiceImpl.java
M
karaf/gshell/gshell-admin/src/main/java/org/apache/felix/karaf/gshell/admin/main/Execute.java
M
karaf/gshell/gshell-admin/src/main/resources/OSGI-INF/blueprint/gshell-admin.xml
Committed r812879
The above commit fix the fact that instances are not always created in
<root>/instances.
Not sure if this is the real cause of your problem but I haven't been able to
reproduce it with the above fix on Max OsX.
For the JMX/RMI exception, i'll raise a separate issue.
> Some Karaf instances never reach the 'started' state
> ----------------------------------------------------
>
> Key: FELIX-1574
> URL: https://issues.apache.org/jira/browse/FELIX-1574
> Project: Felix
> Issue Type: Bug
> Components: Karaf
> Affects Versions: karaf-1.0.0
> Reporter: David Bosschaert
>
> Instances crested from the default karaf instance shell never show up as
> started
> Here's how it's reproduced:
> 1. create an instance from command line
> 2. start that instance from the command lie
> 3. start default karaf instance
> (this throws up an JMX/RMI exception)
> 4. create & start another instance form within the default karaf one
> now the admin list shows the other new one as 'starting'
> both in karaf as well as from the command line
> An interesting observation is that these instances get created in
> <root>/bin/instances instead of <root>/instances
> BTW: The CWD when I started karaf was <root>/bin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
