[jira] [Resolved] (KARAF-5064) Karaf freezes and shutdowns when typed ']' in shell
[
https://issues.apache.org/jira/browse/KARAF-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved KARAF-5064.
Resolution: Fixed
Assignee: Guillaume Nodet
Fix Version/s: 4.1.2
4.2.0.M1
> Karaf freezes and shutdowns when typed ']' in shell
> ---
>
> Key: KARAF-5064
> URL: https://issues.apache.org/jira/browse/KARAF-5064
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Dominik Przybysz
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.2.0.M1, 4.1.2
>
>
> I start karaf and type ']':
> {code}
> bash$ ./bin/karaf
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.1.0)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()> Error executing command: Java heap space
>
>
> bash$
> {code}
> Karaf freezes and shutdowns.
> Exception from karaf.log:
> {code}
> 2017-03-25T10:12:06,085 | ERROR | Karaf local console user karaf | ShellUtil
> | 43 - org.apache.karaf.shell.core - 4.1.0 | Exception
> caught while executing command
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:3181) ~[?:?]
> at java.util.ArrayList.grow(ArrayList.java:261) ~[?:?]
> at java.util.ArrayList.ensureExplicitCapacity(ArrayList.java:235)
> ~[?:?]
> at java.util.ArrayList.ensureCapacityInternal(ArrayList.java:227)
> ~[?:?]
> at java.util.ArrayList.add(ArrayList.java:458) ~[?:?]
> at org.apache.felix.gogo.runtime.Parser.statement(Parser.java:381)
> ~[?:?]
> at org.apache.felix.gogo.runtime.Parser.program(Parser.java:229)
> ~[?:?]
> at
> org.apache.felix.gogo.jline.Highlighter.highlight(Highlighter.java:58) ~[?:?]
> at
> org.jline.reader.impl.LineReaderImpl.getDisplayedBufferWithPrompts(LineReaderImpl.java:3263)
> ~[50:org.jline:3.1.3]
> at
> org.jline.reader.impl.LineReaderImpl.redisplay(LineReaderImpl.java:3203)
> ~[50:org.jline:3.1.3]
> at
> org.jline.reader.impl.LineReaderImpl.cleanup(LineReaderImpl.java:2180)
> ~[50:org.jline:3.1.3]
> at
> org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:570)
> ~[50:org.jline:3.1.3]
> at
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:332)
> [43:org.apache.karaf.shell.core:4.1.0]
> at java.lang.Thread.run(Thread.java:745) [?:?]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5064) Karaf freezes and shutdowns when typed ']' in shell
[
https://issues.apache.org/jira/browse/KARAF-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16354445#comment-16354445
]
Guillaume Nodet commented on KARAF-5064:
Fixed in gogo-jline 1.0.6
> Karaf freezes and shutdowns when typed ']' in shell
> ---
>
> Key: KARAF-5064
> URL: https://issues.apache.org/jira/browse/KARAF-5064
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Dominik Przybysz
>Priority: Major
>
> I start karaf and type ']':
> {code}
> bash$ ./bin/karaf
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.1.0)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()> Error executing command: Java heap space
>
>
> bash$
> {code}
> Karaf freezes and shutdowns.
> Exception from karaf.log:
> {code}
> 2017-03-25T10:12:06,085 | ERROR | Karaf local console user karaf | ShellUtil
> | 43 - org.apache.karaf.shell.core - 4.1.0 | Exception
> caught while executing command
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:3181) ~[?:?]
> at java.util.ArrayList.grow(ArrayList.java:261) ~[?:?]
> at java.util.ArrayList.ensureExplicitCapacity(ArrayList.java:235)
> ~[?:?]
> at java.util.ArrayList.ensureCapacityInternal(ArrayList.java:227)
> ~[?:?]
> at java.util.ArrayList.add(ArrayList.java:458) ~[?:?]
> at org.apache.felix.gogo.runtime.Parser.statement(Parser.java:381)
> ~[?:?]
> at org.apache.felix.gogo.runtime.Parser.program(Parser.java:229)
> ~[?:?]
> at
> org.apache.felix.gogo.jline.Highlighter.highlight(Highlighter.java:58) ~[?:?]
> at
> org.jline.reader.impl.LineReaderImpl.getDisplayedBufferWithPrompts(LineReaderImpl.java:3263)
> ~[50:org.jline:3.1.3]
> at
> org.jline.reader.impl.LineReaderImpl.redisplay(LineReaderImpl.java:3203)
> ~[50:org.jline:3.1.3]
> at
> org.jline.reader.impl.LineReaderImpl.cleanup(LineReaderImpl.java:2180)
> ~[50:org.jline:3.1.3]
> at
> org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:570)
> ~[50:org.jline:3.1.3]
> at
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:332)
> [43:org.apache.karaf.shell.core:4.1.0]
> at java.lang.Thread.run(Thread.java:745) [?:?]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (KARAF-5052) Change console color scheme
[ https://issues.apache.org/jira/browse/KARAF-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16354439#comment-16354439 ] Guillaume Nodet edited comment on KARAF-5052 at 2/6/18 7:38 PM: JLine 3.6.0 has a new styling feature which supports ansi sequences, but also more user friendly syntax, so I'm planning to add that into gogo at some point. Though the above `HIGHLIGHTER_COLORS` can already be customized. was (Author: gnt): JLine 3.6.0 has a new styling feature which supports ansi sequences, but also more user friendly syntax, so I'm planning to add that into gogo at some point. > Change console color scheme > --- > > Key: KARAF-5052 > URL: https://issues.apache.org/jira/browse/KARAF-5052 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.1.0 >Reporter: Jean-Baptiste Onofré >Assignee: Christian Schneider >Priority: Major > > With Karaf 4.1.x and use of JLine 3.x, we now have colors in the shell > console. However, some colors are not very convenient (and not really > read-able), especially on Windows as the default background of terminal > windows is dark (for instance, it's pretty hard to read dark blue font with > dark background). > So, as a quick workaround, it would be great to use light color instead of > dark color. > Generally speaking, it would be good to be able to customize the color scheme. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5052) Change console color scheme
[ https://issues.apache.org/jira/browse/KARAF-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16354439#comment-16354439 ] Guillaume Nodet commented on KARAF-5052: JLine 3.6.0 has a new styling feature which supports ansi sequences, but also more user friendly syntax, so I'm planning to add that into gogo at some point. > Change console color scheme > --- > > Key: KARAF-5052 > URL: https://issues.apache.org/jira/browse/KARAF-5052 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.1.0 >Reporter: Jean-Baptiste Onofré >Assignee: Christian Schneider >Priority: Major > > With Karaf 4.1.x and use of JLine 3.x, we now have colors in the shell > console. However, some colors are not very convenient (and not really > read-able), especially on Windows as the default background of terminal > windows is dark (for instance, it's pretty hard to read dark blue font with > dark background). > So, as a quick workaround, it would be great to use light color instead of > dark color. > Generally speaking, it would be good to be able to customize the color scheme. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5052) Change console color scheme
[ https://issues.apache.org/jira/browse/KARAF-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated KARAF-5052: --- Summary: Change console color scheme (was: Change console color schema) > Change console color scheme > --- > > Key: KARAF-5052 > URL: https://issues.apache.org/jira/browse/KARAF-5052 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.1.0 >Reporter: Jean-Baptiste Onofré >Assignee: Christian Schneider >Priority: Major > > With Karaf 4.1.x and use of JLine 3.x, we now have colors in the shell > console. However, some colors are not very convenient (and not really > read-able), especially on Windows as the default background of terminal > windows is dark (for instance, it's pretty hard to read dark blue font with > dark background). > So, as a quick workaround, it would be great to use light color instead of > dark color. > Generally speaking, it would be good to be able to customize the color scheme. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-5526) [ERROR] Failed to construct terminal; falling back to unsupported
[ https://issues.apache.org/jira/browse/KARAF-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-5526. Resolution: Fixed Assignee: Guillaume Nodet Fix Version/s: 4.0.11 > [ERROR] Failed to construct terminal; falling back to unsupported > - > > Key: KARAF-5526 > URL: https://issues.apache.org/jira/browse/KARAF-5526 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.9 > Environment: % mvn -version > Apache Maven 3.5.0 (Red Hat 3.5.0-6) > Maven home: /usr/share/maven > Java version: 1.8.0_151, vendor: Oracle Corporation > Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.151-1.b12.fc27.x86_64/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "4.13.16-302.fc27.x86_64", arch: "amd64", family: > "unix" > % java -version > openjdk version "1.8.0_151" > OpenJDK Runtime Environment (build 1.8.0_151-b12) > OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode) > % cat /etc/redhat-release > Fedora release 27 (Twenty Seven) > % env|grep TERM > COLORTERM=truecolor > TERM=screen-256color >Reporter: Lars Kiesow >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.11 > > > Upgrading to Fedora 27 which comes with a newer Java and Maven version, I > found that the Karaf shell was not working properly anymore. For once, I got > a stack trace right after starting the application and then the shell history > does not work and Ctrl+C which previously would stop commands like > `log:tail`, now terminates the application. > A workaround I could find in this answer on StackOverflow: > https://stackoverflow.com/a/44361749/2352895 > …setting the `TERM` variable to `xterm-color` did help. Though previously, it > worked just fine with the set `screen-256color` -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5526) [ERROR] Failed to construct terminal; falling back to unsupported
[ https://issues.apache.org/jira/browse/KARAF-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16354425#comment-16354425 ] ASF subversion and git services commented on KARAF-5526: Commit bf99b779b7de33be017db0d0e6cbeef319212f69 in karaf's branch refs/heads/karaf-4.0.x from [~gnt] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=bf99b77 ] [KARAF-5526] Upgrade to JLine 2.14.4 > [ERROR] Failed to construct terminal; falling back to unsupported > - > > Key: KARAF-5526 > URL: https://issues.apache.org/jira/browse/KARAF-5526 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.9 > Environment: % mvn -version > Apache Maven 3.5.0 (Red Hat 3.5.0-6) > Maven home: /usr/share/maven > Java version: 1.8.0_151, vendor: Oracle Corporation > Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.151-1.b12.fc27.x86_64/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "4.13.16-302.fc27.x86_64", arch: "amd64", family: > "unix" > % java -version > openjdk version "1.8.0_151" > OpenJDK Runtime Environment (build 1.8.0_151-b12) > OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode) > % cat /etc/redhat-release > Fedora release 27 (Twenty Seven) > % env|grep TERM > COLORTERM=truecolor > TERM=screen-256color >Reporter: Lars Kiesow >Priority: Major > > Upgrading to Fedora 27 which comes with a newer Java and Maven version, I > found that the Karaf shell was not working properly anymore. For once, I got > a stack trace right after starting the application and then the shell history > does not work and Ctrl+C which previously would stop commands like > `log:tail`, now terminates the application. > A workaround I could find in this answer on StackOverflow: > https://stackoverflow.com/a/44361749/2352895 > …setting the `TERM` variable to `xterm-color` did help. Though previously, it > worked just fine with the set `screen-256color` -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (KARAF-5092) An Invalid input during log:tail results in blocking keyboard inputs.
[
https://issues.apache.org/jira/browse/KARAF-5092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed KARAF-5092.
--
Resolution: Duplicate
Assignee: Guillaume Nodet
> An Invalid input during log:tail results in blocking keyboard inputs.
> -
>
> Key: KARAF-5092
> URL: https://issues.apache.org/jira/browse/KARAF-5092
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
>Affects Versions: 4.1.1
> Environment: Windows 7 x64, CMD
>Reporter: Daniel Estermann
>Assignee: Guillaume Nodet
>Priority: Minor
>
> During log:tail was active I accidentally pressed arrow up and the log showed
> an exception:
> {code}2017-04-12 14:36:14,652 | WARN | indowsStreamPump |
> | 49 - org.jline - 3.2.0 | Error
> java.io.IOException: Read end dead
> at
> java.io.PipedInputStream.checkStateForReceive(PipedInputStream.java:262)
> ~[?:?]
> at java.io.PipedInputStream.receive(PipedInputStream.java:201) ~[?:?]
> at java.io.PipedOutputStream.write(PipedOutputStream.java:122) ~[?:?]
> at
> org.jline.terminal.impl.AbstractWindowsTerminal.processInputByte(AbstractWindowsTerminal.java:333)
> ~[?:?]
> at
> org.jline.terminal.impl.AbstractWindowsTerminal.pump(AbstractWindowsTerminal.java:294)
> ~[?:?]
> at java.lang.Thread.run(Thread.java:745) [?:?]{code}
> After that the keyboard inputs were ignored, because the input stream was
> probably closed. Since Ctrl+D is ignored at this state, the only way to quit
> karaf is to kill the java process.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (KARAF-5295) log:tail kills the current session
[ https://issues.apache.org/jira/browse/KARAF-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed KARAF-5295. -- Resolution: Duplicate Assignee: Guillaume Nodet (was: Jean-Baptiste Onofré) > log:tail kills the current session > -- > > Key: KARAF-5295 > URL: https://issues.apache.org/jira/browse/KARAF-5295 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.2 >Reporter: J. Brébec >Assignee: Guillaume Nodet >Priority: Major > > When using "Ctrl-C" to close the "log:tail" command, the current ssh session > is killed with the message "java.nio.channels.ClosedByInterruptException" and > then "Error executing command: java.io.IOException: Pipe closed" > Moreover, on windows with karaf.bat, this error kills the java process. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (KARAF-5428) console watch bundle:list fails with NPE
[
https://issues.apache.org/jira/browse/KARAF-5428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed KARAF-5428.
--
Resolution: Duplicate
Assignee: Guillaume Nodet
> console watch bundle:list fails with NPE
>
>
> Key: KARAF-5428
> URL: https://issues.apache.org/jira/browse/KARAF-5428
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Windows and Linux (occurs on both) running console from
> putty (windows)
>Reporter: Peter Berkman
>Assignee: Guillaume Nodet
>Priority: Major
> Labels: console, watch
>
> log into the karaf console and issue a watch bunlde:list
> {code}
> watch bundle:list
> java.lang.NullPointerException
> at org.apache.felix.gogo.jline.Posix.lambda$watch$6(Posix.java:846)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> java.lang.NullPointerException
> at org.apache.felix.gogo.jline.Posix.lambda$watch$6(Posix.java:846)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-5509) http-whiteboard resources are not published properly
[
https://issues.apache.org/jira/browse/KARAF-5509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated KARAF-5509:
---
Description:
Hello everybody,
the feature http-whiteboard does not work as expected.
I have built a simple osgi application (jar bundle) with the following
component:
{code:java}
import org.osgi.service.component.annotations.Component;
@Component (service = HomepageResources.class, property =
{"osgi.http.whiteboard.resource.pattern = / static / *",
"osgi.http.whiteboard.resource.prefix = / static"})
public class HomepageResources {}
{code}
After installing the http-whiteboard and scr features my bundle is active but
my resource is not available at http://localhost:8181/static/img/profile.png.
Apache Karaf bundle:list output - All bundles are active / no exceptions in log
{code}
START LEVEL 100 , List Threshold: 0
ID | State| Lvl | Version | Name
+--+-+---+-
0 | Active | 0 | 5.6.8 | System Bundle, Fragments: 1
1 | Resolved | 1 | 4.1.3 | Apache Karaf :: Features ::
Extension, Hosts: 0
2 | Active | 5 | 1.1.4 | Apache Felix Metatype Service
3 | Active | 5 | 4.1.3 | Apache Karaf :: OSGi Services ::
EventAdmin
4 | Active | 5 | 2.5.3 | OPS4J Pax Url - aether:
5 | Active | 8 | 1.10.1| OPS4J Pax Logging - API
6 | Active | 8 | 1.10.1| OPS4J Pax Logging - Log4j v2
7 | Active | 10 | 1.8.16| Apache Felix Configuration Admin
Service
8 | Active | 11 | 3.5.8 | Apache Felix File Install
9 | Active | 15 | 4.1.3 | Apache Karaf :: Features :: Core
10 | Active | 20 | 1.0.1 | Apache Aries Blueprint API
11 | Active | 20 | 1.1.0 | Apache Aries Blueprint CM
12 | Active | 20 | 1.8.3 | Apache Aries Blueprint Core
13 | Active | 30 | 1.1.5 | Apache Aries JMX API
14 | Active | 30 | 1.1.5 | Apache Aries JMX Blueprint API
15 | Active | 30 | 1.1.5 | Apache Aries JMX Blueprint Core
16 | Active | 30 | 1.1.7 | Apache Aries JMX Core
17 | Active | 30 | 1.1.5 | Apache Aries Whiteboard support
for JMX DynamicMBean services
18 | Active | 20 | 1.1.1 | Apache Aries Proxy Service
19 | Active | 20 | 1.1.3 | Apache Aries Util
20 | Active | 30 | 4.1.3 | Apache Karaf :: Bundle ::
BlueprintStateService
21 | Active | 30 | 4.1.3 | Apache Karaf :: Bundle :: Core
22 | Active | 30 | 4.1.3 | Apache Karaf :: ConfigAdmin ::
Core
23 | Active | 24 | 4.1.3 | Apache Karaf :: Deployer ::
Blueprint
24 | Active | 26 | 4.1.3 | Apache Karaf :: Deployer ::
Features
25 | Active | 24 | 4.1.3 | Apache Karaf :: Deployer ::
Karaf Archive (.kar)
26 | Active | 24 | 4.1.3 | Apache Karaf :: Deployer :: Wrap
Non OSGi Jar
27 | Active | 30 | 4.1.3 | Apache Karaf :: Diagnostic ::
Core
28 | Active | 80 | 4.1.3 | Apache Karaf :: OSGi Services ::
Event
29 | Active | 30 | 4.1.3 | Apache Karaf :: Features ::
Command
30 | Active | 30 | 4.1.3 | Apache Karaf :: Instance :: Core
31 | Active | 30 | 4.1.3 | Apache Karaf :: JAAS ::
Blueprint :: Config
32 | Active | 30 | 4.1.3 | Apache Karaf :: JAAS :: Command
33 | Active | 30 | 4.1.3 | Apache Karaf :: JAAS :: Config
34 | Active | 30 | 4.1.3 | Apache Karaf :: JAAS :: Modules
35 | Active | 30 | 4.1.3 | Apache Karaf :: KAR :: Core
36 | Active | 30 | 4.1.3 | Apache Karaf :: Log :: Core
37 | Active | 30 | 4.1.3 | Apache Karaf :: Management
38 | Active | 30 | 4.1.3 | Apache Karaf :: Package :: Core
39 | Active | 30 | 4.1.3 | Apache Karaf :: Service :: Core
40 | Active | 30 | 4.1.3 | Apache Karaf :: Shell :: Various
Commands
41 | Resolved | 30 | 4.1.3 | Apache Karaf :: Shell ::
Console, Hosts: 42
42 | Active | 30 | 4.1.3 | Apache Karaf :: Shell :: Core,
Fragments: 41
43 | Active | 30 | 4.1.3 | Apache Karaf :: Shell :: SSH
44 | Active | 30 | 4.1.3 | Apache Karaf :: Shell :: Table
45 | Active | 30 | 4.1.3 | Apache Karaf :: System :: Core
46 | Active | 30 | 0.3.11.1 | Apache ServiceMix :: Bundles ::
not-yet-commons-ssl
47 | Active | 30 | 1.6.0 |
[jira] [Commented] (KARAF-5526) [ERROR] Failed to construct terminal; falling back to unsupported
[ https://issues.apache.org/jira/browse/KARAF-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16354401#comment-16354401 ] Guillaume Nodet commented on KARAF-5526: See https://github.com/jline/jline2/issues/281, this has been fixed in jline 2.14.4. > [ERROR] Failed to construct terminal; falling back to unsupported > - > > Key: KARAF-5526 > URL: https://issues.apache.org/jira/browse/KARAF-5526 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.9 > Environment: % mvn -version > Apache Maven 3.5.0 (Red Hat 3.5.0-6) > Maven home: /usr/share/maven > Java version: 1.8.0_151, vendor: Oracle Corporation > Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.151-1.b12.fc27.x86_64/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "4.13.16-302.fc27.x86_64", arch: "amd64", family: > "unix" > % java -version > openjdk version "1.8.0_151" > OpenJDK Runtime Environment (build 1.8.0_151-b12) > OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode) > % cat /etc/redhat-release > Fedora release 27 (Twenty Seven) > % env|grep TERM > COLORTERM=truecolor > TERM=screen-256color >Reporter: Lars Kiesow >Priority: Major > > Upgrading to Fedora 27 which comes with a newer Java and Maven version, I > found that the Karaf shell was not working properly anymore. For once, I got > a stack trace right after starting the application and then the shell history > does not work and Ctrl+C which previously would stop commands like > `log:tail`, now terminates the application. > A workaround I could find in this answer on StackOverflow: > https://stackoverflow.com/a/44361749/2352895 > …setting the `TERM` variable to `xterm-color` did help. Though previously, it > worked just fine with the set `screen-256color` -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5469) Installation of a non blueprint feature triggers the installation of the blueprint compatibility bundle
[ https://issues.apache.org/jira/browse/KARAF-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated KARAF-5469: --- Docs Text: (was: Adding features: paybox-io-modbus/[0.1.0.SNAPSHOT,0.1.0.SNAPSHOT] Wiring: root#cxf-bindings-soap-3.1.10 / 0.0.0 cxf-bindings-soap / 3.1.10 root#cxf-http-jetty_fix-3.1.10 / 0.0.0 cxf-http-jetty_fix / 3.1.10 root#paybox-io-modbus-0.1.0.SNAPSHOT / 0.0.0 paybox-io-modbus / 0.1.0.SNAPSHOT root#http-4.1.3 / 0.0.0 http / 4.1.3 com.sun.jna / 4.4.0 root#621e1d5c-bb18-4d10-ac42-5dcad3b832eb-0.0.0 / 0.0.0 root#log-4.1.3 / 0.0.0 log / 4.1.3 root#pax-http-jetty-6.0.7 / 0.0.0 pax-http-jetty / 6.0.7 root#aries-rsa-discovery-zookeeper-server-1.10.0 / 0.0.0 aries-rsa-discovery-zookeeper-server / 1.10.0 root#hibernate-5.2.8.Final / 0.0.0 hibernate / 5.2.8.Final root#ssh-4.1.3 / 0.0.0 ssh / 4.1.3 root#transaction-api-1.2.0 / 0.0.0 transaction-api / 1.2.0 org.eclipse.jdt.core.compiler.batch / 3.10.0.v20140604-1726 root / 0.0.0 root#pax-http-whiteboard-6.0.7 / 0.0.0 pax-http-whiteboard / 6.0.7 root#cxf-databinding-jaxb-3.1.10 / 0.0.0 cxf-databinding-jaxb / 3.1.10 javassist / 3.20.0.GA root#hibernate-orm-5.2.8.Final / 0.0.0 org.fusesource.hawtbuf.hawtbuf / 1.11.0 root#aries-rsa-provider-fastbin-1.10.0 / 0.0.0 root#shell-4.1.3 / 0.0.0 shell / 4.1.3 root#transaction-manager-geronimo-1.3.3 / 0.0.0 transaction-manager-geronimo / 1.3.3 net.bytebuddy.byte-buddy / 1.6.6 root / 0.0.0 org.apache.felix.framework / 5.6.8 root#framework-4.1.3 / 0.0.0 org.apache.servicemix.bundles.javax-inject / 1.0.0.2 root / 0.0.0 root#aries-rsa-provider-fastbin-1.10.0 / 0.0.0 aries-rsa-provider-fastbin / 1.10.0 root#cxf-http-3.1.10 / 0.0.0 cxf-http / 3.1.10 root#pax-jdbc-1.1.0 / 0.0.0 pax-jdbc / 1.1.0 root#shell-compat-4.1.3 / 0.0.0 shell-compat / 4.1.3 root#jdbc-4.1.3 / 0.0.0 jdbc / 4.1.3 root#pax-http-6.0.7 / 0.0.0 pax-http / 6.0.7 javax.el-api / 3.0.0 root / 0.0.0 javax.servlet-api / 3.1.0 root / 0.0.0 org.jboss.jandex / 2.0.3.Final root#hibernate-orm-5.2.8.Final / 0.0.0 root#cxf-jaxws-3.1.10 / 0.0.0 cxf-jaxws / 3.1.10 root#jaas-boot / 0.0.0 jaas-boot / 0.0.0 root#pax-jdbc-postgresql-1.1.0 / 0.0.0 pax-jdbc-postgresql / 1.1.0 root#aries-proxy-4.1.3 / 0.0.0 aries-proxy / 4.1.3 root#package-4.1.3 / 0.0.0 package / 4.1.3 jaas-boot / 0.0.0 root#jaas-boot / 0.0.0 root#framework-4.1.3 / 0.0.0 framework / 4.1.3 root#diagnostic-4.1.3 / 0.0.0 diagnostic / 4.1.3 root#pax-jdbc-config-1.1.0 / 0.0.0 pax-jdbc-config / 1.1.0 root#cxf-core-3.1.10 / 0.0.0 cxf-core / 3.1.10 org.ops4j.base.spi / 1.5.0 root / 0.0.0 root#aries-rsa-discovery-zookeeper-1.10.0 / 0.0.0 aries-rsa-discovery-zookeeper / 1.10.0 javax.interceptor-api / 1.2.0 root / 0.0.0 root#hibernate-orm-5.2.8.Final / 0.0.0 hibernate-orm / 5.2.8.Final root#pax-jdbc-spec-1.1.0 / 0.0.0 pax-jdbc-spec / 1.1.0 root#service-4.1.3 / 0.0.0 service / 4.1.3 root#instance-4.1.3 / 0.0.0 instance / 4.1.3 root#621e1d5c-bb18-4d10-ac42-5dcad3b832eb-0.0.0 / 0.0.0 621e1d5c-bb18-4d10-ac42-5dcad3b832eb / 0.0.0 root#wrap / 0.0.0 wrap / 0.0.0 root#cxf-specs-3.1.10 / 0.0.0 cxf-specs / 3.1.10 root#cxf-wsdl-3.1.10 / 0.0.0 cxf-wsdl / 3.1.10 transaction / 2.0.0 root#transaction-2.0.0 / 0.0.0 transaction-manager-geronimo / 1.3.3 root#jpa-2.6.1 / 0.0.0 jpa-condition-aries_blueprint / 2.6.1 jpa / 2.6.1 org.fusesource.jansi / 1.16.0 org.apache.felix.framework / 5.6.8 root / 0.0.0 aries-rsa-discovery-zookeeper-server / 1.10.0 root#aries-rsa-discovery-zookeeper-server-1.10.0 / 0.0.0 aries-rsa-discovery-zookeeper / 1.10.0 org.apache.karaf.shell.console / 4.1.3 root#shell-4.1.3 / 0.0.0 org.apache.karaf.shell.core / 4.1.3 root / 0.0.0 621e1d5c-bb18-4d10-ac42-5dcad3b832eb / 0.0.0 paybox-io-modbus / 0.1.0.SNAPSHOT org.hibernate.javax.persistence.hibernate-jpa-2.1-api / 1.0.0.Final org.apache.felix.framework / 5.6.8 root / 0.0.0 pax-jdbc-spec / 1.1.0 root#pax-jdbc-spec-1.1.0 / 0.0.0 org.osgi.service.jdbc / 1.0.0.201505202023 org.apache.servicemix.specs.jsr339-api-2.0.1 / 2.6.0 root#cxf-specs-3.1.10 / 0.0.0 org.apache.felix.framework / 5.6.8 diagnostic / 4.1.3 org.apache.karaf.diagnostic.core / 4.1.3 root#diagnostic-4.1.3 / 0.0.0
[jira] [Updated] (KARAF-5469) Installation of a non blueprint feature triggers the installation of the blueprint compatibility bundle
[
https://issues.apache.org/jira/browse/KARAF-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated KARAF-5469:
---
Attachment: wiring.txt
> Installation of a non blueprint feature triggers the installation of the
> blueprint compatibility bundle
> ---
>
> Key: KARAF-5469
> URL: https://issues.apache.org/jira/browse/KARAF-5469
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
>Affects Versions: 4.1.3
>Reporter: Joao Assuncao
>Priority: Major
> Attachments: wiring.txt
>
>
> In Karaf 4.1.3 when installing some custom made features karaf triggers the
> installation of the org.apache.aries.blueprint.core.compatibility bundle
> causing a refresh of all bundles and a Karaf shutdown.
> None of the bundles in the feature uses blueprint and the more exotic thing
> is that one of the bundles uses a Contional-Package instruction.
> The feature I'm trying to install:
> {code}
> karaf@root()> feature:info paybox-io-modbus
> Feature paybox-io-modbus 0.1.0.SNAPSHOT
> Description:
> Modbus I/O implementation
> Feature has no configuration
> Feature has no configuration files
> Feature has no dependencies.
> Feature contains followed bundles:
> mvn:pt.brisa.common/common-service-core/1.3.0
> mvn:pt.brisa.paybox/io-api/0.1.0-SNAPSHOT
> mvn:pt.brisa.paybox/io-modbus/0.1.0-SNAPSHOT
> mvn:pt.brisa.paybox/io-commands/0.1.0-SNAPSHOT
> Feature has no conditionals.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-5469) Installation of a non blueprint feature triggers the installation of the blueprint compatibility bundle
[
https://issues.apache.org/jira/browse/KARAF-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated KARAF-5469:
---
Description:
In Karaf 4.1.3 when installing some custom made features karaf triggers the
installation of the org.apache.aries.blueprint.core.compatibility bundle
causing a refresh of all bundles and a Karaf shutdown.
None of the bundles in the feature uses blueprint and the more exotic thing is
that one of the bundles uses a Contional-Package instruction.
The feature I'm trying to install:
{code}
karaf@root()> feature:info paybox-io-modbus
Feature paybox-io-modbus 0.1.0.SNAPSHOT
Description:
Modbus I/O implementation
Feature has no configuration
Feature has no configuration files
Feature has no dependencies.
Feature contains followed bundles:
mvn:pt.brisa.common/common-service-core/1.3.0
mvn:pt.brisa.paybox/io-api/0.1.0-SNAPSHOT
mvn:pt.brisa.paybox/io-modbus/0.1.0-SNAPSHOT
mvn:pt.brisa.paybox/io-commands/0.1.0-SNAPSHOT
Feature has no conditionals.
{code}
was:
In Karaf 4.1.3 when installing some custom made features karaf triggers the
installation of the org.apache.aries.blueprint.core.compatibility bundle
causing a refresh of all bundles and a Karaf shutdown.
None of the bundles in the feature uses blueprint and the more exotic thing is
that one of the bundles uses a Contional-Package instruction.
The feature I'm trying to install:
{{
karaf@root()> feature:info paybox-io-modbus
Feature paybox-io-modbus 0.1.0.SNAPSHOT
Description:
Modbus I/O implementation
Feature has no configuration
Feature has no configuration files
Feature has no dependencies.
Feature contains followed bundles:
mvn:pt.brisa.common/common-service-core/1.3.0
mvn:pt.brisa.paybox/io-api/0.1.0-SNAPSHOT
mvn:pt.brisa.paybox/io-modbus/0.1.0-SNAPSHOT
mvn:pt.brisa.paybox/io-commands/0.1.0-SNAPSHOT
Feature has no conditionals.}}
> Installation of a non blueprint feature triggers the installation of the
> blueprint compatibility bundle
> ---
>
> Key: KARAF-5469
> URL: https://issues.apache.org/jira/browse/KARAF-5469
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
>Affects Versions: 4.1.3
>Reporter: Joao Assuncao
>Priority: Major
>
> In Karaf 4.1.3 when installing some custom made features karaf triggers the
> installation of the org.apache.aries.blueprint.core.compatibility bundle
> causing a refresh of all bundles and a Karaf shutdown.
> None of the bundles in the feature uses blueprint and the more exotic thing
> is that one of the bundles uses a Contional-Package instruction.
> The feature I'm trying to install:
> {code}
> karaf@root()> feature:info paybox-io-modbus
> Feature paybox-io-modbus 0.1.0.SNAPSHOT
> Description:
> Modbus I/O implementation
> Feature has no configuration
> Feature has no configuration files
> Feature has no dependencies.
> Feature contains followed bundles:
> mvn:pt.brisa.common/common-service-core/1.3.0
> mvn:pt.brisa.paybox/io-api/0.1.0-SNAPSHOT
> mvn:pt.brisa.paybox/io-modbus/0.1.0-SNAPSHOT
> mvn:pt.brisa.paybox/io-commands/0.1.0-SNAPSHOT
> Feature has no conditionals.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5600) Browsing Files via sftp under Windows is not possible
[ https://issues.apache.org/jira/browse/KARAF-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16354322#comment-16354322 ] Guillaume Nodet commented on KARAF-5600: Yes, please give Karaf 4.1.x a try in your environment to make sure it works, but I've successfully connected to Karaf with cyberduck. > Browsing Files via sftp under Windows is not possible > - > > Key: KARAF-5600 > URL: https://issues.apache.org/jira/browse/KARAF-5600 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.4 >Reporter: Andre Schlegel >Priority: Major > > If Karaf is running on unix I can connect with tools like WinSCP (Windows) or > Cyberduck (Mac) to browse the directories. > > If Karaf is running on Windows I can't see any directory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (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
]
Guillaume Nodet reassigned KARAF-5246:
--
Assignee: Guillaume Nodet
> 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
>Assignee: Guillaume Nodet
>Priority: Major
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5600) Browsing Files via sftp under Windows is not possible
[
https://issues.apache.org/jira/browse/KARAF-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16354010#comment-16354010
]
Guillaume Nodet commented on KARAF-5600:
Fwiw, I've investigated the issue, and it's not the fact that the parent {{..}}
file is not listed.
I've also seen SSHD-802, but that does not cause any real problem either.
> Browsing Files via sftp under Windows is not possible
> -
>
> Key: KARAF-5600
> URL: https://issues.apache.org/jira/browse/KARAF-5600
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.4
>Reporter: Andre Schlegel
>Priority: Major
>
> If Karaf is running on unix I can connect with tools like WinSCP (Windows) or
> Cyberduck (Mac) to browse the directories.
>
> If Karaf is running on Windows I can't see any directory.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel=16354004#comment-16354004
]
ASF subversion and git services commented on KARAF-5246:
Commit e637284031da0d8c8dc3e8ac2e8557928f0eaf00 in karaf's branch
refs/heads/master from [~gnt]
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=e637284 ]
[KARAF-5246] The command parser should be more tolerant when parsing the line
during completion
> 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
>Priority: Major
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5473) Karaf SSH session timing out
[ https://issues.apache.org/jira/browse/KARAF-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353991#comment-16353991 ] Daniel Malmgren commented on KARAF-5473: Yep, the same exception. But as said, I haven't been able to reproduce it with keepalive set to 60, so maybe it was simply a matter of too long between the null packets :) > Karaf SSH session timing out > > > Key: KARAF-5473 > URL: https://issues.apache.org/jira/browse/KARAF-5473 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.2, 4.2.0.M1 > Environment: Tried on two different machines, both running Debian 8.9 >Reporter: Daniel Malmgren >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0, 4.1.5 > > > SSH sessions into Karaf are aborted after about ten minutes of inactivity. > The following message is written to the log: > 14:35:26.042 WARN [sshd-SshServer[616ddc]-nio2-thread-2] > exceptionCaught(ServerSessionImpl[karaf@/127.0.0.1:40676])[state=Opened] > InterruptedByTimeoutException: null > The problem started some weeks ago with the Karaf version shipped with > openHAB, it's currently on 4.1.2. I've also tried a plain Karaf container > though (version 4.2.0.M1) and get the exact same problem there. This has been > discussed in the openHAB forum here: > [https://community.openhab.org/t/timeout-in-karaf-console/35443] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel=16353981#comment-16353981
]
Guillaume Nodet commented on KARAF-5246:
The exception is caught, so there's no bad display in the console. However,
the reason is that the parsing fails, in which case the completer is not called
at all.
> 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
>Priority: Major
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5600) Browsing Files via sftp under Windows is not possible
[ https://issues.apache.org/jira/browse/KARAF-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353970#comment-16353970 ] Andre Schlegel commented on KARAF-5600: --- Ist this issue fixed in karaf 4.1.* ? In this case, I think we have to live with this issue in 4.0.* > Browsing Files via sftp under Windows is not possible > - > > Key: KARAF-5600 > URL: https://issues.apache.org/jira/browse/KARAF-5600 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.4 >Reporter: Andre Schlegel >Priority: Major > > If Karaf is running on unix I can connect with tools like WinSCP (Windows) or > Cyberduck (Mac) to browse the directories. > > If Karaf is running on Windows I can't see any directory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-4255) karaf-maven-plugin does include unused feature conditional dependencies in assembly
[
https://issues.apache.org/jira/browse/KARAF-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-4255:
Fix Version/s: (was: 4.1.5)
> karaf-maven-plugin does include unused feature conditional dependencies in
> assembly
> ---
>
> Key: KARAF-4255
> URL: https://issues.apache.org/jira/browse/KARAF-4255
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Fabian Lange
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.0.11
>
>
> I am using karaf-maven-plugin to make a custom assembly.
> I do include SCR, but I do not include webconsole.
> When I look into the system folder of my generated assembly, I can see:
> {code}
> target/assembly/system/org/apache/felix/org.apache.felix.webconsole.plugins.ds/2.0.2/org.apache.felix.webconsole.plugins.ds-2.0.2.jar
> {code}
> this correlates to the maven output:
> {code}
> [INFO] Feature scr is defined as a boot feature
> [INFO] == Installing artifact
> mvn:org.apache.karaf.scr/org.apache.karaf.scr.command/4.0.3
> [INFO] == Installing artifact mvn:org.apache.felix/org.apache.felix.scr/2.0.2
> [INFO] == Installing artifact
> mvn:org.apache.felix/org.apache.felix.scr.compat/1.0.2
> [INFO] == Installing artifact
> mvn:org.apache.felix/org.apache.felix.webconsole.plugins.ds/2.0.2
> [INFO] == Installing artifact
> mvn:org.apache.felix/org.apache.felix.metatype/1.1.2
> [INFO] == Installing artifact
> mvn:org.apache.karaf.scr/org.apache.karaf.scr.management/4.0.3
> {code}
> however looking at:
> https://github.com/apache/karaf/blob/master/assemblies/features/standard/src/main/feature/feature.xml#L524
> you can see that this is an conditional dependency only.
> This is caused by the fact that assembly does not check if the conditional
> had been met:
> https://github.com/apache/karaf/blob/master/profile/src/main/java/org/apache/karaf/profile/assembly/Builder.java#L822
> I believe we need a check for the conditionals wether the condition is
> actually met.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-3572) Override resources for instance:create in custom distributions
[
https://issues.apache.org/jira/browse/KARAF-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3572:
Fix Version/s: (was: 4.1.5)
> Override resources for instance:create in custom distributions
> --
>
> Key: KARAF-3572
> URL: https://issues.apache.org/jira/browse/KARAF-3572
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-instance
>Affects Versions: 3.0.3, 2.4.1, 4.0.0.M2
>Reporter: Krzysztof Sobkowiak
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.2.0
>
>
> Currently the command {{instance:create}} creates a new instance using the
> resources included in {{org.apache.karaf.instance.core}} bundle. It would be
> resonable to allow people to override the resources in custom distributions,
> e.g. in the same way like branding bundles.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-1677) Unpacked KAR deployment
[ https://issues.apache.org/jira/browse/KARAF-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1677: Fix Version/s: (was: 4.1.5) > Unpacked KAR deployment > --- > > Key: KARAF-1677 > URL: https://issues.apache.org/jira/browse/KARAF-1677 > Project: Karaf > Issue Type: New Feature > Components: karaf-kar >Reporter: Lars-Erik Helander >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.2.0 > > > I am looking for a method, similar to KAR where the > "repository//features.xml" are automatically registered, but where the > data is not in a KAR file, but in a directory, e.g. unpacking a KAR file to a > folder and then somehow point that the content of that folder should be > recognised as a repo and the features under the repository folder is > automatically registered. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-4809) SSHd should not listen to all hosts
[
https://issues.apache.org/jira/browse/KARAF-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353952#comment-16353952
]
ASF GitHub Bot commented on KARAF-4809:
---
jbonofre closed pull request #260: KARAF-4809, SSH should not listen to all
hosts
URL: https://github.com/apache/karaf/pull/260
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/assemblies/features/base/src/main/resources/resources/etc/org.apache.karaf.shell.cfg
b/assemblies/features/base/src/main/resources/resources/etc/org.apache.karaf.shell.cfg
index de4b163909..2734b4a061 100644
---
a/assemblies/features/base/src/main/resources/resources/etc/org.apache.karaf.shell.cfg
+++
b/assemblies/features/base/src/main/resources/resources/etc/org.apache.karaf.shell.cfg
@@ -23,9 +23,10 @@
#
# Via sshPort and sshHost you define the address you can login into Karaf.
-#
-sshPort = 8101
-sshHost = 0.0.0.0
+# Default(sshPort): 8101
+# Default(sshHost): 127.0.0.1
+#sshPort = 8101
+#sshHost = 127.0.0.1
#
# The sshIdleTimeout defines the inactivity timeout to logout the SSH session.
diff --git a/shell/ssh/src/main/java/org/apache/karaf/shell/ssh/Activator.java
b/shell/ssh/src/main/java/org/apache/karaf/shell/ssh/Activator.java
index 2714398d47..44f5ec06c4 100644
--- a/shell/ssh/src/main/java/org/apache/karaf/shell/ssh/Activator.java
+++ b/shell/ssh/src/main/java/org/apache/karaf/shell/ssh/Activator.java
@@ -140,8 +140,8 @@ protected void doStop() {
}
protected SshServer createSshServer(SessionFactory sessionFactory) {
-int sshPort = getInt("sshPort", 8181);
-String sshHost= getString("sshHost", "0.0.0.0");
+int sshPort = getInt("sshPort", 8101);
+String sshHost= getString("sshHost", "127.0.0.1");
long sshIdleTimeout = getLong("sshIdleTimeout", 180);
String sshRealm = getString("sshRealm", "karaf");
String hostKey= getString("hostKey",
System.getProperty("karaf.etc") + "/host.key");
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> SSHd should not listen to all hosts
> ---
>
> Key: KARAF-4809
> URL: https://issues.apache.org/jira/browse/KARAF-4809
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.7
>Reporter: Lars Kiesow
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>
> The default SSH server configuration will make Karaf listen to all hosts. It
> is usually good practice to instead listen to localhost only by default to
> avoid possible security risks (e.g. accidentally exposing an unconfigured SSH
> server).
> This can be fixed by adjusting `sshHost` in `org.apache.karaf.shell.cfg`
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5600) Browsing Files via sftp under Windows is not possible
[ https://issues.apache.org/jira/browse/KARAF-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353951#comment-16353951 ] Guillaume Nodet commented on KARAF-5600: This is specific to windows on karaf 4.0.x. Unfortunately, this has been fixed in SSHD 1.x, but upgrading is not an easy task and may lead to some incompatible behaviors, so I'm quite reluctant. > Browsing Files via sftp under Windows is not possible > - > > Key: KARAF-5600 > URL: https://issues.apache.org/jira/browse/KARAF-5600 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.4 >Reporter: Andre Schlegel >Priority: Major > > If Karaf is running on unix I can connect with tools like WinSCP (Windows) or > Cyberduck (Mac) to browse the directories. > > If Karaf is running on Windows I can't see any directory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5473) Karaf SSH session timing out
[ https://issues.apache.org/jira/browse/KARAF-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353950#comment-16353950 ] ASF GitHub Bot commented on KARAF-5473: --- jbonofre opened a new pull request #440: [KARAF-5473] Add heartbeat by default in Karaf ssh client URL: https://github.com/apache/karaf/pull/440 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Karaf SSH session timing out > > > Key: KARAF-5473 > URL: https://issues.apache.org/jira/browse/KARAF-5473 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.2, 4.2.0.M1 > Environment: Tried on two different machines, both running Debian 8.9 >Reporter: Daniel Malmgren >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0, 4.1.5 > > > SSH sessions into Karaf are aborted after about ten minutes of inactivity. > The following message is written to the log: > 14:35:26.042 WARN [sshd-SshServer[616ddc]-nio2-thread-2] > exceptionCaught(ServerSessionImpl[karaf@/127.0.0.1:40676])[state=Opened] > InterruptedByTimeoutException: null > The problem started some weeks ago with the Karaf version shipped with > openHAB, it's currently on 4.1.2. I've also tried a plain Karaf container > though (version 4.2.0.M1) and get the exact same problem there. This has been > discussed in the openHAB forum here: > [https://community.openhab.org/t/timeout-in-karaf-console/35443] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5473) Karaf SSH session timing out
[ https://issues.apache.org/jira/browse/KARAF-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353948#comment-16353948 ] Jean-Baptiste Onofré commented on KARAF-5473: - I didn't reproduce the problem with heartbeat. Did you get the exception in the log still ? > Karaf SSH session timing out > > > Key: KARAF-5473 > URL: https://issues.apache.org/jira/browse/KARAF-5473 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.2, 4.2.0.M1 > Environment: Tried on two different machines, both running Debian 8.9 >Reporter: Daniel Malmgren >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0, 4.1.5 > > > SSH sessions into Karaf are aborted after about ten minutes of inactivity. > The following message is written to the log: > 14:35:26.042 WARN [sshd-SshServer[616ddc]-nio2-thread-2] > exceptionCaught(ServerSessionImpl[karaf@/127.0.0.1:40676])[state=Opened] > InterruptedByTimeoutException: null > The problem started some weeks ago with the Karaf version shipped with > openHAB, it's currently on 4.1.2. I've also tried a plain Karaf container > though (version 4.2.0.M1) and get the exact same problem there. This has been > discussed in the openHAB forum here: > [https://community.openhab.org/t/timeout-in-karaf-console/35443] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5600) Browsing Files via sftp under Windows is not possible
[ https://issues.apache.org/jira/browse/KARAF-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated KARAF-5600: --- Summary: Browsing Files via sftp under Windows is not possible (was: Browsing Files via scp under Windows is not possible) > Browsing Files via sftp under Windows is not possible > - > > Key: KARAF-5600 > URL: https://issues.apache.org/jira/browse/KARAF-5600 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.4 >Reporter: Andre Schlegel >Priority: Major > > If Karaf is running on unix I can connect with tools like WinSCP (Windows) or > Cyberduck (Mac) to browse the directories. > > If Karaf is running on Windows I can't see any directory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-3152) scp does not work under Windows
[
https://issues.apache.org/jira/browse/KARAF-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353885#comment-16353885
]
Guillaume Nodet commented on KARAF-3152:
Actually, it seems to work well with 4.1.x and 4.2.x, so this clearly looks
like problems in the underlying sshd libraries because 4.0.x uses a very old
version of sshd.
> scp does not work under Windows
> ---
>
> Key: KARAF-3152
> URL: https://issues.apache.org/jira/browse/KARAF-3152
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 2.3.4
> Environment: Win7
>Reporter: Martin Lichtin
>Assignee: Guillaume Nodet
>Priority: Major
>
> $ scp -P 8101 karaf@localhost:lock .
> causes
> {noformat}
> Exception in thread "ScpCommand: [scp, -f, lock]"
> java.lang.IllegalArgumentException: The path is not relative to KARAF_BASE.
> Fo2014-08-08 18:05:59,585 | INFO | NioProcessor-2 | ChannelSession
> | hd.server.channel.ChannelSession 373 | 23 -
> org.apache.sshd.core - 0.8.0 | Executing command: scp -f lock
> r security reason, it's not allowed.
> at
> org.apache.karaf.shell.ssh.KarafFileSystemView.getFile(KarafFileSystemView.java:51)
> at
> org.apache.karaf.shell.ssh.KarafFileSystemView.getFile(KarafFileSystemView.java:39)
> at org.apache.sshd.server.command.ScpCommand.run(ScpCommand.java:212)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KARAF-5599) Upgrade Narayana to version 5.7.2.Final
[ https://issues.apache.org/jira/browse/KARAF-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved KARAF-5599. - Resolution: Fixed > Upgrade Narayana to version 5.7.2.Final > --- > > Key: KARAF-5599 > URL: https://issues.apache.org/jira/browse/KARAF-5599 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5599) Upgrade Narayana to version 5.7.2.Final
[ https://issues.apache.org/jira/browse/KARAF-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353748#comment-16353748 ] ASF subversion and git services commented on KARAF-5599: Commit 68a7240c6f874b1dbe81899186fa04585faf74b0 in karaf's branch refs/heads/master from [~ancosen] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=68a7240 ] [KARAF-5599] Upgrade Narayana to version 5.7.2.Final > Upgrade Narayana to version 5.7.2.Final > --- > > Key: KARAF-5599 > URL: https://issues.apache.org/jira/browse/KARAF-5599 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-3152) scp does not work under Windows
[
https://issues.apache.org/jira/browse/KARAF-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353721#comment-16353721
]
Andre Schlegel commented on KARAF-3152:
---
Ok. I have opened KARAF-5600
> scp does not work under Windows
> ---
>
> Key: KARAF-3152
> URL: https://issues.apache.org/jira/browse/KARAF-3152
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 2.3.4
> Environment: Win7
>Reporter: Martin Lichtin
>Assignee: Guillaume Nodet
>Priority: Major
>
> $ scp -P 8101 karaf@localhost:lock .
> causes
> {noformat}
> Exception in thread "ScpCommand: [scp, -f, lock]"
> java.lang.IllegalArgumentException: The path is not relative to KARAF_BASE.
> Fo2014-08-08 18:05:59,585 | INFO | NioProcessor-2 | ChannelSession
> | hd.server.channel.ChannelSession 373 | 23 -
> org.apache.sshd.core - 0.8.0 | Executing command: scp -f lock
> r security reason, it's not allowed.
> at
> org.apache.karaf.shell.ssh.KarafFileSystemView.getFile(KarafFileSystemView.java:51)
> at
> org.apache.karaf.shell.ssh.KarafFileSystemView.getFile(KarafFileSystemView.java:39)
> at org.apache.sshd.server.command.ScpCommand.run(ScpCommand.java:212)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KARAF-5600) Browsing Files via scp under Windows is not possible
Andre Schlegel created KARAF-5600: - Summary: Browsing Files via scp under Windows is not possible Key: KARAF-5600 URL: https://issues.apache.org/jira/browse/KARAF-5600 Project: Karaf Issue Type: Bug Affects Versions: 4.0.4 Reporter: Andre Schlegel If Karaf is running on unix I can connect with tools like WinSCP (Windows) or Cyberduck (Mac) to browse the directories. If Karaf is running on Windows I can't see any directory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5473) Karaf SSH session timing out
[ https://issues.apache.org/jira/browse/KARAF-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353701#comment-16353701 ] Daniel Malmgren commented on KARAF-5473: Are we sure the keepalive really solves the problem, or does it only make it less likely to occur? I was just thrown out after two hours of inactivity. Now I had the keepalive set to 180 seconds though (have been experimenting with different values), maybe it can not happen at all with 60 seconds? Just want to be sure it's a solution and not a half-working workaround :) > Karaf SSH session timing out > > > Key: KARAF-5473 > URL: https://issues.apache.org/jira/browse/KARAF-5473 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.2, 4.2.0.M1 > Environment: Tried on two different machines, both running Debian 8.9 >Reporter: Daniel Malmgren >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0, 4.1.5 > > > SSH sessions into Karaf are aborted after about ten minutes of inactivity. > The following message is written to the log: > 14:35:26.042 WARN [sshd-SshServer[616ddc]-nio2-thread-2] > exceptionCaught(ServerSessionImpl[karaf@/127.0.0.1:40676])[state=Opened] > InterruptedByTimeoutException: null > The problem started some weeks ago with the Karaf version shipped with > openHAB, it's currently on 4.1.2. I've also tried a plain Karaf container > though (version 4.2.0.M1) and get the exact same problem there. This has been > discussed in the openHAB forum here: > [https://community.openhab.org/t/timeout-in-karaf-console/35443] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-3152) scp does not work under Windows
[
https://issues.apache.org/jira/browse/KARAF-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353690#comment-16353690
]
Guillaume Nodet commented on KARAF-3152:
This is a different issue and I've been able to reproduce it with cyberduck on
4.2.x branch. I'm investigating, could you please open a new jira ?
> scp does not work under Windows
> ---
>
> Key: KARAF-3152
> URL: https://issues.apache.org/jira/browse/KARAF-3152
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 2.3.4
> Environment: Win7
>Reporter: Martin Lichtin
>Assignee: Guillaume Nodet
>Priority: Major
>
> $ scp -P 8101 karaf@localhost:lock .
> causes
> {noformat}
> Exception in thread "ScpCommand: [scp, -f, lock]"
> java.lang.IllegalArgumentException: The path is not relative to KARAF_BASE.
> Fo2014-08-08 18:05:59,585 | INFO | NioProcessor-2 | ChannelSession
> | hd.server.channel.ChannelSession 373 | 23 -
> org.apache.sshd.core - 0.8.0 | Executing command: scp -f lock
> r security reason, it's not allowed.
> at
> org.apache.karaf.shell.ssh.KarafFileSystemView.getFile(KarafFileSystemView.java:51)
> at
> org.apache.karaf.shell.ssh.KarafFileSystemView.getFile(KarafFileSystemView.java:39)
> at org.apache.sshd.server.command.ScpCommand.run(ScpCommand.java:212)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (KARAF-1954) NullPointerException on custom Karaf shell command: ClassNotFoundException: org.apache.felix.service.command.Function not found
[
https://issues.apache.org/jira/browse/KARAF-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed KARAF-1954.
--
Resolution: Won't Fix
> NullPointerException on custom Karaf shell command: ClassNotFoundException:
> org.apache.felix.service.command.Function not found
> ---
>
> Key: KARAF-1954
> URL: https://issues.apache.org/jira/browse/KARAF-1954
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 2.3.0
> Environment: Karaf
> Karaf version 2.3.0
> Karaf home /home/ceefour/git/bippo-commerce5/karaf
> Karaf base /home/ceefour/git/bippo-commerce5/karaf
> OSGi Framework org.apache.felix.framework - 4.0.3
> JVM
> Java Virtual MachineOpenJDK 64-Bit Server VM version 23.2-b09
> Version 1.7.0_07
> Vendor Oracle Corporation
> Uptime 6 hours 27 minutes
> Total compile time 35.832 seconds
> Threads
> Live threads187
> Daemon threads 169
> Peak216
> Total started 1656
> Memory
> Current heap size 147,445 kbytes
> Maximum heap size 466,048 kbytes
> Committed heap size 275,200 kbytes
> Pending objects 0
> Garbage collector Name = 'PS Scavenge', Collections = 1648, Time
> = 7.910 seconds
> Garbage collector Name = 'PS MarkSweep', Collections = 10, Time =
> 1.679 seconds
> Classes
> Current classes loaded 12,470
> Total classes loaded17,370
> Total classes unloaded 4,900
> Operating system
> NameLinux version 3.2.0-32-generic
> Architectureamd64
> Processors 8
>Reporter: Hendy Irawan
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Attachments: karaf1954.zip
>
>
> I have a shell command extending OsgiSupportCommand which always throws
> NullPointerException no matter what.
> {code}
> karaf@root> as:json
> Error executing command: java.lang.NullPointerException
> {code}
> trace:
> {code}
> 2012-10-19 21:10:43,862 | ERROR | l Console Thread | ServiceRecipe
> | lueprint.container.ServiceRecipe 294 | 7 -
> org.apache.aries.blueprint.core - 1.0.1 | Error retrieving service from
> ServiceRecipe[name='shell-350']
> java.lang.ClassNotFoundException: org.apache.felix.service.command.Function
> not found by soluvas-json [1774]
> at
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1460)[org.apache.felix.framework-4.0.3.jar:]
> at
> org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72)[org.apache.felix.framework-4.0.3.jar:]
> at
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843)[org.apache.felix.framework-4.0.3.jar:]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)[:1.7.0_07]
> at
> org.apache.felix.framework.Felix.loadBundleClass(Felix.java:1723)[org.apache.felix.framework-4.0.3.jar:]
> at
> org.apache.felix.framework.BundleImpl.loadClass(BundleImpl.java:926)[org.apache.felix.framework-4.0.3.jar:]
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.loadClass(BlueprintContainerImpl.java:401)[7:org.apache.aries.blueprint.core:1.0.1]
> at
> org.apache.aries.blueprint.container.ServiceRecipe.convertStringsToClasses(ServiceRecipe.java:416)[7:org.apache.aries.blueprint.core:1.0.1]
> at
> org.apache.aries.blueprint.container.ServiceRecipe.getClassesForProxying(ServiceRecipe.java:406)[7:org.apache.aries.blueprint.core:1.0.1]
> at
> org.apache.aries.blueprint.container.ServiceRecipe.createService(ServiceRecipe.java:288)[7:org.apache.aries.blueprint.core:1.0.1]
> at
> org.apache.aries.blueprint.container.ServiceRecipe.internalGetService(ServiceRecipe.java:247)[7:org.apache.aries.blueprint.core:1.0.1]
> at
> org.apache.aries.blueprint.container.ServiceRecipe.getService(ServiceRecipe.java:349)[7:org.apache.aries.blueprint.core:1.0.1]
> at
> org.apache.aries.blueprint.container.ServiceRecipe$TriggerServiceFactory.getService(ServiceRecipe.java:502)[7:org.apache.aries.blueprint.core:1.0.1]
> at
> org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:308)[org.apache.felix.framework-4.0.3.jar:]
> at
> org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:219)[org.apache.felix.framework-4.0.3.jar:]
> at
>
[jira] [Closed] (KARAF-5392) watch command throws NPE
[
https://issues.apache.org/jira/browse/KARAF-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed KARAF-5392.
--
Resolution: Duplicate
Assignee: Guillaume Nodet
> watch command throws NPE
>
>
> Key: KARAF-5392
> URL: https://issues.apache.org/jira/browse/KARAF-5392
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.2
>Reporter: Claus Ibsen
>Assignee: Guillaume Nodet
>Priority: Minor
>
> If you run the watch command you get a NPE
> {code}
> java.lang.NullPointerException
> at org.apache.felix.gogo.jline.Posix.lambda$watch$6(Posix.java:872)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5469) Installation of a non blueprint feature triggers the installation of the blueprint compatibility bundle
[
https://issues.apache.org/jira/browse/KARAF-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353609#comment-16353609
]
Guillaume Nodet commented on KARAF-5469:
The cxf-http-jetty 3.1.x bundle does require the
org.apache.aries.blueprint.core.compatibility bundle. The question is more how
did you manage to have it not installed in the first place ?
What you see is just the resolver fixing this missing bundle.
> Installation of a non blueprint feature triggers the installation of the
> blueprint compatibility bundle
> ---
>
> Key: KARAF-5469
> URL: https://issues.apache.org/jira/browse/KARAF-5469
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
>Affects Versions: 4.1.3
>Reporter: Joao Assuncao
>Priority: Major
>
> In Karaf 4.1.3 when installing some custom made features karaf triggers the
> installation of the org.apache.aries.blueprint.core.compatibility bundle
> causing a refresh of all bundles and a Karaf shutdown.
> None of the bundles in the feature uses blueprint and the more exotic thing
> is that one of the bundles uses a Contional-Package instruction.
> The feature I'm trying to install:
> {{
> karaf@root()> feature:info paybox-io-modbus
> Feature paybox-io-modbus 0.1.0.SNAPSHOT
> Description:
> Modbus I/O implementation
> Feature has no configuration
> Feature has no configuration files
> Feature has no dependencies.
> Feature contains followed bundles:
> mvn:pt.brisa.common/common-service-core/1.3.0
> mvn:pt.brisa.paybox/io-api/0.1.0-SNAPSHOT
> mvn:pt.brisa.paybox/io-modbus/0.1.0-SNAPSHOT
> mvn:pt.brisa.paybox/io-commands/0.1.0-SNAPSHOT
> Feature has no conditionals.}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KARAF-5056) Error executing command: [25] Inappropriate ioctl for device with Karaf-4.1.0 in ARM (BeagleBone)
[
https://issues.apache.org/jira/browse/KARAF-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved KARAF-5056.
Resolution: Cannot Reproduce
Closing as it has been reported as fixed.
> Error executing command: [25] Inappropriate ioctl for device with Karaf-4.1.0
> in ARM (BeagleBone)
> -
>
> Key: KARAF-5056
> URL: https://issues.apache.org/jira/browse/KARAF-5056
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
> Environment: Beagle Bone Black (BeagleBoard.org Debian Image
> 2015-11-12) / (BeagleBoard.org Debian Image 2016-11-06),
> Java JDK 1.8.0_91 / 1.8.0_112
>Reporter: Alvaro Marco
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>
> When starting a fresh distribution of apache-karaf-4.1.0 on the BeagleBone
> with bin/karaf, the following is displayed (after a while...):
> {code}
> root@beaglebone:~/sandbox/apache-karaf-4.1.0# bin/karaf
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.1.0)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> Error executing command: [25] Inappropriate ioctl for device
> root@beaglebone:~/sandbox/apache-karaf-4.1.0#
> {code}
> and returns to the shell
> The karaf.log register this exception:
> {code}
> ...
> 2017-03-23T06:25:18,543 | INFO | pool-13-thread-1 | core
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
> org.osgi.jmx.framework.PackageStateMBean to MBeanServer
> com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
> osgi.core:type=packageState,version=1.5,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
> 2017-03-23T06:25:18,576 | INFO | pool-13-thread-1 | core
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
> org.osgi.jmx.framework.wiring.BundleWiringStateMBean to MBeanServer
> com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
> osgi.core:type=wiringState,version=1.1,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
> 2017-03-23T06:25:18,453 | ERROR | Karaf local console user karaf | ShellUtil
> | 43 - org.apache.karaf.shell.core - 4.1.0 | Exception
> caught while executing command
> com.sun.jna.LastErrorException: [25] Inappropriate ioctl for device
> at com.sun.jna.Native.invokeVoid(Native Method) ~[?:?]
> at com.sun.jna.Function.invoke(Function.java:374) [?:?]
> at com.sun.jna.Function.invoke(Function.java:323) [?:?]
> at com.sun.jna.Library$Handler.invoke(Library.java:236) [?:?]
> at com.sun.proxy.$Proxy35.ioctl(Unknown Source) [50:org.jline:3.1.3]
> at
> org.jline.terminal.impl.jna.linux.LinuxNativePty.getSize(LinuxNativePty.java:82)
> [50:org.jline:3.1.3]
> at
> org.jline.terminal.impl.AbstractPosixTerminal.getSize(AbstractPosixTerminal.java:58)
> [50:org.jline:3.1.3]
> at
> org.apache.karaf.shell.impl.console.JLineTerminal.getSize(JLineTerminal.java:166)
> [43:org.apache.karaf.shell.core:4.1.0]
> at
> org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:477)
> [50:org.jline:3.1.3]
> at
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:332)
> [43:org.apache.karaf.shell.core:4.1.0]
> at java.lang.Thread.run(Thread.java:745) [?:?]
> 2017-03-23T06:25:19,236 | INFO | FelixShutdown| BlueprintExtender
> | 12 - org.apache.aries.blueprint.core - 1.7.1 | Destroying
> BlueprintContainer for bundle org.apache.karaf.jaas.blueprint.config/4.1.0
> 2017-03-23T06:25:19,455 | INFO | FelixShutdown| BlueprintExtender
> | 12 - org.apache.aries.blueprint.core - 1.7.1 | Destroying
> BlueprintContainer for bundle org.apache.karaf.shell.core/4.1.0
> 2017-03-23T06:25:19,482 | INFO | pool-3-thread-1 | CommandExtension
> | 43 - org.apache.karaf.shell.core - 4.1.0 | Registering commands for
> bundle org.apache.karaf.features.command/4.1.0
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KARAF-5595) Upgrade toJLine 3.6.0 and Jansi 1.17
[ https://issues.apache.org/jira/browse/KARAF-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-5595. Resolution: Fixed Fix Version/s: 4.1.5 > Upgrade toJLine 3.6.0 and Jansi 1.17 > > > Key: KARAF-5595 > URL: https://issues.apache.org/jira/browse/KARAF-5595 > Project: Karaf > Issue Type: Dependency upgrade >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.2.0, 4.1.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5595) Upgrade toJLine 3.6.0 and Jansi 1.17
[ https://issues.apache.org/jira/browse/KARAF-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353572#comment-16353572 ] ASF subversion and git services commented on KARAF-5595: Commit 3c08df93605c96a17815736bdb46d0379de20cd0 in karaf's branch refs/heads/karaf-4.1.x from [~gnt] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=3c08df9 ] [KARAF-5595] Upgrade to JLine 3.6.0 and Jansi 1.17 > Upgrade toJLine 3.6.0 and Jansi 1.17 > > > Key: KARAF-5595 > URL: https://issues.apache.org/jira/browse/KARAF-5595 > Project: Karaf > Issue Type: Dependency upgrade >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.2.0, 4.1.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-5333) UnsupportedCharsetException: cp65001 and unprintable characters from karaf 4.1.2 console
[
https://issues.apache.org/jira/browse/KARAF-5333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved KARAF-5333.
Resolution: Fixed
This should be fixed with the upgrade to JLine 3.6.0.
> UnsupportedCharsetException: cp65001 and unprintable characters from karaf
> 4.1.2 console
> -
>
> Key: KARAF-5333
> URL: https://issues.apache.org/jira/browse/KARAF-5333
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.2
> Environment: Windows OS, Java 8
>Reporter: Xilai Dai
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.1.5, 4.2.0.M1
>
> Attachments: gitcmd.png, jline-3.4.0.jar, lucida.png,
> pax-logging-api-1.10.1.jar, pax-logging-log4j2-1.10.1.jar
>
>
> In case of Windows OS and the cp65001 CodePage setting, there is
> UnsupportedCharsetException: cp65001 happening and the console display really
> not good many of the unprintable characters showing ...
> {code}
> 2017-08-29 11:34:41,204 CM Configuration Updater (Update:
> pid=org.ops4j.pax.logging) ERROR Unable to inject fields into
> builder class for plugin type class
> org.apache.logging.log4j.core.appender.ConsoleAppender, element Console.
> java.nio.ch
> arset.UnsupportedCharsetException: cp65001
> at java.nio.charset.Charset.forName(Charset.java:531)
> at
> org.apache.logging.log4j.util.PropertiesUtil.getCharsetProperty(PropertiesUtil.java:146)
> at
> org.apache.logging.log4j.util.PropertiesUtil.getCharsetProperty(PropertiesUtil.java:134)
> at
> org.apache.logging.log4j.core.appender.ConsoleAppender$Target.getCharset(ConsoleAppender.java:85)
> at
> org.apache.logging.log4j.core.appender.ConsoleAppender$Target$1.getDefaultCharset(ConsoleAppender.java:71)
> at
> org.apache.logging.log4j.core.appender.ConsoleAppender$Builder.build(ConsoleAppender.java:218)
> at
> org.apache.logging.log4j.core.appender.ConsoleAppender$Builder.build(ConsoleAppender.java:185)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:122)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:952)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:892
> )
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:884
> )
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:508)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:232)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:244)
> at
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:545)
> at
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:261)
> at
> org.ops4j.pax.logging.log4j2.internal.PaxLoggingServiceImpl.doUpdate(PaxLoggingServiceImpl.java:213)
> at
> org.ops4j.pax.logging.log4j2.internal.PaxLoggingServiceImpl.updated(PaxLoggingServiceImpl.java:158)
> at
> org.ops4j.pax.logging.log4j2.internal.PaxLoggingServiceImpl$1ManagedPaxLoggingService.updated(PaxLoggingServi
> ceImpl.java:426)
> at
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189)
> at
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152)
> at
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85)
> at
> org.apache.felix.cm.impl.ConfigurationManager$UpdateConfiguration.run(ConfigurationManager.java:1776)
> at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:141)
> at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:109)
> at java.lang.Thread.run(Thread.java:745)
> 2017-08-29 11:34:41,214 CM Configuration Updater (Update:
> pid=org.ops4j.pax.logging) ERROR Unable to invoke factory meth
> od in class class org.apache.logging.log4j.core.appender.ConsoleAppender for
> element Console. java.lang.IllegalStateExce
> ption: No factory method found for class
> org.apache.logging.log4j.core.appender.ConsoleAppender
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.findFactoryMethod(PluginBuilder.java:224)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:130)
> at
>
[jira] [Updated] (KARAF-5333) UnsupportedCharsetException: cp65001 and unprintable characters from karaf 4.1.2 console
[
https://issues.apache.org/jira/browse/KARAF-5333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated KARAF-5333:
---
Fix Version/s: (was: 4.1.3)
4.1.5
> UnsupportedCharsetException: cp65001 and unprintable characters from karaf
> 4.1.2 console
> -
>
> Key: KARAF-5333
> URL: https://issues.apache.org/jira/browse/KARAF-5333
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.2
> Environment: Windows OS, Java 8
>Reporter: Xilai Dai
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.2.0.M1, 4.1.5
>
> Attachments: gitcmd.png, jline-3.4.0.jar, lucida.png,
> pax-logging-api-1.10.1.jar, pax-logging-log4j2-1.10.1.jar
>
>
> In case of Windows OS and the cp65001 CodePage setting, there is
> UnsupportedCharsetException: cp65001 happening and the console display really
> not good many of the unprintable characters showing ...
> {code}
> 2017-08-29 11:34:41,204 CM Configuration Updater (Update:
> pid=org.ops4j.pax.logging) ERROR Unable to inject fields into
> builder class for plugin type class
> org.apache.logging.log4j.core.appender.ConsoleAppender, element Console.
> java.nio.ch
> arset.UnsupportedCharsetException: cp65001
> at java.nio.charset.Charset.forName(Charset.java:531)
> at
> org.apache.logging.log4j.util.PropertiesUtil.getCharsetProperty(PropertiesUtil.java:146)
> at
> org.apache.logging.log4j.util.PropertiesUtil.getCharsetProperty(PropertiesUtil.java:134)
> at
> org.apache.logging.log4j.core.appender.ConsoleAppender$Target.getCharset(ConsoleAppender.java:85)
> at
> org.apache.logging.log4j.core.appender.ConsoleAppender$Target$1.getDefaultCharset(ConsoleAppender.java:71)
> at
> org.apache.logging.log4j.core.appender.ConsoleAppender$Builder.build(ConsoleAppender.java:218)
> at
> org.apache.logging.log4j.core.appender.ConsoleAppender$Builder.build(ConsoleAppender.java:185)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:122)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:952)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:892
> )
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:884
> )
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:508)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:232)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:244)
> at
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:545)
> at
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:261)
> at
> org.ops4j.pax.logging.log4j2.internal.PaxLoggingServiceImpl.doUpdate(PaxLoggingServiceImpl.java:213)
> at
> org.ops4j.pax.logging.log4j2.internal.PaxLoggingServiceImpl.updated(PaxLoggingServiceImpl.java:158)
> at
> org.ops4j.pax.logging.log4j2.internal.PaxLoggingServiceImpl$1ManagedPaxLoggingService.updated(PaxLoggingServi
> ceImpl.java:426)
> at
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189)
> at
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152)
> at
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85)
> at
> org.apache.felix.cm.impl.ConfigurationManager$UpdateConfiguration.run(ConfigurationManager.java:1776)
> at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:141)
> at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:109)
> at java.lang.Thread.run(Thread.java:745)
> 2017-08-29 11:34:41,214 CM Configuration Updater (Update:
> pid=org.ops4j.pax.logging) ERROR Unable to invoke factory meth
> od in class class org.apache.logging.log4j.core.appender.ConsoleAppender for
> element Console. java.lang.IllegalStateExce
> ption: No factory method found for class
> org.apache.logging.log4j.core.appender.ConsoleAppender
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.findFactoryMethod(PluginBuilder.java:224)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:130)
> at
>
[jira] [Reopened] (KARAF-5595) Upgrade toJLine 3.6.0 and Jansi 1.17
[ https://issues.apache.org/jira/browse/KARAF-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reopened KARAF-5595: We need to upgrade jline on 4.1.x too. > Upgrade toJLine 3.6.0 and Jansi 1.17 > > > Key: KARAF-5595 > URL: https://issues.apache.org/jira/browse/KARAF-5595 > Project: Karaf > Issue Type: Dependency upgrade >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
