[jira] [Resolved] (KARAF-2970) Software deployed on Karaf will not update if Karaf detects the presence of a previous .M2 directory
[ https://issues.apache.org/jira/browse/KARAF-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek resolved KARAF-2970. - Resolution: Not A Problem > Software deployed on Karaf will not update if Karaf detects the presence of a > previous .M2 directory > - > > Key: KARAF-2970 > URL: https://issues.apache.org/jira/browse/KARAF-2970 > Project: Karaf > Issue Type: Bug > Components: karaf-archetypes, karaf-config, karaf-core, > karaf-documentation, karaf-exam, karaf-feature, karaf-instance, karaf-kar, > karaf-os-integration, karaf-osgi, karaf-repository, karaf-scheduler, > karaf-scr, karaf-security, karaf-shell, karaf-test, karaf-tooling, > karaf-webconsole, karaf-webcontainer >Affects Versions: 3.0.0 > Environment: Windows Server 2008 R2, Windows 2008 R2 SP2, Windows > 2012 R2 >Reporter: Chris Longo >Assignee: Grzegorz Grzybek > > The presence of a .M2 directory causes an application deployed on Karaf not > to update. > Prerequisites: > A) Deploy an application on Karaf > B) Verify there is the presence of an .M2 directory > Steps to Reproduce: > Deploy a revised application build on Karaf > Actual Result: > The bits from the local .M2 repo are kept and not overwritten with the newest > modified bits > Expected Result: > The bits from the local .M2 repo should be updated even if the .M2 directory > was present prior to installing the updated app deployed on Karaf > Workaround: > 1.Delete the .M2 directory > 2.Deploy the software on Karaf > 3.The local .M2 directory will now be updated -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KARAF-5247) java.lang.InterruptedException after logout command in shell
[ https://issues.apache.org/jira/browse/KARAF-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved KARAF-5247. - Resolution: Fixed Fix Version/s: 4.1.2 4.2.0 > java.lang.InterruptedException after logout command in shell > > > Key: KARAF-5247 > URL: https://issues.apache.org/jira/browse/KARAF-5247 > Project: Karaf > Issue Type: Bug >Reporter: Freeman Fang >Assignee: Freeman Fang > Fix For: 4.2.0, 4.1.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5247) java.lang.InterruptedException after logout command in shell
[ https://issues.apache.org/jira/browse/KARAF-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16085272#comment-16085272 ] ASF subversion and git services commented on KARAF-5247: Commit 8fd6f4a3e5ff2ca3eb87fb2032fe6be34bb6971a in karaf's branch refs/heads/karaf-4.1.x from [~ffang] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=8fd6f4a ] [KARAF-5247]java.lang.InterruptedException after logout command in shell (cherry picked from commit 0f2b18176d551619e846282e3faaed6f646b7e51) > java.lang.InterruptedException after logout command in shell > > > Key: KARAF-5247 > URL: https://issues.apache.org/jira/browse/KARAF-5247 > Project: Karaf > Issue Type: Bug >Reporter: Freeman Fang >Assignee: Freeman Fang > Fix For: 4.2.0, 4.1.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5247) java.lang.InterruptedException after logout command in shell
[ https://issues.apache.org/jira/browse/KARAF-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16085269#comment-16085269 ] ASF subversion and git services commented on KARAF-5247: Commit 0f2b18176d551619e846282e3faaed6f646b7e51 in karaf's branch refs/heads/master from [~ffang] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=0f2b181 ] [KARAF-5247]java.lang.InterruptedException after logout command in shell > java.lang.InterruptedException after logout command in shell > > > Key: KARAF-5247 > URL: https://issues.apache.org/jira/browse/KARAF-5247 > Project: Karaf > Issue Type: Bug >Reporter: Freeman Fang >Assignee: Freeman Fang > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KARAF-5247) java.lang.InterruptedException after logout command in shell
[ https://issues.apache.org/jira/browse/KARAF-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-5247: --- Assignee: Freeman Fang > java.lang.InterruptedException after logout command in shell > > > Key: KARAF-5247 > URL: https://issues.apache.org/jira/browse/KARAF-5247 > Project: Karaf > Issue Type: Bug >Reporter: Freeman Fang >Assignee: Freeman Fang > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KARAF-5247) java.lang.InterruptedException after logout command in shell
Freeman Fang created KARAF-5247: --- Summary: java.lang.InterruptedException after logout command in shell Key: KARAF-5247 URL: https://issues.apache.org/jira/browse/KARAF-5247 Project: Karaf Issue Type: Bug Reporter: Freeman Fang -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-5069) Support include/exclude filter for topic for appenders
[ https://issues.apache.org/jira/browse/KARAF-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5069: Fix Version/s: (was: decanter-1.4.0) > Support include/exclude filter for topic for appenders > -- > > Key: KARAF-5069 > URL: https://issues.apache.org/jira/browse/KARAF-5069 > Project: Karaf > Issue Type: New Feature > Components: decanter >Affects Versions: decanter-1.3.0 >Reporter: Oliver Wulff >Assignee: Jean-Baptiste Onofré > > Some collector events should be sent to one appender (ex. kafka) whereas > other events to another appender (ex. camel) for custom enrichement of the > event. > Implementation proposal: > Every appender could provide an exclude and include property to configure to > which appender the events should be sent to. The exclude/include condition > could be based on the topic. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KARAF-4559) Provide more Elasticsearch features
[ https://issues.apache.org/jira/browse/KARAF-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-4559. - Resolution: Won't Fix Fix Version/s: (was: decanter-1.4.0) The problem is that the new elasticsearch features won't be compliant with the kibana and head features. So, I think it's better to just keep the working elasticsearch/kibana/head features combination. Anyway, users who want to use new elasticsearch version do it as a standalone instance anyway. > Provide more Elasticsearch features > --- > > Key: KARAF-4559 > URL: https://issues.apache.org/jira/browse/KARAF-4559 > Project: Karaf > Issue Type: Dependency upgrade > Components: decanter >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5069) Support include/exclude filter for topic for appenders
[ https://issues.apache.org/jira/browse/KARAF-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16085217#comment-16085217 ] Jean-Baptiste Onofré commented on KARAF-5069: - Agree, it's already possible to define the target topic. > Support include/exclude filter for topic for appenders > -- > > Key: KARAF-5069 > URL: https://issues.apache.org/jira/browse/KARAF-5069 > Project: Karaf > Issue Type: New Feature > Components: decanter >Affects Versions: decanter-1.3.0 >Reporter: Oliver Wulff >Assignee: Jean-Baptiste Onofré > > Some collector events should be sent to one appender (ex. kafka) whereas > other events to another appender (ex. camel) for custom enrichement of the > event. > Implementation proposal: > Every appender could provide an exclude and include property to configure to > which appender the events should be sent to. The exclude/include condition > could be based on the topic. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-5246) Karaf shell command crashes on tab-completion when quotes are used
[
https://issues.apache.org/jira/browse/KARAF-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlo Dapor updated KARAF-5246:
---
Description:
Commands bail out when a starting quote - single or double quote - preceedes a
tab-completion.
E.g.:
Type
{code:java}
feature:install -s
{code}
and hit the tab key, you are prompted with the question whether you want to
see all 40+ completions.
But if you type
{code:java}
feature:install -s " # also with a single quote, btw
{code}
and then hit the tab key, you see an error: {color:red}Error executing command:
String index out of range: 21{color}
The log shows:
{noformat}
2017-07-12 21:39:44,803 | ERROR | nsole user karaf | ShellUtil
| 43 - org.apache.karaf.shell.core - 4.0.9 | Exception caught while
executing command
java.lang.StringIndexOutOfBoundsException: String index out of range: 21
at java.lang.String.substring(String.java:1963)[:1.8.0_131]
at
org.apache.karaf.shell.support.parsing.GogoParser.value(GogoParser.java:300)[43:org.apache.karaf.shell.core:4.0.9]
at
org.apache.karaf.shell.support.parsing.GogoParser.messy(GogoParser.java:223)[43:org.apache.karaf.shell.core:4.0.9]
at
org.apache.karaf.shell.support.parsing.GogoParser.statement(GogoParser.java:195)[43:org.apache.karaf.shell.core:4.0.9]
at
org.apache.karaf.shell.support.parsing.DefaultParser.parse(DefaultParser.java:34)[43:org.apache.karaf.shell.core:4.0.9]
at
org.apache.karaf.shell.impl.console.parsing.CommandLineParser.buildCommandLine(CommandLineParser.java:56)[43:org.apache.karaf.shell.core:4.0.9]
at
org.apache.karaf.shell.impl.console.CompleterAsCompletor.complete(CompleterAsCompletor.java:42)[43:org.apache.karaf.shell.core:4.0.9]
at
jline.console.ConsoleReader.complete(ConsoleReader.java:3296)[9:jline:2.14.1]
at
jline.console.ConsoleReader.readLine(ConsoleReader.java:2636)[9:jline:2.14.1]
at
jline.console.ConsoleReader.readLine(ConsoleReader.java:2362)[9:jline:2.14.1]
at
jline.console.ConsoleReader.readLine(ConsoleReader.java:2350)[9:jline:2.14.1]
at
org.apache.karaf.shell.impl.console.ConsoleSessionImpl.readAndParseCommand(ConsoleSessionImpl.java:373)[43:org.apache.karaf.shell.core:4.0.9]
at
org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:269)[43:org.apache.karaf.shell.core:4.0.9]
at java.lang.Thread.run(Thread.java:748)[:1.8.0_131]
{noformat}
What I would like to achieve, actually is with a StringsCompleter that accepts
say 4 constants ("CODE", "TIME", "RUN", "ERROR"), I'd like to get multiple
completions in the end.
In other words, I would like to be able to this:
> cool-command --expr '({color:#14892c}CODE{color}="A34" and
> {color:#14892c}TIME{color}=60) or ({color:#14892c}RUN{color} > 10 and
> {color:#14892c}ERROR{color}="E517")'
where each {color:#14892c}green{color} completion above I would tab-select as I
type along.
This is currently not possible.
was:
Commands bail out when a starting quote preceed a tab-completion.
E.g.:
Type
{code:java}
feature:install -s
{code}
and hit the tab key, you are prompted with the question whether you want to
see all 40+ completions.
But if you type
{code:java}
feature:install -s " # also with a single quote, btw
{code}
and then hit the tab key, you see an error: {color:red}Error executing command:
String index out of range: 21{color}
The log shows:
{noformat}
2017-07-12 21:39:44,803 | ERROR | nsole user karaf | ShellUtil
| 43 - org.apache.karaf.shell.core - 4.0.9 | Exception caught while
executing command
java.lang.StringIndexOutOfBoundsException: String index out of range: 21
at java.lang.String.substring(String.java:1963)[:1.8.0_131]
at
org.apache.karaf.shell.support.parsing.GogoParser.value(GogoParser.java:300)[43:org.apache.karaf.shell.core:4.0.9]
at
org.apache.karaf.shell.support.parsing.GogoParser.messy(GogoParser.java:223)[43:org.apache.karaf.shell.core:4.0.9]
at
org.apache.karaf.shell.support.parsing.GogoParser.statement(GogoParser.java:195)[43:org.apache.karaf.shell.core:4.0.9]
at
org.apache.karaf.shell.support.parsing.DefaultParser.parse(DefaultParser.java:34)[43:org.apache.karaf.shell.core:4.0.9]
at
org.apache.karaf.shell.impl.console.parsing.CommandLineParser.buildCommandLine(CommandLineParser.java:56)[43:org.apache.karaf.shell.core:4.0.9]
at
org.apache.karaf.shell.impl.console.CompleterAsCompletor.complete(CompleterAsCompletor.java:42)[43:org.apache.karaf.shell.core:4.0.9]
at
jline.console.ConsoleReader.complete(ConsoleReader.java:3296)[9:jline:2.14.1]
at
jline.console.ConsoleReader.readLine(ConsoleReader.java:2636)[9:jline:2.14.1]
at
jline.console.ConsoleReader.readLine(ConsoleReader.java:2362)[9:jline:2.14.1]
at
jline.console.ConsoleRea
[jira] [Updated] (KARAF-5246) Karaf shell command crashes on tab-completion when quotes are used
[
https://issues.apache.org/jira/browse/KARAF-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlo Dapor updated KARAF-5246:
---
Summary: Karaf shell command crashes on tab-completion when quotes are used
(was: Karaf shell command crashed on tab-completion when quotes are used)
> Karaf shell command crashes on tab-completion when quotes are used
> --
>
> Key: KARAF-5246
> URL: https://issues.apache.org/jira/browse/KARAF-5246
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.0.9
>Reporter: Carlo Dapor
>
> Commands bail out when a starting quote preceed a tab-completion.
> E.g.:
> Type
> {code:java}
> feature:install -s
> {code}
> and hit the tab key, you are prompted with the question whether you want to
> see all 40+ completions.
> But if you type
> {code:java}
> feature:install -s " # also with a single quote, btw
> {code}
> and then hit the tab key, you see an error: {color:red}Error executing
> command: String index out of range: 21{color}
> The log shows:
>
> {noformat}
> 2017-07-12 21:39:44,803 | ERROR | nsole user karaf | ShellUtil
> | 43 - org.apache.karaf.shell.core - 4.0.9 | Exception caught while
> executing command
> java.lang.StringIndexOutOfBoundsException: String index out of range: 21
> at java.lang.String.substring(String.java:1963)[:1.8.0_131]
> at
> org.apache.karaf.shell.support.parsing.GogoParser.value(GogoParser.java:300)[43:org.apache.karaf.shell.core:4.0.9]
> at
> org.apache.karaf.shell.support.parsing.GogoParser.messy(GogoParser.java:223)[43:org.apache.karaf.shell.core:4.0.9]
> at
> org.apache.karaf.shell.support.parsing.GogoParser.statement(GogoParser.java:195)[43:org.apache.karaf.shell.core:4.0.9]
> at
> org.apache.karaf.shell.support.parsing.DefaultParser.parse(DefaultParser.java:34)[43:org.apache.karaf.shell.core:4.0.9]
> at
> org.apache.karaf.shell.impl.console.parsing.CommandLineParser.buildCommandLine(CommandLineParser.java:56)[43:org.apache.karaf.shell.core:4.0.9]
> at
> org.apache.karaf.shell.impl.console.CompleterAsCompletor.complete(CompleterAsCompletor.java:42)[43:org.apache.karaf.shell.core:4.0.9]
> at
> jline.console.ConsoleReader.complete(ConsoleReader.java:3296)[9:jline:2.14.1]
> at
> jline.console.ConsoleReader.readLine(ConsoleReader.java:2636)[9:jline:2.14.1]
> at
> jline.console.ConsoleReader.readLine(ConsoleReader.java:2362)[9:jline:2.14.1]
> at
> jline.console.ConsoleReader.readLine(ConsoleReader.java:2350)[9:jline:2.14.1]
> at
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.readAndParseCommand(ConsoleSessionImpl.java:373)[43:org.apache.karaf.shell.core:4.0.9]
> at
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:269)[43:org.apache.karaf.shell.core:4.0.9]
> at java.lang.Thread.run(Thread.java:748)[:1.8.0_131]
> {noformat}
> What I would like to achieve, actually is with a StringsCompleter that
> accepts say 4 constants ("CODE", "TIME", "RUN", "ERROR"), I'd like to get
> multiple completions in the end.
> In other words, I would like to be able to this:
> > cool-command --expr '({color:#14892c}CODE{color}="A34" and
> > {color:#14892c}TIME{color}=60) or ({color:#14892c}RUN{color} > 10 and
> > {color:#14892c}ERROR{color}="E517")'
> where each {color:#14892c}green{color} completion above I would tab-select as
> I type along.
> This is currently not possible.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (KARAF-5246) Karaf shell command crashed on tab-completion when quotes are used
Carlo Dapor created KARAF-5246:
--
Summary: Karaf shell command crashed on tab-completion when quotes
are used
Key: KARAF-5246
URL: https://issues.apache.org/jira/browse/KARAF-5246
Project: Karaf
Issue Type: Bug
Components: karaf-shell
Affects Versions: 4.0.9
Reporter: Carlo Dapor
Commands bail out when a starting quote preceed a tab-completion.
E.g.:
Type
{code:java}
feature:install -s
{code}
and hit the tab key, you are prompted with the question whether you want to
see all 40+ completions.
But if you type
{code:java}
feature:install -s " # also with a single quote, btw
{code}
and then hit the tab key, you see an error: {color:red}Error executing command:
String index out of range: 21{color}
The log shows:
{noformat}
2017-07-12 21:39:44,803 | ERROR | nsole user karaf | ShellUtil
| 43 - org.apache.karaf.shell.core - 4.0.9 | Exception caught while
executing command
java.lang.StringIndexOutOfBoundsException: String index out of range: 21
at java.lang.String.substring(String.java:1963)[:1.8.0_131]
at
org.apache.karaf.shell.support.parsing.GogoParser.value(GogoParser.java:300)[43:org.apache.karaf.shell.core:4.0.9]
at
org.apache.karaf.shell.support.parsing.GogoParser.messy(GogoParser.java:223)[43:org.apache.karaf.shell.core:4.0.9]
at
org.apache.karaf.shell.support.parsing.GogoParser.statement(GogoParser.java:195)[43:org.apache.karaf.shell.core:4.0.9]
at
org.apache.karaf.shell.support.parsing.DefaultParser.parse(DefaultParser.java:34)[43:org.apache.karaf.shell.core:4.0.9]
at
org.apache.karaf.shell.impl.console.parsing.CommandLineParser.buildCommandLine(CommandLineParser.java:56)[43:org.apache.karaf.shell.core:4.0.9]
at
org.apache.karaf.shell.impl.console.CompleterAsCompletor.complete(CompleterAsCompletor.java:42)[43:org.apache.karaf.shell.core:4.0.9]
at
jline.console.ConsoleReader.complete(ConsoleReader.java:3296)[9:jline:2.14.1]
at
jline.console.ConsoleReader.readLine(ConsoleReader.java:2636)[9:jline:2.14.1]
at
jline.console.ConsoleReader.readLine(ConsoleReader.java:2362)[9:jline:2.14.1]
at
jline.console.ConsoleReader.readLine(ConsoleReader.java:2350)[9:jline:2.14.1]
at
org.apache.karaf.shell.impl.console.ConsoleSessionImpl.readAndParseCommand(ConsoleSessionImpl.java:373)[43:org.apache.karaf.shell.core:4.0.9]
at
org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:269)[43:org.apache.karaf.shell.core:4.0.9]
at java.lang.Thread.run(Thread.java:748)[:1.8.0_131]
{noformat}
What I would like to achieve, actually is with a StringsCompleter that accepts
say 4 constants ("CODE", "TIME", "RUN", "ERROR"), I'd like to get multiple
completions in the end.
In other words, I would like to be able to this:
> cool-command --expr '({color:#14892c}CODE{color}="A34" and
> {color:#14892c}TIME{color}=60) or ({color:#14892c}RUN{color} > 10 and
> {color:#14892c}ERROR{color}="E517")'
where each {color:#14892c}green{color} completion above I would tab-select as I
type along.
This is currently not possible.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (KARAF-4753) Kafka appender highly uses CPU when using non existing DNS server name
[ https://issues.apache.org/jira/browse/KARAF-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-4753. - Resolution: Cannot Reproduce > Kafka appender highly uses CPU when using non existing DNS server name > -- > > Key: KARAF-4753 > URL: https://issues.apache.org/jira/browse/KARAF-4753 > Project: Karaf > Issue Type: Bug > Components: decanter >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Minor > > If you add a DNS name for Kafka for a not existing server, the appender will > result in a very high CPU usage (near to 100%). > This will also be the case, when you define mutliple kafka server locations > and if just one of the DNS names are not resolved. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-4541) Upgrade to Kafka 0.11.0.0
[ https://issues.apache.org/jira/browse/KARAF-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083971#comment-16083971 ] ASF subversion and git services commented on KARAF-4541: Commit 3a241d7f4618383b915705f8a26f2f5637c6 in karaf-decanter's branch refs/heads/master from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=3a241d7 ] [KARAF-4541] Upgrade to Kafka 0.11.0.0 > Upgrade to Kafka 0.11.0.0 > - > > Key: KARAF-4541 > URL: https://issues.apache.org/jira/browse/KARAF-4541 > Project: Karaf > Issue Type: Dependency upgrade > Components: decanter >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: decanter-1.4.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-4541) Upgrade to Kafka 0.11.0.0
[ https://issues.apache.org/jira/browse/KARAF-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4541: Summary: Upgrade to Kafka 0.11.0.0 (was: Upgrade to Kafka 0.10) > Upgrade to Kafka 0.11.0.0 > - > > Key: KARAF-4541 > URL: https://issues.apache.org/jira/browse/KARAF-4541 > Project: Karaf > Issue Type: Dependency upgrade > Components: decanter >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: decanter-1.4.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KARAF-4541) Upgrade to Kafka 0.11.0.0
[ https://issues.apache.org/jira/browse/KARAF-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-4541. - Resolution: Fixed > Upgrade to Kafka 0.11.0.0 > - > > Key: KARAF-4541 > URL: https://issues.apache.org/jira/browse/KARAF-4541 > Project: Karaf > Issue Type: Dependency upgrade > Components: decanter >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: decanter-1.4.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-4753) Kafka appender highly uses CPU when using non existing DNS server name
[ https://issues.apache.org/jira/browse/KARAF-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4753: Fix Version/s: (was: decanter-1.4.0) > Kafka appender highly uses CPU when using non existing DNS server name > -- > > Key: KARAF-4753 > URL: https://issues.apache.org/jira/browse/KARAF-4753 > Project: Karaf > Issue Type: Bug > Components: decanter >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Minor > > If you add a DNS name for Kafka for a not existing server, the appender will > result in a very high CPU usage (near to 100%). > This will also be the case, when you define mutliple kafka server locations > and if just one of the DNS names are not resolved. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-4753) Kafka appender highly uses CPU when using non existing DNS server name
[ https://issues.apache.org/jira/browse/KARAF-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083977#comment-16083977 ] Jean-Baptiste Onofré commented on KARAF-4753: - I'm not able to reproduce the issue. Can you please provide a simple test case and eventually attach a thread dump ? Thanks ! > Kafka appender highly uses CPU when using non existing DNS server name > -- > > Key: KARAF-4753 > URL: https://issues.apache.org/jira/browse/KARAF-4753 > Project: Karaf > Issue Type: Bug > Components: decanter >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Minor > > If you add a DNS name for Kafka for a not existing server, the appender will > result in a very high CPU usage (near to 100%). > This will also be the case, when you define mutliple kafka server locations > and if just one of the DNS names are not resolved. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5164) karaf-maven-plugin fails to verify artifacts if only available within local reactor
[ https://issues.apache.org/jira/browse/KARAF-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083963#comment-16083963 ] Guillaume Nodet commented on KARAF-5164: The patch looks good to me. > karaf-maven-plugin fails to verify artifacts if only available within local > reactor > --- > > Key: KARAF-5164 > URL: https://issues.apache.org/jira/browse/KARAF-5164 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 4.2.0 >Reporter: Patrick Fink >Assignee: Grzegorz Grzybek >Priority: Minor > Labels: maven > > When the karaf-maven-plugin is used as part of the build process (e.g. to > verify features), it currently requires that the verified artifacts are > available in the local repository while it's not sufficient that they're > avaible within the local reactor. > This means, build processes which contain the karaf-maven-plugin to verify > features, fail when the user don't wants to install artifacts in their local > repository. So,e.g. > `mvn clean install` works fine and like expected while commands like > `mvn clean package` or `mvn clean verify` will fail with resolution errors > (if the artifacts just built are not already available within the local repo). > The karaf-maven-plugin should support artifacts which are not available in > the local repository, but in the local reactor. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5164) karaf-maven-plugin fails to verify artifacts if only available within local reactor
[ https://issues.apache.org/jira/browse/KARAF-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083950#comment-16083950 ] Grzegorz Grzybek commented on KARAF-5164: - PR: https://github.com/apache/karaf/pull/329 - [~gnt], [~jbonofre], [~cschneider] may I ask for review? > karaf-maven-plugin fails to verify artifacts if only available within local > reactor > --- > > Key: KARAF-5164 > URL: https://issues.apache.org/jira/browse/KARAF-5164 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 4.2.0 >Reporter: Patrick Fink >Assignee: Grzegorz Grzybek >Priority: Minor > Labels: maven > > When the karaf-maven-plugin is used as part of the build process (e.g. to > verify features), it currently requires that the verified artifacts are > available in the local repository while it's not sufficient that they're > avaible within the local reactor. > This means, build processes which contain the karaf-maven-plugin to verify > features, fail when the user don't wants to install artifacts in their local > repository. So,e.g. > `mvn clean install` works fine and like expected while commands like > `mvn clean package` or `mvn clean verify` will fail with resolution errors > (if the artifacts just built are not already available within the local repo). > The karaf-maven-plugin should support artifacts which are not available in > the local repository, but in the local reactor. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5164) karaf-maven-plugin fails to verify artifacts if only available within local reactor
[ https://issues.apache.org/jira/browse/KARAF-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083948#comment-16083948 ] ASF subversion and git services commented on KARAF-5164: Commit 58827d8b6e47d1b1c11b33ab942acadfbcbc3f80 in karaf's branch refs/heads/grgrzybek-KARAF-5164-master from [~gzres] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=58827d8 ] [KARAF-5164] Use Maven reactor to resolve artifacts needed by VerifyMojo and AssemblyMojo > karaf-maven-plugin fails to verify artifacts if only available within local > reactor > --- > > Key: KARAF-5164 > URL: https://issues.apache.org/jira/browse/KARAF-5164 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 4.2.0 >Reporter: Patrick Fink >Assignee: Grzegorz Grzybek >Priority: Minor > Labels: maven > > When the karaf-maven-plugin is used as part of the build process (e.g. to > verify features), it currently requires that the verified artifacts are > available in the local repository while it's not sufficient that they're > avaible within the local reactor. > This means, build processes which contain the karaf-maven-plugin to verify > features, fail when the user don't wants to install artifacts in their local > repository. So,e.g. > `mvn clean install` works fine and like expected while commands like > `mvn clean package` or `mvn clean verify` will fail with resolution errors > (if the artifacts just built are not already available within the local repo). > The karaf-maven-plugin should support artifacts which are not available in > the local repository, but in the local reactor. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KARAF-5245) Running karaf.bat inside a "Program Files (x86)" directory
Michael Zimmermann created KARAF-5245:
-
Summary: Running karaf.bat inside a "Program Files (x86)" directory
Key: KARAF-5245
URL: https://issues.apache.org/jira/browse/KARAF-5245
Project: Karaf
Issue Type: Bug
Components: karaf-os-integration
Affects Versions: 4.0.7
Reporter: Michael Zimmermann
There are missing quotes in the karaf.bat file to correctly handle
subdirectories with spaces. Please add them to the lines 80 and 81 as shown
here:
if not "%KARAF_DATA%" == "" (
if not exist "%KARAF_DATA%" (
call :warn KARAF_DATA is not valid: "%KARAF_DATA%"
rem quotes are required here
*{color:red}call :warn Creating "%KARAF_DATA%"
mkdir "%KARAF_DATA%"
{color}*)
)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5164) karaf-maven-plugin fails to verify artifacts if only available within local reactor
[ https://issues.apache.org/jira/browse/KARAF-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083945#comment-16083945 ] ASF subversion and git services commented on KARAF-5164: Commit 5f5163d13df1ee2fdfc3857bec1e67272fa78c47 in karaf's branch refs/heads/grgrzybek-KARAF-5164-master from [~gzres] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=5f5163d ] [KARAF-5164] Use Maven reactor to resolve artifacts needed by VerifyMojo and AssemblyMojo > karaf-maven-plugin fails to verify artifacts if only available within local > reactor > --- > > Key: KARAF-5164 > URL: https://issues.apache.org/jira/browse/KARAF-5164 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 4.2.0 >Reporter: Patrick Fink >Assignee: Grzegorz Grzybek >Priority: Minor > Labels: maven > > When the karaf-maven-plugin is used as part of the build process (e.g. to > verify features), it currently requires that the verified artifacts are > available in the local repository while it's not sufficient that they're > avaible within the local reactor. > This means, build processes which contain the karaf-maven-plugin to verify > features, fail when the user don't wants to install artifacts in their local > repository. So,e.g. > `mvn clean install` works fine and like expected while commands like > `mvn clean package` or `mvn clean verify` will fail with resolution errors > (if the artifacts just built are not already available within the local repo). > The karaf-maven-plugin should support artifacts which are not available in > the local repository, but in the local reactor. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5164) karaf-maven-plugin fails to verify artifacts if only available within local reactor
[ https://issues.apache.org/jira/browse/KARAF-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083949#comment-16083949 ] ASF GitHub Bot commented on KARAF-5164: --- GitHub user grgrzybek opened a pull request: https://github.com/apache/karaf/pull/329 [KARAF-5164] Use Maven reactor to resolve artifacts needed by VerifyM… …ojo and AssemblyMojo You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/karaf grgrzybek-KARAF-5164-master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/karaf/pull/329.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 #329 commit 58827d8b6e47d1b1c11b33ab942acadfbcbc3f80 Author: Grzegorz Grzybek Date: 2017-07-12T13:06:58Z [KARAF-5164] Use Maven reactor to resolve artifacts needed by VerifyMojo and AssemblyMojo > karaf-maven-plugin fails to verify artifacts if only available within local > reactor > --- > > Key: KARAF-5164 > URL: https://issues.apache.org/jira/browse/KARAF-5164 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 4.2.0 >Reporter: Patrick Fink >Assignee: Grzegorz Grzybek >Priority: Minor > Labels: maven > > When the karaf-maven-plugin is used as part of the build process (e.g. to > verify features), it currently requires that the verified artifacts are > available in the local repository while it's not sufficient that they're > avaible within the local reactor. > This means, build processes which contain the karaf-maven-plugin to verify > features, fail when the user don't wants to install artifacts in their local > repository. So,e.g. > `mvn clean install` works fine and like expected while commands like > `mvn clean package` or `mvn clean verify` will fail with resolution errors > (if the artifacts just built are not already available within the local repo). > The karaf-maven-plugin should support artifacts which are not available in > the local repository, but in the local reactor. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-4541) Upgrade to Kafka 0.10
[ https://issues.apache.org/jira/browse/KARAF-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4541: Fix Version/s: decanter-1.4.0 > Upgrade to Kafka 0.10 > - > > Key: KARAF-4541 > URL: https://issues.apache.org/jira/browse/KARAF-4541 > Project: Karaf > Issue Type: Dependency upgrade > Components: decanter >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: decanter-1.4.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KARAF-4545) Add support of Kafka 0.8.2.X
[ https://issues.apache.org/jira/browse/KARAF-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-4545. - Resolution: Won't Fix > Add support of Kafka 0.8.2.X > > > Key: KARAF-4545 > URL: https://issues.apache.org/jira/browse/KARAF-4545 > Project: Karaf > Issue Type: Improvement > Components: decanter >Reporter: Viacheslav Gagara >Assignee: Jean-Baptiste Onofré > > As per Kafka upgrade guide: > http://kafka.apache.org/090/documentation.html#upgrade > upgrade from 0.8 to 0.9 has breaking changes. > It would be good to support older version of Kafka (0.8.x) in Decanter. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KARAF-5244) Refactor kafka config handling
[ https://issues.apache.org/jira/browse/KARAF-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-5244. - Resolution: Fixed > Refactor kafka config handling > -- > > Key: KARAF-5244 > URL: https://issues.apache.org/jira/browse/KARAF-5244 > Project: Karaf > Issue Type: Improvement > Components: decanter >Affects Versions: decanter-1.3.0 >Reporter: Christian Schneider >Assignee: Christian Schneider > Fix For: decanter-1.4.0 > > > The config handling in kafka appender has a lot of duplication. We should > refactor this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KARAF-5164) karaf-maven-plugin fails to verify artifacts if only available within local reactor
[ https://issues.apache.org/jira/browse/KARAF-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek reassigned KARAF-5164: --- Assignee: Grzegorz Grzybek > karaf-maven-plugin fails to verify artifacts if only available within local > reactor > --- > > Key: KARAF-5164 > URL: https://issues.apache.org/jira/browse/KARAF-5164 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 4.2.0 >Reporter: Patrick Fink >Assignee: Grzegorz Grzybek >Priority: Minor > Labels: maven > > When the karaf-maven-plugin is used as part of the build process (e.g. to > verify features), it currently requires that the verified artifacts are > available in the local repository while it's not sufficient that they're > avaible within the local reactor. > This means, build processes which contain the karaf-maven-plugin to verify > features, fail when the user don't wants to install artifacts in their local > repository. So,e.g. > `mvn clean install` works fine and like expected while commands like > `mvn clean package` or `mvn clean verify` will fail with resolution errors > (if the artifacts just built are not already available within the local repo). > The karaf-maven-plugin should support artifacts which are not available in > the local repository, but in the local reactor. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-955) Confusing behavior of ConfigAdmin
[
https://issues.apache.org/jira/browse/KARAF-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083771#comment-16083771
]
Grzegorz Grzybek commented on KARAF-955:
[~gnt], [~jbonofre] I think it'd be ok to _won't fix_ this issue.
> Confusing behavior of ConfigAdmin
> -
>
> Key: KARAF-955
> URL: https://issues.apache.org/jira/browse/KARAF-955
> Project: Karaf
> Issue Type: Bug
> Components: karaf-config
>Affects Versions: 2.2.4
>Reporter: Sergey Zhemzhitsky
>
> Hi there,
> I've faced with the following behavior of ConfigAdmin which I suppose is a
> little bit confusing.
> Steps to reproduce:
> # Start Karaf
> # Go to *$\{karaf.home}/data/log* directory
> # *karaf.log* file should be there
> # Stop Karaf
> # Go to *$\{karaf.home}/data/log* directory and delete *karaf.log* file
> # When Karaf is stopped change *log4j.appender.out.file* property in the
> *$\{karaf.home}/etc/org.ops4j.pax.logging.cfg* file from
> *$\{karaf.data}/log/karaf.log* to *$\{karaf.data}/log/karaf1.log*
> # Start Karaf
> # Go to *$\{karaf.home}/data/log* directory
> # Only *karaf1.log* file is expected to be there, but empty *karaf.log* that
> has been deleted on the step 4 is also there.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-2970) Software deployed on Karaf will not update if Karaf detects the presence of a previous .M2 directory
[
https://issues.apache.org/jira/browse/KARAF-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083770#comment-16083770
]
Grzegorz Grzybek commented on KARAF-2970:
-
[~ChrisIsGood], are you still interested in this issue?
Shortly - I don't think it's valid. local maven repository (by default
{{~/.m2/repository}}) is not something specific to Karaf, but pax-url-aether.
{{etc/org.ops4j.pax.url.mvn.cfg}} file contains
{{org.ops4j.pax.url.mvn.localRepository}} property (if not specified, it
defaults to {{~/.m2/repository}}) which is used to store artifacts resolved in
remote Maven repositories (e.g., in Maven Central).
I'm not sure what you mean by _Deploy a revised application build on Karaf_ -
usually it's done by {{mvn clean install}} new version of artifact to your
local repository and doing {{osgi:update BundleId}} from Karaf shell. Did you
expect something opposite?
> Software deployed on Karaf will not update if Karaf detects the presence of a
> previous .M2 directory
> -
>
> Key: KARAF-2970
> URL: https://issues.apache.org/jira/browse/KARAF-2970
> Project: Karaf
> Issue Type: Bug
> Components: karaf-archetypes, karaf-config, karaf-core,
> karaf-documentation, karaf-exam, karaf-feature, karaf-instance, karaf-kar,
> karaf-os-integration, karaf-osgi, karaf-repository, karaf-scheduler,
> karaf-scr, karaf-security, karaf-shell, karaf-test, karaf-tooling,
> karaf-webconsole, karaf-webcontainer
>Affects Versions: 3.0.0
> Environment: Windows Server 2008 R2, Windows 2008 R2 SP2, Windows
> 2012 R2
>Reporter: Chris Longo
>
> The presence of a .M2 directory causes an application deployed on Karaf not
> to update.
> Prerequisites:
> A) Deploy an application on Karaf
> B) Verify there is the presence of an .M2 directory
> Steps to Reproduce:
> Deploy a revised application build on Karaf
> Actual Result:
> The bits from the local .M2 repo are kept and not overwritten with the newest
> modified bits
> Expected Result:
> The bits from the local .M2 repo should be updated even if the .M2 directory
> was present prior to installing the updated app deployed on Karaf
> Workaround:
> 1.Delete the .M2 directory
> 2.Deploy the software on Karaf
> 3.The local .M2 directory will now be updated
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (KARAF-2970) Software deployed on Karaf will not update if Karaf detects the presence of a previous .M2 directory
[ https://issues.apache.org/jira/browse/KARAF-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek reassigned KARAF-2970: --- Assignee: Grzegorz Grzybek > Software deployed on Karaf will not update if Karaf detects the presence of a > previous .M2 directory > - > > Key: KARAF-2970 > URL: https://issues.apache.org/jira/browse/KARAF-2970 > Project: Karaf > Issue Type: Bug > Components: karaf-archetypes, karaf-config, karaf-core, > karaf-documentation, karaf-exam, karaf-feature, karaf-instance, karaf-kar, > karaf-os-integration, karaf-osgi, karaf-repository, karaf-scheduler, > karaf-scr, karaf-security, karaf-shell, karaf-test, karaf-tooling, > karaf-webconsole, karaf-webcontainer >Affects Versions: 3.0.0 > Environment: Windows Server 2008 R2, Windows 2008 R2 SP2, Windows > 2012 R2 >Reporter: Chris Longo >Assignee: Grzegorz Grzybek > > The presence of a .M2 directory causes an application deployed on Karaf not > to update. > Prerequisites: > A) Deploy an application on Karaf > B) Verify there is the presence of an .M2 directory > Steps to Reproduce: > Deploy a revised application build on Karaf > Actual Result: > The bits from the local .M2 repo are kept and not overwritten with the newest > modified bits > Expected Result: > The bits from the local .M2 repo should be updated even if the .M2 directory > was present prior to installing the updated app deployed on Karaf > Workaround: > 1.Delete the .M2 directory > 2.Deploy the software on Karaf > 3.The local .M2 directory will now be updated -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5244) Refactor kafka config handling
[ https://issues.apache.org/jira/browse/KARAF-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083539#comment-16083539 ] ASF subversion and git services commented on KARAF-5244: Commit 79d1154f2992addc90d4bc59eaaa829d6de878d2 in karaf-decanter's branch refs/heads/master from [~ch...@die-schneider.net] [ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=79d1154 ] [KARAF-5244] Refactor kafka appender config handling > Refactor kafka config handling > -- > > Key: KARAF-5244 > URL: https://issues.apache.org/jira/browse/KARAF-5244 > Project: Karaf > Issue Type: Improvement > Components: decanter >Affects Versions: decanter-1.3.0 >Reporter: Christian Schneider >Assignee: Christian Schneider > Fix For: decanter-1.4.0 > > > The config handling in kafka appender has a lot of duplication. We should > refactor this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KARAF-5244) Refactor kafka config handling
Christian Schneider created KARAF-5244: -- Summary: Refactor kafka config handling Key: KARAF-5244 URL: https://issues.apache.org/jira/browse/KARAF-5244 Project: Karaf Issue Type: Improvement Components: decanter Affects Versions: decanter-1.3.0 Reporter: Christian Schneider Assignee: Christian Schneider Fix For: decanter-1.4.0 The config handling in kafka appender has a lot of duplication. We should refactor this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
