[jira] [Created] (KARAF-4873) keystore.jks update in karaf requires force restart

[Suresh Perumal (JIRA)]

Suresh Perumal created KARAF-4873:
-

 Summary: keystore.jks update in karaf requires force restart
 Key: KARAF-4873
 URL: https://issues.apache.org/jira/browse/KARAF-4873
 Project: Karaf
  Issue Type: Question
  Components: cellar-http
Affects Versions: 4.0.5
 Environment: karaf 4.0.5/4.0.6 on Linux CentOS, RHEL Platform
Reporter: Suresh Perumal
Priority: Blocker


We are using Karaf 4.0.5, 4.0.6.

We are using self signed certificate for https support.

There are some scenarios where the certificate will get expired where we need 
to regenerate the certificate again.
During this scenario, newly generated keystore.jks getting stored in Karaf. 
,KARAF_HOME/etc folder.
But looks like it is not picking up the latest keystore.jks and it requires 
restart of karaf server. 

To some extent we will not be able to restart the karaf server which might not 
be correct approach.

I would like to know the approach to force update of certificates without 
restarts.



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

[jira] [Assigned] (KARAF-4834) Infinite loop if Exception occurs during the execution of karaf.shell.init.script

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet reassigned KARAF-4834:
--

Assignee: Guillaume Nodet

> Infinite loop if Exception occurs during the execution of 
> karaf.shell.init.script
> -
>
> Key: KARAF-4834
> URL: https://issues.apache.org/jira/browse/KARAF-4834
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
> Attachments: karaf.log
>
>
> The while block between line 329 and line 352 in 
> https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
>  will never break if Exception other than EndOfFileException is thrown, e.g. 
> StreamClosed exception.
> After executing a karaf command (the commands are in a scritp which will be 
> executed via the command source) I happened to get the Interrupted error, 
> then the branding screen was shown, followed by infinite Stream Closed 
> IOException. Sorry I got this phenomenon onlyfrom time to time and cannot 
> provide stable steps to reproduce it.
> {code}
> karaf@root() 
> Error executing command: java.lang.InterruptedException
> gogo: InterruptedException: null
> __ __  
>/ //_/ __ _/ __/
>   / ,<  / __ `/ ___/ __ `/ /_
>  / /| |/ /_/ / /  / /_/ / __/
> /_/ |_|\__,_/_/   \__,_/_/
>   Apache Karaf (4.1.0-SNAPSHOT)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()>  Error executing command: java.io.IOException: Stream Closed
> ... hunderts lines with same content ignored here ...
> karaf@root()>  Error executing command: java.io.IOException: Stream Closed
> {code}
> I have attached the log.



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

[jira] [Resolved] (KARAF-4872) Karaf build failed when assemby the minimal distribution

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet resolved KARAF-4872.

   Resolution: Fixed
 Assignee: Guillaume Nodet
Fix Version/s: 4.1.0

> Karaf build failed when assemby the minimal distribution
> 
>
> Key: KARAF-4872
> URL: https://issues.apache.org/jira/browse/KARAF-4872
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-osgi
>Reporter: Zheng Feng
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> [ERROR] Failed to execute goal 
> org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:assembly 
> (process-resources) on project apache-karaf-minimal: Unable to parse 
> configuration of mojo 
> org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:assembly for 
> parameter pidsToExtract: Cannot assign configuration entry 'pidsToExtract' 
> with value '!jmx.acl.*,
> [ERROR] !org.apache.karaf.command.acl.*,
> [ERROR] *' of type java.lang.String to property of type java.util.List



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

[jira] [Commented] (KARAF-4872) Karaf build failed when assemby the minimal distribution

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4872:


Commit 88d9480d13f7a0983368bbad4413d5448d79acd8 in karaf's branch 
refs/heads/master from [~gnt]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=88d9480 ]

[KARAF-4872] Require maven >= 3.3

> Karaf build failed when assemby the minimal distribution
> 
>
> Key: KARAF-4872
> URL: https://issues.apache.org/jira/browse/KARAF-4872
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-osgi
>Reporter: Zheng Feng
> Fix For: 4.1.0
>
>
> [ERROR] Failed to execute goal 
> org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:assembly 
> (process-resources) on project apache-karaf-minimal: Unable to parse 
> configuration of mojo 
> org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:assembly for 
> parameter pidsToExtract: Cannot assign configuration entry 'pidsToExtract' 
> with value '!jmx.acl.*,
> [ERROR] !org.apache.karaf.command.acl.*,
> [ERROR] *' of type java.lang.String to property of type java.util.List



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

[jira] [Resolved] (KARAF-4858) Upgrade to Felix Resolver 1.10.1

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4858.
-
Resolution: Fixed

> Upgrade to Felix Resolver 1.10.1
> 
>
> Key: KARAF-4858
> URL: https://issues.apache.org/jira/browse/KARAF-4858
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.8
>
>




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

[jira] [Commented] (KARAF-4858) Upgrade to Felix Resolver 1.10.1

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4858:


Commit 68f31c09f8fffcc1399e8061ee2993844605965e in karaf's branch 
refs/heads/karaf-4.0.x from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=68f31c0 ]

[KARAF-4858] Upgrade to Felix Resolver 1.10.1


> Upgrade to Felix Resolver 1.10.1
> 
>
> Key: KARAF-4858
> URL: https://issues.apache.org/jira/browse/KARAF-4858
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.8
>
>




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

[jira] [Commented] (KARAF-4858) Upgrade to Felix Resolver 1.10.1

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4858:


Commit 412afa4baa4b44c1e8b2a6c4744cfe333a832da2 in karaf's branch 
refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=412afa4 ]

[KARAF-4858] Upgrade to Felix Resolver 1.10.1


> Upgrade to Felix Resolver 1.10.1
> 
>
> Key: KARAF-4858
> URL: https://issues.apache.org/jira/browse/KARAF-4858
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.8
>
>




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

[jira] [Created] (KARAF-4872) Karaf build failed when assemby the minimal distribution

[Zheng Feng (JIRA)]

Zheng Feng created KARAF-4872:
-

 Summary: Karaf build failed when assemby the minimal distribution
 Key: KARAF-4872
 URL: https://issues.apache.org/jira/browse/KARAF-4872
 Project: Karaf
  Issue Type: Bug
  Components: karaf-osgi
Reporter: Zheng Feng


[ERROR] Failed to execute goal 
org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:assembly 
(process-resources) on project apache-karaf-minimal: Unable to parse 
configuration of mojo 
org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:assembly for 
parameter pidsToExtract: Cannot assign configuration entry 'pidsToExtract' with 
value '!jmx.acl.*,
[ERROR] !org.apache.karaf.command.acl.*,
[ERROR] *' of type java.lang.String to property of type java.util.List



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

[jira] [Assigned] (KARAF-4871) LDAPLoginModule NPEs if no role filter is specified

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré reassigned KARAF-4871:
---

Assignee: Jean-Baptiste Onofré

> LDAPLoginModule NPEs if no role filter is specified
> ---
>
> Key: KARAF-4871
> URL: https://issues.apache.org/jira/browse/KARAF-4871
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.7
>Reporter: Colm O hEigeartaigh
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.8
>
> Attachments: KARAF-4871.patch
>
>
> The LDAPLoginModule throws a NullPointerException if no role filter is 
> specified. However, it's perfectly valid to use a LDAPLoginModule just for 
> authentication, and not perform any group/role lookup.



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

[jira] [Resolved] (KARAF-4857) Upgrade to Felix EventAdmin 1.4.8

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4857.
-
Resolution: Fixed

> Upgrade to Felix EventAdmin 1.4.8
> -
>
> Key: KARAF-4857
> URL: https://issues.apache.org/jira/browse/KARAF-4857
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.8
>
>




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

[jira] [Commented] (KARAF-4857) Upgrade to Felix EventAdmin 1.4.8

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4857:


Commit 26bff67a259d838d2adcbafa3e04549f47ad7e36 in karaf's branch 
refs/heads/karaf-4.0.x from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=26bff67a ]

[KARAF-4857] Upgrade to Felix EventAdmin 1.4.8


> Upgrade to Felix EventAdmin 1.4.8
> -
>
> Key: KARAF-4857
> URL: https://issues.apache.org/jira/browse/KARAF-4857
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.8
>
>




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

[jira] [Commented] (KARAF-4857) Upgrade to Felix EventAdmin 1.4.8

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4857:


Commit 7cf00038a5eaa4487045aac99f1b547a2093aefe in karaf's branch 
refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=7cf0003 ]

[KARAF-4857] Upgrade to Felix EventAdmin 1.4.8


> Upgrade to Felix EventAdmin 1.4.8
> -
>
> Key: KARAF-4857
> URL: https://issues.apache.org/jira/browse/KARAF-4857
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.8
>
>




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

[jira] [Commented] (KARAF-4869) Instance start failed.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4869:


Commit d6ef76feb67b2250f40d1157c9b9658edf5ba0e7 in karaf's branch 
refs/heads/master from [~gnt]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=d6ef76f ]

[KARAF-4869] Instance start failed

> Instance start failed.
> --
>
> Key: KARAF-4869
> URL: https://issues.apache.org/jira/browse/KARAF-4869
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-instance
>Affects Versions: 4.1.0
>Reporter: Jens Offenbach
> Fix For: 4.1.0
>
>
> Start of an instance fails without any printed error in the CLI. The instance 
> log shows the error:
> {code}
> Nov 30, 2016 9:27:00 AM org.apache.karaf.main.Main main
> SEVERE: Could not launch framework
> java.lang.RuntimeException: Could not resolve 
> mvn:org.apache.felix/org.apache.felix.framework/@@felix.framework.version@@
>   at 
> org.apache.karaf.main.util.SimpleMavenResolver.resolve(SimpleMavenResolver.java:59)
>   at org.apache.karaf.main.Main.createClassLoader(Main.java:445)
>   at org.apache.karaf.main.Main.launch(Main.java:252)
>   at org.apache.karaf.main.Main.main(Main.java:178)
> {code}
> It seems to be a variable interpolation problem. The file "config.properties" 
> that gets added to the bundle "org.apache.karaf.instance.core" contains some 
> non-interpolated values.



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

[jira] [Resolved] (KARAF-4869) Instance start failed.

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet resolved KARAF-4869.

   Resolution: Fixed
Fix Version/s: 4.1.0

> Instance start failed.
> --
>
> Key: KARAF-4869
> URL: https://issues.apache.org/jira/browse/KARAF-4869
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-instance
>Affects Versions: 4.1.0
>Reporter: Jens Offenbach
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> Start of an instance fails without any printed error in the CLI. The instance 
> log shows the error:
> {code}
> Nov 30, 2016 9:27:00 AM org.apache.karaf.main.Main main
> SEVERE: Could not launch framework
> java.lang.RuntimeException: Could not resolve 
> mvn:org.apache.felix/org.apache.felix.framework/@@felix.framework.version@@
>   at 
> org.apache.karaf.main.util.SimpleMavenResolver.resolve(SimpleMavenResolver.java:59)
>   at org.apache.karaf.main.Main.createClassLoader(Main.java:445)
>   at org.apache.karaf.main.Main.launch(Main.java:252)
>   at org.apache.karaf.main.Main.main(Main.java:178)
> {code}
> It seems to be a variable interpolation problem. The file "config.properties" 
> that gets added to the bundle "org.apache.karaf.instance.core" contains some 
> non-interpolated values.



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

[jira] [Assigned] (KARAF-4869) Instance start failed.

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet reassigned KARAF-4869:
--

Assignee: Guillaume Nodet

> Instance start failed.
> --
>
> Key: KARAF-4869
> URL: https://issues.apache.org/jira/browse/KARAF-4869
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-instance
>Affects Versions: 4.1.0
>Reporter: Jens Offenbach
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> Start of an instance fails without any printed error in the CLI. The instance 
> log shows the error:
> {code}
> Nov 30, 2016 9:27:00 AM org.apache.karaf.main.Main main
> SEVERE: Could not launch framework
> java.lang.RuntimeException: Could not resolve 
> mvn:org.apache.felix/org.apache.felix.framework/@@felix.framework.version@@
>   at 
> org.apache.karaf.main.util.SimpleMavenResolver.resolve(SimpleMavenResolver.java:59)
>   at org.apache.karaf.main.Main.createClassLoader(Main.java:445)
>   at org.apache.karaf.main.Main.launch(Main.java:252)
>   at org.apache.karaf.main.Main.main(Main.java:178)
> {code}
> It seems to be a variable interpolation problem. The file "config.properties" 
> that gets added to the bundle "org.apache.karaf.instance.core" contains some 
> non-interpolated values.



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

[jira] [Commented] (KARAF-4841) Add support for Felix httplite

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4841:


Commit 3059885f3a141a3ce4b6b147c5a8d0475b07aa4d in karaf's branch 
refs/heads/master from [~gnt]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=3059885 ]

[KARAF-4841] Make sure httplite can be used as a provider for the webconsole

> Add support for Felix httplite
> --
>
> Key: KARAF-4841
> URL: https://issues.apache.org/jira/browse/KARAF-4841
> Project: Karaf
>  Issue Type: New Feature
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> When only a very basic http service is needed, Felix HttpLite is very 
> lightweight.



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

[jira] [Resolved] (KARAF-4841) Add support for Felix httplite

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet resolved KARAF-4841.

Resolution: Fixed

> Add support for Felix httplite
> --
>
> Key: KARAF-4841
> URL: https://issues.apache.org/jira/browse/KARAF-4841
> Project: Karaf
>  Issue Type: New Feature
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> When only a very basic http service is needed, Felix HttpLite is very 
> lightweight.



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

[jira] [Commented] (KARAF-4838) The shell:source command does not forward Ctrl+C to the command being executed

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet commented on KARAF-4838:


Need to upgrade to felix gogo runtime 1.0.1

> The shell:source command does not forward Ctrl+C to the command being executed
> --
>
> Key: KARAF-4838
> URL: https://issues.apache.org/jira/browse/KARAF-4838
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded 
> by the karaf shell to the commands executed via source. This forwarding is 
> useful since the application can then decide whether it should cancel the 
> action. However this forwarding has been deactivated in karaf 4.1.0.
> Steps to reproduce the problem in Linux:
> 1. Create a file demo.script that contains the line
>"sleep 10"
> 2. In karaf shell, execute the commands via
>   "source demo.scipt"
> 3. In karaf shell, enter CTRL + C, you will see
> "gogo: InterruptedException: null" instead of the expected "sleep: 
> interrupted"
> Additionally, if you enter CTRL + D after step 3 to exit karaf, the 
> OS-terminal will be in invalid state. You cannot see what you enter in the 
> OS-terminal.



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

[jira] [Work started] (KARAF-4838) The shell:source command does not forward Ctrl+C to the command being executed

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on KARAF-4838 started by Guillaume Nodet.
--
> The shell:source command does not forward Ctrl+C to the command being executed
> --
>
> Key: KARAF-4838
> URL: https://issues.apache.org/jira/browse/KARAF-4838
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded 
> by the karaf shell to the commands executed via source. This forwarding is 
> useful since the application can then decide whether it should cancel the 
> action. However this forwarding has been deactivated in karaf 4.1.0.
> Steps to reproduce the problem in Linux:
> 1. Create a file demo.script that contains the line
>"sleep 10"
> 2. In karaf shell, execute the commands via
>   "source demo.scipt"
> 3. In karaf shell, enter CTRL + C, you will see
> "gogo: InterruptedException: null" instead of the expected "sleep: 
> interrupted"
> Additionally, if you enter CTRL + D after step 3 to exit karaf, the 
> OS-terminal will be in invalid state. You cannot see what you enter in the 
> OS-terminal.



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

[jira] [Updated] (KARAF-4871) LDAPLoginModule NPEs if no role filter is specified

[Colm O hEigeartaigh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Colm O hEigeartaigh updated KARAF-4871:
---
Attachment: KARAF-4871.patch

> LDAPLoginModule NPEs if no role filter is specified
> ---
>
> Key: KARAF-4871
> URL: https://issues.apache.org/jira/browse/KARAF-4871
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.7
>Reporter: Colm O hEigeartaigh
> Fix For: 4.1.0, 4.0.8
>
> Attachments: KARAF-4871.patch
>
>
> The LDAPLoginModule throws a NullPointerException if no role filter is 
> specified. However, it's perfectly valid to use a LDAPLoginModule just for 
> authentication, and not perform any group/role lookup.



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

[jira] [Created] (KARAF-4871) LDAPLoginModule NPEs if no role filter is specified

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created KARAF-4871:
--

 Summary: LDAPLoginModule NPEs if no role filter is specified
 Key: KARAF-4871
 URL: https://issues.apache.org/jira/browse/KARAF-4871
 Project: Karaf
  Issue Type: Bug
Affects Versions: 4.0.7
Reporter: Colm O hEigeartaigh
 Fix For: 4.1.0, 4.0.8


The LDAPLoginModule throws a NullPointerException if no role filter is 
specified. However, it's perfectly valid to use a LDAPLoginModule just for 
authentication, and not perform any group/role lookup.



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

[jira] [Commented] (KARAF-4843) Updating factory configuration leads to new configuration instance

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4843:


Commit edf41f7ba67d2107b0f2ed0ae876362b48f222c5 in karaf's branch 
refs/heads/master from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=edf41f7 ]

[KARAF-4843] Force ascii for some tests


> Updating factory configuration leads to new configuration instance
> --
>
> Key: KARAF-4843
> URL: https://issues.apache.org/jira/browse/KARAF-4843
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-config
>Affects Versions: 4.1.0
>Reporter: Jens Offenbach
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> Start with a fresh Karaf 4.1.0-SNAPSHOT installation and validate that 
> felix.fileinstall.enableConfigSave = true is set. 
> Scenario:
> - Create a factory configuration.
> - Update the configuration.
> Result:
> The configuration gets updated, but a new configuration with another 
> incorrect service.factoryPid gets created:
> Steps to reproduce:
> {code}
> karaf@root()> config:edit --factory com.example.TestConfig
> karaf@root()> config:property-set A B
> karaf@root()> config:update
> karaf@root()> config:list '(service.factoryPid=com.example.TestConfig*)'
> 
> Pid:com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> FactoryPid: com.example.TestConfig
> BundleLocation: null
> Properties:
>A = B
>service.factoryPid = com.example.TestConfig
>service.pid = com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> karaf@root()> config:edit 
> com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> karaf@root()> config:property-set A C
> karaf@root()> config:update
> karaf@root()> config:list '(service.factoryPid=com.example.TestConfig*)'
> 
> Pid:com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> FactoryPid: com.example.TestConfig
> BundleLocation: null
> Properties:
>A = C
>service.factoryPid = com.example.TestConfig
>service.pid = com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> 
> Pid:
> com.example.TestConfig.8d22975e.22055df0-4a85-4b87-94c6-7787cd84a8e5
> FactoryPid: com.example.TestConfig.8d22975e
> BundleLocation: null
> Properties:
>A = C
>felix.fileinstall.filename = 
> file:/opt/apache-karaf-4.1.0-SNAPSHOT/etc/com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af.cfg
>service.factoryPid = com.example.TestConfig.8d22975e
>service.pid = 
> com.example.TestConfig.8d22975e.22055df0-4a85-4b87-94c6-7787cd84a8e5
> karaf@root()> config:list '(service.factoryPid=com.example.TestConfigd*)'
> {code}
> I think that there is a problem with fileinstall and hyphen handling. The 
> string before the hyphen is interpreted as factoryPid resulting in 
> "com.example.TestConfig.8d22975e". Fileinstall tries to find the existing 
> configuration using the key "felix.fileinstall.filename" which is not set by 
> "ConfigRepositoryImpl".
> Solution:
> I am not sure, but I think, that in the "update"-method of 
> "ConfigRepositoryImpl", the "felix.fileinstall.filename"-property has to be 
> set explicitly and that an alias has be used that does not contain a hyphen.
> It would be nice to add an "-alias" option to the command "config:edit" that 
> allows a user to specify the alias that gets used for the factory 
> configuration. Unfortunately, the alias does not get used when the 
> configuration gets created for the first time. Only its update leads to a 
> file creation that gets considered by Fileinstall.
> What are your thoughts?



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

[jira] [Commented] (KARAF-4844) ERROR logged if the property featuresBoot contains pax-jetty in 2nd stage

[Lijun Liao (JIRA)]

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

Lijun Liao commented on KARAF-4844:
---

Have just tried 
https://repository.apache.org/content/groups/snapshots-group/org/apache/karaf/apache-karaf/4.1.0-SNAPSHOT/apache-karaf-4.1.0-20161130.104509-248.tar.gz,
 but with the same problem.

> ERROR logged if the property featuresBoot contains pax-jetty in 2nd stage  
> ---
>
> Key: KARAF-4844
> URL: https://issues.apache.org/jira/browse/KARAF-4844
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> By starting karaf with the following property in 
> etc/org.apache.karaf.features.cfg 
> {code}
> featuresBoot = \
> (instance, \
> ...
> kar), pax-jetty
> {code}
> , one will get the following ERROR messages in data/log/karaf.log:
> {code}
> 2016-11-23T21:31:43,216 | ERROR | FelixStartLevel  | Felix
> |  -  -  | Bundle org.objectweb.asm.all [52] Error locking 
> mvn:org.ow2.asm/asm-all/6.0_ALPHA (java.lang.IllegalStateException: Bundle in 
> unexpected state.)
> java.lang.IllegalStateException: Bundle in unexpected state.
> at 
> org.apache.felix.framework.Felix.acquireBundleLock(Felix.java:5272) [?:?]
> at 
> org.apache.felix.framework.Felix.setBundleStartLevel(Felix.java:1524) [?:?]
> at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:338)
>  [?:?]
> at java.lang.Thread.run(Thread.java:745) [?:?]
> 2016-11-23T21:31:43,215 | ERROR | FelixDispatchQueue | all
>   | 85 - org.objectweb.asm.all - 5.0.2 | FrameworkEvent ERROR - 
> org.objectweb.asm.all
> java.lang.IllegalStateException: Bundle in unexpected state.
> at 
> org.apache.felix.framework.Felix.acquireBundleLock(Felix.java:5272) [?:?]
> at 
> org.apache.felix.framework.Felix.setBundleStartLevel(Felix.java:1524) [?:?]
> at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:338)
>  [?:?]
> at java.lang.Thread.run(Thread.java:745) [?:?]
> {code}



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

[jira] [Updated] (KARAF-4838) The shell:source command does not forward Ctrl+C to the command being executed

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet updated KARAF-4838:
---
Summary: The shell:source command does not forward Ctrl+C to the command 
being executed  (was: InterruptedException of karaf shell will not be forwarded 
to the commands executed via source)

> The shell:source command does not forward Ctrl+C to the command being executed
> --
>
> Key: KARAF-4838
> URL: https://issues.apache.org/jira/browse/KARAF-4838
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded 
> by the karaf shell to the commands executed via source. This forwarding is 
> useful since the application can then decide whether it should cancel the 
> action. However this forwarding has been deactivated in karaf 4.1.0.
> Steps to reproduce the problem in Linux:
> 1. Create a file demo.script that contains the line
>"sleep 10"
> 2. In karaf shell, execute the commands via
>   "source demo.scipt"
> 3. In karaf shell, enter CTRL + C, you will see
> "gogo: InterruptedException: null" instead of the expected "sleep: 
> interrupted"
> Additionally, if you enter CTRL + D after step 3 to exit karaf, the 
> OS-terminal will be in invalid state. You cannot see what you enter in the 
> OS-terminal.



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

[jira] [Assigned] (KARAF-4838) InterruptedException of karaf shell will not be forwarded to the commands executed via source

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet reassigned KARAF-4838:
--

Assignee: Guillaume Nodet

> InterruptedException of karaf shell will not be forwarded to the commands 
> executed via source
> -
>
> Key: KARAF-4838
> URL: https://issues.apache.org/jira/browse/KARAF-4838
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded 
> by the karaf shell to the commands executed via source. This forwarding is 
> useful since the application can then decide whether it should cancel the 
> action. However this forwarding has been deactivated in karaf 4.1.0.
> Steps to reproduce the problem in Linux:
> 1. Create a file demo.script that contains the line
>"sleep 10"
> 2. In karaf shell, execute the commands via
>   "source demo.scipt"
> 3. In karaf shell, enter CTRL + C, you will see
> "gogo: InterruptedException: null" instead of the expected "sleep: 
> interrupted"
> Additionally, if you enter CTRL + D after step 3 to exit karaf, the 
> OS-terminal will be in invalid state. You cannot see what you enter in the 
> OS-terminal.



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

[jira] [Reopened] (KARAF-4841) Add support for Felix httplite

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet reopened KARAF-4841:


We need to make sure the webconsole feature can be used with httplite.

> Add support for Felix httplite
> --
>
> Key: KARAF-4841
> URL: https://issues.apache.org/jira/browse/KARAF-4841
> Project: Karaf
>  Issue Type: New Feature
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> When only a very basic http service is needed, Felix HttpLite is very 
> lightweight.



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

[jira] [Resolved] (KARAF-4870) Store the wiring in the output file when using "feature:install --store"

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet resolved KARAF-4870.

Resolution: Fixed

> Store the wiring in the output file when using "feature:install --store"
> 
>
> Key: KARAF-4870
> URL: https://issues.apache.org/jira/browse/KARAF-4870
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-feature
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>




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

[jira] [Commented] (KARAF-4870) Store the wiring in the output file when using "feature:install --store"

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4870:


Commit c7806957e042fe90087a52b4d19ff7c31e9c5950 in karaf's branch 
refs/heads/master from [~gnt]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=c780695 ]

[KARAF-4870] Store the wiring in the output file when using "feature:install 
--store"

> Store the wiring in the output file when using "feature:install --store"
> 
>
> Key: KARAF-4870
> URL: https://issues.apache.org/jira/browse/KARAF-4870
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-feature
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>




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

[jira] [Created] (KARAF-4870) Store the wiring in the output file when using "feature:install --store"

[Guillaume Nodet (JIRA)]

Guillaume Nodet created KARAF-4870:
--

 Summary: Store the wiring in the output file when using 
"feature:install --store"
 Key: KARAF-4870
 URL: https://issues.apache.org/jira/browse/KARAF-4870
 Project: Karaf
  Issue Type: Improvement
  Components: karaf-feature
Reporter: Guillaume Nodet
Assignee: Guillaume Nodet
 Fix For: 4.1.0






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

[jira] [Commented] (KARAF-4843) Updating factory configuration leads to new configuration instance

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on KARAF-4843:
---

Github user cfiehe closed the pull request at:

https://github.com/apache/karaf/pull/268


> Updating factory configuration leads to new configuration instance
> --
>
> Key: KARAF-4843
> URL: https://issues.apache.org/jira/browse/KARAF-4843
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-config
>Affects Versions: 4.1.0
>Reporter: Jens Offenbach
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> Start with a fresh Karaf 4.1.0-SNAPSHOT installation and validate that 
> felix.fileinstall.enableConfigSave = true is set. 
> Scenario:
> - Create a factory configuration.
> - Update the configuration.
> Result:
> The configuration gets updated, but a new configuration with another 
> incorrect service.factoryPid gets created:
> Steps to reproduce:
> {code}
> karaf@root()> config:edit --factory com.example.TestConfig
> karaf@root()> config:property-set A B
> karaf@root()> config:update
> karaf@root()> config:list '(service.factoryPid=com.example.TestConfig*)'
> 
> Pid:com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> FactoryPid: com.example.TestConfig
> BundleLocation: null
> Properties:
>A = B
>service.factoryPid = com.example.TestConfig
>service.pid = com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> karaf@root()> config:edit 
> com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> karaf@root()> config:property-set A C
> karaf@root()> config:update
> karaf@root()> config:list '(service.factoryPid=com.example.TestConfig*)'
> 
> Pid:com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> FactoryPid: com.example.TestConfig
> BundleLocation: null
> Properties:
>A = C
>service.factoryPid = com.example.TestConfig
>service.pid = com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> 
> Pid:
> com.example.TestConfig.8d22975e.22055df0-4a85-4b87-94c6-7787cd84a8e5
> FactoryPid: com.example.TestConfig.8d22975e
> BundleLocation: null
> Properties:
>A = C
>felix.fileinstall.filename = 
> file:/opt/apache-karaf-4.1.0-SNAPSHOT/etc/com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af.cfg
>service.factoryPid = com.example.TestConfig.8d22975e
>service.pid = 
> com.example.TestConfig.8d22975e.22055df0-4a85-4b87-94c6-7787cd84a8e5
> karaf@root()> config:list '(service.factoryPid=com.example.TestConfigd*)'
> {code}
> I think that there is a problem with fileinstall and hyphen handling. The 
> string before the hyphen is interpreted as factoryPid resulting in 
> "com.example.TestConfig.8d22975e". Fileinstall tries to find the existing 
> configuration using the key "felix.fileinstall.filename" which is not set by 
> "ConfigRepositoryImpl".
> Solution:
> I am not sure, but I think, that in the "update"-method of 
> "ConfigRepositoryImpl", the "felix.fileinstall.filename"-property has to be 
> set explicitly and that an alias has be used that does not contain a hyphen.
> It would be nice to add an "-alias" option to the command "config:edit" that 
> allows a user to specify the alias that gets used for the factory 
> configuration. Unfortunately, the alias does not get used when the 
> configuration gets created for the first time. Only its update leads to a 
> file creation that gets considered by Fileinstall.
> What are your thoughts?



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

[jira] [Commented] (KARAF-4868) Encoding problems in CLI with shell table output

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on KARAF-4868:
---

Github user cfiehe closed the pull request at:

https://github.com/apache/karaf/pull/272


> Encoding problems in CLI with shell table output
> 
>
> Key: KARAF-4868
> URL: https://issues.apache.org/jira/browse/KARAF-4868
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Jens Offenbach
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> When terminal encoding does not support UTF-8, the output gives something 
> like this:
> {code}
> instance:list 08:31:41
> > SSH Port ? SSH Host ? RMI Registry ? RMI Registry Host ? RMI Server ? RMI 
> > Server Host ? State ? PID ? Name
> > ??
> > 8101 ? 0.0.0.0 ? 1099 ? 127.0.0.1 ? 4 ? 127.0.0.1 ? Started ? 26740 ? 
> > root
> {code}
> In this case, I would be more preferable to suppress the special characters 
> (used as separators) in the shell table output.



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

[jira] [Commented] (KARAF-4846) Property karaf.etc must be a canoncial path

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on KARAF-4846:
---

Github user cfiehe closed the pull request at:

https://github.com/apache/karaf/pull/267


> Property karaf.etc must be a canoncial path
> ---
>
> Key: KARAF-4846
> URL: https://issues.apache.org/jira/browse/KARAF-4846
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Affects Versions: 4.1.0
>Reporter: Jens Offenbach
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> Under Windows 7 the environment variable {{karaf.etc}} points to 
> {{C:\Users\myuser\Desktop\apache-karaf-4.1.0-SNAPSHOT\bin\..\etc}} causing 
> inconsistencies when the canoncial path representation gets used.



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

[jira] [Commented] (KARAF-4813) RMI should not listen to all hosts

[JIRA]

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

Jean-Baptiste Onofré commented on KARAF-4813:
-

That's why a bit reluctant to such change ;)

> RMI should not listen to all hosts
> --
>
> Key: KARAF-4813
> URL: https://issues.apache.org/jira/browse/KARAF-4813
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.7
>Reporter: Lars Kiesow
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> The default RMI configuration will make Karaf listen to all hosts. Instead. 
> it is usually good practice to, by default, listen to localhost only to avoid 
> possible security risks.



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

[jira] [Resolved] (KARAF-4813) RMI should not listen to all hosts

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet resolved KARAF-4813.

Resolution: Fixed

Tests fixed

> RMI should not listen to all hosts
> --
>
> Key: KARAF-4813
> URL: https://issues.apache.org/jira/browse/KARAF-4813
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.7
>Reporter: Lars Kiesow
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> The default RMI configuration will make Karaf listen to all hosts. Instead. 
> it is usually good practice to, by default, listen to localhost only to avoid 
> possible security risks.



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

[jira] [Updated] (KARAF-4834) Infinite loop if Exception occurs during the execution of karaf.shell.init.script

[Lijun Liao (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lijun Liao updated KARAF-4834:
--
Description: 
The while block between line 329 and line 352 in 
https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
 will never break if Exception other than EndOfFileException is thrown, e.g. 
StreamClosed exception.

After executing a karaf command (the commands are in a scritp which will be 
executed via the command source) I happened to get the Interrupted error, then 
the branding screen was shown, followed by infinite Stream Closed IOException. 
Sorry I got this phenomenon only  from time to time and cannot provide 
stable steps to reproduce it.

{code}
karaf@root() 
Error executing command: java.lang.InterruptedException
gogo: InterruptedException: null
__ __  
   / //_/ __ _/ __/
  / ,<  / __ `/ ___/ __ `/ /_
 / /| |/ /_/ / /  / /_/ / __/
/_/ |_|\__,_/_/   \__,_/_/

  Apache Karaf (4.1.0-SNAPSHOT)

Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.

karaf@root()>  Error executing command: java.io.IOException: Stream Closed
... hunderts lines with same content ignored here ...
karaf@root()>  Error executing command: java.io.IOException: Stream Closed
{code}

I have attached the log.

  was:
The while block between line 329 and line 352 in 
https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
 will never break if Exception other than EndOfFileException is thrown, e.g. 
StreamClosed exception.

After executing a karaf command (the commands are in a scritp which will be 
executed via the command `source`) I happened to get the Interrupted error, 
then the branding screen was shown, followed by infinite Stream Closed 
IOException. Sorry I got this phenomenon onlyfrom time to time and cannot 
provide stable steps to reproduce it.

{code}
karaf@root() 
Error executing command: java.lang.InterruptedException
gogo: InterruptedException: null
__ __  
   / //_/ __ _/ __/
  / ,<  / __ `/ ___/ __ `/ /_
 / /| |/ /_/ / /  / /_/ / __/
/_/ |_|\__,_/_/   \__,_/_/

  Apache Karaf (4.1.0-SNAPSHOT)

Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.

karaf@root()>  Error executing command: java.io.IOException: Stream Closed
... hunderts lines with same content ignored here ...
karaf@root()>  Error executing command: java.io.IOException: Stream Closed
{code}

I have attached the log.


> Infinite loop if Exception occurs during the execution of 
> karaf.shell.init.script
> -
>
> Key: KARAF-4834
> URL: https://issues.apache.org/jira/browse/KARAF-4834
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
> Attachments: karaf.log
>
>
> The while block between line 329 and line 352 in 
> https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
>  will never break if Exception other than EndOfFileException is thrown, e.g. 
> StreamClosed exception.
> After executing a karaf command (the commands are in a scritp which will be 
> executed via the command source) I happened to get the Interrupted error, 
> then the branding screen was shown, followed by infinite Stream Closed 
> IOException. Sorry I got this phenomenon onlyfrom time to time and cannot 
> provide stable steps to reproduce it.
> {code}
> karaf@root() 
> Error executing command: java.lang.InterruptedException
> gogo: InterruptedException: null
> __ __  
>/ //_/ __ _/ __/
>   / ,<  / __ `/ ___/ __ `/ /_
>  / /| |/ /_/ / /  / /_/ / __/
> /_/ |_|\__,_/_/   \__,_/_/
>   Apache Karaf (4.1.0-SNAPSHOT)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()>  Error executing command: java.io.IOException: Stream Closed
> ... hunderts lines with same content ignored here ...
> karaf@root()>  Error executing command: java.io.IOException: Stream Closed
> {code}
> I have attached the log.



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

[jira] [Updated] (KARAF-4834) Infinite loop if Exception occurs during the execution of karaf.shell.init.script

[Lijun Liao (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lijun Liao updated KARAF-4834:
--
Description: 
The while block between line 329 and line 352 in 
https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
 will never break if Exception other than EndOfFileException is thrown, e.g. 
StreamClosed exception.

After executing a karaf command (the commands are in a scritp which will be 
executed via the command `source`) I happened to get the Interrupted error, 
then the branding screen was shown, followed by infinite Stream Closed 
IOException. Sorry I got this phenomenon onlyfrom time to time and cannot 
provide stable steps to reproduce it.

{code}
karaf@root() 
Error executing command: java.lang.InterruptedException
gogo: InterruptedException: null
__ __  
   / //_/ __ _/ __/
  / ,<  / __ `/ ___/ __ `/ /_
 / /| |/ /_/ / /  / /_/ / __/
/_/ |_|\__,_/_/   \__,_/_/

  Apache Karaf (4.1.0-SNAPSHOT)

Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.

karaf@root()>  Error executing command: java.io.IOException: Stream Closed
... hunderts lines with same content ignored here ...
karaf@root()>  Error executing command: java.io.IOException: Stream Closed
{code}

I have attached the log.

  was:
The while block between line 329 and line 352 in 
https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
 will never break if Exception other than EndOfFileException is thrown, e.g. 
StreamClosed exception.

After executing a karaf command I happened to get the Interrupted error, then 
the branding screen was shown, followed by infinite Stream Closed IOException. 
Sorry I got this phenomenon only   from time to time and cannot provide stable 
steps to reproduce it.

{code}
karaf@root() 
Error executing command: java.lang.InterruptedException
gogo: InterruptedException: null
__ __  
   / //_/ __ _/ __/
  / ,<  / __ `/ ___/ __ `/ /_
 / /| |/ /_/ / /  / /_/ / __/
/_/ |_|\__,_/_/   \__,_/_/

  Apache Karaf (4.1.0-SNAPSHOT)

Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.

karaf@root()>  Error executing command: java.io.IOException: Stream Closed
... hunderts lines with same content ignored here ...
karaf@root()>  Error executing command: java.io.IOException: Stream Closed
{code}

I have attached the log.


> Infinite loop if Exception occurs during the execution of 
> karaf.shell.init.script
> -
>
> Key: KARAF-4834
> URL: https://issues.apache.org/jira/browse/KARAF-4834
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
> Attachments: karaf.log
>
>
> The while block between line 329 and line 352 in 
> https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
>  will never break if Exception other than EndOfFileException is thrown, e.g. 
> StreamClosed exception.
> After executing a karaf command (the commands are in a scritp which will be 
> executed via the command `source`) I happened to get the Interrupted error, 
> then the branding screen was shown, followed by infinite Stream Closed 
> IOException. Sorry I got this phenomenon only  from time to time and cannot 
> provide stable steps to reproduce it.
> {code}
> karaf@root() 
> Error executing command: java.lang.InterruptedException
> gogo: InterruptedException: null
> __ __  
>/ //_/ __ _/ __/
>   / ,<  / __ `/ ___/ __ `/ /_
>  / /| |/ /_/ / /  / /_/ / __/
> /_/ |_|\__,_/_/   \__,_/_/
>   Apache Karaf (4.1.0-SNAPSHOT)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()>  Error executing command: java.io.IOException: Stream Closed
> ... hunderts lines with same content ignored here ...
> karaf@root()>  Error executing command: java.io.IOException: Stream Closed
> {code}
> I have attached the log.



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

[jira] [Updated] (KARAF-4849) Corrupt EventAdmin file in etc

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet updated KARAF-4849:
---
Fix Version/s: 4.0.8

> Corrupt EventAdmin file in etc
> --
>
> Key: KARAF-4849
> URL: https://issues.apache.org/jira/browse/KARAF-4849
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.7
>Reporter: Kai Kreuzer
>Priority: Minor
> Fix For: 4.0.8
>
>
> In the Karaf 4.0.7 distro, there is a file 
> org.apache.felix.eventadmin.impl.EventAdmin 
> with the content: 
> " 
> org.apache.felix.eventadmin.AddTimestamp=true 
> org.apache.felix.eventadmin.AddSubject=true 
> " 
> I'd assume it should have a .cfg suffix and no tabs in front of its entries.
> See 
> http://karaf.922171.n3.nabble.com/Corrupt-EventAdmin-file-in-etc-tt4048586.html



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

[jira] [Commented] (KARAF-4843) Updating factory configuration leads to new configuration instance

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4843:


Commit 416d22a97755a10b659e1e37ba08180b3176a93a in karaf's branch 
refs/heads/master from Christoph Fiehe
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=416d22a ]

[KARAF-4843] Fix SEP_VERTICAL in ShellTable


> Updating factory configuration leads to new configuration instance
> --
>
> Key: KARAF-4843
> URL: https://issues.apache.org/jira/browse/KARAF-4843
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-config
>Affects Versions: 4.1.0
>Reporter: Jens Offenbach
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> Start with a fresh Karaf 4.1.0-SNAPSHOT installation and validate that 
> felix.fileinstall.enableConfigSave = true is set. 
> Scenario:
> - Create a factory configuration.
> - Update the configuration.
> Result:
> The configuration gets updated, but a new configuration with another 
> incorrect service.factoryPid gets created:
> Steps to reproduce:
> {code}
> karaf@root()> config:edit --factory com.example.TestConfig
> karaf@root()> config:property-set A B
> karaf@root()> config:update
> karaf@root()> config:list '(service.factoryPid=com.example.TestConfig*)'
> 
> Pid:com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> FactoryPid: com.example.TestConfig
> BundleLocation: null
> Properties:
>A = B
>service.factoryPid = com.example.TestConfig
>service.pid = com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> karaf@root()> config:edit 
> com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> karaf@root()> config:property-set A C
> karaf@root()> config:update
> karaf@root()> config:list '(service.factoryPid=com.example.TestConfig*)'
> 
> Pid:com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> FactoryPid: com.example.TestConfig
> BundleLocation: null
> Properties:
>A = C
>service.factoryPid = com.example.TestConfig
>service.pid = com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> 
> Pid:
> com.example.TestConfig.8d22975e.22055df0-4a85-4b87-94c6-7787cd84a8e5
> FactoryPid: com.example.TestConfig.8d22975e
> BundleLocation: null
> Properties:
>A = C
>felix.fileinstall.filename = 
> file:/opt/apache-karaf-4.1.0-SNAPSHOT/etc/com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af.cfg
>service.factoryPid = com.example.TestConfig.8d22975e
>service.pid = 
> com.example.TestConfig.8d22975e.22055df0-4a85-4b87-94c6-7787cd84a8e5
> karaf@root()> config:list '(service.factoryPid=com.example.TestConfigd*)'
> {code}
> I think that there is a problem with fileinstall and hyphen handling. The 
> string before the hyphen is interpreted as factoryPid resulting in 
> "com.example.TestConfig.8d22975e". Fileinstall tries to find the existing 
> configuration using the key "felix.fileinstall.filename" which is not set by 
> "ConfigRepositoryImpl".
> Solution:
> I am not sure, but I think, that in the "update"-method of 
> "ConfigRepositoryImpl", the "felix.fileinstall.filename"-property has to be 
> set explicitly and that an alias has be used that does not contain a hyphen.
> It would be nice to add an "-alias" option to the command "config:edit" that 
> allows a user to specify the alias that gets used for the factory 
> configuration. Unfortunately, the alias does not get used when the 
> configuration gets created for the first time. Only its update leads to a 
> file creation that gets considered by Fileinstall.
> What are your thoughts?



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

[jira] [Comment Edited] (KARAF-4838) InterruptedException of karaf shell will not be forwarded to the commands executed via source

[Lijun Liao (JIRA)]

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

Lijun Liao edited comment on KARAF-4838 at 11/30/16 9:50 AM:
-

I have updated the issue description by adding the steps to reproduce the error.


was (Author: lliao):
I have updated the issue description to add the steps to reproduce the error.

> InterruptedException of karaf shell will not be forwarded to the commands 
> executed via source
> -
>
> Key: KARAF-4838
> URL: https://issues.apache.org/jira/browse/KARAF-4838
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
>
> In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded 
> by the karaf shell to the commands executed via source. This forwarding is 
> useful since the application can then decide whether it should cancel the 
> action. However this forwarding has been deactivated in karaf 4.1.0.
> Steps to reproduce the problem in Linux:
> 1. Create a file demo.script that contains the line
>"sleep 10"
> 2. In karaf shell, execute the commands via
>   "source demo.scipt"
> 3. In karaf shell, enter CTRL + C, you will see
> "gogo: InterruptedException: null" instead of the expected "sleep: 
> interrupted"
> Additionally, if you enter CTRL + D after step 3 to exit karaf, the 
> OS-terminal will be in invalid state. You cannot see what you enter in the 
> OS-terminal.



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

[jira] [Commented] (KARAF-4838) InterruptedException of karaf shell will not be forwarded to the commands executed via source

[Lijun Liao (JIRA)]

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

Lijun Liao commented on KARAF-4838:
---

I have updated the issue description to add the steps to reproduce the error.

> InterruptedException of karaf shell will not be forwarded to the commands 
> executed via source
> -
>
> Key: KARAF-4838
> URL: https://issues.apache.org/jira/browse/KARAF-4838
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
>
> In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded 
> by the karaf shell to the commands executed via source. This forwarding is 
> useful since the application can then decide whether it should cancel the 
> action. However this forwarding has been deactivated in karaf 4.1.0.
> Steps to reproduce the problem in Linux:
> 1. Create a file demo.script that contains the line
>"sleep 10"
> 2. In karaf shell, execute the commands via
>   "source demo.scipt"
> 3. In karaf shell, enter CTRL + C, you will see
> "gogo: InterruptedException: null" instead of the expected "sleep: 
> interrupted"
> Additionally, if you enter CTRL + D after step 3 to exit karaf, the 
> OS-terminal will be in invalid state. You cannot see what you enter in the 
> OS-terminal.



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

[jira] [Updated] (KARAF-4838) InterruptedException of karaf shell will not be forwarded to the commands executed via source

[Lijun Liao (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lijun Liao updated KARAF-4838:
--
Description: 
In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded 
by the karaf shell to the commands executed via source. This forwarding is 
useful since the application can then decide whether it should cancel the 
action. However this forwarding has been deactivated in karaf 4.1.0.

Steps to reproduce the problem in Linux:

1. Create a file demo.script that contains the line
   "sleep 10"
2. In karaf shell, execute the commands via
  "source demo.scipt"
3. In karaf shell, enter CTRL + C, you will see
"gogo: InterruptedException: null" instead of the expected "sleep: interrupted"

Additionally, if you enter CTRL + D after step 3 to exit karaf, the OS-terminal 
will be in invalid state. You cannot see what you enter in the OS-terminal.


  was:
In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded 
by the karaf shell to the commands executed via source. This forwarding is 
useful since the application can then decide whether it should cancel the 
action. However this forwarding has been deactivated in karaf 4.1.0.

Steps to reproduce the problem:

1. Create a file demo.script that contains the line
   "sleep 10"
2. In karaf shell, execute the commands via
  "source demo.scipt"
3. In karaf shell, enter CTRL + C

Even w





> InterruptedException of karaf shell will not be forwarded to the commands 
> executed via source
> -
>
> Key: KARAF-4838
> URL: https://issues.apache.org/jira/browse/KARAF-4838
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
>
> In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded 
> by the karaf shell to the commands executed via source. This forwarding is 
> useful since the application can then decide whether it should cancel the 
> action. However this forwarding has been deactivated in karaf 4.1.0.
> Steps to reproduce the problem in Linux:
> 1. Create a file demo.script that contains the line
>"sleep 10"
> 2. In karaf shell, execute the commands via
>   "source demo.scipt"
> 3. In karaf shell, enter CTRL + C, you will see
> "gogo: InterruptedException: null" instead of the expected "sleep: 
> interrupted"
> Additionally, if you enter CTRL + D after step 3 to exit karaf, the 
> OS-terminal will be in invalid state. You cannot see what you enter in the 
> OS-terminal.



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

[jira] [Updated] (KARAF-4869) Instance start failed.

[Jens Offenbach (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jens Offenbach updated KARAF-4869:
--
Environment: (was: Start of an instance fails without any printed error 
in the CLI. The instance log shows the error:
{code}
Nov 30, 2016 9:27:00 AM org.apache.karaf.main.Main main
SEVERE: Could not launch framework
java.lang.RuntimeException: Could not resolve 
mvn:org.apache.felix/org.apache.felix.framework/@@felix.framework.version@@
at 
org.apache.karaf.main.util.SimpleMavenResolver.resolve(SimpleMavenResolver.java:59)
at org.apache.karaf.main.Main.createClassLoader(Main.java:445)
at org.apache.karaf.main.Main.launch(Main.java:252)
at org.apache.karaf.main.Main.main(Main.java:178)
{code}

It seems to be a variable interpolation problem. The file "config.properties" 
that gets added to the bundle "org.apache.karaf.instance.core" contains some 
non-interpolated values. )

> Instance start failed.
> --
>
> Key: KARAF-4869
> URL: https://issues.apache.org/jira/browse/KARAF-4869
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-instance
>Affects Versions: 4.1.0
>Reporter: Jens Offenbach
>




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

[jira] [Updated] (KARAF-4869) Instance start failed.

[Jens Offenbach (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jens Offenbach updated KARAF-4869:
--
Description: 
Start of an instance fails without any printed error in the CLI. The instance 
log shows the error:
{code}
Nov 30, 2016 9:27:00 AM org.apache.karaf.main.Main main
SEVERE: Could not launch framework
java.lang.RuntimeException: Could not resolve 
mvn:org.apache.felix/org.apache.felix.framework/@@felix.framework.version@@
at 
org.apache.karaf.main.util.SimpleMavenResolver.resolve(SimpleMavenResolver.java:59)
at org.apache.karaf.main.Main.createClassLoader(Main.java:445)
at org.apache.karaf.main.Main.launch(Main.java:252)
at org.apache.karaf.main.Main.main(Main.java:178)
{code}

It seems to be a variable interpolation problem. The file "config.properties" 
that gets added to the bundle "org.apache.karaf.instance.core" contains some 
non-interpolated values.

> Instance start failed.
> --
>
> Key: KARAF-4869
> URL: https://issues.apache.org/jira/browse/KARAF-4869
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-instance
>Affects Versions: 4.1.0
>Reporter: Jens Offenbach
>
> Start of an instance fails without any printed error in the CLI. The instance 
> log shows the error:
> {code}
> Nov 30, 2016 9:27:00 AM org.apache.karaf.main.Main main
> SEVERE: Could not launch framework
> java.lang.RuntimeException: Could not resolve 
> mvn:org.apache.felix/org.apache.felix.framework/@@felix.framework.version@@
>   at 
> org.apache.karaf.main.util.SimpleMavenResolver.resolve(SimpleMavenResolver.java:59)
>   at org.apache.karaf.main.Main.createClassLoader(Main.java:445)
>   at org.apache.karaf.main.Main.launch(Main.java:252)
>   at org.apache.karaf.main.Main.main(Main.java:178)
> {code}
> It seems to be a variable interpolation problem. The file "config.properties" 
> that gets added to the bundle "org.apache.karaf.instance.core" contains some 
> non-interpolated values.



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

[jira] [Created] (KARAF-4869) Instance start failed.

[Jens Offenbach (JIRA)]

Jens Offenbach created KARAF-4869:
-

 Summary: Instance start failed.
 Key: KARAF-4869
 URL: https://issues.apache.org/jira/browse/KARAF-4869
 Project: Karaf
  Issue Type: Bug
  Components: karaf-instance
Affects Versions: 4.1.0
 Environment: Start of an instance fails without any printed error in 
the CLI. The instance log shows the error:
{code}
Nov 30, 2016 9:27:00 AM org.apache.karaf.main.Main main
SEVERE: Could not launch framework
java.lang.RuntimeException: Could not resolve 
mvn:org.apache.felix/org.apache.felix.framework/@@felix.framework.version@@
at 
org.apache.karaf.main.util.SimpleMavenResolver.resolve(SimpleMavenResolver.java:59)
at org.apache.karaf.main.Main.createClassLoader(Main.java:445)
at org.apache.karaf.main.Main.launch(Main.java:252)
at org.apache.karaf.main.Main.main(Main.java:178)
{code}

It seems to be a variable interpolation problem. The file "config.properties" 
that gets added to the bundle "org.apache.karaf.instance.core" contains some 
non-interpolated values. 
Reporter: Jens Offenbach






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

[jira] [Reopened] (KARAF-4813) RMI should not listen to all hosts

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet reopened KARAF-4813:


Reopening because the commit cause 4 integration tests failures in 
JMXSecurityTest, so I'll revert the commit.

> RMI should not listen to all hosts
> --
>
> Key: KARAF-4813
> URL: https://issues.apache.org/jira/browse/KARAF-4813
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.7
>Reporter: Lars Kiesow
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> The default RMI configuration will make Karaf listen to all hosts. Instead. 
> it is usually good practice to, by default, listen to localhost only to avoid 
> possible security risks.



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

[jira] [Updated] (KARAF-4838) InterruptedException of karaf shell will not be forwarded to the commands executed via source

[Lijun Liao (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lijun Liao updated KARAF-4838:
--
Description: 
In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded 
by the karaf shell to the commands executed via source. This forwarding is 
useful since the application can then decide whether it should cancel the 
action. However this forwarding has been deactivated in karaf 4.1.0.

Steps to reproduce the problem:

1. Create a file demo.script that contains the line
   "sleep 10"
2. In karaf shell, execute the commands via
  "source demo.scipt"
3. In karaf shell, enter CTRL + C

Even w




  was:
In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded 
by the karaf shell to the commands . This forwarding is useful since the 
application can then decide whether it should cancel the action. However this 
forwarding has been deactivated in karaf 4.1.0.






> InterruptedException of karaf shell will not be forwarded to the commands 
> executed via source
> -
>
> Key: KARAF-4838
> URL: https://issues.apache.org/jira/browse/KARAF-4838
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
>
> In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded 
> by the karaf shell to the commands executed via source. This forwarding is 
> useful since the application can then decide whether it should cancel the 
> action. However this forwarding has been deactivated in karaf 4.1.0.
> Steps to reproduce the problem:
> 1. Create a file demo.script that contains the line
>"sleep 10"
> 2. In karaf shell, execute the commands via
>   "source demo.scipt"
> 3. In karaf shell, enter CTRL + C
> Even w



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

[jira] [Updated] (KARAF-4838) InterruptedException of karaf shell will not be forwarded to the commands executed via source

[Lijun Liao (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lijun Liao updated KARAF-4838:
--
Summary: InterruptedException of karaf shell will not be forwarded to the 
commands executed via source  (was: InterruptedException of karaf shell will 
not be forwarded to the command executed via source)

> InterruptedException of karaf shell will not be forwarded to the commands 
> executed via source
> -
>
> Key: KARAF-4838
> URL: https://issues.apache.org/jira/browse/KARAF-4838
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
>
> In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded 
> by the karaf shell to the commands . This forwarding is useful since the 
> application can then decide whether it should cancel the action. However this 
> forwarding has been deactivated in karaf 4.1.0.



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

[jira] [Updated] (KARAF-4838) InterruptedException of karaf shell will not be forwarded to the command executed via source

[Lijun Liao (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lijun Liao updated KARAF-4838:
--
Summary: InterruptedException of karaf shell will not be forwarded to the 
command executed via source  (was: InterruptedException of karaf shell will not 
be forwarded to the command)

> InterruptedException of karaf shell will not be forwarded to the command 
> executed via source
> 
>
> Key: KARAF-4838
> URL: https://issues.apache.org/jira/browse/KARAF-4838
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
>
> In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded 
> by the karaf shell to the command. This forwarding is useful since the 
> application can then decide whether it should cancel the action. However this 
> forwarding has been deactivated in karaf 4.1.0.



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

[jira] [Updated] (KARAF-4838) InterruptedException of karaf shell will not be forwarded to the command executed via source

[Lijun Liao (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lijun Liao updated KARAF-4838:
--
Description: 
In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded 
by the karaf shell to the commands . This forwarding is useful since the 
application can then decide whether it should cancel the action. However this 
forwarding has been deactivated in karaf 4.1.0.





  was:
In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded 
by the karaf shell to the command. This forwarding is useful since the 
application can then decide whether it should cancel the action. However this 
forwarding has been deactivated in karaf 4.1.0.




> InterruptedException of karaf shell will not be forwarded to the command 
> executed via source
> 
>
> Key: KARAF-4838
> URL: https://issues.apache.org/jira/browse/KARAF-4838
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
>
> In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded 
> by the karaf shell to the commands . This forwarding is useful since the 
> application can then decide whether it should cancel the action. However this 
> forwarding has been deactivated in karaf 4.1.0.



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

[jira] [Commented] (KARAF-4843) Updating factory configuration leads to new configuration instance

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on KARAF-4843:
---

GitHub user cfiehe opened a pull request:

https://github.com/apache/karaf/pull/272

[KARAF-4843] Fix SEP_VERTICAL in ShellTable



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cfiehe/karaf fix_sep_vertical

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/karaf/pull/272.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #272


commit 749ae875683f3b3eff60e7d203112b85ab43f021
Author: Christoph Fiehe 
Date:   2016-11-30T09:01:35Z

[KARAF-4843] Fix SEP_VERTICAL in ShellTable




> Updating factory configuration leads to new configuration instance
> --
>
> Key: KARAF-4843
> URL: https://issues.apache.org/jira/browse/KARAF-4843
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-config
>Affects Versions: 4.1.0
>Reporter: Jens Offenbach
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> Start with a fresh Karaf 4.1.0-SNAPSHOT installation and validate that 
> felix.fileinstall.enableConfigSave = true is set. 
> Scenario:
> - Create a factory configuration.
> - Update the configuration.
> Result:
> The configuration gets updated, but a new configuration with another 
> incorrect service.factoryPid gets created:
> Steps to reproduce:
> {code}
> karaf@root()> config:edit --factory com.example.TestConfig
> karaf@root()> config:property-set A B
> karaf@root()> config:update
> karaf@root()> config:list '(service.factoryPid=com.example.TestConfig*)'
> 
> Pid:com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> FactoryPid: com.example.TestConfig
> BundleLocation: null
> Properties:
>A = B
>service.factoryPid = com.example.TestConfig
>service.pid = com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> karaf@root()> config:edit 
> com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> karaf@root()> config:property-set A C
> karaf@root()> config:update
> karaf@root()> config:list '(service.factoryPid=com.example.TestConfig*)'
> 
> Pid:com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> FactoryPid: com.example.TestConfig
> BundleLocation: null
> Properties:
>A = C
>service.factoryPid = com.example.TestConfig
>service.pid = com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> 
> Pid:
> com.example.TestConfig.8d22975e.22055df0-4a85-4b87-94c6-7787cd84a8e5
> FactoryPid: com.example.TestConfig.8d22975e
> BundleLocation: null
> Properties:
>A = C
>felix.fileinstall.filename = 
> file:/opt/apache-karaf-4.1.0-SNAPSHOT/etc/com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af.cfg
>service.factoryPid = com.example.TestConfig.8d22975e
>service.pid = 
> com.example.TestConfig.8d22975e.22055df0-4a85-4b87-94c6-7787cd84a8e5
> karaf@root()> config:list '(service.factoryPid=com.example.TestConfigd*)'
> {code}
> I think that there is a problem with fileinstall and hyphen handling. The 
> string before the hyphen is interpreted as factoryPid resulting in 
> "com.example.TestConfig.8d22975e". Fileinstall tries to find the existing 
> configuration using the key "felix.fileinstall.filename" which is not set by 
> "ConfigRepositoryImpl".
> Solution:
> I am not sure, but I think, that in the "update"-method of 
> "ConfigRepositoryImpl", the "felix.fileinstall.filename"-property has to be 
> set explicitly and that an alias has be used that does not contain a hyphen.
> It would be nice to add an "-alias" option to the command "config:edit" that 
> allows a user to specify the alias that gets used for the factory 
> configuration. Unfortunately, the alias does not get used when the 
> configuration gets created for the first time. Only its update leads to a 
> file creation that gets considered by Fileinstall.
> What are your thoughts?



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

[jira] [Resolved] (KARAF-4842) Karaf Maven Plugin builds features with invalid configuration

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet resolved KARAF-4842.

   Resolution: Fixed
 Assignee: Guillaume Nodet
Fix Version/s: 4.0.8
   4.1.0

> Karaf Maven Plugin builds features with invalid configuration
> -
>
> Key: KARAF-4842
> URL: https://issues.apache.org/jira/browse/KARAF-4842
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 4.0.7
>Reporter: Achim Finke
>Assignee: Guillaume Nodet
> Fix For: 4.1.0, 4.0.8
>
>
> I generated a Karaf Feature using the karaf-feature-archetype. This will add 
> the following configuration to the POM file.
> {code:xml}
> 
> 
> 
> 
> org.apache.karaf.tooling
> karaf-maven-plugin
> 4.0.7
> true
> 
> 
> 
> 
> 
> org.apache.karaf.tooling
> karaf-maven-plugin
> 
> 50
> true
> (obr)
> true
> false
> true
> 
> true
> 
> 
> 
> 
> {code}
> The feature can be built but on installation the feature validation fails.
> {code}
> Caused by: org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 
> 'resolver' is not allowed to appear in element 'feature'.
> {code}
> Basically here are two issues:
> - Karaf Maven Plugin builds a feature with invalid configuration
> - The karaf-feature-archetype contains invalid configuration
> So to solve this Karaf Maven plugin should be enhanced and the resolver tag 
> should be deleted within the archetype.



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

[jira] [Commented] (KARAF-4842) Karaf Maven Plugin builds features with invalid configuration

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4842:


Commit 4627aa94f647b53ac0fc0953c3df73a468a596f5 in karaf's branch 
refs/heads/master from [~gnt]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=4627aa9 ]

[KARAF-4842] Karaf Maven Plugin builds features with invalid configuration

> Karaf Maven Plugin builds features with invalid configuration
> -
>
> Key: KARAF-4842
> URL: https://issues.apache.org/jira/browse/KARAF-4842
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 4.0.7
>Reporter: Achim Finke
>
> I generated a Karaf Feature using the karaf-feature-archetype. This will add 
> the following configuration to the POM file.
> {code:xml}
> 
> 
> 
> 
> org.apache.karaf.tooling
> karaf-maven-plugin
> 4.0.7
> true
> 
> 
> 
> 
> 
> org.apache.karaf.tooling
> karaf-maven-plugin
> 
> 50
> true
> (obr)
> true
> false
> true
> 
> true
> 
> 
> 
> 
> {code}
> The feature can be built but on installation the feature validation fails.
> {code}
> Caused by: org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 
> 'resolver' is not allowed to appear in element 'feature'.
> {code}
> Basically here are two issues:
> - Karaf Maven Plugin builds a feature with invalid configuration
> - The karaf-feature-archetype contains invalid configuration
> So to solve this Karaf Maven plugin should be enhanced and the resolver tag 
> should be deleted within the archetype.



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

[jira] [Commented] (KARAF-4842) Karaf Maven Plugin builds features with invalid configuration

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4842:


Commit b51331cb6cb9d561c82a052247e3758c4301d0ce in karaf's branch 
refs/heads/karaf-4.0.x from [~gnt]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=b51331c ]

[KARAF-4842] Karaf Maven Plugin builds features with invalid configuration

> Karaf Maven Plugin builds features with invalid configuration
> -
>
> Key: KARAF-4842
> URL: https://issues.apache.org/jira/browse/KARAF-4842
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 4.0.7
>Reporter: Achim Finke
>
> I generated a Karaf Feature using the karaf-feature-archetype. This will add 
> the following configuration to the POM file.
> {code:xml}
> 
> 
> 
> 
> org.apache.karaf.tooling
> karaf-maven-plugin
> 4.0.7
> true
> 
> 
> 
> 
> 
> org.apache.karaf.tooling
> karaf-maven-plugin
> 
> 50
> true
> (obr)
> true
> false
> true
> 
> true
> 
> 
> 
> 
> {code}
> The feature can be built but on installation the feature validation fails.
> {code}
> Caused by: org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 
> 'resolver' is not allowed to appear in element 'feature'.
> {code}
> Basically here are two issues:
> - Karaf Maven Plugin builds a feature with invalid configuration
> - The karaf-feature-archetype contains invalid configuration
> So to solve this Karaf Maven plugin should be enhanced and the resolver tag 
> should be deleted within the archetype.



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

[jira] [Commented] (KARAF-4838) InterruptedException of karaf shell will not be forwarded to the command

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet commented on KARAF-4838:


Any way to reproduce your problem ? Else I'm going to close this issue.

> InterruptedException of karaf shell will not be forwarded to the command
> 
>
> Key: KARAF-4838
> URL: https://issues.apache.org/jira/browse/KARAF-4838
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
>
> In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded 
> by the karaf shell to the command. This forwarding is useful since the 
> application can then decide whether it should cancel the action. However this 
> forwarding has been deactivated in karaf 4.1.0.



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

[jira] [Resolved] (KARAF-4856) Upgrade to maven-bundle-plugin 3.2.0

[JIRA]

 [ 
https://issues.apache.org/jira/browse/KARAF-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4856.
-
Resolution: Fixed

> Upgrade to maven-bundle-plugin 3.2.0
> 
>
> Key: KARAF-4856
> URL: https://issues.apache.org/jira/browse/KARAF-4856
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.8
>
>




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

[jira] [Closed] (KARAF-4840) Add support for Felix httplite

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet closed KARAF-4840.
--
   Resolution: Duplicate
Fix Version/s: (was: 4.1.0)

> Add support for Felix httplite
> --
>
> Key: KARAF-4840
> URL: https://issues.apache.org/jira/browse/KARAF-4840
> Project: Karaf
>  Issue Type: Bug
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>
> When only a very basic http service is needed, Felix HttpLite is very 
> lightweight.



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

[jira] [Resolved] (KARAF-4844) ERROR logged if the property featuresBoot contains pax-jetty in 2nd stage

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet resolved KARAF-4844.

Resolution: Fixed
  Assignee: Guillaume Nodet

It seems that has been already fixed by 
https://github.com/apache/karaf/commit/46793684018bf02ab87957546285a6935d800573 

> ERROR logged if the property featuresBoot contains pax-jetty in 2nd stage  
> ---
>
> Key: KARAF-4844
> URL: https://issues.apache.org/jira/browse/KARAF-4844
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> By starting karaf with the following property in 
> etc/org.apache.karaf.features.cfg 
> {code}
> featuresBoot = \
> (instance, \
> ...
> kar), pax-jetty
> {code}
> , one will get the following ERROR messages in data/log/karaf.log:
> {code}
> 2016-11-23T21:31:43,216 | ERROR | FelixStartLevel  | Felix
> |  -  -  | Bundle org.objectweb.asm.all [52] Error locking 
> mvn:org.ow2.asm/asm-all/6.0_ALPHA (java.lang.IllegalStateException: Bundle in 
> unexpected state.)
> java.lang.IllegalStateException: Bundle in unexpected state.
> at 
> org.apache.felix.framework.Felix.acquireBundleLock(Felix.java:5272) [?:?]
> at 
> org.apache.felix.framework.Felix.setBundleStartLevel(Felix.java:1524) [?:?]
> at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:338)
>  [?:?]
> at java.lang.Thread.run(Thread.java:745) [?:?]
> 2016-11-23T21:31:43,215 | ERROR | FelixDispatchQueue | all
>   | 85 - org.objectweb.asm.all - 5.0.2 | FrameworkEvent ERROR - 
> org.objectweb.asm.all
> java.lang.IllegalStateException: Bundle in unexpected state.
> at 
> org.apache.felix.framework.Felix.acquireBundleLock(Felix.java:5272) [?:?]
> at 
> org.apache.felix.framework.Felix.setBundleStartLevel(Felix.java:1524) [?:?]
> at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:338)
>  [?:?]
> at java.lang.Thread.run(Thread.java:745) [?:?]
> {code}



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

[jira] [Resolved] (KARAF-4843) Updating factory configuration leads to new configuration instance

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KARAF-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet resolved KARAF-4843.

   Resolution: Fixed
Fix Version/s: 4.1.0

Thx a ton for the patch !

> Updating factory configuration leads to new configuration instance
> --
>
> Key: KARAF-4843
> URL: https://issues.apache.org/jira/browse/KARAF-4843
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-config
>Affects Versions: 4.1.0
>Reporter: Jens Offenbach
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> Start with a fresh Karaf 4.1.0-SNAPSHOT installation and validate that 
> felix.fileinstall.enableConfigSave = true is set. 
> Scenario:
> - Create a factory configuration.
> - Update the configuration.
> Result:
> The configuration gets updated, but a new configuration with another 
> incorrect service.factoryPid gets created:
> Steps to reproduce:
> {code}
> karaf@root()> config:edit --factory com.example.TestConfig
> karaf@root()> config:property-set A B
> karaf@root()> config:update
> karaf@root()> config:list '(service.factoryPid=com.example.TestConfig*)'
> 
> Pid:com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> FactoryPid: com.example.TestConfig
> BundleLocation: null
> Properties:
>A = B
>service.factoryPid = com.example.TestConfig
>service.pid = com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> karaf@root()> config:edit 
> com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> karaf@root()> config:property-set A C
> karaf@root()> config:update
> karaf@root()> config:list '(service.factoryPid=com.example.TestConfig*)'
> 
> Pid:com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> FactoryPid: com.example.TestConfig
> BundleLocation: null
> Properties:
>A = C
>service.factoryPid = com.example.TestConfig
>service.pid = com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> 
> Pid:
> com.example.TestConfig.8d22975e.22055df0-4a85-4b87-94c6-7787cd84a8e5
> FactoryPid: com.example.TestConfig.8d22975e
> BundleLocation: null
> Properties:
>A = C
>felix.fileinstall.filename = 
> file:/opt/apache-karaf-4.1.0-SNAPSHOT/etc/com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af.cfg
>service.factoryPid = com.example.TestConfig.8d22975e
>service.pid = 
> com.example.TestConfig.8d22975e.22055df0-4a85-4b87-94c6-7787cd84a8e5
> karaf@root()> config:list '(service.factoryPid=com.example.TestConfigd*)'
> {code}
> I think that there is a problem with fileinstall and hyphen handling. The 
> string before the hyphen is interpreted as factoryPid resulting in 
> "com.example.TestConfig.8d22975e". Fileinstall tries to find the existing 
> configuration using the key "felix.fileinstall.filename" which is not set by 
> "ConfigRepositoryImpl".
> Solution:
> I am not sure, but I think, that in the "update"-method of 
> "ConfigRepositoryImpl", the "felix.fileinstall.filename"-property has to be 
> set explicitly and that an alias has be used that does not contain a hyphen.
> It would be nice to add an "-alias" option to the command "config:edit" that 
> allows a user to specify the alias that gets used for the factory 
> configuration. Unfortunately, the alias does not get used when the 
> configuration gets created for the first time. Only its update leads to a 
> file creation that gets considered by Fileinstall.
> What are your thoughts?



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

[jira] [Commented] (KARAF-4843) Updating factory configuration leads to new configuration instance

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4843:


Commit ddeef77cad3df9965766dc661f85525d1b149461 in karaf's branch 
refs/heads/master from Christoph Fiehe
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=ddeef77 ]

[KARAF-4843] Updating factory configuration leads to new configuration instance

> Updating factory configuration leads to new configuration instance
> --
>
> Key: KARAF-4843
> URL: https://issues.apache.org/jira/browse/KARAF-4843
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-config
>Affects Versions: 4.1.0
>Reporter: Jens Offenbach
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> Start with a fresh Karaf 4.1.0-SNAPSHOT installation and validate that 
> felix.fileinstall.enableConfigSave = true is set. 
> Scenario:
> - Create a factory configuration.
> - Update the configuration.
> Result:
> The configuration gets updated, but a new configuration with another 
> incorrect service.factoryPid gets created:
> Steps to reproduce:
> {code}
> karaf@root()> config:edit --factory com.example.TestConfig
> karaf@root()> config:property-set A B
> karaf@root()> config:update
> karaf@root()> config:list '(service.factoryPid=com.example.TestConfig*)'
> 
> Pid:com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> FactoryPid: com.example.TestConfig
> BundleLocation: null
> Properties:
>A = B
>service.factoryPid = com.example.TestConfig
>service.pid = com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> karaf@root()> config:edit 
> com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> karaf@root()> config:property-set A C
> karaf@root()> config:update
> karaf@root()> config:list '(service.factoryPid=com.example.TestConfig*)'
> 
> Pid:com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> FactoryPid: com.example.TestConfig
> BundleLocation: null
> Properties:
>A = C
>service.factoryPid = com.example.TestConfig
>service.pid = com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af
> 
> Pid:
> com.example.TestConfig.8d22975e.22055df0-4a85-4b87-94c6-7787cd84a8e5
> FactoryPid: com.example.TestConfig.8d22975e
> BundleLocation: null
> Properties:
>A = C
>felix.fileinstall.filename = 
> file:/opt/apache-karaf-4.1.0-SNAPSHOT/etc/com.example.TestConfig.8d22975e-3cb3-477c-985d-7c1a1d9f98af.cfg
>service.factoryPid = com.example.TestConfig.8d22975e
>service.pid = 
> com.example.TestConfig.8d22975e.22055df0-4a85-4b87-94c6-7787cd84a8e5
> karaf@root()> config:list '(service.factoryPid=com.example.TestConfigd*)'
> {code}
> I think that there is a problem with fileinstall and hyphen handling. The 
> string before the hyphen is interpreted as factoryPid resulting in 
> "com.example.TestConfig.8d22975e". Fileinstall tries to find the existing 
> configuration using the key "felix.fileinstall.filename" which is not set by 
> "ConfigRepositoryImpl".
> Solution:
> I am not sure, but I think, that in the "update"-method of 
> "ConfigRepositoryImpl", the "felix.fileinstall.filename"-property has to be 
> set explicitly and that an alias has be used that does not contain a hyphen.
> It would be nice to add an "-alias" option to the command "config:edit" that 
> allows a user to specify the alias that gets used for the factory 
> configuration. Unfortunately, the alias does not get used when the 
> configuration gets created for the first time. Only its update leads to a 
> file creation that gets considered by Fileinstall.
> What are your thoughts?



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