[jira] [Created] (KARAF-4326) karaf client not executing logout when processing command file
Massimo Pichini created KARAF-4326:
--
Summary: karaf client not executing logout when processing command
file
Key: KARAF-4326
URL: https://issues.apache.org/jira/browse/KARAF-4326
Project: Karaf
Issue Type: Bug
Affects Versions: 3.0.5
Environment: Apache ServiceMix 6.0.0 running on RedHat ES 6.2
Reporter: Massimo Pichini
I'm using the karaf client to perform bundle install/uninstall in my Apache
Servicemix instance (I'm using release 6.0.0 on RHES 6.2). This is part of the
software install/upgrade process executed via a bash script.
I pass a command file to the client with last command being a {{shell:logout}},
in order to exit from the shell once all commands have been processed. The
commands are actually processed, but there's no way for the logout command to
be processed: the console remains opened in a strange state, since the input
commands are not processed (that is even entering {{shell:logout}} nothing
happen).
The only way to exit is by entering Ctrl-C. I run the Apache Karaf client with
the command:
{{./client -u smx -f }}
On other way, if a execute the same command file ({{shell:source }})
from within the karaf console (started with {{./client -u smx}} without
additional arguments) all commands are processed, including the last
{{shell:logout}} command that causes the logoff of the karaf console.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3698) Add decanter cassandra appender
[ https://issues.apache.org/jira/browse/KARAF-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139880#comment-15139880 ] ASF subversion and git services commented on KARAF-3698: Commit 82687b5782c3e92c63033197a6a39976178d763c in karaf-decanter's branch refs/heads/master from [~achim_nierbeck] [ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=82687b5 ] [KARAF-3698] - Add decanter cassandra appender > Add decanter cassandra appender > --- > > Key: KARAF-3698 > URL: https://issues.apache.org/jira/browse/KARAF-3698 > Project: Karaf > Issue Type: New Feature > Components: decanter >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-3698) Add decanter cassandra appender
[ https://issues.apache.org/jira/browse/KARAF-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-3698. --- Resolution: Fixed I'm not quite satisfied with the current solution. It's adequate to store the data, but actually the json part should be "disassembled" to columns. Field -> Column > Add decanter cassandra appender > --- > > Key: KARAF-3698 > URL: https://issues.apache.org/jira/browse/KARAF-3698 > Project: Karaf > Issue Type: New Feature > Components: decanter >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-3698) Add decanter cassandra appender
[ https://issues.apache.org/jira/browse/KARAF-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck reassigned KARAF-3698: - Assignee: Achim Nierbeck (was: Jean-Baptiste Onofré) > Add decanter cassandra appender > --- > > Key: KARAF-3698 > URL: https://issues.apache.org/jira/browse/KARAF-3698 > Project: Karaf > Issue Type: New Feature > Components: decanter >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4325) Duplicate scr:list command
J. Brébec created KARAF-4325: Summary: Duplicate scr:list command Key: KARAF-4325 URL: https://issues.apache.org/jira/browse/KARAF-4325 Project: Karaf Issue Type: Bug Components: karaf-scr Affects Versions: 4.0.4 Reporter: J. Brébec Priority: Minor The command 'scr:list' is exported by the felix implementation, and by the bundle org.apache.karaf.scr.commands As a consequence, this command is randomly handled by one of these implementations (the latest bundle started) and the behavior is not coherent between restarts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4324) Shell commands and optional @Reference
J. Brébec created KARAF-4324: Summary: Shell commands and optional @Reference Key: KARAF-4324 URL: https://issues.apache.org/jira/browse/KARAF-4324 Project: Karaf Issue Type: Bug Components: karaf-shell Affects Versions: 4.0.4 Reporter: J. Brébec Priority: Minor The annotation @Reference have a optional property, but this property is not used to resolve the dependencies of a command. Moreover, if I define in a bundle two commands, and one of this command can't be deployed because of an optional dependencies, then none of the command of the bundle is not deployed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3798) FeaturesServiceImpl not threadsafe
[
https://issues.apache.org/jira/browse/KARAF-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139349#comment-15139349
]
Fabian Lange commented on KARAF-3798:
-
Also this is probably the cause for the state problem:
{code}
void bootDone() {
synchronized (lock) {
state.bootDone.set(true);
saveState();
}
}
{code}
will save the state while features are still installing
> FeaturesServiceImpl not threadsafe
> --
>
> Key: KARAF-3798
> URL: https://issues.apache.org/jira/browse/KARAF-3798
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.0.0.M3
>Reporter: Fabian Lange
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> This error happens pretty frequently with M3, when there are multiple
> features installed on startup and config files to activate them created.
> {code}
> 2015-06-19 15:55:12,249 | ERROR | 43-3aaf88a7bd8b) | configadmin
> | 3 - org.apache.felix.configadmin - 1.8.4 | Unexpected problem
> delivering configuration event to [org.osgi.service.cm.ConfigurationListener,
> id=30, bundle=9/mvn:org.apache.felix/org.apache.felix.scr/1.8.2]
> java.lang.NullPointerException
> at
> org.apache.felix.scr.impl.config.ConfigurationSupport.configurationEvent(ConfigurationSupport.java:283)[9:org.apache.felix.scr:1.8.2]
> at
> org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.sendEvent(ConfigurationManager.java:2036)[3:org.apache.felix.configadmin:1.8.4]
> at
> org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.run(ConfigurationManager.java:2005)[3:org.apache.felix.configadmin:1.8.4]
> at
> org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:103)[3:org.apache.felix.configadmin:1.8.4]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_40]
> {code}
> As written in latest comment, the root cause seems to be that multiple
> installFeature calls to FeatureService mess up the state of the bundles. In
> my case it left a bundle in a corrupt state, which was noticed when the
> configuration change did not really activate the service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3798) FeaturesServiceImpl not threadsafe
[
https://issues.apache.org/jira/browse/KARAF-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139344#comment-15139344
]
Fabian Lange commented on KARAF-3798:
-
A new stack trace which seems common in 4.0.4 for the same issue:
{code}
java.lang.NullPointerException
at java.io.FileOutputStream.(FileOutputStream.java:203)[:1.8.0_72]
at java.io.FileOutputStream.(FileOutputStream.java:162)[:1.8.0_72]
at
org.apache.karaf.features.internal.osgi.Activator$1.getOutputStream(Activator.java:197)[7:org.apache.karaf.features.core:4.0.4]
at
org.apache.karaf.features.internal.service.StateStorage.save(StateStorage.java:56)[7:org.apache.karaf.features.core:4.0.4]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.saveState(FeaturesServiceImpl.java:297)[7:org.apache.karaf.features.core:4.0.4]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.saveState(FeaturesServiceImpl.java:1154)[7:org.apache.karaf.features.core:4.0.4]
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:764)[7:org.apache.karaf.features.core:4.0.4]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)[7:org.apache.karaf.features.core:4.0.4]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)[7:org.apache.karaf.features.core:4.0.4]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_72]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_72]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_72]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_72]
{code}
What I noticed is that also "BootFinished" is called prematurely.
>From
>org.apache.karaf.features.internal.service.BootFeaturesInstaller.installBootFeatures():
{code}
List> stagedFeatures = parseBootFeatures(features);
for (Set features : stagedFeatures) {
featuresService.installFeatures(features,
EnumSet.of(FeaturesService.Option.NoFailOnFeatureNotFound));
}
featuresService.bootDone();
publishBootFinished();
{code}
because installFeatures is async, bootFinished is invoked as soon as the task
for the thread has been scheduled, but not when the boot is actually done (and
all boot features are in state installed
> FeaturesServiceImpl not threadsafe
> --
>
> Key: KARAF-3798
> URL: https://issues.apache.org/jira/browse/KARAF-3798
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.0.0.M3
>Reporter: Fabian Lange
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> This error happens pretty frequently with M3, when there are multiple
> features installed on startup and config files to activate them created.
> {code}
> 2015-06-19 15:55:12,249 | ERROR | 43-3aaf88a7bd8b) | configadmin
> | 3 - org.apache.felix.configadmin - 1.8.4 | Unexpected problem
> delivering configuration event to [org.osgi.service.cm.ConfigurationListener,
> id=30, bundle=9/mvn:org.apache.felix/org.apache.felix.scr/1.8.2]
> java.lang.NullPointerException
> at
> org.apache.felix.scr.impl.config.ConfigurationSupport.configurationEvent(ConfigurationSupport.java:283)[9:org.apache.felix.scr:1.8.2]
> at
> org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.sendEvent(ConfigurationManager.java:2036)[3:org.apache.felix.configadmin:1.8.4]
> at
> org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.run(ConfigurationManager.java:2005)[3:org.apache.felix.configadmin:1.8.4]
> at
> org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:103)[3:org.apache.felix.configadmin:1.8.4]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_40]
> {code}
> As written in latest comment, the root cause seems to be that multiple
> installFeature calls to FeatureService mess up the state of the bundles. In
> my case it left a bundle in a corrupt state, which was noticed when the
> configuration change did not really activate the service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4323) Can't install features openejb-cxf openejb-rest
[
https://issues.apache.org/jira/browse/KARAF-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rocco Lagrotteria updated KARAF-4323:
-
Description:
The installation of features openejb-cxf and openejb-rest fails because of
missing requirement.
{panel}
*karaf@root()>* repo-add openejb 4.5.2
Adding feature url mvn:org.apache.openejb/openejb-feature/4.5.2/xml/features
*karaf@root()>* feature:install openejb-cxf
{color:red}Error executing command: Unable to resolve root: missing requirement
\[root\] osgi.identity; osgi.identity=openejb-cxf; type=karaf.feature;
version="\[4.5.2,4.5.2\]";
filter:="(&(osgi.identity=openejb-cxf)(type=karaf.feature)(version>=4.5.2)(version<=4.5.2))"
[caused by: Unable to resolve openejb-cxf/4.5.2: missing requirement
\[openejb-cxf/4.5.2\] osgi.identity;
osgi.identity=org.apache.openejb.cxf-transport; type=osgi.bundle;
version="\[4.5.2,4.5.2\]"; resolution:=mandatory [caused by: Unable to resolve
org.apache.openejb.cxf-transport/4.5.2: missing requirement
\[org.apache.openejb.cxf-transport/4.5.2\] osgi.wiring.package;
filter:="(&(osgi.wiring.package=org.apache.cxf.transport.http)(version>=2.6.0)(!(version>=3.0.0)))"\]\]{color}
*karaf@root()>* feature:install openejb-rest
{color:red}Error executing command: Unable to resolve root: missing requirement
\[root\] osgi.identity; osgi.identity=http-whiteboard; type=karaf.feature;
version="\[2.0.0,4.0.0)"{color}
{panel}
was:
The installation of features openejb-cxf and openejb-rest fails because of
missing requirement.
karaf@root()> repo-add openejb 4.5.2
Adding feature url mvn:org.apache.openejb/openejb-feature/4.5.2/xml/features
karaf@root()> feature:install openejb-cxf
Error executing command: Unable to resolve root: missing requirement [root]
osgi.identity; osgi.identity=openejb-cxf; type=karaf.feature;
version="[4.5.2,4.5.2]";
filter:="(&(osgi.identity=openejb-cxf)(type=karaf.feature)(version>=4.5.2)(version<=4.5.2))"
[caused by: Unable to resolve openejb-cxf/4.5.2: missing requirement
[openejb-cxf/4.5.2] osgi.identity;
osgi.identity=org.apache.openejb.cxf-transport; type=osgi.bundle;
version="[4.5.2,4.5.2]"; resolution:=mandatory [caused by: Unable to resolve
org.apache.openejb.cxf-transport/4.5.2: missing requirement
[org.apache.openejb.cxf-transport/4.5.2] osgi.wiring.package;
filter:="(&(osgi.wiring.package=org.apache.cxf.transport.http)(version>=2.6.0)(!(version>=3.0.0)))"]]
karaf@root()> feature:install openejb-rest
Error executing command: Unable to resolve root: missing requirement [root]
osgi.identity; osgi.identity=http-whiteboard; type=karaf.feature;
version="[2.0.0,4.0.0)"
> Can't install features openejb-cxf openejb-rest
> ---
>
> Key: KARAF-4323
> URL: https://issues.apache.org/jira/browse/KARAF-4323
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 3.0.5, 4.0.4
>Reporter: Rocco Lagrotteria
>Priority: Critical
> Labels: features, karaf, openejb
>
> The installation of features openejb-cxf and openejb-rest fails because of
> missing requirement.
> {panel}
> *karaf@root()>* repo-add openejb 4.5.2
> Adding feature url mvn:org.apache.openejb/openejb-feature/4.5.2/xml/features
> *karaf@root()>* feature:install openejb-cxf
> {color:red}Error executing command: Unable to resolve root: missing
> requirement \[root\] osgi.identity; osgi.identity=openejb-cxf;
> type=karaf.feature; version="\[4.5.2,4.5.2\]";
> filter:="(&(osgi.identity=openejb-cxf)(type=karaf.feature)(version>=4.5.2)(version<=4.5.2))"
> [caused by: Unable to resolve openejb-cxf/4.5.2: missing requirement
> \[openejb-cxf/4.5.2\] osgi.identity;
> osgi.identity=org.apache.openejb.cxf-transport; type=osgi.bundle;
> version="\[4.5.2,4.5.2\]"; resolution:=mandatory [caused by: Unable to
> resolve org.apache.openejb.cxf-transport/4.5.2: missing requirement
> \[org.apache.openejb.cxf-transport/4.5.2\] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=org.apache.cxf.transport.http)(version>=2.6.0)(!(version>=3.0.0)))"\]\]{color}
> *karaf@root()>* feature:install openejb-rest
> {color:red}Error executing command: Unable to resolve root: missing
> requirement \[root\] osgi.identity; osgi.identity=http-whiteboard;
> type=karaf.feature; version="\[2.0.0,4.0.0)"{color}
> {panel}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4323) Can't install features openejb-cxf openejb-rest
Rocco Lagrotteria created KARAF-4323: Summary: Can't install features openejb-cxf openejb-rest Key: KARAF-4323 URL: https://issues.apache.org/jira/browse/KARAF-4323 Project: Karaf Issue Type: Bug Components: karaf-feature Affects Versions: 4.0.4, 3.0.5 Reporter: Rocco Lagrotteria Priority: Critical The installation of features openejb-cxf and openejb-rest fails because of missing requirement. karaf@root()> repo-add openejb 4.5.2 Adding feature url mvn:org.apache.openejb/openejb-feature/4.5.2/xml/features karaf@root()> feature:install openejb-cxf Error executing command: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=openejb-cxf; type=karaf.feature; version="[4.5.2,4.5.2]"; filter:="(&(osgi.identity=openejb-cxf)(type=karaf.feature)(version>=4.5.2)(version<=4.5.2))" [caused by: Unable to resolve openejb-cxf/4.5.2: missing requirement [openejb-cxf/4.5.2] osgi.identity; osgi.identity=org.apache.openejb.cxf-transport; type=osgi.bundle; version="[4.5.2,4.5.2]"; resolution:=mandatory [caused by: Unable to resolve org.apache.openejb.cxf-transport/4.5.2: missing requirement [org.apache.openejb.cxf-transport/4.5.2] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.apache.cxf.transport.http)(version>=2.6.0)(!(version>=3.0.0)))"]] karaf@root()> feature:install openejb-rest Error executing command: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=http-whiteboard; type=karaf.feature; version="[2.0.0,4.0.0)" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3698) Add decanter cassandra appender
[ https://issues.apache.org/jira/browse/KARAF-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3698: Fix Version/s: decanter-1.0.2 > Add decanter cassandra appender > --- > > Key: KARAF-3698 > URL: https://issues.apache.org/jira/browse/KARAF-3698 > Project: Karaf > Issue Type: New Feature > Components: decanter >Reporter: Achim Nierbeck >Assignee: Jean-Baptiste Onofré > Fix For: decanter-1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-3698) Add decanter cassandra appender
[ https://issues.apache.org/jira/browse/KARAF-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-3698: --- Assignee: Jean-Baptiste Onofré > Add decanter cassandra appender > --- > > Key: KARAF-3698 > URL: https://issues.apache.org/jira/browse/KARAF-3698 > Project: Karaf > Issue Type: New Feature > Components: decanter >Reporter: Achim Nierbeck >Assignee: Jean-Baptiste Onofré > Fix For: decanter-1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KARAF-3698) Add decanter cassandra appender
[ https://issues.apache.org/jira/browse/KARAF-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-3698 started by Jean-Baptiste Onofré. --- > Add decanter cassandra appender > --- > > Key: KARAF-3698 > URL: https://issues.apache.org/jira/browse/KARAF-3698 > Project: Karaf > Issue Type: New Feature > Components: decanter >Reporter: Achim Nierbeck >Assignee: Jean-Baptiste Onofré > Fix For: decanter-1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4322) feature:repo-remove / cluster:feature-repo-remove -u flag has no effect
[
https://issues.apache.org/jira/browse/KARAF-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roland Hauser updated KARAF-4322:
-
Description:
When I remove a feature repository from the default cluster group with command
{{cluster:feature-repo-remove -u default com.some.feature.repo}}, the feature
repository is removed from the default group as expected (the repository is not
listed in the console output of {{cluster:feature-repo-list default}} anymore).
The problem is, that no feature derived from the removed repository is being
uninstalled, but the -u flag should trigger that behaviour.
{code}
man cluster:feature-repo-remove
...
-u, --uninstall-all
Uninstall all features contained in the features repositories
{code}
Note: I tested the same process with the local feature: commands and it seems
that the local -u flag with the feature:repo-remove command does not work as
well.
was:
When I remove a feature repository from the default cluster group with command
{{cluster:feature-repo-remove -u default com.some.feature.repo}}, the feature
repository is removed from the default group as expected (the repository is not
listed in the console output of {{cluster:feature-repo-list default}} anymore).
The problem is, that no feature derived from the removed repository is being
uninstalled, but the -u flag should trigger that behaviour.
{code}
man cluster:feature-repo-remove
...
-u, --uninstall-all
Uninstall all features contained in the features repositories
{code}
Component/s: karaf-feature
Summary: feature:repo-remove / cluster:feature-repo-remove -u flag has
no effect (was: cluster:feature-repo-remove -u flag has no effect)
> feature:repo-remove / cluster:feature-repo-remove -u flag has no effect
> ---
>
> Key: KARAF-4322
> URL: https://issues.apache.org/jira/browse/KARAF-4322
> Project: Karaf
> Issue Type: Bug
> Components: cellar-features, karaf-feature
>Affects Versions: 4.0.4
>Reporter: Roland Hauser
>
> When I remove a feature repository from the default cluster group with
> command {{cluster:feature-repo-remove -u default com.some.feature.repo}}, the
> feature repository is removed from the default group as expected (the
> repository is not listed in the console output of {{cluster:feature-repo-list
> default}} anymore). The problem is, that no feature derived from the removed
> repository is being uninstalled, but the -u flag should trigger that
> behaviour.
> {code}
> man cluster:feature-repo-remove
> ...
> -u, --uninstall-all
> Uninstall all features contained in the features repositories
> {code}
> Note: I tested the same process with the local feature: commands and it seems
> that the local -u flag with the feature:repo-remove command does not work as
> well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4322) cluster:feature-repo-remove -u flag has no effect
Roland Hauser created KARAF-4322:
Summary: cluster:feature-repo-remove -u flag has no effect
Key: KARAF-4322
URL: https://issues.apache.org/jira/browse/KARAF-4322
Project: Karaf
Issue Type: Bug
Components: cellar-features
Affects Versions: 4.0.4
Reporter: Roland Hauser
When I remove a feature repository from the default cluster group with command
{{cluster:feature-repo-remove -u default com.some.feature.repo}}, the feature
repository is removed from the default group as expected (the repository is not
listed in the console output of {{cluster:feature-repo-list default}} anymore).
The problem is, that no feature derived from the removed repository is being
uninstalled, but the -u flag should trigger that behaviour.
{code}
man cluster:feature-repo-remove
...
-u, --uninstall-all
Uninstall all features contained in the features repositories
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Work started] (KARAF-4321) Add log4j socket collector
[ https://issues.apache.org/jira/browse/KARAF-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-4321 started by Christian Schneider. -- > Add log4j socket collector > -- > > Key: KARAF-4321 > URL: https://issues.apache.org/jira/browse/KARAF-4321 > Project: Karaf > Issue Type: New Feature > Components: decanter >Affects Versions: decanter-1.0.1 >Reporter: Christian Schneider >Assignee: Christian Schneider > Fix For: decanter-1.0.2 > > > One use case for decanter is to run it as a kind of logging aggregator for a > machine. > You start up one instance of karaf with decanter and let it collect logging > informations for all other processes on the machine. > So we need a slim mechanism to transport logging informations from OSGi and > non OSGi processes to decanter. > The og4j socket appender seems like a good candidate. So we should have a > decanter collector that listens for log4j messages on a socket. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4321) Add log4j socket collector
Christian Schneider created KARAF-4321: -- Summary: Add log4j socket collector Key: KARAF-4321 URL: https://issues.apache.org/jira/browse/KARAF-4321 Project: Karaf Issue Type: New Feature Components: decanter Affects Versions: decanter-1.0.1 Reporter: Christian Schneider Assignee: Christian Schneider Fix For: decanter-1.0.2 One use case for decanter is to run it as a kind of logging aggregator for a machine. You start up one instance of karaf with decanter and let it collect logging informations for all other processes on the machine. So we need a slim mechanism to transport logging informations from OSGi and non OSGi processes to decanter. The og4j socket appender seems like a good candidate. So we should have a decanter collector that listens for log4j messages on a socket. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4320) Create socket collector
Jean-Baptiste Onofré created KARAF-4320: --- Summary: Create socket collector Key: KARAF-4320 URL: https://issues.apache.org/jira/browse/KARAF-4320 Project: Karaf Issue Type: New Feature Components: decanter Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré In addition of the rest/API collector, we can provide a socket collector to receive collected data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4317) NullPointerException when adding a feature repository to a cluster
[
https://issues.apache.org/jira/browse/KARAF-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roland Hauser updated KARAF-4317:
-
Description:
I have a cluster with 2 nodes. Both nodes have the feature listener enabled
(org.apache.karaf.cellar.node.cfg / feature.listener = true).
On node 1, I install a custom feature repository with following command:
{{feature:repo-add
mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features}}
On node 2, I get a NullPointerException:
{code}
2016-02-05 11:10:39,849 | ERROR | pool-50-thread-1 | RepositoryEventHandler
| 64 - org.apache.karaf.cellar.features - 4.0.0 | CELLAR FEATURE: failed
to add/remove repository URL
mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features
java.lang.NullPointerException
at
org.apache.karaf.cellar.features.RepositoryEventHandler.handle(RepositoryEventHandler.java:80)[64:org.apache.karaf.cellar.features:4.0.0]
at
org.apache.karaf.cellar.features.RepositoryEventHandler.handle(RepositoryEventHandler.java:29)[64:org.apache.karaf.cellar.features:4.0.0]
at
org.apache.karaf.cellar.core.event.EventDispatchTask.run(EventDispatchTask.java:57)[63:org.apache.karaf.cellar.core:4.0.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown
Source)[:1.7.0_55]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
Source)[:1.7.0_55]
at java.lang.Thread.run(Unknown Source)[:1.7.0_55]
{code}
The same effect occurs when I use the dedicated cluster command:
{{cluster:feature-repo-add default
mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features}}
When I disable the feature listener (org.apache.karaf.cellar.node.cfg /
feature.listener = false), the cluster-command
{{cluster:feature-repo-add default
mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features}}
works as exepected. The repository is then also available on node 2 and the
feature can be installed.
If I did something wrong, it would nevertheless be helpful if an error message
would tell what caused the problem.
was:
I have a cluster with 2 nodes. Both nodes have the feature listener enabled
(org.apache.karaf.cellar.node.cfg / feature.listener = true).
On node 1, I install a custom feature repository with following command:
{{feature:repo-add
mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features}}
On node 2, I get a NullPointerException:
{code}
2016-02-05 11:10:39,849 | ERROR | pool-50-thread-1 | RepositoryEventHandler
| 64 - org.apache.karaf.cellar.features - 4.0.0 | CELLAR FEATURE: failed
to add/remove repository URL
mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features
java.lang.NullPointerException
at
org.apache.karaf.cellar.features.RepositoryEventHandler.handle(RepositoryEventHandler.java:80)[64:org.apache.karaf.cellar.features:4.0.0]
at
org.apache.karaf.cellar.features.RepositoryEventHandler.handle(RepositoryEventHandler.java:29)[64:org.apache.karaf.cellar.features:4.0.0]
at
org.apache.karaf.cellar.core.event.EventDispatchTask.run(EventDispatchTask.java:57)[63:org.apache.karaf.cellar.core:4.0.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown
Source)[:1.7.0_55]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
Source)[:1.7.0_55]
at java.lang.Thread.run(Unknown Source)[:1.7.0_55]
{code}
The same effect occurs when I use the dedicated cluster command:
{{cluster:feature-repo-add default
mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features}}
When I disable the feature listener (org.apache.karaf.cellar.node.cfg /
feature.listener = true), the cluster-command
{{cluster:feature-repo-add default
mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features}}
works as exepected. The repository is then also available on node 2 and the
feature can be installed.
If I did something wrong, it would nevertheless be helpful if an error message
would tell what caused the problem.
> NullPointerException when adding a feature repository to a cluster
> --
>
> Key: KARAF-4317
> URL: https://issues.apache.org/jira/browse/KARAF-4317
> Project: Karaf
> Issue Type: Bug
> Components: cellar-features
>Reporter: Roland Hauser
>Priority: Critical
>
> I have a cluster with 2 nodes. Both nodes have the feature listener enabled
> (org.apache.karaf.cellar.node.cfg / feature.listener = true).
> On node 1, I install a custom feature repository with following command:
> {{feature:repo-add
> mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features}}
> On node 2, I get a NullPointerException:
> {code}
> 2016-02-05 11:10:39,849
[jira] [Updated] (KARAF-4317) NullPointerException when adding a feature repository to a cluster
[
https://issues.apache.org/jira/browse/KARAF-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roland Hauser updated KARAF-4317:
-
Priority: Major (was: Critical)
> NullPointerException when adding a feature repository to a cluster
> --
>
> Key: KARAF-4317
> URL: https://issues.apache.org/jira/browse/KARAF-4317
> Project: Karaf
> Issue Type: Bug
> Components: cellar-features
>Reporter: Roland Hauser
>
> I have a cluster with 2 nodes. Both nodes have the feature listener enabled
> (org.apache.karaf.cellar.node.cfg / feature.listener = true).
> On node 1, I install a custom feature repository with following command:
> {{feature:repo-add
> mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features}}
> On node 2, I get a NullPointerException:
> {code}
> 2016-02-05 11:10:39,849 | ERROR | pool-50-thread-1 | RepositoryEventHandler
> | 64 - org.apache.karaf.cellar.features - 4.0.0 | CELLAR FEATURE:
> failed to add/remove repository URL
> mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features
> java.lang.NullPointerException
> at
> org.apache.karaf.cellar.features.RepositoryEventHandler.handle(RepositoryEventHandler.java:80)[64:org.apache.karaf.cellar.features:4.0.0]
> at
> org.apache.karaf.cellar.features.RepositoryEventHandler.handle(RepositoryEventHandler.java:29)[64:org.apache.karaf.cellar.features:4.0.0]
> at
> org.apache.karaf.cellar.core.event.EventDispatchTask.run(EventDispatchTask.java:57)[63:org.apache.karaf.cellar.core:4.0.0]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown
> Source)[:1.7.0_55]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
> Source)[:1.7.0_55]
> at java.lang.Thread.run(Unknown Source)[:1.7.0_55]
> {code}
> The same effect occurs when I use the dedicated cluster command:
> {{cluster:feature-repo-add default
> mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features}}
> When I disable the feature listener (org.apache.karaf.cellar.node.cfg /
> feature.listener = false), the cluster-command
> {{cluster:feature-repo-add default
> mvn:com.bechtle.terra/com.bechtle.terra.renderer.feature/LATEST/xml/features}}
> works as exepected. The repository is then also available on node 2 and the
> feature can be installed.
> If I did something wrong, it would nevertheless be helpful if an error
> message would tell what caused the problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
