[jira] [Updated] (KARAF-5357) Help string for feature:stop is incorrect

[JIRA]

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

Jean-Baptiste Onofré updated KARAF-5357:

Component/s: karaf-shell
 karaf-feature

> Help string for feature:stop is incorrect
> -
>
> Key: KARAF-5357
> URL: https://issues.apache.org/jira/browse/KARAF-5357
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-feature, karaf-shell
>Reporter: Bethany Seeger
>Assignee: Jean-Baptiste Onofré
>Priority: Trivial
> Fix For: 4.2.0, 4.0.10, 4.1.3
>
>
> The information displayed regarding `feature:stop` when a user types `help 
> feature` in the karaf client console is incorrect.  It shows: 
> `feature:stop   Start features with the specified name and 
> version.`
> It should say `Stop features...`



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (KARAF-5357) Help string for feature:stop is incorrect

[JIRA]

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

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

Assignee: Jean-Baptiste Onofré

> Help string for feature:stop is incorrect
> -
>
> Key: KARAF-5357
> URL: https://issues.apache.org/jira/browse/KARAF-5357
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-feature, karaf-shell
>Reporter: Bethany Seeger
>Assignee: Jean-Baptiste Onofré
>Priority: Trivial
> Fix For: 4.2.0, 4.0.10, 4.1.3
>
>
> The information displayed regarding `feature:stop` when a user types `help 
> feature` in the karaf client console is incorrect.  It shows: 
> `feature:stop   Start features with the specified name and 
> version.`
> It should say `Stop features...`



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5357) Help string for feature:stop is incorrect

[Bethany Seeger (JIRA)]

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

Bethany Seeger commented on KARAF-5357:
---

I created PR to fix this typo:  https://github.com/apache/karaf/pull/348


> Help string for feature:stop is incorrect
> -
>
> Key: KARAF-5357
> URL: https://issues.apache.org/jira/browse/KARAF-5357
> Project: Karaf
>  Issue Type: Documentation
>Reporter: Bethany Seeger
>Priority: Trivial
>
> The information displayed regarding `feature:stop` when a user types `help 
> feature` in the karaf client console is incorrect.  It shows: 
> `feature:stop   Start features with the specified name and 
> version.`
> It should say `Stop features...`



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (KARAF-5357) Help string for feature:stop is incorrect

[Bethany Seeger (JIRA)]

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

Bethany Seeger updated KARAF-5357:
--
Comment: was deleted

(was: I created PR to fix this typo:  https://github.com/apache/karaf/pull/348
)

> Help string for feature:stop is incorrect
> -
>
> Key: KARAF-5357
> URL: https://issues.apache.org/jira/browse/KARAF-5357
> Project: Karaf
>  Issue Type: Documentation
>Reporter: Bethany Seeger
>Priority: Trivial
>
> The information displayed regarding `feature:stop` when a user types `help 
> feature` in the karaf client console is incorrect.  It shows: 
> `feature:stop   Start features with the specified name and 
> version.`
> It should say `Stop features...`



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5357) Help string for feature:stop is incorrect

[ASF GitHub Bot (JIRA)]

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

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

GitHub user bseeger opened a pull request:

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

[KARAF-5357] Fixes mistake in feature help info

This PR simply fixes a typo in the text that is displayed when someone 
looks up the 'feature' command.  

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

$ git pull https://github.com/bseeger/karaf KARAF-5357

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

https://github.com/apache/karaf/pull/348.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 #348


commit 5eb7c0d690a89c00f96769fab5a88291c2df6780
Author: bseeger 
Date:   2017-09-08T20:19:01Z

[KARAF-5357] Fixes mistake in feature help info




> Help string for feature:stop is incorrect
> -
>
> Key: KARAF-5357
> URL: https://issues.apache.org/jira/browse/KARAF-5357
> Project: Karaf
>  Issue Type: Documentation
>Reporter: Bethany Seeger
>Priority: Trivial
>
> The information displayed regarding `feature:stop` when a user types `help 
> feature` in the karaf client console is incorrect.  It shows: 
> `feature:stop   Start features with the specified name and 
> version.`
> It should say `Stop features...`



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (KARAF-5357) Help string for feature:stop is incorrect

[Bethany Seeger (JIRA)]

Bethany Seeger created KARAF-5357:
-

 Summary: Help string for feature:stop is incorrect
 Key: KARAF-5357
 URL: https://issues.apache.org/jira/browse/KARAF-5357
 Project: Karaf
  Issue Type: Documentation
Reporter: Bethany Seeger
Priority: Trivial


The information displayed regarding `feature:stop` when a user types `help 
feature` in the karaf client console is incorrect.  It shows: 

`feature:stop   Start features with the specified name and version.`

It should say `Stop features...`



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5356) feature:install fails if log4j has a fragment attached

[Johannes Utzig (JIRA)]

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

Johannes Utzig commented on KARAF-5356:
---

A workaround for the issue seems to be adding the log4j2 bundle into the same 
feature:

{code:xml}
 
mvn:org.example/myfragment/${project.version}
mvn:org.ops4j.pax.logging/pax-logging-log4j2/1.10.1    

{code}

> feature:install fails if log4j has a fragment attached
> --
>
> Key: KARAF-5356
> URL: https://issues.apache.org/jira/browse/KARAF-5356
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.1.2
>Reporter: Johannes Utzig
>
> I am facing an issue similar to KARAF-4129
> To add a custom appender, I created a fragment for pax-logging-log4j2.
> We create a custom distribution with this fragment. To make sure the fragment 
> is attached to log4j2, I created a feature for it and added it to the 
> startupFeatures
> {code:xml} install="auto" hidden="true">
>  start-level="7">mvn:org.example/myfragment/${project.version}
> 
> base-startup
> framework
> {code}
> When starting this custom distribution, it works fine initially, but when you 
> try to install a new feature (like webconsole for instance) you end up with:
> {code}
> java.lang.IllegalStateException: Resource has no uri
>   at 
> org.apache.karaf.features.internal.service.Deployer.getBundleInputStream(Deployer.java:1460)
>  [8:org.apache.karaf.features.core:4.1.2]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:766) 
> [8:org.apache.karaf.features.core:4.1.2]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1233)
>  [8:org.apache.karaf.features.core:4.1.2]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1132)
>  [8:org.apache.karaf.features.core:4.1.2]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$$Lambda$15/1744474597.call(Unknown
>  Source) [8:org.apache.karaf.features.core:4.1.2]
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KARAF-5356) feature:install fails if log4j has a fragment attached

[Johannes Utzig (JIRA)]

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

Johannes Utzig updated KARAF-5356:
--
Description: 
I am facing an issue similar to KARAF-4129
To add a custom appender, I created a fragment for pax-logging-log4j2.
We create a custom distribution with this fragment. To make sure the fragment 
is attached to log4j2, I created a feature for it and added it to the 
startupFeatures

{code:xml}
mvn:org.example/myfragment/${project.version}


base-startup
framework
{code}

When starting this custom distribution, it works fine initially, but when you 
try to install a new feature (like webconsole for instance) you end up with:
{code}
java.lang.IllegalStateException: Resource has no uri
at 
org.apache.karaf.features.internal.service.Deployer.getBundleInputStream(Deployer.java:1460)
 [8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:766) 
[8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1233)
 [8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1132)
 [8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl$$Lambda$15/1744474597.call(Unknown
 Source) [8:org.apache.karaf.features.core:4.1.2]
{code}


  was:
I am facing an issue similar to KARAF-4129
To add a custom appender, I created a fragment for pax-logging-log4j2.
We create a custom distribution with this fragment. To make sure the fragment 
is attached to log4j2, I created a feature for it and added it to the 
startupFeatures

{{
mvn:org.example/myfragment/${project.version}


base-startup
framework
}}

When starting this custom distribution, it works fine initially, but when you 
try to install a new feature (like webconsole for instance) you end up with:

java.lang.IllegalStateException: Resource has no uri
at 
org.apache.karaf.features.internal.service.Deployer.getBundleInputStream(Deployer.java:1460)
 [8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:766) 
[8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1233)
 [8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1132)
 [8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl$$Lambda$15/1744474597.call(Unknown
 Source) [8:org.apache.karaf.features.core:4.1.2]



> feature:install fails if log4j has a fragment attached
> --
>
> Key: KARAF-5356
> URL: https://issues.apache.org/jira/browse/KARAF-5356
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.1.2
>Reporter: Johannes Utzig
>
> I am facing an issue similar to KARAF-4129
> To add a custom appender, I created a fragment for pax-logging-log4j2.
> We create a custom distribution with this fragment. To make sure the fragment 
> is attached to log4j2, I created a feature for it and added it to the 
> startupFeatures
> {code:xml} install="auto" hidden="true">
>  start-level="7">mvn:org.example/myfragment/${project.version}
> 
> base-startup
> framework
> {code}
> When starting this custom distribution, it works fine initially, but when you 
> try to install a new feature (like webconsole for instance) you end up with:
> {code}
> java.lang.IllegalStateException: Resource has no uri
>   at 
> org.apache.karaf.features.internal.service.Deployer.getBundleInputStream(Deployer.java:1460)
>  [8:org.apache.karaf.features.core:4.1.2]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:766) 
> [8:org.apache.karaf.features.core:4.1.2]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1233)
>  [8:org.apache.karaf.features.core:4.1.2]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1132)
>  [8:org.apache.karaf.features.core:4.1.2]
>   at 
> 

[jira] [Updated] (KARAF-5356) feature:install fails if log4j has a fragment attached

[Johannes Utzig (JIRA)]

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

Johannes Utzig updated KARAF-5356:
--
Description: 
I am facing an issue similar to KARAF-4129
To add a custom appender, I created a fragment for pax-logging-log4j2.
We create a custom distribution with this fragment. To make sure the fragment 
is attached to log4j2, I created a feature for it and added it to the 
startupFeatures

{{
mvn:org.example/myfragment/${project.version}


base-startup
framework
}}

When starting this custom distribution, it works fine initially, but when you 
try to install a new feature (like webconsole for instance) you end up with:

java.lang.IllegalStateException: Resource has no uri
at 
org.apache.karaf.features.internal.service.Deployer.getBundleInputStream(Deployer.java:1460)
 [8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:766) 
[8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1233)
 [8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1132)
 [8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl$$Lambda$15/1744474597.call(Unknown
 Source) [8:org.apache.karaf.features.core:4.1.2]


  was:
I am facing an issue similar to KARAF-4129
To add a custom appender, I created a fragment for pax-logging-log4j2.
We create a custom distribution with this fragment. To make sure the fragment 
is attached to log4j2, I created a feature for it and added it to the 
startupFeatures


mvn:org.example/myfragment/${project.version}


base-startup
framework


When starting this custom distribution, it works fine initially, but when you 
try to install a new feature (like webconsole for instance) you end up with:

java.lang.IllegalStateException: Resource has no uri
at 
org.apache.karaf.features.internal.service.Deployer.getBundleInputStream(Deployer.java:1460)
 [8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:766) 
[8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1233)
 [8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1132)
 [8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl$$Lambda$15/1744474597.call(Unknown
 Source) [8:org.apache.karaf.features.core:4.1.2]



> feature:install fails if log4j has a fragment attached
> --
>
> Key: KARAF-5356
> URL: https://issues.apache.org/jira/browse/KARAF-5356
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.1.2
>Reporter: Johannes Utzig
>
> I am facing an issue similar to KARAF-4129
> To add a custom appender, I created a fragment for pax-logging-log4j2.
> We create a custom distribution with this fragment. To make sure the fragment 
> is attached to log4j2, I created a feature for it and added it to the 
> startupFeatures
> {{ install="auto" hidden="true">
>  start-level="7">mvn:org.example/myfragment/${project.version}
> 
> base-startup
> framework
> }}
> When starting this custom distribution, it works fine initially, but when you 
> try to install a new feature (like webconsole for instance) you end up with:
> java.lang.IllegalStateException: Resource has no uri
>   at 
> org.apache.karaf.features.internal.service.Deployer.getBundleInputStream(Deployer.java:1460)
>  [8:org.apache.karaf.features.core:4.1.2]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:766) 
> [8:org.apache.karaf.features.core:4.1.2]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1233)
>  [8:org.apache.karaf.features.core:4.1.2]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1132)
>  [8:org.apache.karaf.features.core:4.1.2]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$$Lambda$15/1744474597.call(Unknown
>  Source) 

[jira] [Created] (KARAF-5356) feature:install fails if log4j has a fragment attached

[Johannes Utzig (JIRA)]

Johannes Utzig created KARAF-5356:
-

 Summary: feature:install fails if log4j has a fragment attached
 Key: KARAF-5356
 URL: https://issues.apache.org/jira/browse/KARAF-5356
 Project: Karaf
  Issue Type: Bug
  Components: karaf-feature
Affects Versions: 4.1.2
Reporter: Johannes Utzig


I am facing an issue similar to KARAF-4129
To add a custom appender, I created a fragment for pax-logging-log4j2.
We create a custom distribution with this fragment. To make sure the fragment 
is attached to log4j2, I created a feature for it and added it to the 
startupFeatures


mvn:org.example/myfragment/${project.version}


base-startup
framework


When starting this custom distribution, it works fine initially, but when you 
try to install a new feature (like webconsole for instance) you end up with:

java.lang.IllegalStateException: Resource has no uri
at 
org.apache.karaf.features.internal.service.Deployer.getBundleInputStream(Deployer.java:1460)
 [8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:766) 
[8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1233)
 [8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1132)
 [8:org.apache.karaf.features.core:4.1.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl$$Lambda$15/1744474597.call(Unknown
 Source) [8:org.apache.karaf.features.core:4.1.2]




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5350) Get auto update functionality like "bundle:watch *" on snapshot artifacts from remote repositories

[Steinar Bang (JIRA)]

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

Steinar Bang commented on KARAF-5350:
-

How costly is the "feature:install" operation on a feature consisting of 
snapshot bundles from a remote repository?

(I'm thinking of just the ballpark numbers. Ie. is this so time consuming it 
should only be run once a day? Or is this so low-cost it could be run once a 
minute?)

> Get auto update functionality like "bundle:watch *" on snapshot artifacts 
> from remote repositories
> --
>
> Key: KARAF-5350
> URL: https://issues.apache.org/jira/browse/KARAF-5350
> Project: Karaf
>  Issue Type: Improvement
>Reporter: Steinar Bang
>
> I now have a continous deployment pipeline for [my 
> project|https://github.com/steinarb/ukelonn] almost automated:
> # All changes I would like deployed, I merge to master and then push master 
> to github
> # New pushes on master triggers a build on travis-ci
> # A successful build on travis-ci results in a new snapshot being deployed to 
> a maven repository accessible via HTTP
> ## The bundles that make up my application have been installed from snapshots 
> in the maven repository, like so (karaf consolle commands):
> {noformat}
> config:edit org.ops4j.pax.url.mvn
> config:property-append org.ops4j.pax.url.mvn.repositories ", 
> https://maven.bang.priv.no/repository/@snapshots, 
> http://maven.vaadin.com/vaadin-addons;
> config:property-set org.ops4j.pax.url.mvn.globalUpdatePolicy always
> config:update
> feature:repo-add mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features
> feature:install ukelonn-db-postgresql
> feature:install ukelonn
> {noformat}
> # The final step I have to do during a deployment, is to log in with ssh to 
> the karaf console and give "bundle:update" on each bundle
> {noformat}
> bundle:update no.priv.bang.ukelonn.api
> bundle:update no.priv.bang.ukelonn.db.liquibase
> bundle:update no.priv.bang.ukelonn.db.postgresql
> bundle:update no.priv.bang.ukelonn
> {noformat}
> It is the final step I would like to have automated, so that new snapshots 
> deployed to the remote repository is automatically picked up by karaf.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5352) KARAF_ETC envvar ignored

[JIRA]

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

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

Indeed, it works fine with Karaf 4.0.x, including the {{shell.init.script}} 
loading. Let me fix that on master & 4.1.x first.

> KARAF_ETC envvar ignored
> 
>
> Key: KARAF-5352
> URL: https://issues.apache.org/jira/browse/KARAF-5352
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Affects Versions: 4.1.2
> Environment: Tested on CentOS 7.x
>Reporter: Thomas Bouron
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.3
>
>
> I'm currently working on upgrading the RPM and DEB packaging for Apache 
> Brooklyn. The project uses Karaf and has the following folder structure for 
> the RPM package:
> {code}
> /-
>  +- etc
>  |+- brooklyn
>  +- opt
>  |+- brooklyn-0.12.0-SNAPSHOT
>  ||+- bin
>  ||+- data
>  ||+- deploy
>  ||+- lib
>  ||+- system
> {code}
> The {{etc}} folder is not part of {{KARAF_HOME}} but in {{/etc/brooklyn}}. I 
> setup my {{KARAF_ETC}} to point to this folder, however when I start Karaf, I 
> get the followoing
> {code}
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 systemd[1]: Started 
> Apache Brooklyn Service.
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 systemd[1]: Starting 
> Apache Brooklyn Service...
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: JAVA_HOME 
> not set; results may vary
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: karaf: 
> Ignoring predefined value for KARAF_HOME
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: 
> 15:27:17.085 [pool-1-thread-2] ERROR org.apache.karaf.features.inte
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: 
> java.io.IOException: /opt/brooklyn-0.12.0-SNAPSHOT/etc/0d218152-8d8
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.RepositoryImpl.load(R
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.l
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.a
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.a
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.BootFeaturesInstaller
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.BootFeaturesInstaller
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.osgi.Activator.doStart(Activa
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.ja
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.ja
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.lang.Thread.run(Thread.java:748) [?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: Caused 
> by: java.io.FileNotFoundException: /opt/brooklyn-0.12.0-SNAP
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.io.FileInputStream.open0(Native Method) ~[?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.io.FileInputStream.open(FileInputStream.java:195) ~[?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.io.FileInputStream.(FileInputStream.java:138) ~[?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.io.FileInputStream.(FileInputStream.java:93) ~[?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConne
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileU
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.net.URL.openStream(URL.java:1045) ~[?:?]
> Sep 07 15:27:17 

[jira] [Commented] (KARAF-5352) KARAF_ETC envvar ignored

[JIRA]

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

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

Same thing on 4.1.x. Just the {{shell.init.script}} is not happy. Other parts 
of Karaf are just fine. For the record, I defined {{KARAF_ETC}} in 
{{bin/setenv}}.

> KARAF_ETC envvar ignored
> 
>
> Key: KARAF-5352
> URL: https://issues.apache.org/jira/browse/KARAF-5352
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Affects Versions: 4.1.2
> Environment: Tested on CentOS 7.x
>Reporter: Thomas Bouron
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.3
>
>
> I'm currently working on upgrading the RPM and DEB packaging for Apache 
> Brooklyn. The project uses Karaf and has the following folder structure for 
> the RPM package:
> {code}
> /-
>  +- etc
>  |+- brooklyn
>  +- opt
>  |+- brooklyn-0.12.0-SNAPSHOT
>  ||+- bin
>  ||+- data
>  ||+- deploy
>  ||+- lib
>  ||+- system
> {code}
> The {{etc}} folder is not part of {{KARAF_HOME}} but in {{/etc/brooklyn}}. I 
> setup my {{KARAF_ETC}} to point to this folder, however when I start Karaf, I 
> get the followoing
> {code}
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 systemd[1]: Started 
> Apache Brooklyn Service.
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 systemd[1]: Starting 
> Apache Brooklyn Service...
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: JAVA_HOME 
> not set; results may vary
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: karaf: 
> Ignoring predefined value for KARAF_HOME
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: 
> 15:27:17.085 [pool-1-thread-2] ERROR org.apache.karaf.features.inte
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: 
> java.io.IOException: /opt/brooklyn-0.12.0-SNAPSHOT/etc/0d218152-8d8
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.RepositoryImpl.load(R
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.l
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.a
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.a
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.BootFeaturesInstaller
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.BootFeaturesInstaller
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.osgi.Activator.doStart(Activa
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.ja
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.ja
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.lang.Thread.run(Thread.java:748) [?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: Caused 
> by: java.io.FileNotFoundException: /opt/brooklyn-0.12.0-SNAP
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.io.FileInputStream.open0(Native Method) ~[?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.io.FileInputStream.open(FileInputStream.java:195) ~[?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.io.FileInputStream.(FileInputStream.java:138) ~[?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.io.FileInputStream.(FileInputStream.java:93) ~[?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConne
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileU
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.net.URL.openStream(URL.java:1045) ~[?:?]
> 

[jira] [Commented] (KARAF-5352) KARAF_ETC envvar ignored

[JIRA]

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

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

It could be related to Felix FileInstall update too. I'm investigating.

> KARAF_ETC envvar ignored
> 
>
> Key: KARAF-5352
> URL: https://issues.apache.org/jira/browse/KARAF-5352
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Affects Versions: 4.1.2
> Environment: Tested on CentOS 7.x
>Reporter: Thomas Bouron
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.3
>
>
> I'm currently working on upgrading the RPM and DEB packaging for Apache 
> Brooklyn. The project uses Karaf and has the following folder structure for 
> the RPM package:
> {code}
> /-
>  +- etc
>  |+- brooklyn
>  +- opt
>  |+- brooklyn-0.12.0-SNAPSHOT
>  ||+- bin
>  ||+- data
>  ||+- deploy
>  ||+- lib
>  ||+- system
> {code}
> The {{etc}} folder is not part of {{KARAF_HOME}} but in {{/etc/brooklyn}}. I 
> setup my {{KARAF_ETC}} to point to this folder, however when I start Karaf, I 
> get the followoing
> {code}
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 systemd[1]: Started 
> Apache Brooklyn Service.
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 systemd[1]: Starting 
> Apache Brooklyn Service...
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: JAVA_HOME 
> not set; results may vary
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: karaf: 
> Ignoring predefined value for KARAF_HOME
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: 
> 15:27:17.085 [pool-1-thread-2] ERROR org.apache.karaf.features.inte
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: 
> java.io.IOException: /opt/brooklyn-0.12.0-SNAPSHOT/etc/0d218152-8d8
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.RepositoryImpl.load(R
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.l
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.a
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.a
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.BootFeaturesInstaller
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.BootFeaturesInstaller
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.osgi.Activator.doStart(Activa
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.ja
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.ja
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.lang.Thread.run(Thread.java:748) [?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: Caused 
> by: java.io.FileNotFoundException: /opt/brooklyn-0.12.0-SNAP
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.io.FileInputStream.open0(Native Method) ~[?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.io.FileInputStream.open(FileInputStream.java:195) ~[?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.io.FileInputStream.(FileInputStream.java:138) ~[?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.io.FileInputStream.(FileInputStream.java:93) ~[?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConne
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileU
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.net.URL.openStream(URL.java:1045) ~[?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> 

[jira] [Updated] (KARAF-5351) Command-line doc is not precising for "" that at least one letter need to be provided

[JIRA]

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

Jean-Baptiste Onofré updated KARAF-5351:

Component/s: karaf-documentation

> Command-line doc is not precising for "" that at least one letter need 
> to be provided
> --
>
> Key: KARAF-5351
> URL: https://issues.apache.org/jira/browse/KARAF-5351
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-documentation, karaf-shell
>Affects Versions: 4.1.2
>Reporter: Aurélien Pupier
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> so either:
> - implement the list of commands when there is no letter yet
> - update the documentation printed when starting Fuse to something like "Type 
> a letter and then hit '' for a list of available commands with the 
> provided prefix"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (KARAF-5351) Command-line doc is not precising for "" that at least one letter need to be provided

[JIRA]

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

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

Assignee: Jean-Baptiste Onofré

> Command-line doc is not precising for "" that at least one letter need 
> to be provided
> --
>
> Key: KARAF-5351
> URL: https://issues.apache.org/jira/browse/KARAF-5351
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-documentation, karaf-shell
>Affects Versions: 4.1.2
>Reporter: Aurélien Pupier
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> so either:
> - implement the list of commands when there is no letter yet
> - update the documentation printed when starting Fuse to something like "Type 
> a letter and then hit '' for a list of available commands with the 
> provided prefix"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KARAF-5351) Command-line doc is not precising for "" that at least one letter need to be provided

[JIRA]

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

Jean-Baptiste Onofré updated KARAF-5351:

Component/s: karaf-shell

> Command-line doc is not precising for "" that at least one letter need 
> to be provided
> --
>
> Key: KARAF-5351
> URL: https://issues.apache.org/jira/browse/KARAF-5351
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-documentation, karaf-shell
>Affects Versions: 4.1.2
>Reporter: Aurélien Pupier
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> so either:
> - implement the list of commands when there is no letter yet
> - update the documentation printed when starting Fuse to something like "Type 
> a letter and then hit '' for a list of available commands with the 
> provided prefix"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5355) The scripts triggered with {{scheduler::schedule}} command fail to execute

[JIRA]

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

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

To reproduce, you just do {{scheduler:schedule}} ?

> The scripts triggered with {{scheduler::schedule}} command fail to execute
> --
>
> Key: KARAF-5355
> URL: https://issues.apache.org/jira/browse/KARAF-5355
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-scheduler
>Reporter: Guillaume Nodet
>Assignee: Jean-Baptiste Onofré
>
> See the following exception
> {code}
> 2017-09-08 07:46:49,818 | WARN  | null_Worker-1| ScriptJob
> | 35 - org.apache.karaf.scheduler.core - 4.2.0.SNAPSHOT | Error 
> executing script
> java.lang.IllegalStateException: A job is already in foreground
>   at 
> org.apache.felix.gogo.runtime.CommandSessionImpl$JobImpl.foreground(CommandSessionImpl.java:643)
>  [28:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.gogo.runtime.CommandSessionImpl$JobImpl.start(CommandSessionImpl.java:760)
>  [28:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:295) 
> [28:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:168) 
> [28:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:148) 
> [28:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand$VersatileFunction.execute(SecuredCommand.java:107)
>  [28:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.scheduler.command.support.ScriptJob.execute(ScriptJob.java:43)
>  [35:org.apache.karaf.scheduler.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.scheduler.core.QuartzJobExecutor.execute(QuartzJobExecutor.java:52)
>  [35:org.apache.karaf.scheduler.core:4.2.0.SNAPSHOT]
>   at org.quartz.core.JobRunShell.run(JobRunShell.java:202) 
> [35:org.apache.karaf.scheduler.core:4.2.0.SNAPSHOT]
>   at 
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) 
> [35:org.apache.karaf.scheduler.core:4.2.0.SNAPSHOT
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KARAF-5354) log:get and log:set Do Not Work for a etc/log4j2.xml Configuration File

[JIRA]

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

Jean-Baptiste Onofré updated KARAF-5354:

Component/s: karaf-logging

> log:get and log:set Do Not Work for a etc/log4j2.xml Configuration File
> ---
>
> Key: KARAF-5354
> URL: https://issues.apache.org/jira/browse/KARAF-5354
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-logging
>Affects Versions: 4.1.2
>Reporter: Emily Berk
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> Steps to reproduce:
> 1. Replace contents of {{etc/org.ops4j.pax.logging.cfg}} with 
> {code}
> org.ops4j.pax.logging.log4j2.config.file=${karaf.etc}/log4j2.xml
> {code}
> 2. Add an {{etc/log4j2.xml}} configuration file with a configuration like
> {code}
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> 3. Start up Karaf.
> Notice that {{log:set}} and {{log:get}} fail with 
> {code}
> 2017-09-07 18:28:39,352 | ERROR | nsole user karaf | ShellUtil
> | 42 - org.apache.karaf.shell.core - 4.1.2 | Exception caught while 
> executing command
> java.lang.IllegalStateException: Unrecognized configuration
>   at 
> org.apache.karaf.log.core.internal.LogServiceImpl.getDelegate(LogServiceImpl.java:55)
>  [36:org.apache.karaf.log.core:4.1.2]
>   at 
> org.apache.karaf.log.core.internal.LogServiceImpl.setLevel(LogServiceImpl.java:98)
>  [36:org.apache.karaf.log.core:4.1.2]
>   at 
> org.apache.karaf.log.command.SetLogLevel.execute(SetLogLevel.java:48) 
> [36:org.apache.karaf.log.core:4.1.2]
>   at 
> org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:84)
>  [42:org.apache.karaf.shell.core:4.1.2]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
>  [42:org.apache.karaf.shell.core:4.1.2]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
>  [42:org.apache.karaf.shell.core:4.1.2]
>   at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:571) 
> [42:org.apache.karaf.shell.core:4.1.2]
>   at 
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:497) 
> [42:org.apache.karaf.shell.core:4.1.2]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:386) 
> [42:org.apache.karaf.shell.core:4.1.2]
>   at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:417) 
> [42:org.apache.karaf.shell.core:4.1.2]
>   at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229) 
> [42:org.apache.karaf.shell.core:4.1.2]
>   at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59) 
> [42:org.apache.karaf.shell.core:4.1.2]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [?:?]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [?:?]
>   at java.lang.Thread.run(Thread.java:745) [?:?]
> {code}
> {{log:set}} and {{log:get}} should behave the same when using the 
> {{log4j2.xml}} configuration as when using the {{org.ops4j.pax.logging.cfg}} 
> configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (KARAF-5354) log:get and log:set Do Not Work for a etc/log4j2.xml Configuration File

[JIRA]

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

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

Assignee: Jean-Baptiste Onofré

> log:get and log:set Do Not Work for a etc/log4j2.xml Configuration File
> ---
>
> Key: KARAF-5354
> URL: https://issues.apache.org/jira/browse/KARAF-5354
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-logging
>Affects Versions: 4.1.2
>Reporter: Emily Berk
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> Steps to reproduce:
> 1. Replace contents of {{etc/org.ops4j.pax.logging.cfg}} with 
> {code}
> org.ops4j.pax.logging.log4j2.config.file=${karaf.etc}/log4j2.xml
> {code}
> 2. Add an {{etc/log4j2.xml}} configuration file with a configuration like
> {code}
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> 3. Start up Karaf.
> Notice that {{log:set}} and {{log:get}} fail with 
> {code}
> 2017-09-07 18:28:39,352 | ERROR | nsole user karaf | ShellUtil
> | 42 - org.apache.karaf.shell.core - 4.1.2 | Exception caught while 
> executing command
> java.lang.IllegalStateException: Unrecognized configuration
>   at 
> org.apache.karaf.log.core.internal.LogServiceImpl.getDelegate(LogServiceImpl.java:55)
>  [36:org.apache.karaf.log.core:4.1.2]
>   at 
> org.apache.karaf.log.core.internal.LogServiceImpl.setLevel(LogServiceImpl.java:98)
>  [36:org.apache.karaf.log.core:4.1.2]
>   at 
> org.apache.karaf.log.command.SetLogLevel.execute(SetLogLevel.java:48) 
> [36:org.apache.karaf.log.core:4.1.2]
>   at 
> org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:84)
>  [42:org.apache.karaf.shell.core:4.1.2]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
>  [42:org.apache.karaf.shell.core:4.1.2]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
>  [42:org.apache.karaf.shell.core:4.1.2]
>   at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:571) 
> [42:org.apache.karaf.shell.core:4.1.2]
>   at 
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:497) 
> [42:org.apache.karaf.shell.core:4.1.2]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:386) 
> [42:org.apache.karaf.shell.core:4.1.2]
>   at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:417) 
> [42:org.apache.karaf.shell.core:4.1.2]
>   at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229) 
> [42:org.apache.karaf.shell.core:4.1.2]
>   at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59) 
> [42:org.apache.karaf.shell.core:4.1.2]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [?:?]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [?:?]
>   at java.lang.Thread.run(Thread.java:745) [?:?]
> {code}
> {{log:set}} and {{log:get}} should behave the same when using the 
> {{log4j2.xml}} configuration as when using the {{org.ops4j.pax.logging.cfg}} 
> configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5354) log:get and log:set Do Not Work for a etc/log4j2.xml Configuration File

[JIRA]

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

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

I think we already have a Jira about that. Let me find it.

> log:get and log:set Do Not Work for a etc/log4j2.xml Configuration File
> ---
>
> Key: KARAF-5354
> URL: https://issues.apache.org/jira/browse/KARAF-5354
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-logging
>Affects Versions: 4.1.2
>Reporter: Emily Berk
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> Steps to reproduce:
> 1. Replace contents of {{etc/org.ops4j.pax.logging.cfg}} with 
> {code}
> org.ops4j.pax.logging.log4j2.config.file=${karaf.etc}/log4j2.xml
> {code}
> 2. Add an {{etc/log4j2.xml}} configuration file with a configuration like
> {code}
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> 3. Start up Karaf.
> Notice that {{log:set}} and {{log:get}} fail with 
> {code}
> 2017-09-07 18:28:39,352 | ERROR | nsole user karaf | ShellUtil
> | 42 - org.apache.karaf.shell.core - 4.1.2 | Exception caught while 
> executing command
> java.lang.IllegalStateException: Unrecognized configuration
>   at 
> org.apache.karaf.log.core.internal.LogServiceImpl.getDelegate(LogServiceImpl.java:55)
>  [36:org.apache.karaf.log.core:4.1.2]
>   at 
> org.apache.karaf.log.core.internal.LogServiceImpl.setLevel(LogServiceImpl.java:98)
>  [36:org.apache.karaf.log.core:4.1.2]
>   at 
> org.apache.karaf.log.command.SetLogLevel.execute(SetLogLevel.java:48) 
> [36:org.apache.karaf.log.core:4.1.2]
>   at 
> org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:84)
>  [42:org.apache.karaf.shell.core:4.1.2]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
>  [42:org.apache.karaf.shell.core:4.1.2]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
>  [42:org.apache.karaf.shell.core:4.1.2]
>   at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:571) 
> [42:org.apache.karaf.shell.core:4.1.2]
>   at 
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:497) 
> [42:org.apache.karaf.shell.core:4.1.2]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:386) 
> [42:org.apache.karaf.shell.core:4.1.2]
>   at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:417) 
> [42:org.apache.karaf.shell.core:4.1.2]
>   at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229) 
> [42:org.apache.karaf.shell.core:4.1.2]
>   at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59) 
> [42:org.apache.karaf.shell.core:4.1.2]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [?:?]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [?:?]
>   at java.lang.Thread.run(Thread.java:745) [?:?]
> {code}
> {{log:set}} and {{log:get}} should behave the same when using the 
> {{log4j2.xml}} configuration as when using the {{org.ops4j.pax.logging.cfg}} 
> configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (KARAF-5355) The scripts triggered with {{scheduler::schedule}} command fail to execute

[JIRA]

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

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

Assignee: Jean-Baptiste Onofré

> The scripts triggered with {{scheduler::schedule}} command fail to execute
> --
>
> Key: KARAF-5355
> URL: https://issues.apache.org/jira/browse/KARAF-5355
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-scheduler
>Reporter: Guillaume Nodet
>Assignee: Jean-Baptiste Onofré
>
> See the following exception
> {code}
> 2017-09-08 07:46:49,818 | WARN  | null_Worker-1| ScriptJob
> | 35 - org.apache.karaf.scheduler.core - 4.2.0.SNAPSHOT | Error 
> executing script
> java.lang.IllegalStateException: A job is already in foreground
>   at 
> org.apache.felix.gogo.runtime.CommandSessionImpl$JobImpl.foreground(CommandSessionImpl.java:643)
>  [28:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.gogo.runtime.CommandSessionImpl$JobImpl.start(CommandSessionImpl.java:760)
>  [28:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:295) 
> [28:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:168) 
> [28:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:148) 
> [28:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand$VersatileFunction.execute(SecuredCommand.java:107)
>  [28:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.scheduler.command.support.ScriptJob.execute(ScriptJob.java:43)
>  [35:org.apache.karaf.scheduler.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.scheduler.core.QuartzJobExecutor.execute(QuartzJobExecutor.java:52)
>  [35:org.apache.karaf.scheduler.core:4.2.0.SNAPSHOT]
>   at org.quartz.core.JobRunShell.run(JobRunShell.java:202) 
> [35:org.apache.karaf.scheduler.core:4.2.0.SNAPSHOT]
>   at 
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) 
> [35:org.apache.karaf.scheduler.core:4.2.0.SNAPSHOT
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KARAF-5355) The scripts triggered with {{scheduler::schedule}} command fail to execute

[JIRA]

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

Jean-Baptiste Onofré updated KARAF-5355:

Component/s: karaf-scheduler

> The scripts triggered with {{scheduler::schedule}} command fail to execute
> --
>
> Key: KARAF-5355
> URL: https://issues.apache.org/jira/browse/KARAF-5355
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-scheduler
>Reporter: Guillaume Nodet
>Assignee: Jean-Baptiste Onofré
>
> See the following exception
> {code}
> 2017-09-08 07:46:49,818 | WARN  | null_Worker-1| ScriptJob
> | 35 - org.apache.karaf.scheduler.core - 4.2.0.SNAPSHOT | Error 
> executing script
> java.lang.IllegalStateException: A job is already in foreground
>   at 
> org.apache.felix.gogo.runtime.CommandSessionImpl$JobImpl.foreground(CommandSessionImpl.java:643)
>  [28:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.gogo.runtime.CommandSessionImpl$JobImpl.start(CommandSessionImpl.java:760)
>  [28:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:295) 
> [28:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:168) 
> [28:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:148) 
> [28:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand$VersatileFunction.execute(SecuredCommand.java:107)
>  [28:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.scheduler.command.support.ScriptJob.execute(ScriptJob.java:43)
>  [35:org.apache.karaf.scheduler.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.scheduler.core.QuartzJobExecutor.execute(QuartzJobExecutor.java:52)
>  [35:org.apache.karaf.scheduler.core:4.2.0.SNAPSHOT]
>   at org.quartz.core.JobRunShell.run(JobRunShell.java:202) 
> [35:org.apache.karaf.scheduler.core:4.2.0.SNAPSHOT]
>   at 
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) 
> [35:org.apache.karaf.scheduler.core:4.2.0.SNAPSHOT
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (KARAF-5350) Get auto update functionality like "bundle:watch *" on snapshot artifacts from remote repositories

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet edited comment on KARAF-5350 at 9/8/17 10:43 AM:
-

A way to automate that is to trigger a feature installation on a regular basis:
{code}
> feature:install scheduler
> scheduler:schedule --period 60 { feature:install shell }
{code}

Note that the code should update all snapshot bundles from remote repositories 
installed through features (not only the one from the {{shell}} feature).  The 
reason is that the FeatureService always work on a global way, so any call to 
it will update all the necessary bundles. 


was (Author: gnt):
A way to automate that is to trigger a feature installation on a regular basis:
{code}
> feature:install scheduler
> scheduler:schedule --period 60 { feature:install shell }
{code}

> Get auto update functionality like "bundle:watch *" on snapshot artifacts 
> from remote repositories
> --
>
> Key: KARAF-5350
> URL: https://issues.apache.org/jira/browse/KARAF-5350
> Project: Karaf
>  Issue Type: Improvement
>Reporter: Steinar Bang
>
> I now have a continous deployment pipeline for [my 
> project|https://github.com/steinarb/ukelonn] almost automated:
> # All changes I would like deployed, I merge to master and then push master 
> to github
> # New pushes on master triggers a build on travis-ci
> # A successful build on travis-ci results in a new snapshot being deployed to 
> a maven repository accessible via HTTP
> ## The bundles that make up my application have been installed from snapshots 
> in the maven repository, like so (karaf consolle commands):
> {noformat}
> config:edit org.ops4j.pax.url.mvn
> config:property-append org.ops4j.pax.url.mvn.repositories ", 
> https://maven.bang.priv.no/repository/@snapshots, 
> http://maven.vaadin.com/vaadin-addons;
> config:property-set org.ops4j.pax.url.mvn.globalUpdatePolicy always
> config:update
> feature:repo-add mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features
> feature:install ukelonn-db-postgresql
> feature:install ukelonn
> {noformat}
> # The final step I have to do during a deployment, is to log in with ssh to 
> the karaf console and give "bundle:update" on each bundle
> {noformat}
> bundle:update no.priv.bang.ukelonn.api
> bundle:update no.priv.bang.ukelonn.db.liquibase
> bundle:update no.priv.bang.ukelonn.db.postgresql
> bundle:update no.priv.bang.ukelonn
> {noformat}
> It is the final step I would like to have automated, so that new snapshots 
> deployed to the remote repository is automatically picked up by karaf.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5352) KARAF_ETC envvar ignored

[Thomas Bouron (JIRA)]

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

Thomas Bouron commented on KARAF-5352:
--

Obviously, I can provide you the RPM package I'm testing, if needed.

> KARAF_ETC envvar ignored
> 
>
> Key: KARAF-5352
> URL: https://issues.apache.org/jira/browse/KARAF-5352
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Affects Versions: 4.1.2
> Environment: Tested on CentOS 7.x
>Reporter: Thomas Bouron
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.3
>
>
> I'm currently working on upgrading the RPM and DEB packaging for Apache 
> Brooklyn. The project uses Karaf and has the following folder structure for 
> the RPM package:
> {code}
> /-
>  +- etc
>  |+- brooklyn
>  +- opt
>  |+- brooklyn-0.12.0-SNAPSHOT
>  ||+- bin
>  ||+- data
>  ||+- deploy
>  ||+- lib
>  ||+- system
> {code}
> The {{etc}} folder is not part of {{KARAF_HOME}} but in {{/etc/brooklyn}}. I 
> setup my {{KARAF_ETC}} to point to this folder, however when I start Karaf, I 
> get the followoing
> {code}
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 systemd[1]: Started 
> Apache Brooklyn Service.
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 systemd[1]: Starting 
> Apache Brooklyn Service...
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: JAVA_HOME 
> not set; results may vary
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: karaf: 
> Ignoring predefined value for KARAF_HOME
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: 
> 15:27:17.085 [pool-1-thread-2] ERROR org.apache.karaf.features.inte
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: 
> java.io.IOException: /opt/brooklyn-0.12.0-SNAPSHOT/etc/0d218152-8d8
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.RepositoryImpl.load(R
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.l
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.a
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.a
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.BootFeaturesInstaller
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.BootFeaturesInstaller
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.osgi.Activator.doStart(Activa
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.ja
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.ja
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.lang.Thread.run(Thread.java:748) [?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: Caused 
> by: java.io.FileNotFoundException: /opt/brooklyn-0.12.0-SNAP
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.io.FileInputStream.open0(Native Method) ~[?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.io.FileInputStream.open(FileInputStream.java:195) ~[?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.io.FileInputStream.(FileInputStream.java:138) ~[?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.io.FileInputStream.(FileInputStream.java:93) ~[?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConne
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileU
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.net.URL.openStream(URL.java:1045) ~[?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> 

[jira] [Commented] (KARAF-5352) KARAF_ETC envvar ignored

[Thomas Bouron (JIRA)]

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

Thomas Bouron commented on KARAF-5352:
--

Thanks for looking into this [~jbonofre]

Let me give you a bit more details. Here are my envvars:
{code}
KARAF_HOME=/opt/brooklyn
KARAF_ETC=/etc/brooklyn
KARAF_REDIRECT=/dev/null
{code}

and the launch command executed:
{code}
/opt/brooklyn/bin/karaf server  >> "$KARAF_REDIRECT" 2>&1
{code}

It is worth noting that on a fresh VM, if I launch without the {{etc}} 
softlink, Karaf *_seems_* to start: PID file is created and {{karaf.log}} 
displays this:
{code}
Sep 07, 2017 4:07:04 PM org.apache.karaf.main.Main launch
INFO: Installing and starting initial bundles
Sep 07, 2017 4:07:04 PM org.apache.karaf.main.Main launch
INFO: All initial bundles installed and set to start
Sep 07, 2017 4:07:04 PM org.apache.karaf.main.lock.SimpleFileLock lock
INFO: Trying to lock /opt/brooklyn-0.12.0-SNAPSHOT/lock
Sep 07, 2017 4:07:04 PM org.apache.karaf.main.lock.SimpleFileLock lock
INFO: Lock acquired
Sep 07, 2017 4:07:04 PM org.apache.karaf.main.Main$KarafLockCallback lockAquired
INFO: Lock acquired. Setting startlevel to 100
{code}

However the application does not start and it's impossible to log into the 
Karaf shell. Even if I softlink {{etc}} thereafter, it does the same thing. It 
seems that the first failed launch puts Karaf into an unstable state.

BUT, if I setup the {{etc}} softlink *BEFORE* starting Karaf for the first 
time, it then works.

Hope that is enough details to untangle this issue :)

> KARAF_ETC envvar ignored
> 
>
> Key: KARAF-5352
> URL: https://issues.apache.org/jira/browse/KARAF-5352
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Affects Versions: 4.1.2
> Environment: Tested on CentOS 7.x
>Reporter: Thomas Bouron
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.3
>
>
> I'm currently working on upgrading the RPM and DEB packaging for Apache 
> Brooklyn. The project uses Karaf and has the following folder structure for 
> the RPM package:
> {code}
> /-
>  +- etc
>  |+- brooklyn
>  +- opt
>  |+- brooklyn-0.12.0-SNAPSHOT
>  ||+- bin
>  ||+- data
>  ||+- deploy
>  ||+- lib
>  ||+- system
> {code}
> The {{etc}} folder is not part of {{KARAF_HOME}} but in {{/etc/brooklyn}}. I 
> setup my {{KARAF_ETC}} to point to this folder, however when I start Karaf, I 
> get the followoing
> {code}
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 systemd[1]: Started 
> Apache Brooklyn Service.
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 systemd[1]: Starting 
> Apache Brooklyn Service...
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: JAVA_HOME 
> not set; results may vary
> Sep 07 15:27:14 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: karaf: 
> Ignoring predefined value for KARAF_HOME
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: 
> 15:27:17.085 [pool-1-thread-2] ERROR org.apache.karaf.features.inte
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: 
> java.io.IOException: /opt/brooklyn-0.12.0-SNAPSHOT/etc/0d218152-8d8
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.RepositoryImpl.load(R
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.l
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.a
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.a
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.BootFeaturesInstaller
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.service.BootFeaturesInstaller
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.features.internal.osgi.Activator.doStart(Activa
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.ja
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.ja
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
> Sep 07 15:27:17 br-ovx1by-amp-appl-om8x-empty-t0ww-280 karaf[1919]: at 
>