[ 
https://issues.apache.org/jira/browse/KARAF-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131025#comment-14131025
 ] 

Nitai Pramanik commented on KARAF-3218:
---------------------------------------

Hi Freeman
Thanks
Could you please point out where i can get binary compatible with 2.3.2
version...it looks like i need some jar files..
Could u please send me pointer for getting binaries compatible to 2.3.2...
I need to replace impacted binaries.
Thanks



> Sometimes instance.properties or org.apache.karaf.management.cfg or 
> org.apache.karaf.shell.cfg becomes zero size or contents are not fully 
> populated
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KARAF-3218
>                 URL: https://issues.apache.org/jira/browse/KARAF-3218
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-instance
>    Affects Versions: 2.3.2
>         Environment: apache karaf 2.3.2 running on RedHat vmware.   (OS : 
> Linux 6.32-431.el6.x86_64 #1 SMP Sun Nov 10 22:19:54 EST 2013 x86_64 x86_64 
> x86_64 GNU/Linux)
>            Reporter: Nitai Pramanik
>            Assignee: Freeman Fang
>
> Here is the following steps we do --
> 1- Running karaf with root instance  name (Say - "base")
> 2- Create 2 instances using "admin:create instance" (Say - "child1", "child2")
> 3- We do monitor the list of instances running using "admin:list" or "admin 
> list"
> We have noticed that instance.properties, two config files for each 
> instance(org.apache.karaf.management.cfg and org.apache.karaf.shell.cfg)  are 
> getting recreated once we run "admin:list" or "admin list" command.
> Sometime files are truncated to zero size or files have incomlete contents 
> after the reboot.
> Also, we have seen the similar issue when we do kill the "admin list" command 
> abnormally using ^C.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to