[jira] [Closed] (KARAF-4667) system-script : add templates to manage child instances
[ https://issues.apache.org/jira/browse/KARAF-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli closed KARAF-4667. -- Resolution: Won't Fix > system-script : add templates to manage child instances > --- > > Key: KARAF-4667 > URL: https://issues.apache.org/jira/browse/KARAF-4667 > Project: Karaf > Issue Type: Improvement > Components: karaf >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > > As today the system script-templates are mainly developed for root > container, it would be nice to add some additional templates to manage child > instances. > I will submit a PR -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (KARAF-4188) Add support for Systemd's watchdog
[ https://issues.apache.org/jira/browse/KARAF-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15744394#comment-15744394 ] Luca Burgazzoli edited comment on KARAF-4188 at 12/13/16 7:04 AM: -- Does JNA break karaf on ARM and Solaris even without the recent jline upgrade ? was (Author: lb): Does JNA breaks karaf on ARM and Solaris even without the recent jline upgrade ? > Add support for Systemd's watchdog > -- > > Key: KARAF-4188 > URL: https://issues.apache.org/jira/browse/KARAF-4188 > Project: Karaf > Issue Type: New Feature > Components: karaf-core >Reporter: Luca Burgazzoli >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.6, 4.0.9 > > > Systemd has a watchdog feature that could help detecting freeze jvm, > integrating it in karaf would be possible via jna/jnr -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4188) Add support for Systemd's watchdog
[ https://issues.apache.org/jira/browse/KARAF-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15744394#comment-15744394 ] Luca Burgazzoli commented on KARAF-4188: Does JNA breaks karaf on ARM and Solaris even without the recent jline upgrade ? > Add support for Systemd's watchdog > -- > > Key: KARAF-4188 > URL: https://issues.apache.org/jira/browse/KARAF-4188 > Project: Karaf > Issue Type: New Feature > Components: karaf-core >Reporter: Luca Burgazzoli >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.6, 4.0.9 > > > Systemd has a watchdog feature that could help detecting freeze jvm, > integrating it in karaf would be possible via jna/jnr -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-4667) system-script : add templates to manage child instances
[ https://issues.apache.org/jira/browse/KARAF-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli reassigned KARAF-4667: -- Assignee: Luca Burgazzoli > system-script : add templates to manage child instances > --- > > Key: KARAF-4667 > URL: https://issues.apache.org/jira/browse/KARAF-4667 > Project: Karaf > Issue Type: Improvement > Components: karaf-os-integration >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > > As today the system script-templates are mainly developed for root > container, it would be nice to add some additional templates to manage child > instances. > I will submit a PR -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4716) Upgrade to Aries Blueprint Core 1.7.0 and Aries Blueprint CM 1.0.9
[ https://issues.apache.org/jira/browse/KARAF-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516206#comment-15516206 ] Luca Burgazzoli commented on KARAF-4716: https://github.com/apache/karaf/pull/243 > Upgrade to Aries Blueprint Core 1.7.0 and Aries Blueprint CM 1.0.9 > -- > > Key: KARAF-4716 > URL: https://issues.apache.org/jira/browse/KARAF-4716 > 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-4716) Upgrade to Aries Blueprint Core 1.7.0 and Aries Blueprint CM 1.0.9
[ https://issues.apache.org/jira/browse/KARAF-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516154#comment-15516154 ] Luca Burgazzoli commented on KARAF-4716: 2 PR or 1 PR with 2 commits ? > Upgrade to Aries Blueprint Core 1.7.0 and Aries Blueprint CM 1.0.9 > -- > > Key: KARAF-4716 > URL: https://issues.apache.org/jira/browse/KARAF-4716 > 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] [Comment Edited] (KARAF-4716) Upgrade to Aries Blueprint Core 1.7.0 and Aries Blueprint CM 1.0.9
[ https://issues.apache.org/jira/browse/KARAF-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516103#comment-15516103 ] Luca Burgazzoli edited comment on KARAF-4716 at 9/23/16 10:47 AM: -- [~jbonofre] I've upgraded my fork to those blueprint version for my own tests, I can push a PR if you like. Is there anything else to do beside upgrading the versions on pom.xml ? was (Author: lb): [~jbonofre] I've upgraded master branch to those blueprint version for my own test, I can push a PR if you like. Is there anything else to do beside upgrading the versions on pom.xml ? > Upgrade to Aries Blueprint Core 1.7.0 and Aries Blueprint CM 1.0.9 > -- > > Key: KARAF-4716 > URL: https://issues.apache.org/jira/browse/KARAF-4716 > 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-4716) Upgrade to Aries Blueprint Core 1.7.0 and Aries Blueprint CM 1.0.9
[ https://issues.apache.org/jira/browse/KARAF-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516103#comment-15516103 ] Luca Burgazzoli commented on KARAF-4716: [~jbonofre] I've upgraded master branch to those blueprint version for my own test, I can push a PR if you like. Is there anything else to do beside upgrading the versions on pom.xml ? > Upgrade to Aries Blueprint Core 1.7.0 and Aries Blueprint CM 1.0.9 > -- > > Key: KARAF-4716 > URL: https://issues.apache.org/jira/browse/KARAF-4716 > 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] [Updated] (KARAF-4726) Improve os-integration doc
[ https://issues.apache.org/jira/browse/KARAF-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli updated KARAF-4726: --- Assignee: (was: Jean-Baptiste Onofré) > Improve os-integration doc > -- > > Key: KARAF-4726 > URL: https://issues.apache.org/jira/browse/KARAF-4726 > Project: Karaf > Issue Type: Bug > Components: karaf-documentation, karaf-os-integration >Reporter: Luca Burgazzoli >Priority: Minor > > Document bin/contrib usage. > I will provide a PR -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4726) Improve os-integration doc
[ https://issues.apache.org/jira/browse/KARAF-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli updated KARAF-4726: --- Fix Version/s: (was: 4.0.7) (was: 4.1.0) > Improve os-integration doc > -- > > Key: KARAF-4726 > URL: https://issues.apache.org/jira/browse/KARAF-4726 > Project: Karaf > Issue Type: Bug > Components: karaf-documentation, karaf-os-integration >Reporter: Luca Burgazzoli >Priority: Minor > > Document bin/contrib usage. > I will provide a PR -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4726) Improve os-integration doc
Luca Burgazzoli created KARAF-4726: -- Summary: Improve os-integration doc Key: KARAF-4726 URL: https://issues.apache.org/jira/browse/KARAF-4726 Project: Karaf Issue Type: Bug Components: karaf-documentation, karaf-os-integration Reporter: Luca Burgazzoli Assignee: Jean-Baptiste Onofré Priority: Minor Fix For: 4.1.0, 4.0.7 Document bin/contrib usage. I will provide a PR -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4703) system-script: document bin/contrib
Luca Burgazzoli created KARAF-4703: -- Summary: system-script: document bin/contrib Key: KARAF-4703 URL: https://issues.apache.org/jira/browse/KARAF-4703 Project: Karaf Issue Type: Bug Components: karaf-os-integration Reporter: Luca Burgazzoli Priority: Minor Document bin/contrib usage. I will provide a PR -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4672) Make karaf.shutdown.pid.file active by default
Luca Burgazzoli created KARAF-4672: -- Summary: Make karaf.shutdown.pid.file active by default Key: KARAF-4672 URL: https://issues.apache.org/jira/browse/KARAF-4672 Project: Karaf Issue Type: Sub-task Components: karaf-core Reporter: Luca Burgazzoli Priority: Minor Fix For: 4.0.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4666) Have karaf write pid file by default
[
https://issues.apache.org/jira/browse/KARAF-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438785#comment-15438785
]
Luca Burgazzoli commented on KARAF-4666:
+1 for compatibility.
I wanted to avoid having "shutdown" if possible just because it may be
confusing as my main reason to have the pid file written by default if to
improve integration with init systems and it may not the best to say:
{code}
To use the system init scripts, please activate the shutdown pid
{code}
I would say:
- 4.1.x -> rename karaf.shutdown.pid.file to karaf.pid.file + backward
compatibility
- 4.0.x -> make karaf.shutdown.pid.file active by default
Make sense ?
> Have karaf write pid file by default
>
>
> Key: KARAF-4666
> URL: https://issues.apache.org/jira/browse/KARAF-4666
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core
>Reporter: Luca Burgazzoli
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> As today karaf would write the pid file only if karaf.shutdown.pid.file is
> defined but it would be nice to have a pid file always written.
> So I will open a PR with:
> - karaf.shutdown.pid.file renamed to karaf.pid.file
> - set default value to ${karaf.base}/karaf.pid
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4667) system-script : add templates to manage child instances
Luca Burgazzoli created KARAF-4667: -- Summary: system-script : add templates to manage child instances Key: KARAF-4667 URL: https://issues.apache.org/jira/browse/KARAF-4667 Project: Karaf Issue Type: Improvement Components: karaf-os-integration Reporter: Luca Burgazzoli Priority: Minor As today the system script-templates are mainly developed for root container, it would be nice to add some additional templates to manage child instances. I will submit a PR -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4666) Have karaf write pid file by default
[
https://issues.apache.org/jira/browse/KARAF-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437240#comment-15437240
]
Luca Burgazzoli commented on KARAF-4666:
At the moment there's no default file name nor location, isn't KARAF-4260
about the pid file generated by the wrapper ?
> Have karaf write pid file by default
>
>
> Key: KARAF-4666
> URL: https://issues.apache.org/jira/browse/KARAF-4666
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core
>Reporter: Luca Burgazzoli
>Priority: Minor
>
> As today karaf would write the pid file only if karaf.shutdown.pid.file is
> defined but it would be nice to have a pid file always written.
> So I will open a PR with:
> - karaf.shutdown.pid.file renamed to karaf.pid.file
> - set default value to ${karaf.base}/karaf.pid
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4666) Have karaf write pid file by default
[
https://issues.apache.org/jira/browse/KARAF-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Burgazzoli updated KARAF-4666:
---
Description:
As today karaf would write the pid file only if karaf.shutdown.pid.file is
defined but it would be nice to have a pid file always written.
So I will open a PR with:
- karaf.shutdown.pid.file renamed to karaf.pid.file
- set default value to ${karaf.base}/karaf.pid
was:
As today karaf would write the pid file only if karaf.shutdown.pid.file is
defined but it would be nice to have a pid file always written.
So I will open a PR with:
- karaf.shutdown.pid.file renamed to karaf.pid.file
- set default value to ${karaf.base}/karaf.pid
> Have karaf write pid file by default
>
>
> Key: KARAF-4666
> URL: https://issues.apache.org/jira/browse/KARAF-4666
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core
>Reporter: Luca Burgazzoli
>Priority: Minor
>
> As today karaf would write the pid file only if karaf.shutdown.pid.file is
> defined but it would be nice to have a pid file always written.
> So I will open a PR with:
> - karaf.shutdown.pid.file renamed to karaf.pid.file
> - set default value to ${karaf.base}/karaf.pid
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4666) Have karaf write pid file by default
Luca Burgazzoli created KARAF-4666:
--
Summary: Have karaf write pid file by default
Key: KARAF-4666
URL: https://issues.apache.org/jira/browse/KARAF-4666
Project: Karaf
Issue Type: Improvement
Components: karaf-core
Reporter: Luca Burgazzoli
Priority: Minor
As today karaf would write the pid file only if karaf.shutdown.pid.file is
defined but it would be nice to have a pid file always written.
So I will open a PR with:
- karaf.shutdown.pid.file renamed to karaf.pid.file
- set default value to ${karaf.base}/karaf.pid
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4649) AssemblyMojo : blacklistPolicy set to null if not defined in pom
Luca Burgazzoli created KARAF-4649: -- Summary: AssemblyMojo : blacklistPolicy set to null if not defined in pom Key: KARAF-4649 URL: https://issues.apache.org/jira/browse/KARAF-4649 Project: Karaf Issue Type: Bug Components: karaf-tooling Reporter: Luca Burgazzoli In AssemblyMojo the blacklistPolicy does not have a default so when the Mojo sets the policy the assembly Builder should use, it is not explicit configured in the pom, it sets it to null overriding the default value defined by Builder. The effect is that if you do not set the policy in pom, the blacklisted bundles are still listed i.e. in startup.properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (KARAF-4640) Support startLevel in startup bundle/features for kustom karaf distribution
[
https://issues.apache.org/jira/browse/KARAF-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Burgazzoli closed KARAF-4640.
--
Resolution: Not A Bug
It is already supported by bundle attributes:
{code:xml}
mvn:my/bundle-1/version;start-level=70
mvn:my/bundle-2/version;start-level=80
{code}
> Support startLevel in startup bundle/features for kustom karaf distribution
> ---
>
> Key: KARAF-4640
> URL: https://issues.apache.org/jira/browse/KARAF-4640
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-tooling
>Reporter: Luca Burgazzoli
>
> When used to generate a custom distribution, the karaf-maven-plugin place all
> the bundles configured in startupBundles section at the same start level
> which could cause issues if the startup order matters (i.e. a blueprint
> extension is required) so it would be nice if the startup level could be
> configured directly from the plugin to avoid writing a custom feature,
> something like:
> {code:xml}
>
>
>
> mvn:my/bundle-1/version
> 60
>
>
> mvn:my/bundle-2/version
> 80
>
>
>
> {code}
> Or:
> {code:xml}
>
>
> mvn:my/bundle-1/version@60
> mvn:my/bundle-2/version@80
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4640) Support startLevel in startup bundle/features for kustom karaf distribution
[
https://issues.apache.org/jira/browse/KARAF-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Burgazzoli updated KARAF-4640:
---
Description:
When used to generate a custom distribution, the karaf-maven-plugin place all
the bundles configured in startupBundles section at the same start level which
could cause issues if the startup order matters (i.e. a blueprint extension is
required) so it would be nice if the startup level could be configured directly
from the plugin to avoid writing a custom feature, something like:
{code:xml}
mvn:my/bundle-1/version
60
mvn:my/bundle-2/version
80
{code}
Or:
{code:xml}
mvn:my/bundle-1/version@60
mvn:my/bundle-2/version@80
{code}
was:
When used to generate a custom distribution, the karaf-maven-plugin place all
the bundles configured in startupBundles section at the same start level which
could cause issues if the startup order matters (i.e. a blueprint extension is
required) so it would be nice if the startup level could be configured directly
from the plugin to avoid writing a custom feature, something like:
{code:xml}
mvn:my/bundle-1/version
mvn:my/bundle-2/version
{code}
> Support startLevel in startup bundle/features for kustom karaf distribution
> ---
>
> Key: KARAF-4640
> URL: https://issues.apache.org/jira/browse/KARAF-4640
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-tooling
>Reporter: Luca Burgazzoli
>
> When used to generate a custom distribution, the karaf-maven-plugin place all
> the bundles configured in startupBundles section at the same start level
> which could cause issues if the startup order matters (i.e. a blueprint
> extension is required) so it would be nice if the startup level could be
> configured directly from the plugin to avoid writing a custom feature,
> something like:
> {code:xml}
>
>
>
> mvn:my/bundle-1/version
> 60
>
>
> mvn:my/bundle-2/version
> 80
>
>
>
> {code}
> Or:
> {code:xml}
>
>
> mvn:my/bundle-1/version@60
> mvn:my/bundle-2/version@80
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4640) Support startLevel in startup bundle/features for kustom karaf distribution
Luca Burgazzoli created KARAF-4640:
--
Summary: Support startLevel in startup bundle/features for kustom
karaf distribution
Key: KARAF-4640
URL: https://issues.apache.org/jira/browse/KARAF-4640
Project: Karaf
Issue Type: Improvement
Components: karaf-tooling
Reporter: Luca Burgazzoli
When used to generate a custom distribution, the karaf-maven-plugin place all
the bundles configured in startupBundles section at the same start level which
could cause issues if the startup order matters (i.e. a blueprint extension is
required) so it would be nice if the startup level could be configured directly
from the plugin to avoid writing a custom feature, something like:
{code:xml}
mvn:my/bundle-1/version
mvn:my/bundle-2/version
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4569) OSGi framework is not shut-down gracefully on SOGTERM
[ https://issues.apache.org/jira/browse/KARAF-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15328017#comment-15328017 ] Luca Burgazzoli commented on KARAF-4569: I opened a [PR|https://github.com/apache/karaf/pull/198] which install a signal handler rather that using a shutdown hook as the later does not seem to work, I need to digg into this a little bit mode but it could be because of the ordering i.e. the framework may have installed its own hook > OSGi framework is not shut-down gracefully on SOGTERM > - > > Key: KARAF-4569 > URL: https://issues.apache.org/jira/browse/KARAF-4569 > Project: Karaf > Issue Type: Bug >Reporter: Luca Burgazzoli > > When Karaf receive a signal like SIGTERM, the OSGi framework is not > terminated properly but the JVM simply exits. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4569) OSGi framework is not shut-down gracefully on SIGTERM
[ https://issues.apache.org/jira/browse/KARAF-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli updated KARAF-4569: --- Summary: OSGi framework is not shut-down gracefully on SIGTERM (was: OSGi framework is not shut-down gracefully on SOGTERM) > OSGi framework is not shut-down gracefully on SIGTERM > - > > Key: KARAF-4569 > URL: https://issues.apache.org/jira/browse/KARAF-4569 > Project: Karaf > Issue Type: Bug >Reporter: Luca Burgazzoli > > When Karaf receive a signal like SIGTERM, the OSGi framework is not > terminated properly but the JVM simply exits. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4569) OSGi framework is not shut-down gracefully on SOGTERM
Luca Burgazzoli created KARAF-4569: -- Summary: OSGi framework is not shut-down gracefully on SOGTERM Key: KARAF-4569 URL: https://issues.apache.org/jira/browse/KARAF-4569 Project: Karaf Issue Type: Bug Reporter: Luca Burgazzoli When Karaf receive a signal like SIGTERM, the OSGi framework is not terminated properly but the JVM simply exits. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (KARAF-4562) ServiceCall EIP : Support additional attributes in ServiceCallServer
[ https://issues.apache.org/jira/browse/KARAF-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli closed KARAF-4562. -- Resolution: Invalid Wrong project selected, sorry > ServiceCall EIP : Support additional attributes in ServiceCallServer > > > Key: KARAF-4562 > URL: https://issues.apache.org/jira/browse/KARAF-4562 > Project: Karaf > Issue Type: Improvement >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > > As today is it not possible to implement generic enhanced load balancer > strategy as ServiceCallServer is only supposed to provide an ip address and a > port so it would be nice if ServiceCallServer would be enhanced to support > stuffs like attributes, tags and priorities. > By enrich ServiceCallServer we could: > - have more options on final processor > - have a way to filter servers by tags (i.e. servers belonging to a zone) > - have a way to choose a server based on priority -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4562) ServiceCall EIP : Support additional attributes in ServiceCallServer
Luca Burgazzoli created KARAF-4562: -- Summary: ServiceCall EIP : Support additional attributes in ServiceCallServer Key: KARAF-4562 URL: https://issues.apache.org/jira/browse/KARAF-4562 Project: Karaf Issue Type: Improvement Reporter: Luca Burgazzoli Assignee: Luca Burgazzoli Priority: Minor As today is it not possible to implement generic enhanced load balancer strategy as ServiceCallServer is only supposed to provide an ip address and a port so it would be nice if ServiceCallServer would be enhanced to support stuffs like attributes, tags and priorities. By enrich ServiceCallServer we could: - have more options on final processor - have a way to filter servers by tags (i.e. servers belonging to a zone) - have a way to choose a server based on priority -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4551) wrapper:install on solaris lacks instructions to symlink scripts
[ https://issues.apache.org/jira/browse/KARAF-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313833#comment-15313833 ] Luca Burgazzoli commented on KARAF-4551: I will provide a PR > wrapper:install on solaris lacks instructions to symlink scripts > > > Key: KARAF-4551 > URL: https://issues.apache.org/jira/browse/KARAF-4551 > Project: Karaf > Issue Type: Bug > Components: karaf-os-integration >Reporter: Luca Burgazzoli >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4551) wrapper:install on solaris lacks instructions to symlink scripts
Luca Burgazzoli created KARAF-4551: -- Summary: wrapper:install on solaris lacks instructions to symlink scripts Key: KARAF-4551 URL: https://issues.apache.org/jira/browse/KARAF-4551 Project: Karaf Issue Type: Bug Components: karaf-os-integration Reporter: Luca Burgazzoli Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4526) System scripts : Solaris SMS sevice not started if path contains spaces
[ https://issues.apache.org/jira/browse/KARAF-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282615#comment-15282615 ] Luca Burgazzoli commented on KARAF-4526: I will provide a PR > System scripts : Solaris SMS sevice not started if path contains spaces > --- > > Key: KARAF-4526 > URL: https://issues.apache.org/jira/browse/KARAF-4526 > Project: Karaf > Issue Type: Improvement > Components: karaf-os-integration >Reporter: Luca Burgazzoli >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4526) System scripts : Solaris SMS sevice not started if path contains spaces
Luca Burgazzoli created KARAF-4526: -- Summary: System scripts : Solaris SMS sevice not started if path contains spaces Key: KARAF-4526 URL: https://issues.apache.org/jira/browse/KARAF-4526 Project: Karaf Issue Type: Improvement Components: karaf-os-integration Reporter: Luca Burgazzoli Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4519) If an action does not have a @Command annotation, fallback to calling a description() method via reflection to get an Action's description
[
https://issues.apache.org/jira/browse/KARAF-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Burgazzoli updated KARAF-4519:
---
Summary: If an action does not have a @Command annotation, fallback to
calling a description() method via reflection to get an Action's description
(was: Add additional steps to retrieve ActiveMQ command descriptions)
> If an action does not have a @Command annotation, fallback to calling a
> description() method via reflection to get an Action's description
> --
>
> Key: KARAF-4519
> URL: https://issues.apache.org/jira/browse/KARAF-4519
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.5
>Reporter: Luca Burgazzoli
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.6
>
>
> Commands descriptions for ActiveMQ 5.x can't be retrieved by Karaf when using
> help command as the services exported by ActiveMQ do not provide such
> information so Karaf fallback to command name as description which is not
> very useful.
> An enhancement has been added to ActiveMQ:
> https://github.com/apache/activemq/commit/7fd5fa9253deb3a2815cb375b85731a959ad3845
> CommandTracker should be enhanced to try to invoke description method if
> standard methods are not available (i.e. Command annotation not present).
> I will provide a PR
> before:
> {code}
> activemq:browse browse
> activemq:bstatbstat
> activemq:consumer consumer
> activemq:dstatdstat
> activemq:list list
> activemq:producer producer
> activemq:purgepurge
> activemq:queryquery
> {code}
> after:
> {code}
> activemq:browse Display selected messages in a specified
> destination.
> activemq:bstatPerforms a predefined query that displays
> useful statistics regarding the specified broker
> activemq:consumer Receives messages from the broker
> activemq:dstatPerforms a predefined query that displays
> useful tabular statistics regarding the specified destination type
> activemq:list Lists all available brokers in the
> specified JMX context
> activemq:producer Sends messages to the broker
> activemq:purgeDelete selected destination's messages that
> matches the message selector
> activemq:queryDisplay selected broker component's
> attributes and statistics.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4519) Add additional steps to retrieve ActiveMQ command descriptions
Luca Burgazzoli created KARAF-4519:
--
Summary: Add additional steps to retrieve ActiveMQ command
descriptions
Key: KARAF-4519
URL: https://issues.apache.org/jira/browse/KARAF-4519
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.5
Reporter: Luca Burgazzoli
Priority: Minor
Commands descriptions for ActiveMQ 5.x can't be retrieved by Karaf when using
help command as the services exported by ActiveMQ do not provide such
information so Karaf fallback to command name as description which is not very
useful.
An enhancement has been added to ActiveMQ:
https://github.com/apache/activemq/commit/7fd5fa9253deb3a2815cb375b85731a959ad3845
CommandTracker should be enhanced to try to invoke description method if
standard methods are not available (i.e. Command annotation not present).
I will provide a PR
before:
{code}
activemq:browse browse
activemq:bstatbstat
activemq:consumer consumer
activemq:dstatdstat
activemq:list list
activemq:producer producer
activemq:purgepurge
activemq:queryquery
{code}
after:
{code}
activemq:browse Display selected messages in a specified
destination.
activemq:bstatPerforms a predefined query that displays
useful statistics regarding the specified broker
activemq:consumer Receives messages from the broker
activemq:dstatPerforms a predefined query that displays
useful tabular statistics regarding the specified destination type
activemq:list Lists all available brokers in the specified
JMX context
activemq:producer Sends messages to the broker
activemq:purgeDelete selected destination's messages that
matches the message selector
activemq:queryDisplay selected broker component's
attributes and statistics.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4503) Features for spring-security 4.x
Luca Burgazzoli created KARAF-4503: -- Summary: Features for spring-security 4.x Key: KARAF-4503 URL: https://issues.apache.org/jira/browse/KARAF-4503 Project: Karaf Issue Type: Sub-task Components: karaf-feature Affects Versions: 4.0.4 Reporter: Luca Burgazzoli -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4413) Can't start karaf on solaris 10
[ https://issues.apache.org/jira/browse/KARAF-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli updated KARAF-4413: --- Issue Type: Bug (was: Improvement) > Can't start karaf on solaris 10 > --- > > Key: KARAF-4413 > URL: https://issues.apache.org/jira/browse/KARAF-4413 > Project: Karaf > Issue Type: Bug > Components: karaf-os-integration >Reporter: Luca Burgazzoli > > ./karaf: syntax error at line 331: `ROOT_INSTANCE_PID=$' unexpected -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4413) Can't start karaf on solaris 10
Luca Burgazzoli created KARAF-4413: -- Summary: Can't start karaf on solaris 10 Key: KARAF-4413 URL: https://issues.apache.org/jira/browse/KARAF-4413 Project: Karaf Issue Type: Improvement Components: karaf-os-integration Reporter: Luca Burgazzoli ./karaf: syntax error at line 331: `ROOT_INSTANCE_PID=$' unexpected -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4412) system scripts : first line in solaris smf template should not be empty
Luca Burgazzoli created KARAF-4412: -- Summary: system scripts : first line in solaris smf template should not be empty Key: KARAF-4412 URL: https://issues.apache.org/jira/browse/KARAF-4412 Project: Karaf Issue Type: Improvement Components: karaf-os-integration Reporter: Luca Burgazzoli Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KARAF-4371) karaf shell scripts use "local" which is not a posix compliant
[
https://issues.apache.org/jira/browse/KARAF-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15172090#comment-15172090
]
Luca Burgazzoli edited comment on KARAF-4371 at 2/29/16 4:31 PM:
-
I'll provide a PR
was (Author: lb):
I wiull provide a PR
> karaf shell scripts use "local" which is not a posix compliant
> --
>
> Key: KARAF-4371
> URL: https://issues.apache.org/jira/browse/KARAF-4371
> Project: Karaf
> Issue Type: Bug
> Components: karaf-os-integration
>Reporter: Luca Burgazzoli
>Priority: Minor
>
> karaf shell scripts use "local" in function pathCanonical which is not posix
> compliant:
> {code}
> pathCanonical() {
> local dst="${1}"
> while [ -h "${dst}" ] ; do
> ls=`ls -ld "${dst}"`
> link=`expr "$ls" : '.*-> \(.*\)$'`
> if expr "$link" : '/.*' > /dev/null; then
> dst="$link"
> else
> dst="`dirname "${dst}"`/$link"
> fi
> done
> local bas=`basename "${dst}"`
> local dir=`dirname "${dst}"`
> if [ "$bas" != "$dir" ]; then
> dst="`pathCanonical "$dir"`/$bas"
> fi
> echo "${dst}" | sed -e 's#//#/#g' -e 's#/./#/#g' -e 's#/[^/]*/../#/#g'
> }
> {code}
> As a consequence the script fails on non-bash shells:
> {code}
> bin/karaf[169]: local: not found [No such file or directory]
> bin/karaf[179]: local: not found [No such file or directory]
> bin/karaf[180]: local: not found [No such file or directory]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4371) karaf shell scripts use "local" which is not a posix compliant
Luca Burgazzoli created KARAF-4371:
--
Summary: karaf shell scripts use "local" which is not a posix
compliant
Key: KARAF-4371
URL: https://issues.apache.org/jira/browse/KARAF-4371
Project: Karaf
Issue Type: Bug
Components: karaf-os-integration
Reporter: Luca Burgazzoli
Priority: Minor
karaf shell scripts use "local" in function pathCanonical which is not posix
compliant:
{code}
pathCanonical() {
local dst="${1}"
while [ -h "${dst}" ] ; do
ls=`ls -ld "${dst}"`
link=`expr "$ls" : '.*-> \(.*\)$'`
if expr "$link" : '/.*' > /dev/null; then
dst="$link"
else
dst="`dirname "${dst}"`/$link"
fi
done
local bas=`basename "${dst}"`
local dir=`dirname "${dst}"`
if [ "$bas" != "$dir" ]; then
dst="`pathCanonical "$dir"`/$bas"
fi
echo "${dst}" | sed -e 's#//#/#g' -e 's#/./#/#g' -e 's#/[^/]*/../#/#g'
}
{code}
As a consequence the script fails on non-bash shells:
{code}
bin/karaf[169]: local: not found [No such file or directory]
bin/karaf[179]: local: not found [No such file or directory]
bin/karaf[180]: local: not found [No such file or directory]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4371) karaf shell scripts use "local" which is not a posix compliant
[
https://issues.apache.org/jira/browse/KARAF-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15172090#comment-15172090
]
Luca Burgazzoli commented on KARAF-4371:
I wiull provide a PR
> karaf shell scripts use "local" which is not a posix compliant
> --
>
> Key: KARAF-4371
> URL: https://issues.apache.org/jira/browse/KARAF-4371
> Project: Karaf
> Issue Type: Bug
> Components: karaf-os-integration
>Reporter: Luca Burgazzoli
>Priority: Minor
>
> karaf shell scripts use "local" in function pathCanonical which is not posix
> compliant:
> {code}
> pathCanonical() {
> local dst="${1}"
> while [ -h "${dst}" ] ; do
> ls=`ls -ld "${dst}"`
> link=`expr "$ls" : '.*-> \(.*\)$'`
> if expr "$link" : '/.*' > /dev/null; then
> dst="$link"
> else
> dst="`dirname "${dst}"`/$link"
> fi
> done
> local bas=`basename "${dst}"`
> local dir=`dirname "${dst}"`
> if [ "$bas" != "$dir" ]; then
> dst="`pathCanonical "$dir"`/$bas"
> fi
> echo "${dst}" | sed -e 's#//#/#g' -e 's#/./#/#g' -e 's#/[^/]*/../#/#g'
> }
> {code}
> As a consequence the script fails on non-bash shells:
> {code}
> bin/karaf[169]: local: not found [No such file or directory]
> bin/karaf[179]: local: not found [No such file or directory]
> bin/karaf[180]: local: not found [No such file or directory]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4366) system scripts : fallback to generic init script for unknown os
Luca Burgazzoli created KARAF-4366: -- Summary: system scripts : fallback to generic init script for unknown os Key: KARAF-4366 URL: https://issues.apache.org/jira/browse/KARAF-4366 Project: Karaf Issue Type: Improvement Components: karaf-os-integration Reporter: Luca Burgazzoli Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4340) System scripts: improve system scripts templates
Luca Burgazzoli created KARAF-4340: -- Summary: System scripts: improve system scripts templates Key: KARAF-4340 URL: https://issues.apache.org/jira/browse/KARAF-4340 Project: Karaf Issue Type: Improvement Components: karaf-os-integration Reporter: Luca Burgazzoli Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (KARAF-4276) System scripts: provide MacOSX launchd template
[ https://issues.apache.org/jira/browse/KARAF-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli closed KARAF-4276. -- Resolution: Won't Fix > System scripts: provide MacOSX launchd template > --- > > Key: KARAF-4276 > URL: https://issues.apache.org/jira/browse/KARAF-4276 > Project: Karaf > Issue Type: New Feature >Reporter: Luca Burgazzoli >Assignee: Freeman Fang >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (KARAF-4294) System scripts: Improove support for Solaris 10 init scripts
[ https://issues.apache.org/jira/browse/KARAF-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli reopened KARAF-4294: Reopened as Solaris 10 init script needs some additional work > System scripts: Improove support for Solaris 10 init scripts > > > Key: KARAF-4294 > URL: https://issues.apache.org/jira/browse/KARAF-4294 > Project: Karaf > Issue Type: Bug > Components: karaf-os-integration >Reporter: Luca Burgazzoli >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4294) System scripts: Improove support for Solaris 10 init scripts
Luca Burgazzoli created KARAF-4294: -- Summary: System scripts: Improove support for Solaris 10 init scripts Key: KARAF-4294 URL: https://issues.apache.org/jira/browse/KARAF-4294 Project: Karaf Issue Type: Bug Components: karaf-os-integration Reporter: Luca Burgazzoli Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4281) System scripts: provide Systemd templates to manage Karaf child instances
Luca Burgazzoli created KARAF-4281:
--
Summary: System scripts: provide Systemd templates to manage Karaf
child instances
Key: KARAF-4281
URL: https://issues.apache.org/jira/browse/KARAF-4281
Project: Karaf
Issue Type: New Feature
Components: karaf-os-integration
Reporter: Luca Burgazzoli
Priority: Minor
Systemd's has as a sort of template-engine for unit files which are defined in
the form of template-name@.service, i.e. for karaf I've created one named
karaf@.service with content like:
{code}
[Unit]
Description=Karaf - %i
After=syslog.target network.target
[Service]
EnvironmentFile=-/etc/karaf/karaf.conf
Environment=JAVA_HOME=/opt/java/1.8.0
Environment=KARAF_HOME=/opt/apache/karaf-4
Environment=KARAF_BASE=/opt/apache/karaf-4/instances/%i
ExecStart=/opt/apache/karaf-4/bin/karaf daemon
ExecStop=/opt/apache/karaf-4/bin/karaf stop
LimitNOFILE=102642
[Install]
WantedBy=multi-user.target
{code}
With such configuration, you do not need to create a systemd unit file for each
child instance but you can leverage karaf@.service, i.e:
{code}
systemctl start karaf@instance-1
{code}
A service created in such way can also be configured to auto-start at boot like
any other Systemd unit:
{code}
[lb@home]# systemctl enable karaf@instance-1
Created symlink from /etc/systemd/system/multi-user.target.wants
/karaf@instance-1.service to /etc/systemd/system/karaf@.service.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4277) System scripts: add option to configure the executable to use to start/stop karaf
[ https://issues.apache.org/jira/browse/KARAF-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli updated KARAF-4277: --- Summary: System scripts: add option to configure the executable to use to start/stop karaf (was: System scripts : add option to configure the executable to use to start/stop karaf) > System scripts: add option to configure the executable to use to start/stop > karaf > - > > Key: KARAF-4277 > URL: https://issues.apache.org/jira/browse/KARAF-4277 > Project: Karaf > Issue Type: New Feature >Reporter: Luca Burgazzoli >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4276) System scripts: provide MacOSX launchd template
Luca Burgazzoli created KARAF-4276: -- Summary: System scripts: provide MacOSX launchd template Key: KARAF-4276 URL: https://issues.apache.org/jira/browse/KARAF-4276 Project: Karaf Issue Type: New Feature Reporter: Luca Burgazzoli Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4277) System scripts : add option to configure the executable to use to start/stop
Luca Burgazzoli created KARAF-4277: -- Summary: System scripts : add option to configure the executable to use to start/stop Key: KARAF-4277 URL: https://issues.apache.org/jira/browse/KARAF-4277 Project: Karaf Issue Type: New Feature Reporter: Luca Burgazzoli Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4277) System scripts : add option to configure the executable to use to start/stop karaf
[ https://issues.apache.org/jira/browse/KARAF-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli updated KARAF-4277: --- Summary: System scripts : add option to configure the executable to use to start/stop karaf (was: System scripts : add option to configure the executable to use to start/stop) > System scripts : add option to configure the executable to use to start/stop > karaf > -- > > Key: KARAF-4277 > URL: https://issues.apache.org/jira/browse/KARAF-4277 > Project: Karaf > Issue Type: New Feature >Reporter: Luca Burgazzoli >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4157) Provide system script to start Karaf without service wrapper
[
https://issues.apache.org/jira/browse/KARAF-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15097999#comment-15097999
]
Luca Burgazzoli commented on KARAF-4157:
Implemented via
[5ee6a6964267f129a9bd1cfbde1e67f650121218|https://github.com/lburgazzoli/apache-karaf/commit/5ee6a6964267f129a9bd1cfbde1e67f650121218]
{code}
$ tar tvf ./assemblies/apache-karaf/target/apache-karaf-4.0.4-SNAPSHOT.tar.gz |
grep contrib
drwxr-xr-x 0/0 0 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/
-rwxr-xr-x 0/0 542 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/karaf-service-template.systemd
-rwxr-xr-x 0/02587 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/karaf-service-template.solaris-smf
-rwxr-xr-x 0/01541 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/karaf-service-win.xml
-rwxr-xr-x 0/02969 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/karaf-service-template.init
-rwxr-xr-x 0/03394 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/karaf-service-template.init-redhat
-rwxr-xr-x 0/0 360 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/karaf-service-template.conf
-rwxr-xr-x 0/05515 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/karaf-service-template.init-debian
-rwxr-xr-x 0/0 59392 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/karaf-service-win.exe
-rwxr-xr-x 0/05599 2016-01-14 11:41
apache-karaf-4.0.4-SNAPSHOT/bin/contrib/karaf-service.sh
{code}
> Provide system script to start Karaf without service wrapper
>
>
> Key: KARAF-4157
> URL: https://issues.apache.org/jira/browse/KARAF-4157
> Project: Karaf
> Issue Type: New Feature
>Reporter: Luca Burgazzoli
>Assignee: Freeman Fang
>Priority: Minor
>
> For some user/scenario it may be needed to start karaf as a service without
> the service wrapper i.e. on architectures not supported by JSW
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4157) Provide system script to start Karaf without service wrapper
[ https://issues.apache.org/jira/browse/KARAF-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098075#comment-15098075 ] Luca Burgazzoli commented on KARAF-4157: Now squashed in a single commit > Provide system script to start Karaf without service wrapper > > > Key: KARAF-4157 > URL: https://issues.apache.org/jira/browse/KARAF-4157 > Project: Karaf > Issue Type: New Feature >Reporter: Luca Burgazzoli >Assignee: Freeman Fang >Priority: Minor > > For some user/scenario it may be needed to start karaf as a service without > the service wrapper i.e. on architectures not supported by JSW -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4157) Provide system script to start Karaf without service wrapper
[ https://issues.apache.org/jira/browse/KARAF-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15096053#comment-15096053 ] Luca Burgazzoli commented on KARAF-4157: [~jbonofre] [~ffang] 1. what should I do to include them in distribution ? 2. I've removed the hard-coded path which I've replaced with some pseudo variables a user still need to manually expand 3. fixed 4. fixed 5. fixed for redhat/debian init scripts (does not make sense to set it for systemd or smf) > Provide system script to start Karaf without service wrapper > > > Key: KARAF-4157 > URL: https://issues.apache.org/jira/browse/KARAF-4157 > Project: Karaf > Issue Type: New Feature >Reporter: Luca Burgazzoli >Assignee: Freeman Fang >Priority: Minor > > For some user/scenario it may be needed to start karaf as a service without > the service wrapper i.e. on architectures not supported by JSW -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4157) Provide system script to start Karaf without service wrapper
[ https://issues.apache.org/jira/browse/KARAF-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15095783#comment-15095783 ] Luca Burgazzoli commented on KARAF-4157: [~jbonofre] should I fix Freeman's finding ? > Provide system script to start Karaf without service wrapper > > > Key: KARAF-4157 > URL: https://issues.apache.org/jira/browse/KARAF-4157 > Project: Karaf > Issue Type: New Feature >Reporter: Luca Burgazzoli >Assignee: Freeman Fang >Priority: Minor > > For some user/scenario it may be needed to start karaf as a service without > the service wrapper i.e. on architectures not supported by JSW -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4245) Generic discovery service
Luca Burgazzoli created KARAF-4245: -- Summary: Generic discovery service Key: KARAF-4245 URL: https://issues.apache.org/jira/browse/KARAF-4245 Project: Karaf Issue Type: New Feature Components: cellar-cloud Reporter: Luca Burgazzoli I'm wondering if it would make sense to extend current discovery service to make it more generic and shareable among other services that need discovery capabilities. This may be achieved by adding some filtering capability to discoverMembers i.e. Collection discoverMembers(String domain) How domain is used is implementation dependant (labels for kubernetes, path for etcd, etc). Domain used by karaf clustering may be then defined in hazelcast's service configuration file or wherever it make sense. It would also be useful to have additional info about the discovery services like all the kubernetes label or any additional attribute associated with the discovered service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4244) Cellar Etcd nodes discovery
Luca Burgazzoli created KARAF-4244: -- Summary: Cellar Etcd nodes discovery Key: KARAF-4244 URL: https://issues.apache.org/jira/browse/KARAF-4244 Project: Karaf Issue Type: New Feature Components: cellar-cloud Reporter: Luca Burgazzoli Priority: Minor Cellar currently provides nodes discovery via Kubernetes, it would be nice to support also other types like CoreOS's Etcd. I will provide a PR -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4236) Cellar DNS nodes discovery
Luca Burgazzoli created KARAF-4236: -- Summary: Cellar DNS nodes discovery Key: KARAF-4236 URL: https://issues.apache.org/jira/browse/KARAF-4236 Project: Karaf Issue Type: New Feature Components: cellar-core Reporter: Luca Burgazzoli Priority: Minor Cellar currently provides nodes discovery via Kubernetes, it would be nice to support also other types like DNS. I will provide a PR -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4232) Kara Cellar discovery Vs Hazelcast discovery SPI
Luca Burgazzoli created KARAF-4232: -- Summary: Kara Cellar discovery Vs Hazelcast discovery SPI Key: KARAF-4232 URL: https://issues.apache.org/jira/browse/KARAF-4232 Project: Karaf Issue Type: Question Components: cellar-core, cellar-hazelcast Reporter: Luca Burgazzoli Priority: Minor Karaf Cellar has some built-in discovery mechanism that are great but Hazelcast 3.6.0 is going to provide discovery SPIs and some implementations are already available: - https://hazelcast.atlassian.net/wiki/display/COM/HEP+2+-+Hazelcast+Discovery+SPI - http://hazelcast.org/plugins/ - https://github.com/search?p=1=hazelcast-discovery=Repositories=%E2%9C%93 Would Karaf Cellar eventually drop custom discovery plugin in favor native Hazelcast's ones ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4157) Provide system script to start Karaf without service wrapper
[ https://issues.apache.org/jira/browse/KARAF-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066344#comment-15066344 ] Luca Burgazzoli commented on KARAF-4157: PR https://github.com/apache/karaf/pull/113 > Provide system script to start Karaf without service wrapper > > > Key: KARAF-4157 > URL: https://issues.apache.org/jira/browse/KARAF-4157 > Project: Karaf > Issue Type: New Feature >Reporter: Luca Burgazzoli >Priority: Minor > > For some user/scenario it may be needed to start karaf as a service without > the service wrapper i.e. on architectures not supported by JSW -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4188) Add support for Systemd's watchdog
Luca Burgazzoli created KARAF-4188: -- Summary: Add support for Systemd's watchdog Key: KARAF-4188 URL: https://issues.apache.org/jira/browse/KARAF-4188 Project: Karaf Issue Type: New Feature Reporter: Luca Burgazzoli Priority: Minor Systemd has a watchdog feature that could help detecting freeze jvm, integrating it in karaf would be possible via jna/jnr -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4157) Provide system script to start Karaf without service wrapper
Luca Burgazzoli created KARAF-4157: -- Summary: Provide system script to start Karaf without service wrapper Key: KARAF-4157 URL: https://issues.apache.org/jira/browse/KARAF-4157 Project: Karaf Issue Type: New Feature Reporter: Luca Burgazzoli Priority: Minor For some user/scenario it may be needed to start karaf as a service without the service wrapper i.e. on architectures not supported by JSW -- This message was sent by Atlassian JIRA (v6.3.4#6332)
