[jira] [Updated] (KARAF-6975) "java.lang.OutOfMemoryError: GC overhead limit exceeded" thrown while executing 1000s commands via shell:source
[
https://issues.apache.org/jira/browse/KARAF-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-6975:
--
Environment: Tested with apache-karafa-4.2.10 and 4.2.19 in ubuntu 18 and
JDK 8. (was: I tested with apache-karafa-4.2.10 and 4.2.19 in ubuntu 18 and
JDK 8.)
> "java.lang.OutOfMemoryError: GC overhead limit exceeded" thrown while
> executing 1000s commands via shell:source
> ---
>
> Key: KARAF-6975
> URL: https://issues.apache.org/jira/browse/KARAF-6975
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.9, 4.2.10
> Environment: Tested with apache-karafa-4.2.10 and 4.2.19 in ubuntu 18
> and JDK 8.
>Reporter: Lijun Liao
>Priority: Major
> Attachments: test.script
>
>
> Steps to reproduce the exception:
> # Start karaf with bin/karaf
> # Execute shell:source /path/to/test.script (see attachment)
> Error shown in the karaf console:
> {quote}round 2326
> Exception in thread "pool-5-thread-52" java.lang.OutOfMemoryError: GC
> overhead limit exceeded
> Error executing command: java.lang.reflect.InvocationTargetException
> {quote}
> Error in the data/logs/karaf.log
> {quote}2020-12-19T20:46:55,963 | INFO | pipe-source test.script |
> SourceAction | 35 - org.apache.karaf.
> shell.commands - 4.2.10 | Printing file:
> /home/lliao/Downloads/apache-karaf-4.2.10/test.script
> 2020-12-19T20:47:01,684 | ERROR | Karaf local console user karaf | ShellUtil
> | 36 - org.apache
> .karaf.shell.core - 4.2.10 | Exception caught while executing command
> java.lang.reflect.InvocationTargetException: null
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_272]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[?:1.8.0_272]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_272]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_272]
> at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:143)
> ~[?:?]
> at
> org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.lambda$wrap$0(SessionFactoryImpl.java:218)
> ~[?:?]
> at
> org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.execute(SessionFactoryImpl.java:264)
> ~[?:?]
> at
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
> ~[?:?]
> at
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
> ~[?:?]
> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:599) ~[?:?]
> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:526)
> ~[?:?]
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:415) ~[?:?]
> at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:416) ~[?:?]
> at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229) ~[?:?]
> at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59) ~[?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_272]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> ~[?:1.8.0_272]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> ~[?:1.8.0_272]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_272]
> Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (KARAF-6975) "java.lang.OutOfMemoryError: GC overhead limit exceeded" thrown while executing 1000s commands via shell:source
[
https://issues.apache.org/jira/browse/KARAF-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-6975:
--
Attachment: test.script
> "java.lang.OutOfMemoryError: GC overhead limit exceeded" thrown while
> executing 1000s commands via shell:source
> ---
>
> Key: KARAF-6975
> URL: https://issues.apache.org/jira/browse/KARAF-6975
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.9, 4.2.10
> Environment: I tested with apache-karafa-4.2.10 and 4.2.19 in ubuntu
> 18 and JDK 8.
>Reporter: Lijun Liao
>Priority: Major
> Attachments: test.script
>
>
> Copy the following test script to a file, called test.script
> {{i = 0}}
> {{list1 = [1 2 3 4 5 6 7 8 9 10]; each ($list1) {}}
> {{ list2 = [1 2 3 4 5 6 7 8 9 10]; each ($list2) {}}
> {{ list3 = [1 2 3 4 5 6 7 8 9 10]; each ($list3) {}}
> {{ list4 = [1 2 3 4 5 6 7 8 9 10]; each ($list4) {}}
> {{ list5 = [1 2 3 4 5 6 7 8 9 10]; each ($list5) {}}
> {{ date > date.txt}}
> {{ echo round %(i+=1)}}
> {{ }}}
> {{ }}}
> {{ }}}
> {{ }}}
> {{}}}
>
> Steps to reproduce the exception:
> # Start karaf with bin/karaf
> # Execute shell:source /path/to/test-ome.script
> Error shown in the karaf console:
> {quote}round 2326
> Exception in thread "pool-5-thread-52" java.lang.OutOfMemoryError: GC
> overhead limit exceeded
> Error executing command: java.lang.reflect.InvocationTargetException
> {quote}
> Error in the data/logs/karaf.log
> {quote}2020-12-19T20:46:55,963 | INFO | pipe-source test.script |
> SourceAction | 35 - org.apache.karaf.
> shell.commands - 4.2.10 | Printing file:
> /home/lliao/Downloads/apache-karaf-4.2.10/test.script
> 2020-12-19T20:47:01,684 | ERROR | Karaf local console user karaf | ShellUtil
> | 36 - org.apache
> .karaf.shell.core - 4.2.10 | Exception caught while executing command
> java.lang.reflect.InvocationTargetException: null
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_272]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[?:1.8.0_272]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_272]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_272]
> at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:143)
> ~[?:?]
> at
> org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.lambda$wrap$0(SessionFactoryImpl.java:218)
> ~[?:?]
> at
> org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.execute(SessionFactoryImpl.java:264)
> ~[?:?]
> at
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
> ~[?:?]
> at
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
> ~[?:?]
> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:599) ~[?:?]
> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:526)
> ~[?:?]
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:415) ~[?:?]
> at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:416) ~[?:?]
> at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229) ~[?:?]
> at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59) ~[?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_272]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> ~[?:1.8.0_272]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> ~[?:1.8.0_272]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_272]
> Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (KARAF-6975) "java.lang.OutOfMemoryError: GC overhead limit exceeded" thrown while executing 1000s commands via shell:source
[
https://issues.apache.org/jira/browse/KARAF-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-6975:
--
Description:
Steps to reproduce the exception:
# Start karaf with bin/karaf
# Execute shell:source /path/to/test.script (see attachment)
Error shown in the karaf console:
{quote}round 2326
Exception in thread "pool-5-thread-52" java.lang.OutOfMemoryError: GC overhead
limit exceeded
Error executing command: java.lang.reflect.InvocationTargetException
{quote}
Error in the data/logs/karaf.log
{quote}2020-12-19T20:46:55,963 | INFO | pipe-source test.script | SourceAction
| 35 - org.apache.karaf.
shell.commands - 4.2.10 | Printing file:
/home/lliao/Downloads/apache-karaf-4.2.10/test.script
2020-12-19T20:47:01,684 | ERROR | Karaf local console user karaf | ShellUtil |
36 - org.apache
.karaf.shell.core - 4.2.10 | Exception caught while executing command
java.lang.reflect.InvocationTargetException: null
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_272]
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
~[?:1.8.0_272]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[?:1.8.0_272]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_272]
at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:143)
~[?:?]
at
org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.lambda$wrap$0(SessionFactoryImpl.java:218)
~[?:?]
at
org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.execute(SessionFactoryImpl.java:264)
~[?:?]
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
~[?:?]
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
~[?:?]
at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:599) ~[?:?]
at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:526)
~[?:?]
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:415) ~[?:?]
at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:416) ~[?:?]
at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229) ~[?:?]
at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_272]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
~[?:1.8.0_272]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
~[?:1.8.0_272]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_272]
Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
{quote}
was:
Copy the following test script to a file, called test.script
{{i = 0}}
{{list1 = [1 2 3 4 5 6 7 8 9 10]; each ($list1) {}}
{{ list2 = [1 2 3 4 5 6 7 8 9 10]; each ($list2) {}}
{{ list3 = [1 2 3 4 5 6 7 8 9 10]; each ($list3) {}}
{{ list4 = [1 2 3 4 5 6 7 8 9 10]; each ($list4) {}}
{{ list5 = [1 2 3 4 5 6 7 8 9 10]; each ($list5) {}}
{{ date > date.txt}}
{{ echo round %(i+=1)}}
{{ }}}
{{ }}}
{{ }}}
{{ }}}
{{}}}
Steps to reproduce the exception:
# Start karaf with bin/karaf
# Execute shell:source /path/to/test-ome.script
Error shown in the karaf console:
{quote}round 2326
Exception in thread "pool-5-thread-52" java.lang.OutOfMemoryError: GC overhead
limit exceeded
Error executing command: java.lang.reflect.InvocationTargetException
{quote}
Error in the data/logs/karaf.log
{quote}2020-12-19T20:46:55,963 | INFO | pipe-source test.script | SourceAction
| 35 - org.apache.karaf.
shell.commands - 4.2.10 | Printing file:
/home/lliao/Downloads/apache-karaf-4.2.10/test.script
2020-12-19T20:47:01,684 | ERROR | Karaf local console user karaf | ShellUtil |
36 - org.apache
.karaf.shell.core - 4.2.10 | Exception caught while executing command
java.lang.reflect.InvocationTargetException: null
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_272]
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
~[?:1.8.0_272]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[?:1.8.0_272]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_272]
at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:143)
~[?:?]
at
org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.lambda$wrap$0(SessionFactoryImpl.java:218)
~[?:?]
at
org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.execute(SessionFactoryImpl.java:264)
~[?:?]
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
~[?:?]
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
~[?:?]
at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:599)
[jira] [Created] (KARAF-6975) "java.lang.OutOfMemoryError: GC overhead limit exceeded" thrown while executing 1000s commands via shell:source
Lijun Liao created KARAF-6975:
-
Summary: "java.lang.OutOfMemoryError: GC overhead limit exceeded"
thrown while executing 1000s commands via shell:source
Key: KARAF-6975
URL: https://issues.apache.org/jira/browse/KARAF-6975
Project: Karaf
Issue Type: Bug
Components: karaf
Affects Versions: 4.2.10, 4.2.9
Environment: I tested with apache-karafa-4.2.10 and 4.2.19 in ubuntu
18 and JDK 8.
Reporter: Lijun Liao
Copy the following test script to a file, called test.script
{{i = 0}}
{{list1 = [1 2 3 4 5 6 7 8 9 10]; each ($list1) {}}
{{ list2 = [1 2 3 4 5 6 7 8 9 10]; each ($list2) {}}
{{ list3 = [1 2 3 4 5 6 7 8 9 10]; each ($list3) {}}
{{ list4 = [1 2 3 4 5 6 7 8 9 10]; each ($list4) {}}
{{ list5 = [1 2 3 4 5 6 7 8 9 10]; each ($list5) {}}
{{ date > date.txt}}
{{ echo round %(i+=1)}}
{{ }}}
{{ }}}
{{ }}}
{{ }}}
{{}}}
Steps to reproduce the exception:
# Start karaf with bin/karaf
# Execute shell:source /path/to/test-ome.script
Error shown in the karaf console:
{quote}round 2326
Exception in thread "pool-5-thread-52" java.lang.OutOfMemoryError: GC overhead
limit exceeded
Error executing command: java.lang.reflect.InvocationTargetException
{quote}
Error in the data/logs/karaf.log
{quote}2020-12-19T20:46:55,963 | INFO | pipe-source test.script | SourceAction
| 35 - org.apache.karaf.
shell.commands - 4.2.10 | Printing file:
/home/lliao/Downloads/apache-karaf-4.2.10/test.script
2020-12-19T20:47:01,684 | ERROR | Karaf local console user karaf | ShellUtil |
36 - org.apache
.karaf.shell.core - 4.2.10 | Exception caught while executing command
java.lang.reflect.InvocationTargetException: null
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_272]
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
~[?:1.8.0_272]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[?:1.8.0_272]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_272]
at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:143)
~[?:?]
at
org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.lambda$wrap$0(SessionFactoryImpl.java:218)
~[?:?]
at
org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.execute(SessionFactoryImpl.java:264)
~[?:?]
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
~[?:?]
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
~[?:?]
at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:599) ~[?:?]
at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:526)
~[?:?]
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:415) ~[?:?]
at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:416) ~[?:?]
at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229) ~[?:?]
at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_272]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
~[?:1.8.0_272]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
~[?:1.8.0_272]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_272]
Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KARAF-6344) AsyncLogger fails due to bug in pax-logging
[ https://issues.apache.org/jira/browse/KARAF-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875850#comment-16875850 ] Lijun Liao commented on KARAF-6344: --- I am not sure, whether the following behavior is related to this issue. In karaf 4.2.6, my bundle will not log anymore. My bundle use the SLF4J API to log the events. You may test it with any user bundle. > AsyncLogger fails due to bug in pax-logging > --- > > Key: KARAF-6344 > URL: https://issues.apache.org/jira/browse/KARAF-6344 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.2.6 >Reporter: Rico Neubauer >Assignee: Jean-Baptiste Onofré >Priority: Major > Labels: logging > Fix For: 4.3.0, 4.2.7 > > > Just as reference: > Karaf 4.2.6 updated to pax-logging 1.10.2, which introduced this regression: > [https://ops4j1.jira.com/browse/PAXLOGGING-260] > This leads to the logger breaking if e.g. Karaf gets configured for async > logging _log4j2.rootLogger.type = asyncRoot_ in logging config. Exception > below. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5761) Print better usage of commands in karaf shell
[
https://issues.apache.org/jira/browse/KARAF-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-5761:
--
Description:
commands in karaf shell, extend the usage (help page) to indicate that an
option is required and/or multi-valued, and the same for arguments.
An example usage in the current version is as follows:
SYNTAX
xi:demo-cmd [options] arg1 arg2
ARGUMENTS
arg1
Description of arg1
arg2
Description of arg2
OPTIONS
--opt1
Description of opt1
--opt2
Description of opt2
--opt3
Description of opt3
It should be extended to
SYNTAX
xi:demo-cmd [options] arg1 arg2
ARGUMENTS
arg1
Description of arg1
(required, multi-valued)
arg2
Description of arg2
(required)
OPTIONS
--opt1
Description of opt1
(required, multi-valued)
--opt2
Description of opt2
(required)
--opt3
Description of opt3
(multi-valued)
was:
commands in karaf shell, extend the usage (help page) to indicate that an
option is required and/or multi-valued, and the same for arguments.
An example usage in the current version is as follows:
{{SYNTAX
xi:demo-cmd [options] arg1 arg2
ARGUMENTS
arg1
Description of arg1
arg2
Description of arg2
OPTIONS
--opt1
Description of opt1
--opt2
Description of opt2
--opt3
Description of opt3
}}
It should be extended to
{{SYNTAX
xi:demo-cmd [options] arg1 arg2
ARGUMENTS
arg1
Description of arg1
(required, multi-valued)
arg2
Description of arg2
(required)
OPTIONS
--opt1
Description of opt1
(required, multi-valued)
--opt2
Description of opt2
(required)
--opt3
Description of opt3
(multi-valued)
}}
> Print better usage of commands in karaf shell
> -
>
> Key: KARAF-5761
> URL: https://issues.apache.org/jira/browse/KARAF-5761
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-shell
>Affects Versions: 4.2.0
>Reporter: Lijun Liao
>Priority: Minor
> Fix For: 4.2.1
>
>
> commands in karaf shell, extend the usage (help page) to indicate that an
> option is required and/or multi-valued, and the same for arguments.
> An example usage in the current version is as follows:
> SYNTAX
> xi:demo-cmd [options] arg1 arg2
> ARGUMENTS
> arg1
> Description of arg1
> arg2
> Description of arg2
> OPTIONS
> --opt1
> Description of opt1
> --opt2
> Description of opt2
> --opt3
> Description of opt3
> It should be extended to
> SYNTAX
> xi:demo-cmd [options] arg1 arg2
> ARGUMENTS
> arg1
> Description of arg1
> (required, multi-valued)
> arg2
> Description of arg2
> (required)
> OPTIONS
> --opt1
> Description of opt1
> (required, multi-valued)
> --opt2
> Description of opt2
> (required)
> --opt3
> Description of opt3
> (multi-valued)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KARAF-5761) Print better usage of commands in karaf shell
Lijun Liao created KARAF-5761:
-
Summary: Print better usage of commands in karaf shell
Key: KARAF-5761
URL: https://issues.apache.org/jira/browse/KARAF-5761
Project: Karaf
Issue Type: New Feature
Components: karaf-shell
Affects Versions: 4.2.0
Reporter: Lijun Liao
Fix For: 4.2.1
commands in karaf shell, extend the usage (help page) to indicate that an
option is required and/or multi-valued, and the same for arguments.
An example usage in the current version is as follows:
{{SYNTAX
xi:demo-cmd [options] arg1 arg2
ARGUMENTS
arg1
Description of arg1
arg2
Description of arg2
OPTIONS
--opt1
Description of opt1
--opt2
Description of opt2
--opt3
Description of opt3
}}
It should be extended to
{{SYNTAX
xi:demo-cmd [options] arg1 arg2
ARGUMENTS
arg1
Description of arg1
(required, multi-valued)
arg2
Description of arg2
(required)
OPTIONS
--opt1
Description of opt1
(required, multi-valued)
--opt2
Description of opt2
(required)
--opt3
Description of opt3
(multi-valued)
}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5728) Upgrade to Jetty 9.4.7.v20170914
[ https://issues.apache.org/jira/browse/KARAF-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16460115#comment-16460115 ] Lijun Liao commented on KARAF-5728: --- Is there any reason to use 9.4.7.v20170914 instead the latest 9.4.9.v20180320? > Upgrade to Jetty 9.4.7.v20170914 > > > Key: KARAF-5728 > URL: https://issues.apache.org/jira/browse/KARAF-5728 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5724) Add support of JDK 10
[
https://issues.apache.org/jira/browse/KARAF-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459958#comment-16459958
]
Lijun Liao commented on KARAF-5724:
---
This indicates karaf should be tested with both OpenJDK and Oracle JDK.
> Add support of JDK 10
> -
>
> Key: KARAF-5724
> URL: https://issues.apache.org/jira/browse/KARAF-5724
> Project: Karaf
> Issue Type: New Feature
>Affects Versions: 4.2.0
> Environment: Java Version:
> {{$JAVA_HOME/bin/java -version}}
> {{java version "10.0.1" 2018-04-17}}
> {{Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)}}
> {{Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)}}
> OS:
> {{Ubuntu 64 Bit 16.04}}
>Reporter: Lijun Liao
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.1
>
>
> Due to the missing module corba in JDK 10 (tested with the
> serverjre-10.0.1_linux-x64), karaf cannot be started.
> Here is the error message:
> {{apache-karaf-minimal-4.2.0$ bin/karaf }}
> {{Error occurred during initialization of boot layer}}
> {{java.lang.module.FindException: Module java.corba not found}}
> Removing "java.corba" from the line "--add-modules
> java.xml.ws.annotation,java.corba,java.transaction,java.xml.bind,java.xml.ws"
> in bin/karaf fixed the above error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5725) Add support of JDK 11
[ https://issues.apache.org/jira/browse/KARAF-5725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459950#comment-16459950 ] Lijun Liao commented on KARAF-5725: --- The version problem can be solved via the solution in KARAF-5641. But there are many other problems like modules, exported packages, etc. > Add support of JDK 11 > - > > Key: KARAF-5725 > URL: https://issues.apache.org/jira/browse/KARAF-5725 > Project: Karaf > Issue Type: New Feature >Affects Versions: 4.2.0 >Reporter: Lijun Liao >Priority: Major > Fix For: 4.2.1 > > > JDK 11 is the first JDK with LTS (at least 5 years) since version 9. It will > be released in September 2018. Currently the EA for JDK 11 is available under > http://jdk.java.net/11/. So, if possible, please consider it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (KARAF-5722) Upgrade to ASM 6.1.1
[ https://issues.apache.org/jira/browse/KARAF-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458155#comment-16458155 ] Lijun Liao edited comment on KARAF-5722 at 4/30/18 6:36 AM: Please also adapt the file proxy/proxy-impl/src/main/java/org/apache/aries/proxy/impl/ProxyUtils.java in the aries project to support Java 10, 11, and so on. Since release 9, JDK has different release cycle. Every 6 months a new JDK with incremented main version (JDK 10, 11, ...) will be released. Please also consider it. The aries version in karaf 4.2.0 does not like JDK 10+, I got error (as in attachment karaf-4.2.0-error-in-jdk10.txt) in case of exporting a service via aries blueprint (as configured in attachment blueprint.xml). was (Author: lliao): Please also adapt the file proxy/proxy-impl/src/main/java/org/apache/aries/proxy/impl/ProxyUtils.java in the aries project to support Java 10, 11, and so on. Since release 9, JDK has different release cycle. Every 6 months a new JDK with incremented main version (JDK 10, 11, ...) will be released. Please also consider it. The aries version in karaf 4.2.0 does not like JDK 10+, I got the following error in case of exporting a service via aries blueprint. > Upgrade to ASM 6.1.1 > > > Key: KARAF-5722 > URL: https://issues.apache.org/jira/browse/KARAF-5722 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.1.6, 4.2.1 > > Attachments: blueprint.xml, karaf-4.2.0-error-in-jdk10.txt > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5722) Upgrade to ASM 6.1.1
[ https://issues.apache.org/jira/browse/KARAF-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-5722: -- Attachment: blueprint.xml > Upgrade to ASM 6.1.1 > > > Key: KARAF-5722 > URL: https://issues.apache.org/jira/browse/KARAF-5722 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.1.6, 4.2.1 > > Attachments: blueprint.xml, karaf-4.2.0-error-in-jdk10.txt > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5722) Upgrade to ASM 6.1.1
[ https://issues.apache.org/jira/browse/KARAF-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-5722: -- Attachment: (was: config.xml) > Upgrade to ASM 6.1.1 > > > Key: KARAF-5722 > URL: https://issues.apache.org/jira/browse/KARAF-5722 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.1.6, 4.2.1 > > Attachments: karaf-4.2.0-error-in-jdk10.txt > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5722) Upgrade to ASM 6.1.1
[ https://issues.apache.org/jira/browse/KARAF-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-5722: -- Attachment: config.xml > Upgrade to ASM 6.1.1 > > > Key: KARAF-5722 > URL: https://issues.apache.org/jira/browse/KARAF-5722 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.1.6, 4.2.1 > > Attachments: config.xml, karaf-4.2.0-error-in-jdk10.txt > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5722) Upgrade to ASM 6.1.1
[ https://issues.apache.org/jira/browse/KARAF-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-5722: -- Attachment: karaf-4.2.0-error-in-jdk10.txt > Upgrade to ASM 6.1.1 > > > Key: KARAF-5722 > URL: https://issues.apache.org/jira/browse/KARAF-5722 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.1.6, 4.2.1 > > Attachments: karaf-4.2.0-error-in-jdk10.txt > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (KARAF-5722) Upgrade to ASM 6.1.1
[ https://issues.apache.org/jira/browse/KARAF-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458155#comment-16458155 ] Lijun Liao edited comment on KARAF-5722 at 4/30/18 6:07 AM: Please also adapt the file proxy/proxy-impl/src/main/java/org/apache/aries/proxy/impl/ProxyUtils.java in the aries project to support Java 10, 11, and so on. Since release 9, JDK has different release cycle. Every 6 months a new JDK with incremented main version (JDK 10, 11, ...) will be released. Please also consider it. The aries version in karaf 4.2.0 does not like JDK 10+, I got the following error in case of exporting a service via aries blueprint. was (Author: lliao): Please also adapt the file proxy/proxy-impl/src/main/java/org/apache/aries/proxy/impl/ProxyUtils.java in the aries project to support Java 10, 11, and so on. Since release 9, JDK has different release cycle. Every 6 months a new JDK with incremented main version (JDK 10, 11, ...) will be released. Please also consider it. The aries version in karaf 4.2.0 does not like JDK 10+, I got the following error if I want to export a service via aries blueprint. 2018-04-30T07:57:49,830 | ERROR | features-3-thread-1 | BlueprintContainerImpl | 18 - org.apache.aries.blueprint.core - 1.9.0 | Unable to start blueprint container for bundle org.xipki.password/3.1.0.SNAPSHOT org.osgi.service.blueprint.container.ComponentDefinitionException: java.lang.IllegalArgumentException: Invalid Java version 54 at org.apache.aries.blueprint.container.ReferenceRecipe.internalCreate(ReferenceRecipe.java:141) ~[?:?] at org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:81) ~[?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?] at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:90) ~[?:?] at org.apache.aries.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:810) ~[?:?] at org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:784) ~[?:?] at org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:765) ~[?:?] at org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:699) ~[?:?] at org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:666) ~[?:?] at org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:81) ~[?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?] at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:90) ~[?:?] at org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:360) ~[?:?] at org.apache.aries.blueprint.container.BlueprintRepository.createInstance(BlueprintRepository.java:338) ~[?:?] at org.apache.aries.blueprint.container.BlueprintRepository.create(BlueprintRepository.java:162) ~[?:?] at org.apache.aries.blueprint.container.BlueprintContainerImpl.processProcessors(BlueprintContainerImpl.java:551) ~[?:?] at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:397) ~[?:?] at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:278) ~[?:?] at org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:299) ~[?:?] at org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:268) ~[?:?] at org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:264) ~[?:?] at org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:254) ~[?:?] at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500) ~[?:?] at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433) ~[?:?] at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725) ~[?:?] at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463) ~[?:?] at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422) ~[?:?] at org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1179) ~[?:?] at org.apache.felix.framework.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:730) ~[?:?] at org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:485) ~[?:?] at
[jira] [Comment Edited] (KARAF-5722) Upgrade to ASM 6.1.1
[ https://issues.apache.org/jira/browse/KARAF-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458155#comment-16458155 ] Lijun Liao edited comment on KARAF-5722 at 4/30/18 6:05 AM: Please also adapt the file proxy/proxy-impl/src/main/java/org/apache/aries/proxy/impl/ProxyUtils.java in the aries project to support Java 10, 11, and so on. Since release 9, JDK has different release cycle. Every 6 months a new JDK with incremented main version (JDK 10, 11, ...) will be released. Please also consider it. The aries version in karaf 4.2.0 does not like JDK 10+, I got the following error if I want to export a service via aries blueprint. 2018-04-30T07:57:49,830 | ERROR | features-3-thread-1 | BlueprintContainerImpl | 18 - org.apache.aries.blueprint.core - 1.9.0 | Unable to start blueprint container for bundle org.xipki.password/3.1.0.SNAPSHOT org.osgi.service.blueprint.container.ComponentDefinitionException: java.lang.IllegalArgumentException: Invalid Java version 54 at org.apache.aries.blueprint.container.ReferenceRecipe.internalCreate(ReferenceRecipe.java:141) ~[?:?] at org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:81) ~[?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?] at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:90) ~[?:?] at org.apache.aries.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:810) ~[?:?] at org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:784) ~[?:?] at org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:765) ~[?:?] at org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:699) ~[?:?] at org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:666) ~[?:?] at org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:81) ~[?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?] at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:90) ~[?:?] at org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:360) ~[?:?] at org.apache.aries.blueprint.container.BlueprintRepository.createInstance(BlueprintRepository.java:338) ~[?:?] at org.apache.aries.blueprint.container.BlueprintRepository.create(BlueprintRepository.java:162) ~[?:?] at org.apache.aries.blueprint.container.BlueprintContainerImpl.processProcessors(BlueprintContainerImpl.java:551) ~[?:?] at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:397) ~[?:?] at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:278) ~[?:?] at org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:299) ~[?:?] at org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:268) ~[?:?] at org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:264) ~[?:?] at org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:254) ~[?:?] at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500) ~[?:?] at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433) ~[?:?] at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725) ~[?:?] at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463) ~[?:?] at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422) ~[?:?] at org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1179) ~[?:?] at org.apache.felix.framework.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:730) ~[?:?] at org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:485) ~[?:?] at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4579) ~[?:?] at org.apache.felix.framework.Felix.startBundle(Felix.java:2174) ~[?:?] at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) ~[?:?] at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) ~[?:?] at org.apache.karaf.features.internal.service.BundleInstallSupportImpl.startBundle(BundleInstallSupportImpl.java:161) ~[?:?] at
[jira] [Updated] (KARAF-5724) Add support of JDK 10
[
https://issues.apache.org/jira/browse/KARAF-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-5724:
--
Environment:
Java Version:
{{$JAVA_HOME/bin/java -version}}
{{java version "10.0.1" 2018-04-17}}
{{Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)}}
{{Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)}}
OS:
{{Ubuntu 64 Bit 16.04}}
Description:
Due to the missing module corba in JDK 10 (tested with the
serverjre-10.0.1_linux-x64), karaf cannot be started.
Here is the error message:
{{apache-karaf-minimal-4.2.0$ bin/karaf }}
{{Error occurred during initialization of boot layer}}
{{java.lang.module.FindException: Module java.corba not found}}
Removing "java.corba" from the line "--add-modules
java.xml.ws.annotation,java.corba,java.transaction,java.xml.bind,java.xml.ws"
in bin/karaf fixed the above error.
was:Due to the missing module corba in JDK 10 (tested with the
serverjre-10.0.1_linux-x64), karaf cannot be started.
> Add support of JDK 10
> -
>
> Key: KARAF-5724
> URL: https://issues.apache.org/jira/browse/KARAF-5724
> Project: Karaf
> Issue Type: New Feature
>Affects Versions: 4.2.0
> Environment: Java Version:
> {{$JAVA_HOME/bin/java -version}}
> {{java version "10.0.1" 2018-04-17}}
> {{Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)}}
> {{Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)}}
> OS:
> {{Ubuntu 64 Bit 16.04}}
>Reporter: Lijun Liao
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.1
>
>
> Due to the missing module corba in JDK 10 (tested with the
> serverjre-10.0.1_linux-x64), karaf cannot be started.
> Here is the error message:
> {{apache-karaf-minimal-4.2.0$ bin/karaf }}
> {{Error occurred during initialization of boot layer}}
> {{java.lang.module.FindException: Module java.corba not found}}
> Removing "java.corba" from the line "--add-modules
> java.xml.ws.annotation,java.corba,java.transaction,java.xml.bind,java.xml.ws"
> in bin/karaf fixed the above error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-5724) Add support of JDK 10
[ https://issues.apache.org/jira/browse/KARAF-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-5724: -- Affects Version/s: 4.2.0 Fix Version/s: 4.2.1 > Add support of JDK 10 > - > > Key: KARAF-5724 > URL: https://issues.apache.org/jira/browse/KARAF-5724 > Project: Karaf > Issue Type: New Feature >Affects Versions: 4.2.0 >Reporter: Lijun Liao >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.1 > > > Due to the missing module corba in JDK 10 (tested with the > serverjre-10.0.1_linux-x64), karaf cannot be started. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5725) Add support of JDK 11
[ https://issues.apache.org/jira/browse/KARAF-5725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-5725: -- Affects Version/s: 4.2.0 Fix Version/s: 4.2.1 > Add support of JDK 11 > - > > Key: KARAF-5725 > URL: https://issues.apache.org/jira/browse/KARAF-5725 > Project: Karaf > Issue Type: New Feature >Affects Versions: 4.2.0 >Reporter: Lijun Liao >Priority: Major > Fix For: 4.2.1 > > > JDK 11 is the first JDK with LTS (at least 5 years) since version 9. It will > be released in September 2018. Currently the EA for JDK 11 is available under > http://jdk.java.net/11/. So, if possible, please consider it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (KARAF-5722) Upgrade to ASM 6.1.1
[ https://issues.apache.org/jira/browse/KARAF-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458155#comment-16458155 ] Lijun Liao edited comment on KARAF-5722 at 4/29/18 8:34 PM: Please also adapt the file proxy/proxy-impl/src/main/java/org/apache/aries/proxy/impl/ProxyUtils.java in the aries project to support Java 10, 11, and so on. Since release 9, JDK has different release cycle. Every 6 months a new JDK with incremented main version (JDK 10, 11, ...) will be released. Please also consider it. was (Author: lliao): Please also adapt the file proxy/proxy-impl/src/main/java/org/apache/aries/proxy/impl/ProxyUtils.java to support Java 10, 11, and so on. Since release 9, JDK has different release cycle. Every 6 months a new JDK with incremented main version (JDK 10, 11, ...) will be released. Please also consider it. > Upgrade to ASM 6.1.1 > > > Key: KARAF-5722 > URL: https://issues.apache.org/jira/browse/KARAF-5722 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.1.6, 4.2.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5724) Add support of JDK 10
[ https://issues.apache.org/jira/browse/KARAF-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-5724: -- Issue Type: New Feature (was: Bug) > Add support of JDK 10 > - > > Key: KARAF-5724 > URL: https://issues.apache.org/jira/browse/KARAF-5724 > Project: Karaf > Issue Type: New Feature >Reporter: Lijun Liao >Priority: Major > > Due to the missing module corba in JDK 10 (tested with the > serverjre-10.0.1_linux-x64), karaf cannot be started. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5725) Add support of JDK 11
Lijun Liao created KARAF-5725: - Summary: Add support of JDK 11 Key: KARAF-5725 URL: https://issues.apache.org/jira/browse/KARAF-5725 Project: Karaf Issue Type: New Feature Reporter: Lijun Liao JDK 11 is the first JDK with LTS (at least 5 years) since version 9. It will be released in September 2018. Currently the EA for JDK 11 is available under http://jdk.java.net/11/. So, if possible, please consider it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5724) Add support of JDK 10
Lijun Liao created KARAF-5724: - Summary: Add support of JDK 10 Key: KARAF-5724 URL: https://issues.apache.org/jira/browse/KARAF-5724 Project: Karaf Issue Type: Bug Reporter: Lijun Liao Due to the missing module corba in JDK 10 (tested with the serverjre-10.0.1_linux-x64), karaf cannot be started. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5722) Upgrade to ASM 6.1.1
[ https://issues.apache.org/jira/browse/KARAF-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458155#comment-16458155 ] Lijun Liao commented on KARAF-5722: --- Please also adapt the file proxy/proxy-impl/src/main/java/org/apache/aries/proxy/impl/ProxyUtils.java to support Java 10, 11, and so on. Since release 9, JDK has different release cycle. Every 6 months a new JDK with incremented main version (JDK 10, 11, ...) will be released. Please also consider it. > Upgrade to ASM 6.1.1 > > > Key: KARAF-5722 > URL: https://issues.apache.org/jira/browse/KARAF-5722 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.1.6, 4.2.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5708) The system scope shells not available
[ https://issues.apache.org/jira/browse/KARAF-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-5708: -- Component/s: karaf-boot > The system scope shells not available > - > > Key: KARAF-5708 > URL: https://issues.apache.org/jira/browse/KARAF-5708 > Project: Karaf > Issue Type: Bug > Components: karaf-boot, karaf-shell >Affects Versions: 4.2.0 >Reporter: Lijun Liao >Priority: Minor > Fix For: 4.2.1 > > > In apache-karaf-minimal, the system:* shells are not available after starting > karaf. The feature system should be added to the boot features to activate > them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5709) File path completion of shell:source does not work in Windows
[ https://issues.apache.org/jira/browse/KARAF-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-5709: -- Component/s: (was: cave-documentation) > File path completion of shell:source does not work in Windows > - > > Key: KARAF-5709 > URL: https://issues.apache.org/jira/browse/KARAF-5709 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.2.0, 4.1.5 >Reporter: Lijun Liao >Priority: Minor > Fix For: 4.1.6, 4.2.1 > > > There are three issues here (all do not exist in Linux): > 1.Type TAB after "source file:." does not have any effect. > 2.Type TAB after "source file:///D/" does not have any effect. > 3. The completion converts "source file:./step1/step2/filename.script" to a > path containing both the separator '/' and '\' which results in the error > "File not found". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5709) File path completion of shell:source does not work in Windows
Lijun Liao created KARAF-5709: - Summary: File path completion of shell:source does not work in Windows Key: KARAF-5709 URL: https://issues.apache.org/jira/browse/KARAF-5709 Project: Karaf Issue Type: Bug Components: cave-documentation, karaf-shell Affects Versions: 4.1.5, 4.2.0 Reporter: Lijun Liao Fix For: 4.1.6, 4.2.1 There are three issues here (all do not exist in Linux): 1.Type TAB after "source file:." does not have any effect. 2.Type TAB after "source file:///D/" does not have any effect. 3. The completion converts "source file:./step1/step2/filename.script" to a path containing both the separator '/' and '\' which results in the error "File not found". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5708) The system scope shells not available
Lijun Liao created KARAF-5708: - Summary: The system scope shells not available Key: KARAF-5708 URL: https://issues.apache.org/jira/browse/KARAF-5708 Project: Karaf Issue Type: Bug Components: karaf-shell Affects Versions: 4.2.0 Reporter: Lijun Liao Fix For: 4.2.1 In apache-karaf-minimal, the system:* shells are not available after starting karaf. The feature system should be added to the boot features to activate them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5629) Add new karaf commands shell:elif and shell:else
[
https://issues.apache.org/jira/browse/KARAF-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-5629:
--
Description:
Take the following example:
{code:java}
if {"$v" equals "a"} {
do something a
} {
if {"$v" equals "b"} {
do something b
} {
if {"$v" equals "c"} {
do something c
} {
do something others
}
}
}
{code}
By introducing the commands shell:elif and shell:else, this can be simplified
as follows:
{code:java}
if {"$v" equals "a"} {
do something a
} elif {"$v" equals "b"} {
do something b
} elif {"$v" equals "c"} {
do something c
} else {
do something others
}
{code}
was:
Take the following example:
{code:java}
if {"$v" equals "a"} {
do something a
} {
if {"$v" equals "b"} {
do something b
} {
if {"$v" equals "c"} {
do something c
} {
do something others
}
}
}
{code}
By introducing the commands shell:elif and shell:else, this can be simplified
as follows:
{code:java}
if {"$v" equals "a"} {
do something a
} elif {"$v" equals "b"} {
do something b
} elif {"$v" equals "c"} {
do something c
} else {
do something others
}
{code}
> Add new karaf commands shell:elif and shell:else
>
>
> Key: KARAF-5629
> URL: https://issues.apache.org/jira/browse/KARAF-5629
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-shell
>Affects Versions: 4.1.5, 4.2.0.M2
>Reporter: Lijun Liao
>Priority: Minor
> Fix For: 4.2.0, 4.1.6
>
>
> Take the following example:
> {code:java}
> if {"$v" equals "a"} {
> do something a
> } {
> if {"$v" equals "b"} {
> do something b
> } {
> if {"$v" equals "c"} {
> do something c
> } {
> do something others
> }
> }
> }
> {code}
> By introducing the commands shell:elif and shell:else, this can be simplified
> as follows:
> {code:java}
> if {"$v" equals "a"} {
> do something a
> } elif {"$v" equals "b"} {
> do something b
> } elif {"$v" equals "c"} {
> do something c
> } else {
> do something others
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-5629) Add new karaf commands shell:elif and shell:else
[
https://issues.apache.org/jira/browse/KARAF-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-5629:
--
Description:
Take the following example:
{code:java}
if {"$v" equals "a"} {
do something a
} {
if {"$v" equals "b"} {
do something b
} {
if {"$v" equals "c"} {
do something c
} {
do something others
}
}
}
{code}
By introducing the commands shell:elif and shell:else, this can be simplified
as follows:
{code:java}
if {"$v" equals "a"} {
do something a
} elif {"$v" equals "b"} {
do something b
} elif {"$v" equals "c"} {
do something c
} else {
do something others
}
{code}
was:
Take the following example:
{code:java}
if {"$v" equals "a"} {
do something a
} {
if {"$v" equals "b"} {
do something b
} {
if {"$v" equals "c"} {
do something c
} {
do something others
}
}
}
{code}
By introducing the commands shell:elif and shell:else, this can be simplified
as follows:
{code:java}
if {"$v" equals "a"} {
do something a
} elif {"$v" equals "b"} {
do something b
} elif {"$v" equals "c"} {
do something c
} else {
do something others
}
{code}
> Add new karaf commands shell:elif and shell:else
>
>
> Key: KARAF-5629
> URL: https://issues.apache.org/jira/browse/KARAF-5629
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-shell
>Affects Versions: 4.1.5, 4.2.0.M2
>Reporter: Lijun Liao
>Priority: Minor
> Fix For: 4.2.0, 4.1.6
>
>
> Take the following example:
> {code:java}
> if {"$v" equals "a"} {
> do something a
> } {
> if {"$v" equals "b"} {
> do something b
> } {
> if {"$v" equals "c"} {
> do something c
> } {
> do something others
> }
> }
> }
> {code}
>
> By introducing the commands shell:elif and shell:else, this can be simplified
> as follows:
> {code:java}
> if {"$v" equals "a"} {
> do something a
> } elif {"$v" equals "b"} {
> do something b
> } elif {"$v" equals "c"} {
> do something c
> } else {
> do something others
> }
> {code}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KARAF-5629) Add new karaf commands shell:elif and shell:else
Lijun Liao created KARAF-5629:
-
Summary: Add new karaf commands shell:elif and shell:else
Key: KARAF-5629
URL: https://issues.apache.org/jira/browse/KARAF-5629
Project: Karaf
Issue Type: New Feature
Components: karaf-shell
Affects Versions: 4.2.0.M2, 4.1.5
Reporter: Lijun Liao
Fix For: 4.2.0, 4.1.6
Take the following example:
{code:java}
if {"$v" equals "a"} {
do something a
} {
if {"$v" equals "b"} {
do something b
} {
if {"$v" equals "c"} {
do something c
} {
do something others
}
}
}
{code}
By introducing the commands shell:elif and shell:else, this can be simplified
as follows:
{code:java}
if {"$v" equals "a"} {
do something a
} elif {"$v" equals "b"} {
do something b
} elif {"$v" equals "c"} {
do something c
} else {
do something others
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5077) Error installing cxf
[ https://issues.apache.org/jira/browse/KARAF-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15950394#comment-15950394 ] Lijun Liao commented on KARAF-5077: --- I have similar problem while installing a feature containing mvn:org.bouncycastle/bcprov-jdk15on/1.56. > Error installing cxf > - > > Key: KARAF-5077 > URL: https://issues.apache.org/jira/browse/KARAF-5077 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.1.2 >Reporter: Christian Mora > Labels: features > > Installing the last CXF version, we will get this error: > karaf@root()> repo-add cxf > > > Adding feature url mvn:org.apache.cxf.karaf/apache-cxf/RELEASE/xml/features > karaf@root()> feature:install cxf > > > Error executing command: java.lang.InterruptedException -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-4835) Add content assist for paths in shell:source command
[ https://issues.apache.org/jira/browse/KARAF-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15844178#comment-15844178 ] Lijun Liao commented on KARAF-4835: --- I tested the version apache-karaf-4.1.0-20170128.174325-311.tar.gz, and the completion still does not work. I decompiled the org.apache.karaf.shell.commands-4.1.0-SNAPSHOT.jar and saw that the change in https://github.com/apache/karaf/commit/21769793c93257429576ffcd4c69ae94e602194c is contained. > Add content assist for paths in shell:source command > > > Key: KARAF-4835 > URL: https://issues.apache.org/jira/browse/KARAF-4835 > Project: Karaf > Issue Type: Task > Components: karaf-shell >Affects Versions: 4.1.0, 4.0.8 >Reporter: Lijun Liao >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.9 > > > Add auto-completion of file path to the karaf command "shell:source", like in > command "export-bundles". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4835) Add content assist for paths in karaf shell source
[ https://issues.apache.org/jira/browse/KARAF-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15844063#comment-15844063 ] Lijun Liao commented on KARAF-4835: --- I think shell:source is the target of this issue. > Add content assist for paths in karaf shell source > -- > > Key: KARAF-4835 > URL: https://issues.apache.org/jira/browse/KARAF-4835 > Project: Karaf > Issue Type: Task > Components: karaf-shell >Affects Versions: 4.1.0, 4.0.8 >Reporter: Lijun Liao >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > > Add auto-completion of file path to the karaf command "shell:source", like in > command "export-bundles". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4835) Add content assist for paths in karaf shell source
[ https://issues.apache.org/jira/browse/KARAF-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-4835: -- Description: Add auto-completion of file path to the karaf command "shell:source", like in command "export-bundles". (was: Add auto-completion of file path to the karaf command "source", like in command "export-bundles". ) > Add content assist for paths in karaf shell source > -- > > Key: KARAF-4835 > URL: https://issues.apache.org/jira/browse/KARAF-4835 > Project: Karaf > Issue Type: Task > Components: karaf-shell >Affects Versions: 4.1.0, 4.0.8 >Reporter: Lijun Liao >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > > Add auto-completion of file path to the karaf command "shell:source", like in > command "export-bundles". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (KARAF-4835) Add content assist for paths in karaf shell source
[ https://issues.apache.org/jira/browse/KARAF-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao reopened KARAF-4835: --- I tested the version apache-karaf-4.1.0-20170128.054440-308.tar.gz, and this feature is still not available. > Add content assist for paths in karaf shell source > -- > > Key: KARAF-4835 > URL: https://issues.apache.org/jira/browse/KARAF-4835 > Project: Karaf > Issue Type: Task > Components: karaf-shell >Affects Versions: 4.1.0, 4.0.8 >Reporter: Lijun Liao >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > > Add auto-completion of file path to the karaf command "source", like in > command "export-bundles". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4835) Add content assist for paths in karaf shell source
[ https://issues.apache.org/jira/browse/KARAF-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-4835: -- Description: Add auto-completion of file path to the karaf command "source", like in command "export-bundles". (was: Add auto-completion of file path to the karaf command "source", like in command "install". ) > Add content assist for paths in karaf shell source > -- > > Key: KARAF-4835 > URL: https://issues.apache.org/jira/browse/KARAF-4835 > Project: Karaf > Issue Type: Task > Components: karaf-shell >Affects Versions: 4.1.0, 4.0.8 >Reporter: Lijun Liao >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > > Add auto-completion of file path to the karaf command "source", like in > command "export-bundles". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4912) Cannot register Servlet via http-whiteboard under Java 9
[
https://issues.apache.org/jira/browse/KARAF-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15791492#comment-15791492
]
Lijun Liao commented on KARAF-4912:
---
Have just tested. The fix works.
> Cannot register Servlet via http-whiteboard under Java 9
>
>
> Key: KARAF-4912
> URL: https://issues.apache.org/jira/browse/KARAF-4912
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature, karaf-webcontainer
>Affects Versions: 4.1.0
> Environment: Linux (Ubuntu 12.4)
> Java 9 (JDK and JRE 9 - ea+149)
>Reporter: Lijun Liao
>Assignee: Achim Nierbeck
> Fix For: 4.1.0
>
> Attachments: ServletTest-0.0.1.jar, ServletTest-src.zip, karaf.log
>
>
> Under JDK / JRE 9 (tested with ea+149), it is impossibile to register the
> servlet via http-whiteboard.
> Steps to reproduce the problem:
> 1. Delete the folder data
> 2. Start karaf {code}bin/karaf{code}
> 3. Install feature http-whiteboard {code}feature:install http-whiteboard{code}
> 3. Copy the attached ServletTest.jar to $KARAF_HOME/deploy. The blueprint
> configuration tells karaf to register a servlet under the alias "/hw".
> 4. Open the browser and go to http://localhost:8181/hw, you will get an error.
> And ERROR message as follows will be logged in the data/log/karaf.log.
> {code}
> 2017-01-01T12:34:06,862 | ERROR |
> fileinstall-/.../apache-karaf-4.1.0-SNAPSHOT/deploy | WebApplication
> | 97 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.0 |
> Registration skipped for
> [ServletWebElement{mapping=DefaultServletMapping{httpContextId=null,urlPatterns=null,initParams={},servlet=foo.HelloWorldServlet@61a63ed6,
> alias=/hw, servletNamenull}}] due to error during registration
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4912) Cannot register Servlet via http-whiteboard under Java 9
[
https://issues.apache.org/jira/browse/KARAF-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15791323#comment-15791323
]
Lijun Liao commented on KARAF-4912:
---
Thanks. Do you plan to use the up-to-date jetty version 9.3.15.v20161220 in
pax-web? There have been lots of fixes since jetty 9.3.11.
> Cannot register Servlet via http-whiteboard under Java 9
>
>
> Key: KARAF-4912
> URL: https://issues.apache.org/jira/browse/KARAF-4912
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature, karaf-webcontainer
>Affects Versions: 4.1.0
> Environment: Linux (Ubuntu 12.4)
> Java 9 (JDK and JRE 9 - ea+149)
>Reporter: Lijun Liao
>Assignee: Achim Nierbeck
> Fix For: 4.1.0
>
> Attachments: ServletTest-0.0.1.jar, ServletTest-src.zip, karaf.log
>
>
> Under JDK / JRE 9 (tested with ea+149), it is impossibile to register the
> servlet via http-whiteboard.
> Steps to reproduce the problem:
> 1. Delete the folder data
> 2. Start karaf {code}bin/karaf{code}
> 3. Install feature http-whiteboard {code}feature:install http-whiteboard{code}
> 3. Copy the attached ServletTest.jar to $KARAF_HOME/deploy. The blueprint
> configuration tells karaf to register a servlet under the alias "/hw".
> 4. Open the browser and go to http://localhost:8181/hw, you will get an error.
> And ERROR message as follows will be logged in the data/log/karaf.log.
> {code}
> 2017-01-01T12:34:06,862 | ERROR |
> fileinstall-/.../apache-karaf-4.1.0-SNAPSHOT/deploy | WebApplication
> | 97 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.0 |
> Registration skipped for
> [ServletWebElement{mapping=DefaultServletMapping{httpContextId=null,urlPatterns=null,initParams={},servlet=foo.HelloWorldServlet@61a63ed6,
> alias=/hw, servletNamenull}}] due to error during registration
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4912) Cannot register Servlet via http-whiteboard under Java 9
[
https://issues.apache.org/jira/browse/KARAF-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15791013#comment-15791013
]
Lijun Liao commented on KARAF-4912:
---
Note that the problem does not exist in JDK 8.
> Cannot register Servlet via http-whiteboard under Java 9
>
>
> Key: KARAF-4912
> URL: https://issues.apache.org/jira/browse/KARAF-4912
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.1.0
> Environment: Linux (Ubuntu 12.4)
> Java 9 (JDK and JRE 9 - ea+149)
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
> Attachments: ServletTest-0.0.1.jar, ServletTest-src.zip, karaf.log
>
>
> Under JDK / JRE 9 (tested with ea+149), it is impossibile to register the
> servlet via http-whiteboard.
> Steps to reproduce the problem:
> 1. Delete the folder data
> 2. Start karaf {code}bin/karaf{code}
> 3. Install feature http-whiteboard {code}feature:install http-whiteboard{code}
> 3. Copy the attached ServletTest.jar to $KARAF_HOME/deploy. The blueprint
> configuration tells karaf to register a servlet under the alias "/hw".
> 4. Open the browser and go to http://localhost:8181/hw, you will get an error.
> And ERROR message as follows will be logged in the data/log/karaf.log.
> {code}
> 2017-01-01T12:34:06,862 | ERROR |
> fileinstall-/.../apache-karaf-4.1.0-SNAPSHOT/deploy | WebApplication
> | 97 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.0 |
> Registration skipped for
> [ServletWebElement{mapping=DefaultServletMapping{httpContextId=null,urlPatterns=null,initParams={},servlet=foo.HelloWorldServlet@61a63ed6,
> alias=/hw, servletNamenull}}] due to error during registration
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4912) Cannot register Servlet via http-whiteboard under Java 9
[
https://issues.apache.org/jira/browse/KARAF-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15791011#comment-15791011
]
Lijun Liao commented on KARAF-4912:
---
Notice that karaf and pax-web use different major versions of ASM. Karaf uses
version 6.0_ALPHA and pax-web uses the version 5.0.2.
> Cannot register Servlet via http-whiteboard under Java 9
>
>
> Key: KARAF-4912
> URL: https://issues.apache.org/jira/browse/KARAF-4912
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.1.0
> Environment: Linux (Ubuntu 12.4)
> Java 9 (JDK and JRE 9 - ea+149)
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
> Attachments: ServletTest-0.0.1.jar, ServletTest-src.zip, karaf.log
>
>
> Under JDK / JRE 9 (tested with ea+149), it is impossibile to register the
> servlet via http-whiteboard.
> Steps to reproduce the problem:
> 1. Delete the folder data
> 2. Start karaf {code}bin/karaf{code}
> 3. Install feature http-whiteboard {code}feature:install http-whiteboard{code}
> 3. Copy the attached ServletTest.jar to $KARAF_HOME/deploy. The blueprint
> configuration tells karaf to register a servlet under the alias "/hw".
> 4. Open the browser and go to http://localhost:8181/hw, you will get an error.
> And ERROR message as follows will be logged in the data/log/karaf.log.
> {code}
> 2017-01-01T12:34:06,862 | ERROR |
> fileinstall-/.../apache-karaf-4.1.0-SNAPSHOT/deploy | WebApplication
> | 97 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.0 |
> Registration skipped for
> [ServletWebElement{mapping=DefaultServletMapping{httpContextId=null,urlPatterns=null,initParams={},servlet=foo.HelloWorldServlet@61a63ed6,
> alias=/hw, servletNamenull}}] due to error during registration
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4912) Cannot register Servlet via http-whiteboard under Java 9
[
https://issues.apache.org/jira/browse/KARAF-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4912:
--
Description:
Under JDK / JRE 9 (tested with ea+149), it is impossibile to register the
servlet via http-whiteboard.
Steps to reproduce the problem:
1. Delete the folder data
2. Start karaf
3. Install feature http-whiteboard {code}feature:install http-whiteboard{code}
3. Copy the attached ServletTest.jar to $KARAF_HOME/deploy. The blueprint
configuration tells karaf to register a servlet under the alias "/hw".
4. Open the browser and go to http://localhost:8181/hw, you will get an error.
And ERROR message as follows will be logged in the data/log/karaf.log.
{code}
2017-01-01T12:34:06,862 | ERROR |
fileinstall-/.../apache-karaf-4.1.0-SNAPSHOT/deploy | WebApplication
| 97 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.0 |
Registration skipped for
[ServletWebElement{mapping=DefaultServletMapping{httpContextId=null,urlPatterns=null,initParams={},servlet=foo.HelloWorldServlet@61a63ed6,
alias=/hw, servletNamenull}}] due to error during registration
{code}
was:
Under JDK / JRE 9 (tested with ea+149), it is impossibile to register the
servlet via http-whiteboard.
Steps to reproduce the problem:
1. Delete the folder data
2. Start karaf
3. Copy the attached ServletTest.jar to $KARAF_HOME/deploy. The blueprint
configuration tells karaf to register a servlet under the alias "/hw".
4. Open the browser and go to http://localhost:8181/hw, you will get an error.
And ERROR message as follows will be logged in the data/log/karaf.log.
{code}
2017-01-01T12:34:06,862 | ERROR |
fileinstall-/.../apache-karaf-4.1.0-SNAPSHOT/deploy | WebApplication
| 97 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.0 |
Registration skipped for
[ServletWebElement{mapping=DefaultServletMapping{httpContextId=null,urlPatterns=null,initParams={},servlet=foo.HelloWorldServlet@61a63ed6,
alias=/hw, servletNamenull}}] due to error during registration
{code}
> Cannot register Servlet via http-whiteboard under Java 9
>
>
> Key: KARAF-4912
> URL: https://issues.apache.org/jira/browse/KARAF-4912
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.1.0
> Environment: Linux (Ubuntu 12.4)
> Java 9 (JDK and JRE 9 - ea+149)
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
> Attachments: ServletTest-0.0.1.jar, ServletTest-src.zip, karaf.log
>
>
> Under JDK / JRE 9 (tested with ea+149), it is impossibile to register the
> servlet via http-whiteboard.
> Steps to reproduce the problem:
> 1. Delete the folder data
> 2. Start karaf
> 3. Install feature http-whiteboard {code}feature:install http-whiteboard{code}
> 3. Copy the attached ServletTest.jar to $KARAF_HOME/deploy. The blueprint
> configuration tells karaf to register a servlet under the alias "/hw".
> 4. Open the browser and go to http://localhost:8181/hw, you will get an error.
> And ERROR message as follows will be logged in the data/log/karaf.log.
> {code}
> 2017-01-01T12:34:06,862 | ERROR |
> fileinstall-/.../apache-karaf-4.1.0-SNAPSHOT/deploy | WebApplication
> | 97 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.0 |
> Registration skipped for
> [ServletWebElement{mapping=DefaultServletMapping{httpContextId=null,urlPatterns=null,initParams={},servlet=foo.HelloWorldServlet@61a63ed6,
> alias=/hw, servletNamenull}}] due to error during registration
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4912) Cannot register Servlet via http-whiteboard under Java 9
[
https://issues.apache.org/jira/browse/KARAF-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4912:
--
Description:
Under JDK / JRE 9 (tested with ea+149), it is impossibile to register the
servlet via http-whiteboard.
Steps to reproduce the problem:
1. Delete the folder data
2. Start karaf {code}bin/karaf{code}
3. Install feature http-whiteboard {code}feature:install http-whiteboard{code}
3. Copy the attached ServletTest.jar to $KARAF_HOME/deploy. The blueprint
configuration tells karaf to register a servlet under the alias "/hw".
4. Open the browser and go to http://localhost:8181/hw, you will get an error.
And ERROR message as follows will be logged in the data/log/karaf.log.
{code}
2017-01-01T12:34:06,862 | ERROR |
fileinstall-/.../apache-karaf-4.1.0-SNAPSHOT/deploy | WebApplication
| 97 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.0 |
Registration skipped for
[ServletWebElement{mapping=DefaultServletMapping{httpContextId=null,urlPatterns=null,initParams={},servlet=foo.HelloWorldServlet@61a63ed6,
alias=/hw, servletNamenull}}] due to error during registration
{code}
was:
Under JDK / JRE 9 (tested with ea+149), it is impossibile to register the
servlet via http-whiteboard.
Steps to reproduce the problem:
1. Delete the folder data
2. Start karaf
3. Install feature http-whiteboard {code}feature:install http-whiteboard{code}
3. Copy the attached ServletTest.jar to $KARAF_HOME/deploy. The blueprint
configuration tells karaf to register a servlet under the alias "/hw".
4. Open the browser and go to http://localhost:8181/hw, you will get an error.
And ERROR message as follows will be logged in the data/log/karaf.log.
{code}
2017-01-01T12:34:06,862 | ERROR |
fileinstall-/.../apache-karaf-4.1.0-SNAPSHOT/deploy | WebApplication
| 97 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.0 |
Registration skipped for
[ServletWebElement{mapping=DefaultServletMapping{httpContextId=null,urlPatterns=null,initParams={},servlet=foo.HelloWorldServlet@61a63ed6,
alias=/hw, servletNamenull}}] due to error during registration
{code}
> Cannot register Servlet via http-whiteboard under Java 9
>
>
> Key: KARAF-4912
> URL: https://issues.apache.org/jira/browse/KARAF-4912
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.1.0
> Environment: Linux (Ubuntu 12.4)
> Java 9 (JDK and JRE 9 - ea+149)
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
> Attachments: ServletTest-0.0.1.jar, ServletTest-src.zip, karaf.log
>
>
> Under JDK / JRE 9 (tested with ea+149), it is impossibile to register the
> servlet via http-whiteboard.
> Steps to reproduce the problem:
> 1. Delete the folder data
> 2. Start karaf {code}bin/karaf{code}
> 3. Install feature http-whiteboard {code}feature:install http-whiteboard{code}
> 3. Copy the attached ServletTest.jar to $KARAF_HOME/deploy. The blueprint
> configuration tells karaf to register a servlet under the alias "/hw".
> 4. Open the browser and go to http://localhost:8181/hw, you will get an error.
> And ERROR message as follows will be logged in the data/log/karaf.log.
> {code}
> 2017-01-01T12:34:06,862 | ERROR |
> fileinstall-/.../apache-karaf-4.1.0-SNAPSHOT/deploy | WebApplication
> | 97 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.0 |
> Registration skipped for
> [ServletWebElement{mapping=DefaultServletMapping{httpContextId=null,urlPatterns=null,initParams={},servlet=foo.HelloWorldServlet@61a63ed6,
> alias=/hw, servletNamenull}}] due to error during registration
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4912) Cannot register Servlet via http-whiteboard under Java 9
[
https://issues.apache.org/jira/browse/KARAF-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4912:
--
Attachment: ServletTest-src.zip
karaf.log
ServletTest-0.0.1.jar
> Cannot register Servlet via http-whiteboard under Java 9
>
>
> Key: KARAF-4912
> URL: https://issues.apache.org/jira/browse/KARAF-4912
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.1.0
> Environment: Linux (Ubuntu 12.4)
> Java 9 (JDK and JRE 9 - ea+149)
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
> Attachments: ServletTest-0.0.1.jar, ServletTest-src.zip, karaf.log
>
>
> Under JDK / JRE 9 (tested with ea+149), it is impossibile to register the
> servlet via http-whiteboard.
> Steps to reproduce the problem:
> 1. Delete the folder data
> 2. Start karaf
> 3. Copy the attached ServletTest.jar to $KARAF_HOME/deploy. The blueprint
> configuration tells karaf to register a servlet under the alias "/hw".
> 4. Open the browser and go to http://localhost:8181/hw, you will get an error.
> And ERROR message as follows will be logged in the data/log/karaf.log.
> {code}
> 2017-01-01T12:34:06,862 | ERROR |
> fileinstall-/.../apache-karaf-4.1.0-SNAPSHOT/deploy | WebApplication
> | 97 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.0 |
> Registration skipped for
> [ServletWebElement{mapping=DefaultServletMapping{httpContextId=null,urlPatterns=null,initParams={},servlet=foo.HelloWorldServlet@61a63ed6,
> alias=/hw, servletNamenull}}] due to error during registration
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4845) Cannot start karaf with JRE 9
[
https://issues.apache.org/jira/browse/KARAF-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15713030#comment-15713030
]
Lijun Liao commented on KARAF-4845:
---
Have tried the recent SNAPSHOT distribution
(apache-karaf-4.1.0-20161201.164747-261.tar.gz) and karaf starts with JRE 9
successfully. Thanks for the fix.
> Cannot start karaf with JRE 9
> -
>
> Key: KARAF-4845
> URL: https://issues.apache.org/jira/browse/KARAF-4845
> Project: Karaf
> Issue Type: Bug
> Components: karaf-boot
>Affects Versions: 4.1.0
> Environment: Ubuntu
> JRE Early Access Releases 9 Build 146
>Reporter: Lijun Liao
>Assignee: Freeman Fang
> Fix For: 4.1.0
>
>
> Starting karaf with JRE (NOT JDK) 9 fails with the following error message:
> {code}
> $ bin/karaf
> Error occurred during initialization of VM
> java.lang.module.ResolutionException: Module jdk.xml.bind not found
> at java.lang.module.Resolver.fail(java.base@9-ea/Resolver.java:790)
> at
> java.lang.module.Resolver.resolveRequires(java.base@9-ea/Resolver.java:94)
> at
> java.lang.module.Configuration.resolveRequiresAndUses(java.base@9-ea/Configuration.java:370)
> at
> java.lang.module.ModuleDescriptor$1.resolveRequiresAndUses(java.base@9-ea/ModuleDescriptor.java:1987)
> at
> jdk.internal.module.ModuleBootstrap.boot(java.base@9-ea/ModuleBootstrap.java:260)
> at java.lang.System.initPhase2(java.base@9-ea/System.java:1927)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4877) OS-terminal is in invalid state after the shutting down of karaf
[ https://issues.apache.org/jira/browse/KARAF-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-4877: -- Summary: OS-terminal is in invalid state after the shutting down of karaf (was: InterruptedException of karaf shell will not be fo) > OS-terminal is in invalid state after the shutting down of karaf > > > Key: KARAF-4877 > URL: https://issues.apache.org/jira/browse/KARAF-4877 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.1.0 > Environment: Ubuntu 12 > JRE 8, JDK 8, JRE 9 and JDK 9 > apache-karaf-4.1.0-20161201.164747-261.tar.gz >Reporter: Lijun Liao > Fix For: 4.1.0 > > > After shutting down karaf via CTRL + D or shutdown -f, the OS terminal on > which the karaf ran will be in invalid state. The OS terminal still accepts > the user input, but does not print it. > Steps to reproduce the problem: > 1. Start karaf via bin/karaf > 2. Wait several seconds, then type CTRL + D or shutdown -f > 3. Karaf shuts down > 4. Type anything on the terminal on which the karaf ran. You should not see > what you typed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4877) InterruptedException of karaf shell will not be fo
Lijun Liao created KARAF-4877: - Summary: InterruptedException of karaf shell will not be fo Key: KARAF-4877 URL: https://issues.apache.org/jira/browse/KARAF-4877 Project: Karaf Issue Type: Bug Components: karaf-shell Affects Versions: 4.1.0 Environment: Ubuntu 12 JRE 8, JDK 8, JRE 9 and JDK 9 apache-karaf-4.1.0-20161201.164747-261.tar.gz Reporter: Lijun Liao Fix For: 4.1.0 After shutting down karaf via CTRL + D or shutdown -f, the OS terminal on which the karaf ran will be in invalid state. The OS terminal still accepts the user input, but does not print it. Steps to reproduce the problem: 1. Start karaf via bin/karaf 2. Wait several seconds, then type CTRL + D or shutdown -f 3. Karaf shuts down 4. Type anything on the terminal on which the karaf ran. You should not see what you typed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KARAF-4847) Cannot start feature pax-jetty with JDK 9
[
https://issues.apache.org/jira/browse/KARAF-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712980#comment-15712980
]
Lijun Liao edited comment on KARAF-4847 at 12/1/16 8:23 PM:
The fix works. I can start the pax-jetty feature. Thanks!
was (Author: lliao):
The fix works. I can start the pax-jetty feature.
> Cannot start feature pax-jetty with JDK 9
> -
>
> Key: KARAF-4847
> URL: https://issues.apache.org/jira/browse/KARAF-4847
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.1.0
> Environment: Ubuntu
> JDK Early Access Releases 9 Build 146
>Reporter: Lijun Liao
>Assignee: Guillaume Nodet
>Priority: Critical
> Labels: java9
> Fix For: 4.1.0
>
> Attachments: karaf.log
>
>
> Steps to reproduce the error:
> 1. Start a terminal
> 2. Start karaf (bin/karaf)
> 3. Install feature pax-jetty (feature:install pax-jetty)
> Karaf shows the following message immediately
> {code}
> karaf@root()> feature:install pax-jetty xx:xx:xx
> Error executing command: java.lang.InterruptedException
> gogo: InterruptedException: null
> {code}
> After a while or being cancelled by CTRL + C, karaf ends up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4844) ERROR logged if the property featuresBoot contains pax-jetty in 2nd stage
[
https://issues.apache.org/jira/browse/KARAF-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15708314#comment-15708314
]
Lijun Liao commented on KARAF-4844:
---
Have just tried
https://repository.apache.org/content/groups/snapshots-group/org/apache/karaf/apache-karaf/4.1.0-SNAPSHOT/apache-karaf-4.1.0-20161130.104509-248.tar.gz,
but with the same problem.
> ERROR logged if the property featuresBoot contains pax-jetty in 2nd stage
> ---
>
> Key: KARAF-4844
> URL: https://issues.apache.org/jira/browse/KARAF-4844
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> By starting karaf with the following property in
> etc/org.apache.karaf.features.cfg
> {code}
> featuresBoot = \
> (instance, \
> ...
> kar), pax-jetty
> {code}
> , one will get the following ERROR messages in data/log/karaf.log:
> {code}
> 2016-11-23T21:31:43,216 | ERROR | FelixStartLevel | Felix
> | - - | Bundle org.objectweb.asm.all [52] Error locking
> mvn:org.ow2.asm/asm-all/6.0_ALPHA (java.lang.IllegalStateException: Bundle in
> unexpected state.)
> java.lang.IllegalStateException: Bundle in unexpected state.
> at
> org.apache.felix.framework.Felix.acquireBundleLock(Felix.java:5272) [?:?]
> at
> org.apache.felix.framework.Felix.setBundleStartLevel(Felix.java:1524) [?:?]
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:338)
> [?:?]
> at java.lang.Thread.run(Thread.java:745) [?:?]
> 2016-11-23T21:31:43,215 | ERROR | FelixDispatchQueue | all
> | 85 - org.objectweb.asm.all - 5.0.2 | FrameworkEvent ERROR -
> org.objectweb.asm.all
> java.lang.IllegalStateException: Bundle in unexpected state.
> at
> org.apache.felix.framework.Felix.acquireBundleLock(Felix.java:5272) [?:?]
> at
> org.apache.felix.framework.Felix.setBundleStartLevel(Felix.java:1524) [?:?]
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:338)
> [?:?]
> at java.lang.Thread.run(Thread.java:745) [?:?]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4834) Infinite loop if Exception occurs during the execution of karaf.shell.init.script
[
https://issues.apache.org/jira/browse/KARAF-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4834:
--
Description:
The while block between line 329 and line 352 in
https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
will never break if Exception other than EndOfFileException is thrown, e.g.
StreamClosed exception.
After executing a karaf command (the commands are in a scritp which will be
executed via the command source) I happened to get the Interrupted error, then
the branding screen was shown, followed by infinite Stream Closed IOException.
Sorry I got this phenomenon only from time to time and cannot provide
stable steps to reproduce it.
{code}
karaf@root()
Error executing command: java.lang.InterruptedException
gogo: InterruptedException: null
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.0-SNAPSHOT)
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.io.IOException: Stream Closed
... hunderts lines with same content ignored here ...
karaf@root()> Error executing command: java.io.IOException: Stream Closed
{code}
I have attached the log.
was:
The while block between line 329 and line 352 in
https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
will never break if Exception other than EndOfFileException is thrown, e.g.
StreamClosed exception.
After executing a karaf command (the commands are in a scritp which will be
executed via the command `source`) I happened to get the Interrupted error,
then the branding screen was shown, followed by infinite Stream Closed
IOException. Sorry I got this phenomenon onlyfrom time to time and cannot
provide stable steps to reproduce it.
{code}
karaf@root()
Error executing command: java.lang.InterruptedException
gogo: InterruptedException: null
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.0-SNAPSHOT)
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.io.IOException: Stream Closed
... hunderts lines with same content ignored here ...
karaf@root()> Error executing command: java.io.IOException: Stream Closed
{code}
I have attached the log.
> Infinite loop if Exception occurs during the execution of
> karaf.shell.init.script
> -
>
> Key: KARAF-4834
> URL: https://issues.apache.org/jira/browse/KARAF-4834
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
> Attachments: karaf.log
>
>
> The while block between line 329 and line 352 in
> https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
> will never break if Exception other than EndOfFileException is thrown, e.g.
> StreamClosed exception.
> After executing a karaf command (the commands are in a scritp which will be
> executed via the command source) I happened to get the Interrupted error,
> then the branding screen was shown, followed by infinite Stream Closed
> IOException. Sorry I got this phenomenon onlyfrom time to time and cannot
> provide stable steps to reproduce it.
> {code}
> karaf@root()
> Error executing command: java.lang.InterruptedException
> gogo: InterruptedException: null
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.1.0-SNAPSHOT)
> 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.io.IOException: Stream Closed
> ... hunderts lines with same content ignored here ...
> karaf@root()> Error executing command: java.io.IOException: Stream Closed
> {code}
> I have attached the log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4834) Infinite loop if Exception occurs during the execution of karaf.shell.init.script
[
https://issues.apache.org/jira/browse/KARAF-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4834:
--
Description:
The while block between line 329 and line 352 in
https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
will never break if Exception other than EndOfFileException is thrown, e.g.
StreamClosed exception.
After executing a karaf command (the commands are in a scritp which will be
executed via the command `source`) I happened to get the Interrupted error,
then the branding screen was shown, followed by infinite Stream Closed
IOException. Sorry I got this phenomenon onlyfrom time to time and cannot
provide stable steps to reproduce it.
{code}
karaf@root()
Error executing command: java.lang.InterruptedException
gogo: InterruptedException: null
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.0-SNAPSHOT)
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.io.IOException: Stream Closed
... hunderts lines with same content ignored here ...
karaf@root()> Error executing command: java.io.IOException: Stream Closed
{code}
I have attached the log.
was:
The while block between line 329 and line 352 in
https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
will never break if Exception other than EndOfFileException is thrown, e.g.
StreamClosed exception.
After executing a karaf command I happened to get the Interrupted error, then
the branding screen was shown, followed by infinite Stream Closed IOException.
Sorry I got this phenomenon only from time to time and cannot provide stable
steps to reproduce it.
{code}
karaf@root()
Error executing command: java.lang.InterruptedException
gogo: InterruptedException: null
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.0-SNAPSHOT)
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.io.IOException: Stream Closed
... hunderts lines with same content ignored here ...
karaf@root()> Error executing command: java.io.IOException: Stream Closed
{code}
I have attached the log.
> Infinite loop if Exception occurs during the execution of
> karaf.shell.init.script
> -
>
> Key: KARAF-4834
> URL: https://issues.apache.org/jira/browse/KARAF-4834
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
> Attachments: karaf.log
>
>
> The while block between line 329 and line 352 in
> https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
> will never break if Exception other than EndOfFileException is thrown, e.g.
> StreamClosed exception.
> After executing a karaf command (the commands are in a scritp which will be
> executed via the command `source`) I happened to get the Interrupted error,
> then the branding screen was shown, followed by infinite Stream Closed
> IOException. Sorry I got this phenomenon only from time to time and cannot
> provide stable steps to reproduce it.
> {code}
> karaf@root()
> Error executing command: java.lang.InterruptedException
> gogo: InterruptedException: null
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.1.0-SNAPSHOT)
> 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.io.IOException: Stream Closed
> ... hunderts lines with same content ignored here ...
> karaf@root()> Error executing command: java.io.IOException: Stream Closed
> {code}
> I have attached the log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (KARAF-4838) InterruptedException of karaf shell will not be forwarded to the commands executed via source
[ https://issues.apache.org/jira/browse/KARAF-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15708088#comment-15708088 ] Lijun Liao edited comment on KARAF-4838 at 11/30/16 9:50 AM: - I have updated the issue description by adding the steps to reproduce the error. was (Author: lliao): I have updated the issue description to add the steps to reproduce the error. > InterruptedException of karaf shell will not be forwarded to the commands > executed via source > - > > Key: KARAF-4838 > URL: https://issues.apache.org/jira/browse/KARAF-4838 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.1.0 >Reporter: Lijun Liao > Fix For: 4.1.0 > > > In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded > by the karaf shell to the commands executed via source. This forwarding is > useful since the application can then decide whether it should cancel the > action. However this forwarding has been deactivated in karaf 4.1.0. > Steps to reproduce the problem in Linux: > 1. Create a file demo.script that contains the line >"sleep 10" > 2. In karaf shell, execute the commands via > "source demo.scipt" > 3. In karaf shell, enter CTRL + C, you will see > "gogo: InterruptedException: null" instead of the expected "sleep: > interrupted" > Additionally, if you enter CTRL + D after step 3 to exit karaf, the > OS-terminal will be in invalid state. You cannot see what you enter in the > OS-terminal. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4838) InterruptedException of karaf shell will not be forwarded to the commands executed via source
[ https://issues.apache.org/jira/browse/KARAF-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15708088#comment-15708088 ] Lijun Liao commented on KARAF-4838: --- I have updated the issue description to add the steps to reproduce the error. > InterruptedException of karaf shell will not be forwarded to the commands > executed via source > - > > Key: KARAF-4838 > URL: https://issues.apache.org/jira/browse/KARAF-4838 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.1.0 >Reporter: Lijun Liao > Fix For: 4.1.0 > > > In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded > by the karaf shell to the commands executed via source. This forwarding is > useful since the application can then decide whether it should cancel the > action. However this forwarding has been deactivated in karaf 4.1.0. > Steps to reproduce the problem in Linux: > 1. Create a file demo.script that contains the line >"sleep 10" > 2. In karaf shell, execute the commands via > "source demo.scipt" > 3. In karaf shell, enter CTRL + C, you will see > "gogo: InterruptedException: null" instead of the expected "sleep: > interrupted" > Additionally, if you enter CTRL + D after step 3 to exit karaf, the > OS-terminal will be in invalid state. You cannot see what you enter in the > OS-terminal. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4838) InterruptedException of karaf shell will not be forwarded to the commands executed via source
[ https://issues.apache.org/jira/browse/KARAF-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-4838: -- Description: In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded by the karaf shell to the commands executed via source. This forwarding is useful since the application can then decide whether it should cancel the action. However this forwarding has been deactivated in karaf 4.1.0. Steps to reproduce the problem in Linux: 1. Create a file demo.script that contains the line "sleep 10" 2. In karaf shell, execute the commands via "source demo.scipt" 3. In karaf shell, enter CTRL + C, you will see "gogo: InterruptedException: null" instead of the expected "sleep: interrupted" Additionally, if you enter CTRL + D after step 3 to exit karaf, the OS-terminal will be in invalid state. You cannot see what you enter in the OS-terminal. was: In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded by the karaf shell to the commands executed via source. This forwarding is useful since the application can then decide whether it should cancel the action. However this forwarding has been deactivated in karaf 4.1.0. Steps to reproduce the problem: 1. Create a file demo.script that contains the line "sleep 10" 2. In karaf shell, execute the commands via "source demo.scipt" 3. In karaf shell, enter CTRL + C Even w > InterruptedException of karaf shell will not be forwarded to the commands > executed via source > - > > Key: KARAF-4838 > URL: https://issues.apache.org/jira/browse/KARAF-4838 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.1.0 >Reporter: Lijun Liao > Fix For: 4.1.0 > > > In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded > by the karaf shell to the commands executed via source. This forwarding is > useful since the application can then decide whether it should cancel the > action. However this forwarding has been deactivated in karaf 4.1.0. > Steps to reproduce the problem in Linux: > 1. Create a file demo.script that contains the line >"sleep 10" > 2. In karaf shell, execute the commands via > "source demo.scipt" > 3. In karaf shell, enter CTRL + C, you will see > "gogo: InterruptedException: null" instead of the expected "sleep: > interrupted" > Additionally, if you enter CTRL + D after step 3 to exit karaf, the > OS-terminal will be in invalid state. You cannot see what you enter in the > OS-terminal. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4838) InterruptedException of karaf shell will not be forwarded to the commands executed via source
[ https://issues.apache.org/jira/browse/KARAF-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-4838: -- Description: In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded by the karaf shell to the commands executed via source. This forwarding is useful since the application can then decide whether it should cancel the action. However this forwarding has been deactivated in karaf 4.1.0. Steps to reproduce the problem: 1. Create a file demo.script that contains the line "sleep 10" 2. In karaf shell, execute the commands via "source demo.scipt" 3. In karaf shell, enter CTRL + C Even w was: In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded by the karaf shell to the commands . This forwarding is useful since the application can then decide whether it should cancel the action. However this forwarding has been deactivated in karaf 4.1.0. > InterruptedException of karaf shell will not be forwarded to the commands > executed via source > - > > Key: KARAF-4838 > URL: https://issues.apache.org/jira/browse/KARAF-4838 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.1.0 >Reporter: Lijun Liao > Fix For: 4.1.0 > > > In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded > by the karaf shell to the commands executed via source. This forwarding is > useful since the application can then decide whether it should cancel the > action. However this forwarding has been deactivated in karaf 4.1.0. > Steps to reproduce the problem: > 1. Create a file demo.script that contains the line >"sleep 10" > 2. In karaf shell, execute the commands via > "source demo.scipt" > 3. In karaf shell, enter CTRL + C > Even w -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4838) InterruptedException of karaf shell will not be forwarded to the commands executed via source
[ https://issues.apache.org/jira/browse/KARAF-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-4838: -- Summary: InterruptedException of karaf shell will not be forwarded to the commands executed via source (was: InterruptedException of karaf shell will not be forwarded to the command executed via source) > InterruptedException of karaf shell will not be forwarded to the commands > executed via source > - > > Key: KARAF-4838 > URL: https://issues.apache.org/jira/browse/KARAF-4838 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.1.0 >Reporter: Lijun Liao > Fix For: 4.1.0 > > > In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded > by the karaf shell to the commands . This forwarding is useful since the > application can then decide whether it should cancel the action. However this > forwarding has been deactivated in karaf 4.1.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4838) InterruptedException of karaf shell will not be forwarded to the command executed via source
[ https://issues.apache.org/jira/browse/KARAF-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-4838: -- Summary: InterruptedException of karaf shell will not be forwarded to the command executed via source (was: InterruptedException of karaf shell will not be forwarded to the command) > InterruptedException of karaf shell will not be forwarded to the command > executed via source > > > Key: KARAF-4838 > URL: https://issues.apache.org/jira/browse/KARAF-4838 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.1.0 >Reporter: Lijun Liao > Fix For: 4.1.0 > > > In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded > by the karaf shell to the command. This forwarding is useful since the > application can then decide whether it should cancel the action. However this > forwarding has been deactivated in karaf 4.1.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4838) InterruptedException of karaf shell will not be forwarded to the command executed via source
[ https://issues.apache.org/jira/browse/KARAF-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-4838: -- Description: In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded by the karaf shell to the commands . This forwarding is useful since the application can then decide whether it should cancel the action. However this forwarding has been deactivated in karaf 4.1.0. was: In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded by the karaf shell to the command. This forwarding is useful since the application can then decide whether it should cancel the action. However this forwarding has been deactivated in karaf 4.1.0. > InterruptedException of karaf shell will not be forwarded to the command > executed via source > > > Key: KARAF-4838 > URL: https://issues.apache.org/jira/browse/KARAF-4838 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.1.0 >Reporter: Lijun Liao > Fix For: 4.1.0 > > > In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded > by the karaf shell to the commands . This forwarding is useful since the > application can then decide whether it should cancel the action. However this > forwarding has been deactivated in karaf 4.1.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4847) Cannot start feature pax-jetty with JDK 9
[
https://issues.apache.org/jira/browse/KARAF-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4847:
--
Attachment: karaf.log
The command feature:install pax-jetty was executed at 2016-11-24T18:52:28,536
> Cannot start feature pax-jetty with JDK 9
> -
>
> Key: KARAF-4847
> URL: https://issues.apache.org/jira/browse/KARAF-4847
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.1.0
> Environment: Ubuntu
> JDK Early Access Releases 9 Build 146
>Reporter: Lijun Liao
>Priority: Critical
> Fix For: 4.1.0
>
> Attachments: karaf.log
>
>
> Steps to reproduce the error:
> 1. Start a terminal
> 2. Start karaf (bin/karaf)
> 3. Install feature pax-jetty (feature:install pax-jetty)
> Karaf shows the following message immediately
> {code}
> karaf@root()> feature:install pax-jetty xx:xx:xx
> Error executing command: java.lang.InterruptedException
> gogo: InterruptedException: null
> {code}
> After a while or being cancelled by CTRL + C, karaf ends up. Even worse, you
> cannot see what you type on the termial after that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (KARAF-4847) Cannot start feature pax-jetty with JDK 9
[
https://issues.apache.org/jira/browse/KARAF-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15693924#comment-15693924
]
Lijun Liao edited comment on KARAF-4847 at 11/24/16 6:00 PM:
-
The command feature:install pax-jetty was executed at 2016-11-24T18:52:28,536.
was (Author: lliao):
The command feature:install pax-jetty was executed at 2016-11-24T18:52:28,536
> Cannot start feature pax-jetty with JDK 9
> -
>
> Key: KARAF-4847
> URL: https://issues.apache.org/jira/browse/KARAF-4847
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.1.0
> Environment: Ubuntu
> JDK Early Access Releases 9 Build 146
>Reporter: Lijun Liao
>Priority: Critical
> Fix For: 4.1.0
>
> Attachments: karaf.log
>
>
> Steps to reproduce the error:
> 1. Start a terminal
> 2. Start karaf (bin/karaf)
> 3. Install feature pax-jetty (feature:install pax-jetty)
> Karaf shows the following message immediately
> {code}
> karaf@root()> feature:install pax-jetty xx:xx:xx
> Error executing command: java.lang.InterruptedException
> gogo: InterruptedException: null
> {code}
> After a while or being cancelled by CTRL + C, karaf ends up. Even worse, you
> cannot see what you type on the termial after that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4847) Cannot start feature pax-jetty with JDK 9
[
https://issues.apache.org/jira/browse/KARAF-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15693407#comment-15693407
]
Lijun Liao commented on KARAF-4847:
---
I use the JDK (Linux 64 bit) downloaded from https://jdk9.java.net/download/
> Cannot start feature pax-jetty with JDK 9
> -
>
> Key: KARAF-4847
> URL: https://issues.apache.org/jira/browse/KARAF-4847
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.1.0
> Environment: Ubuntu
> JDK Early Access Releases 9 Build 146
>Reporter: Lijun Liao
>Priority: Critical
> Fix For: 4.1.0
>
>
> Steps to reproduce the error:
> 1. Start a terminal
> 2. Start karaf (bin/karaf)
> 3. Install feature pax-jetty (feature:install pax-jetty)
> Karaf shows the following message immediately
> {code}
> karaf@root()> feature:install pax-jetty xx:xx:xx
> Error executing command: java.lang.InterruptedException
> gogo: InterruptedException: null
> {code}
> After a while or being cancelled by CTRL + C, karaf ends up. Even worse, you
> cannot see what you type on the termial after that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4845) Cannot start karaf with JRE 9
[
https://issues.apache.org/jira/browse/KARAF-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15693405#comment-15693405
]
Lijun Liao commented on KARAF-4845:
---
I am using the JRE (Linux 64 bit) downloaded from
https://jdk9.java.net/download/. The folders under $JAVA_HOME are bin, conf,
lib, and plugin. And "find . -name jdk.xml.bind.jmod" does not return any
result.
> Cannot start karaf with JRE 9
> -
>
> Key: KARAF-4845
> URL: https://issues.apache.org/jira/browse/KARAF-4845
> Project: Karaf
> Issue Type: Bug
> Components: karaf-boot
>Affects Versions: 4.1.0
> Environment: Ubuntu
> JRE Early Access Releases 9 Build 146
>Reporter: Lijun Liao
>Assignee: Freeman Fang
> Fix For: 4.1.0
>
>
> Starting karaf with JRE (NOT JDK) 9 fails with the following error message:
> {code}
> $ bin/karaf
> Error occurred during initialization of VM
> java.lang.module.ResolutionException: Module jdk.xml.bind not found
> at java.lang.module.Resolver.fail(java.base@9-ea/Resolver.java:790)
> at
> java.lang.module.Resolver.resolveRequires(java.base@9-ea/Resolver.java:94)
> at
> java.lang.module.Configuration.resolveRequiresAndUses(java.base@9-ea/Configuration.java:370)
> at
> java.lang.module.ModuleDescriptor$1.resolveRequiresAndUses(java.base@9-ea/ModuleDescriptor.java:1987)
> at
> jdk.internal.module.ModuleBootstrap.boot(java.base@9-ea/ModuleBootstrap.java:260)
> at java.lang.System.initPhase2(java.base@9-ea/System.java:1927)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (KARAF-4845) Cannot start karaf with JRE 9
[
https://issues.apache.org/jira/browse/KARAF-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15693405#comment-15693405
]
Lijun Liao edited comment on KARAF-4845 at 11/24/16 2:23 PM:
-
I use the JRE (Linux 64 bit) downloaded from https://jdk9.java.net/download/.
The folders under $JAVA_HOME are bin, conf, lib, and plugin. And "find . -name
jdk.xml.bind.jmod" does not return any result.
was (Author: lliao):
I am using the JRE (Linux 64 bit) downloaded from
https://jdk9.java.net/download/. The folders under $JAVA_HOME are bin, conf,
lib, and plugin. And "find . -name jdk.xml.bind.jmod" does not return any
result.
> Cannot start karaf with JRE 9
> -
>
> Key: KARAF-4845
> URL: https://issues.apache.org/jira/browse/KARAF-4845
> Project: Karaf
> Issue Type: Bug
> Components: karaf-boot
>Affects Versions: 4.1.0
> Environment: Ubuntu
> JRE Early Access Releases 9 Build 146
>Reporter: Lijun Liao
>Assignee: Freeman Fang
> Fix For: 4.1.0
>
>
> Starting karaf with JRE (NOT JDK) 9 fails with the following error message:
> {code}
> $ bin/karaf
> Error occurred during initialization of VM
> java.lang.module.ResolutionException: Module jdk.xml.bind not found
> at java.lang.module.Resolver.fail(java.base@9-ea/Resolver.java:790)
> at
> java.lang.module.Resolver.resolveRequires(java.base@9-ea/Resolver.java:94)
> at
> java.lang.module.Configuration.resolveRequiresAndUses(java.base@9-ea/Configuration.java:370)
> at
> java.lang.module.ModuleDescriptor$1.resolveRequiresAndUses(java.base@9-ea/ModuleDescriptor.java:1987)
> at
> jdk.internal.module.ModuleBootstrap.boot(java.base@9-ea/ModuleBootstrap.java:260)
> at java.lang.System.initPhase2(java.base@9-ea/System.java:1927)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4845) Cannot start karaf with JRE 9
[
https://issues.apache.org/jira/browse/KARAF-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4845:
--
Description:
Starting karaf with JRE (NOT JDK) 9 fails with the following error message:
{code}
$ bin/karaf
Error occurred during initialization of VM
java.lang.module.ResolutionException: Module jdk.xml.bind not found
at java.lang.module.Resolver.fail(java.base@9-ea/Resolver.java:790)
at
java.lang.module.Resolver.resolveRequires(java.base@9-ea/Resolver.java:94)
at
java.lang.module.Configuration.resolveRequiresAndUses(java.base@9-ea/Configuration.java:370)
at
java.lang.module.ModuleDescriptor$1.resolveRequiresAndUses(java.base@9-ea/ModuleDescriptor.java:1987)
at
jdk.internal.module.ModuleBootstrap.boot(java.base@9-ea/ModuleBootstrap.java:260)
at java.lang.System.initPhase2(java.base@9-ea/System.java:1927)
{code}
was:
Starting karaf with JRE 9 fails with the following error message:
{code}
$ bin/karaf
Error occurred during initialization of VM
java.lang.module.ResolutionException: Module jdk.xml.bind not found
at java.lang.module.Resolver.fail(java.base@9-ea/Resolver.java:790)
at
java.lang.module.Resolver.resolveRequires(java.base@9-ea/Resolver.java:94)
at
java.lang.module.Configuration.resolveRequiresAndUses(java.base@9-ea/Configuration.java:370)
at
java.lang.module.ModuleDescriptor$1.resolveRequiresAndUses(java.base@9-ea/ModuleDescriptor.java:1987)
at
jdk.internal.module.ModuleBootstrap.boot(java.base@9-ea/ModuleBootstrap.java:260)
at java.lang.System.initPhase2(java.base@9-ea/System.java:1927)
{code}
> Cannot start karaf with JRE 9
> -
>
> Key: KARAF-4845
> URL: https://issues.apache.org/jira/browse/KARAF-4845
> Project: Karaf
> Issue Type: Bug
> Components: karaf-boot
>Affects Versions: 4.1.0
> Environment: Ubuntu
> JRE Early Access Releases 9 Build 146
>Reporter: Lijun Liao
>Assignee: Freeman Fang
> Fix For: 4.1.0
>
>
> Starting karaf with JRE (NOT JDK) 9 fails with the following error message:
> {code}
> $ bin/karaf
> Error occurred during initialization of VM
> java.lang.module.ResolutionException: Module jdk.xml.bind not found
> at java.lang.module.Resolver.fail(java.base@9-ea/Resolver.java:790)
> at
> java.lang.module.Resolver.resolveRequires(java.base@9-ea/Resolver.java:94)
> at
> java.lang.module.Configuration.resolveRequiresAndUses(java.base@9-ea/Configuration.java:370)
> at
> java.lang.module.ModuleDescriptor$1.resolveRequiresAndUses(java.base@9-ea/ModuleDescriptor.java:1987)
> at
> jdk.internal.module.ModuleBootstrap.boot(java.base@9-ea/ModuleBootstrap.java:260)
> at java.lang.System.initPhase2(java.base@9-ea/System.java:1927)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4845) Cannot start karaf with JRE 9
[
https://issues.apache.org/jira/browse/KARAF-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15693198#comment-15693198
]
Lijun Liao commented on KARAF-4845:
---
There are some scenarios where it is not possible/wished to use JDK due to the
restriction of resource, license, security requirements, etc.
> Cannot start karaf with JRE 9
> -
>
> Key: KARAF-4845
> URL: https://issues.apache.org/jira/browse/KARAF-4845
> Project: Karaf
> Issue Type: Bug
> Components: karaf-boot
>Affects Versions: 4.1.0
> Environment: Ubuntu
> JRE Early Access Releases 9 Build 146
>Reporter: Lijun Liao
>Assignee: Freeman Fang
> Fix For: 4.1.0
>
>
> Starting karaf with JRE 9 fails with the following error message:
> {code}
> $ bin/karaf
> Error occurred during initialization of VM
> java.lang.module.ResolutionException: Module jdk.xml.bind not found
> at java.lang.module.Resolver.fail(java.base@9-ea/Resolver.java:790)
> at
> java.lang.module.Resolver.resolveRequires(java.base@9-ea/Resolver.java:94)
> at
> java.lang.module.Configuration.resolveRequiresAndUses(java.base@9-ea/Configuration.java:370)
> at
> java.lang.module.ModuleDescriptor$1.resolveRequiresAndUses(java.base@9-ea/ModuleDescriptor.java:1987)
> at
> jdk.internal.module.ModuleBootstrap.boot(java.base@9-ea/ModuleBootstrap.java:260)
> at java.lang.System.initPhase2(java.base@9-ea/System.java:1927)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4847) Cannot start feature pax-jetty with JDK 9
[
https://issues.apache.org/jira/browse/KARAF-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4847:
--
Environment:
Ubuntu
JDK Early Access Releases 9 Build 146
was:
Ubuntu
JDK 9 Build 146
> Cannot start feature pax-jetty with JDK 9
> -
>
> Key: KARAF-4847
> URL: https://issues.apache.org/jira/browse/KARAF-4847
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.1.0
> Environment: Ubuntu
> JDK Early Access Releases 9 Build 146
>Reporter: Lijun Liao
>Priority: Critical
> Fix For: 4.1.0
>
>
> Steps to reproduce the error:
> 1. Start a terminal
> 2. Start karaf (bin/karaf)
> 3. Install feature pax-jetty (feature:install pax-jetty)
> Karaf shows the following message immediately
> {code}
> karaf@root()> feature:install pax-jetty xx:xx:xx
> Error executing command: java.lang.InterruptedException
> gogo: InterruptedException: null
> {code}
> After a while or being cancelled by CTRL + C, karaf ends up. Even worse, you
> cannot see what you type on the termial after that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4847) Cannot start feature pax-jetty with JDK 9
Lijun Liao created KARAF-4847:
-
Summary: Cannot start feature pax-jetty with JDK 9
Key: KARAF-4847
URL: https://issues.apache.org/jira/browse/KARAF-4847
Project: Karaf
Issue Type: Bug
Components: karaf-feature
Affects Versions: 4.1.0
Environment: Ubuntu
JDK 9 Build 146
Reporter: Lijun Liao
Priority: Critical
Fix For: 4.1.0
Steps to reproduce the error:
1. Start a terminal
2. Start karaf (bin/karaf)
3. Install feature pax-jetty (feature:install pax-jetty)
Karaf shows the following message immediately
{code}
karaf@root()> feature:install pax-jetty xx:xx:xx
Error executing command: java.lang.InterruptedException
gogo: InterruptedException: null
{code}
After a while or being cancelled by CTRL + C, karaf ends up. Even worse, you
cannot see what you type on the termial after that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4845) Cannot start karaf with JRE 9
Lijun Liao created KARAF-4845:
-
Summary: Cannot start karaf with JRE 9
Key: KARAF-4845
URL: https://issues.apache.org/jira/browse/KARAF-4845
Project: Karaf
Issue Type: Bug
Components: karaf-boot
Affects Versions: 4.1.0
Environment: Ubuntu
JRE Early Access Releases 9 Build 146
Reporter: Lijun Liao
Fix For: 4.1.0
Starting karaf with JRE 9 fails with the following error message:
{code}
$ bin/karaf
Error occurred during initialization of VM
java.lang.module.ResolutionException: Module jdk.xml.bind not found
at java.lang.module.Resolver.fail(java.base@9-ea/Resolver.java:790)
at
java.lang.module.Resolver.resolveRequires(java.base@9-ea/Resolver.java:94)
at
java.lang.module.Configuration.resolveRequiresAndUses(java.base@9-ea/Configuration.java:370)
at
java.lang.module.ModuleDescriptor$1.resolveRequiresAndUses(java.base@9-ea/ModuleDescriptor.java:1987)
at
jdk.internal.module.ModuleBootstrap.boot(java.base@9-ea/ModuleBootstrap.java:260)
at java.lang.System.initPhase2(java.base@9-ea/System.java:1927)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4844) ERROR logged if the property featuresBoot contains pax-jetty in 2nd stage
Lijun Liao created KARAF-4844:
-
Summary: ERROR logged if the property featuresBoot contains
pax-jetty in 2nd stage
Key: KARAF-4844
URL: https://issues.apache.org/jira/browse/KARAF-4844
Project: Karaf
Issue Type: Bug
Affects Versions: 4.1.0
Reporter: Lijun Liao
Fix For: 4.1.0
By starting karaf with the following property in
etc/org.apache.karaf.features.cfg
{code}
featuresBoot = \
(instance, \
...
kar), pax-jetty
{code}
, one will get the following ERROR messages in data/log/karaf.log:
{code}
2016-11-23T21:31:43,216 | ERROR | FelixStartLevel | Felix
| - - | Bundle org.objectweb.asm.all [52] Error locking
mvn:org.ow2.asm/asm-all/6.0_ALPHA (java.lang.IllegalStateException: Bundle in
unexpected state.)
java.lang.IllegalStateException: Bundle in unexpected state.
at org.apache.felix.framework.Felix.acquireBundleLock(Felix.java:5272)
[?:?]
at
org.apache.felix.framework.Felix.setBundleStartLevel(Felix.java:1524) [?:?]
at
org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:338)
[?:?]
at java.lang.Thread.run(Thread.java:745) [?:?]
2016-11-23T21:31:43,215 | ERROR | FelixDispatchQueue | all
| 85 - org.objectweb.asm.all - 5.0.2 | FrameworkEvent ERROR -
org.objectweb.asm.all
java.lang.IllegalStateException: Bundle in unexpected state.
at org.apache.felix.framework.Felix.acquireBundleLock(Felix.java:5272)
[?:?]
at
org.apache.felix.framework.Felix.setBundleStartLevel(Felix.java:1524) [?:?]
at
org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:338)
[?:?]
at java.lang.Thread.run(Thread.java:745) [?:?]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4835) Add content assist for paths in karaf shell source
[ https://issues.apache.org/jira/browse/KARAF-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-4835: -- Affects Version/s: 4.0.8 > Add content assist for paths in karaf shell source > -- > > Key: KARAF-4835 > URL: https://issues.apache.org/jira/browse/KARAF-4835 > Project: Karaf > Issue Type: Task > Components: karaf-shell >Affects Versions: 4.1.0, 4.0.8 >Reporter: Lijun Liao > Fix For: 4.1.0, 4.0.8 > > > Add auto-completion of file path to the karaf command "source", like in > command "install". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4830) Karaf does not start with staged features in etc/org.apache.karaf.features.cfg
[
https://issues.apache.org/jira/browse/KARAF-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15689569#comment-15689569
]
Lijun Liao commented on KARAF-4830:
---
The karaf (both version 4.0.8-SNAPSHOT and 4.1.0-SNAPSHOT) will not start even
if the whole property definition is on one line.
> Karaf does not start with staged features in etc/org.apache.karaf.features.cfg
> --
>
> Key: KARAF-4830
> URL: https://issues.apache.org/jira/browse/KARAF-4830
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.1.0, 4.0.8
>Reporter: Lijun Liao
>Assignee: Guillaume Nodet
> Fix For: 4.1.0, 4.0.8
>
>
> The property featuresBoot in the file etc/org.apache.karaf.features.cfg
> specifies the features to be started during the boot process.
> As described in JIRA issue KARAF-4249, I have to stage the features to
> include features containing wrapped bundle in the boot process. However, such
> configuration prevents from the booting of karaf.
> Steps to reproduce the problem:
> 1. Change the property featuresBoot
> {code}
> featuresBoot = \
> instance, \
> ...
> kar
> {code}
> to
> {code}
> featuresBoot = \
> (instance, \
> ...
> kar), transaction-api
> {code}
> 2. Start karaf (bin/karaf)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4830) Karaf does not start with staged features in etc/org.apache.karaf.features.cfg
[
https://issues.apache.org/jira/browse/KARAF-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4830:
--
Fix Version/s: 4.0.8
> Karaf does not start with staged features in etc/org.apache.karaf.features.cfg
> --
>
> Key: KARAF-4830
> URL: https://issues.apache.org/jira/browse/KARAF-4830
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.1.0, 4.0.8
>Reporter: Lijun Liao
> Fix For: 4.1.0, 4.0.8
>
>
> The property featuresBoot in the file etc/org.apache.karaf.features.cfg
> specifies the features to be started during the boot process.
> As described in JIRA issue KARAF-4249, I have to stage the features to
> include features containing wrapped bundle in the boot process. However, such
> configuration prevents from the booting of karaf.
> Steps to reproduce the problem:
> 1. Change the property featuresBoot
> {code}
> featuresBoot = \
> instance, \
> ...
> kar
> {code}
> to
> {code}
> featuresBoot = \
> (instance, \
> ...
> kar), transaction-api
> {code}
> 2. Start karaf (bin/karaf)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4830) Karaf does not start with staged features in etc/org.apache.karaf.features.cfg
[
https://issues.apache.org/jira/browse/KARAF-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4830:
--
Affects Version/s: 4.0.8
> Karaf does not start with staged features in etc/org.apache.karaf.features.cfg
> --
>
> Key: KARAF-4830
> URL: https://issues.apache.org/jira/browse/KARAF-4830
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.1.0, 4.0.8
>Reporter: Lijun Liao
> Fix For: 4.1.0, 4.0.8
>
>
> The property featuresBoot in the file etc/org.apache.karaf.features.cfg
> specifies the features to be started during the boot process.
> As described in JIRA issue KARAF-4249, I have to stage the features to
> include features containing wrapped bundle in the boot process. However, such
> configuration prevents from the booting of karaf.
> Steps to reproduce the problem:
> 1. Change the property featuresBoot
> {code}
> featuresBoot = \
> instance, \
> ...
> kar
> {code}
> to
> {code}
> featuresBoot = \
> (instance, \
> ...
> kar), transaction-api
> {code}
> 2. Start karaf (bin/karaf)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4837) Session#readLine should not append to history
[
https://issues.apache.org/jira/browse/KARAF-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15687742#comment-15687742
]
Lijun Liao commented on KARAF-4837:
---
No. At least not in karaf 4.0.0 - 4.0.7.
> Session#readLine should not append to history
> -
>
> Key: KARAF-4837
> URL: https://issues.apache.org/jira/browse/KARAF-4837
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
> Attachments: SayHelloCommand.java
>
>
> Considering the karaf shell demo-scope:say-hello implemented by the attached
> file SayHelloCommand.java. The entered text "Bob" is included in the list of
> historical commands. This is not expected.
> {code}
> karaf@root()>demo-scope:say-hello xx:xx:xx
> Enter your name: Bob
> Hello Alice
> karaf@root()
> karaf@root()Bob
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4832) Cannot enter karaf command over multi lines
[
https://issues.apache.org/jira/browse/KARAF-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4832:
--
Description:
Steps to reproduce the problem:
1. In karaf shell, enter "echo \", then enter
2. In the new line, enter any text, then enter
You should get the following error text:
{code}
karaf@root()> echo \ xx:xx:xx
> demo-text
gogo: CommandNotFoundException: Command not found: demo-text
Command not found: demo-text
{code}
was:
Steps to reproduce the problem:
1. In karaf shell, enter "echo \", then enter
2. In the new line, enter any text, then enter
You should get the following error text:
{code}
karaf@root()> echo \ xx:xx:xx
> demo-text
gogo: CommandNotFoundException: Command not found: demo-text
Command not found: demo-text
{code}
> Cannot enter karaf command over multi lines
> ---
>
> Key: KARAF-4832
> URL: https://issues.apache.org/jira/browse/KARAF-4832
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
>
> Steps to reproduce the problem:
> 1. In karaf shell, enter "echo \", then enter
> 2. In the new line, enter any text, then enter
> You should get the following error text:
> {code}
> karaf@root()> echo \ xx:xx:xx
> > demo-text
> gogo: CommandNotFoundException: Command not found: demo-text
> Command not found: demo-text
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4832) Cannot enter karaf command over multi lines
[
https://issues.apache.org/jira/browse/KARAF-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4832:
--
Description:
Steps to reproduce the problem:
1. In karaf shell, enter "echo \", then enter
2. In the new line, enter any text, then enter
You should get the following error text:
{code}
karaf@root()> echo \ xx:xx:xx
> demo-text
gogo: CommandNotFoundException: Command not found: demo-text
Command not found: demo-text
{code}
was:
Steps to reproduce the problem:
1. In karaf shell, enter "echo \", then enter
2. In the new line, enter any text, then enter
You should get the following error text:
{code}
karaf@root()> echo \
xx:xx:xx
> demo-text
gogo: CommandNotFoundException: Command not found: demo-text
Command not found: demo-text
{code}
> Cannot enter karaf command over multi lines
> ---
>
> Key: KARAF-4832
> URL: https://issues.apache.org/jira/browse/KARAF-4832
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
>
> Steps to reproduce the problem:
> 1. In karaf shell, enter "echo \", then enter
> 2. In the new line, enter any text, then enter
> You should get the following error text:
> {code}
> karaf@root()> echo \ xx:xx:xx
> > demo-text
> gogo: CommandNotFoundException: Command not found: demo-text
> Command not found: demo-text
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4834) Infinite loop if Exception occurs during the execution of karaf.shell.init.script
[
https://issues.apache.org/jira/browse/KARAF-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4834:
--
Description:
The while block between line 329 and line 352 in
https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
will never break if Exception other than EndOfFileException is thrown, e.g.
StreamClosed exception.
After executing a karaf command I happened to get the Interrupted error, then
the branding screen was shown, followed by infinite Stream Closed IOException.
Sorry I got this phenomenon only from time to time and cannot provide stable
steps to reproduce it.
{code}
karaf@root()
Error executing command: java.lang.InterruptedException
gogo: InterruptedException: null
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.0-SNAPSHOT)
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.io.IOException: Stream Closed
... hunderts lines with same content ignored here ...
karaf@root()> Error executing command: java.io.IOException: Stream Closed
{code}
I have attached the log.
was:
The while block between line 329 and line 352 in
https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
will never break if Exception other than EndOfFileException is thrown, e.g.
StreamClosed exception.
After executing a karaf command I happened to get the Interrupted error, then
the branding screen was shown, followed by infinite Stream Closed IOException.
Sorry I get this phenomenon only randomly and cannot provide stable steps to
reproduce it.
{code}
karaf@root()
Error executing command: java.lang.InterruptedException
gogo: InterruptedException: null
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.0-SNAPSHOT)
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.io.IOException: Stream Closed
... hunderts lines with same content ignored here ...
karaf@root()> Error executing command: java.io.IOException: Stream Closed
{code}
I have attached the log.
> Infinite loop if Exception occurs during the execution of
> karaf.shell.init.script
> -
>
> Key: KARAF-4834
> URL: https://issues.apache.org/jira/browse/KARAF-4834
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
> Attachments: karaf.log
>
>
> The while block between line 329 and line 352 in
> https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
> will never break if Exception other than EndOfFileException is thrown, e.g.
> StreamClosed exception.
> After executing a karaf command I happened to get the Interrupted error, then
> the branding screen was shown, followed by infinite Stream Closed
> IOException. Sorry I got this phenomenon only from time to time and
> cannot provide stable steps to reproduce it.
> {code}
> karaf@root()
> Error executing command: java.lang.InterruptedException
> gogo: InterruptedException: null
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.1.0-SNAPSHOT)
> 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.io.IOException: Stream Closed
> ... hunderts lines with same content ignored here ...
> karaf@root()> Error executing command: java.io.IOException: Stream Closed
> {code}
> I have attached the log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4838) InterruptedException of karaf shell will not be forwarded to the command
Lijun Liao created KARAF-4838: - Summary: InterruptedException of karaf shell will not be forwarded to the command Key: KARAF-4838 URL: https://issues.apache.org/jira/browse/KARAF-4838 Project: Karaf Issue Type: Bug Components: karaf-shell Affects Versions: 4.1.0 Reporter: Lijun Liao Fix For: 4.1.0 In karaf 4.0.7, the InterruptedException (triggered by CTRL + C) is forwarded by the karaf shell to the command. This forwarding is useful since the application can then decide whether it should cancel the action. However this forwarding has been deactivated in karaf 4.1.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4837) List of historical commands is not correct
[
https://issues.apache.org/jira/browse/KARAF-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4837:
--
Attachment: SayHelloCommand.java
> List of historical commands is not correct
> --
>
> Key: KARAF-4837
> URL: https://issues.apache.org/jira/browse/KARAF-4837
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
> Attachments: SayHelloCommand.java
>
>
> Considering the karaf shell demo-scope:say-hello implemented by the attached
> file SayHelloCommand.java. The entered text "Bob" is included in the list of
> historical commands. This is not expected.
> {code}
> karaf@root()>demo-scope:say-hello
> xx:xx:xx
> Enter your name: Bob
> Hello Alice
> karaf@root()
> karaf@root()Bob
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4837) List of historical commands is not correct
[
https://issues.apache.org/jira/browse/KARAF-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4837:
--
Description:
Considering the karaf shell demo-scope:say-hello implemented by the attached
file SayHelloCommand.java. The entered text "Bob" is included in the list of
historical commands. This is not expected.
{code}
karaf@root()>demo-scope:say-hello xx:xx:xx
Enter your name: Bob
Hello Alice
karaf@root()
karaf@root()Bob
{code}
was:
Considering the karaf shell demo-scope:say-hello implemented by the attached
file SayHelloCommand.java. The entered text "Bob" is included in the list of
historical commands. This is not expected.
{code}
karaf@root()>demo-scope:say-hello
xx:xx:xx
Enter your name: Bob
Hello Alice
karaf@root()
karaf@root()Bob
{code}
> List of historical commands is not correct
> --
>
> Key: KARAF-4837
> URL: https://issues.apache.org/jira/browse/KARAF-4837
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
> Attachments: SayHelloCommand.java
>
>
> Considering the karaf shell demo-scope:say-hello implemented by the attached
> file SayHelloCommand.java. The entered text "Bob" is included in the list of
> historical commands. This is not expected.
> {code}
> karaf@root()>demo-scope:say-hello xx:xx:xx
> Enter your name: Bob
> Hello Alice
> karaf@root()
> karaf@root()Bob
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4836) Incorrect behaviour of the auto-completion of file path in command export-bundles
[
https://issues.apache.org/jira/browse/KARAF-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4836:
--
Attachment: (was: SayHelloCommand.java)
> Incorrect behaviour of the auto-completion of file path in command
> export-bundles
> -
>
> Key: KARAF-4836
> URL: https://issues.apache.org/jira/browse/KARAF-4836
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
>
> 1. The auto-completation converts relative path to absolute path.
> To reproduce start karaf and type
> {code}
> export-bundles jdbc dat
> {code}
> You will get
> {code}
> export-bundles jdbc
> /Users/lliao/Documents/source/t/apache-karaf-4.1.0-SNAPSHOT/./data/
> {code}
> However the following should be expected
> {code}
> export-bundles jdbc data
> {code}
> or
> {code}
> export-bundles jdbc ./data
> {code}
> 2. The auto-completation cannot handle '~' for home directory of current user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4836) Incorrect behaviour of the auto-completion of file path in command export-bundles
[
https://issues.apache.org/jira/browse/KARAF-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4836:
--
Attachment: SayHelloCommand.java
> Incorrect behaviour of the auto-completion of file path in command
> export-bundles
> -
>
> Key: KARAF-4836
> URL: https://issues.apache.org/jira/browse/KARAF-4836
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
> Attachments: SayHelloCommand.java
>
>
> 1. The auto-completation converts relative path to absolute path.
> To reproduce start karaf and type
> {code}
> export-bundles jdbc dat
> {code}
> You will get
> {code}
> export-bundles jdbc
> /Users/lliao/Documents/source/t/apache-karaf-4.1.0-SNAPSHOT/./data/
> {code}
> However the following should be expected
> {code}
> export-bundles jdbc data
> {code}
> or
> {code}
> export-bundles jdbc ./data
> {code}
> 2. The auto-completation cannot handle '~' for home directory of current user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4837) List of historical commands is not correct
Lijun Liao created KARAF-4837:
-
Summary: List of historical commands is not correct
Key: KARAF-4837
URL: https://issues.apache.org/jira/browse/KARAF-4837
Project: Karaf
Issue Type: Bug
Components: karaf-shell
Affects Versions: 4.1.0
Reporter: Lijun Liao
Fix For: 4.1.0
Considering the karaf shell demo-scope:say-hello implemented by the attached
file SayHelloCommand.java. The entered text "Bob" is included in the list of
historical commands. This is not expected.
{code}
karaf@root()>demo-scope:say-hello
xx:xx:xx
Enter your name: Bob
Hello Alice
karaf@root()
karaf@root()Bob
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4836) Incorrect behaviour of the auto-completion of file path in command export-bundles
Lijun Liao created KARAF-4836:
-
Summary: Incorrect behaviour of the auto-completion of file path
in command export-bundles
Key: KARAF-4836
URL: https://issues.apache.org/jira/browse/KARAF-4836
Project: Karaf
Issue Type: Bug
Components: karaf-shell
Affects Versions: 4.1.0
Reporter: Lijun Liao
Fix For: 4.1.0
1. The auto-completation converts relative path to absolute path.
To reproduce start karaf and type
{code}
export-bundles jdbc dat
{code}
You will get
{code}
export-bundles jdbc
/Users/lliao/Documents/source/t/apache-karaf-4.1.0-SNAPSHOT/./data/
{code}
However the following should be expected
{code}
export-bundles jdbc data
{code}
or
{code}
export-bundles jdbc ./data
{code}
2. The auto-completation cannot handle '~' for home directory of current user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4835) Add content assist for paths in karaf shell source
Lijun Liao created KARAF-4835: - Summary: Add content assist for paths in karaf shell source Key: KARAF-4835 URL: https://issues.apache.org/jira/browse/KARAF-4835 Project: Karaf Issue Type: Task Components: karaf-shell Affects Versions: 4.1.0 Reporter: Lijun Liao Fix For: 4.1.0, 4.0.8 Add auto-completion of file path to the karaf command "source", like in command "install". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4834) Infinite loop if Exception occurs during the execution of karaf.shell.init.script
[
https://issues.apache.org/jira/browse/KARAF-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4834:
--
Description:
The while block between line 329 and line 352 in
https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
will never break if Exception other than EndOfFileException is thrown, e.g.
StreamClosed exception.
After executing a karaf command I happened to get the Interrupted error, then
the branding screen was shown, followed by infinite Stream Closed IOException.
Sorry I get this phenomenon only randomly and cannot provide stable steps to
reproduce it.
{code}
karaf@root()
Error executing command: java.lang.InterruptedException
gogo: InterruptedException: null
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.0-SNAPSHOT)
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.io.IOException: Stream Closed
... hunderts lines with same content ignored here ...
karaf@root()> Error executing command: java.io.IOException: Stream Closed
{code}
I have attached the log.
was:
The while block between line 329 and line 352 in
https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
will never break if Exception other than EndOfFileException is thrown, e.g.
StreamClosed exception.
After executing a karaf command I happened to get the Interrupted error, then
the branding screen was shown, followed by infinite StreamClosedException.
Sorry I get this phenomenon only randomly and cannot provide stable steps to
reproduce it.
{code}
karaf@root()
Error executing command: java.lang.InterruptedException
gogo: InterruptedException: null
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.0-SNAPSHOT)
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.io.IOException: Stream Closed
... hunderts lines with same content ignored here ...
karaf@root()> Error executing command: java.io.IOException: Stream Closed
{code}
I have attached the log.
> Infinite loop if Exception occurs during the execution of
> karaf.shell.init.script
> -
>
> Key: KARAF-4834
> URL: https://issues.apache.org/jira/browse/KARAF-4834
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
> Attachments: karaf.log
>
>
> The while block between line 329 and line 352 in
> https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
> will never break if Exception other than EndOfFileException is thrown, e.g.
> StreamClosed exception.
> After executing a karaf command I happened to get the Interrupted error, then
> the branding screen was shown, followed by infinite Stream Closed
> IOException. Sorry I get this phenomenon only randomly and cannot provide
> stable steps to reproduce it.
> {code}
> karaf@root()
> Error executing command: java.lang.InterruptedException
> gogo: InterruptedException: null
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.1.0-SNAPSHOT)
> 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.io.IOException: Stream Closed
> ... hunderts lines with same content ignored here ...
> karaf@root()> Error executing command: java.io.IOException: Stream Closed
> {code}
> I have attached the log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4834) Infinite loop if Exception occurs during the execution of karaf.shell.init.script
[
https://issues.apache.org/jira/browse/KARAF-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4834:
--
Description:
The while block between line 329 and line 352 in
https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
will never break if Exception other than EndOfFileException is thrown, e.g.
StreamClosed exception.
After executing a karaf command I happened to get the Interrupted error, then
the branding screen was shown, followed by infinite StreamClosedException.
Sorry I get this phenomenon only randomly and cannot provide stable steps to
reproduce it.
{code}
karaf@root()
Error executing command: java.lang.InterruptedException
gogo: InterruptedException: null
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.0-SNAPSHOT)
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.io.IOException: Stream Closed
... hunderts lines with same content ignored here ...
karaf@root()> Error executing command: java.io.IOException: Stream Closed
{code}
I have attached the log.
was:
The while block between line 329 and line 352 in
https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
will never break if Exception other than EndOfFileException is thrown, e.g.
StreamClosed exception.
After executing a karaf command I happened to get the Interrupted error, then
the branding screen was shown, followed by infinite StreamClosedException.
Sorry I get this phenomenon only randomly and cannot provide stable steps to
reproce it.
{code}
karaf@root()
Error executing command: java.lang.InterruptedException
gogo: InterruptedException: null
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.0-SNAPSHOT)
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.io.IOException: Stream Closed
... hunderts lines with same content ignored here ...
karaf@root()> Error executing command: java.io.IOException: Stream Closed
{code}
> Infinite loop if Exception occurs during the execution of
> karaf.shell.init.script
> -
>
> Key: KARAF-4834
> URL: https://issues.apache.org/jira/browse/KARAF-4834
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
> Attachments: karaf.log
>
>
> The while block between line 329 and line 352 in
> https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
> will never break if Exception other than EndOfFileException is thrown, e.g.
> StreamClosed exception.
> After executing a karaf command I happened to get the Interrupted error, then
> the branding screen was shown, followed by infinite StreamClosedException.
> Sorry I get this phenomenon only randomly and cannot provide stable steps to
> reproduce it.
> {code}
> karaf@root()
> Error executing command: java.lang.InterruptedException
> gogo: InterruptedException: null
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.1.0-SNAPSHOT)
> 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.io.IOException: Stream Closed
> ... hunderts lines with same content ignored here ...
> karaf@root()> Error executing command: java.io.IOException: Stream Closed
> {code}
> I have attached the log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4834) Infinite loop if Exception occurs during the execution of karaf.shell.init.script
[
https://issues.apache.org/jira/browse/KARAF-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4834:
--
Attachment: karaf.log
> Infinite loop if Exception occurs during the execution of
> karaf.shell.init.script
> -
>
> Key: KARAF-4834
> URL: https://issues.apache.org/jira/browse/KARAF-4834
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
> Attachments: karaf.log
>
>
> The while block between line 329 and line 352 in
> https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
> will never break if Exception other than EndOfFileException is thrown, e.g.
> StreamClosed exception.
> After executing a karaf command I happened to get the Interrupted error, then
> the branding screen was shown, followed by infinite StreamClosedException.
> Sorry I get this phenomenon only randomly and cannot provide stable steps to
> reproduce it.
> {code}
> karaf@root()
> Error executing command: java.lang.InterruptedException
> gogo: InterruptedException: null
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.1.0-SNAPSHOT)
> 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.io.IOException: Stream Closed
> ... hunderts lines with same content ignored here ...
> karaf@root()> Error executing command: java.io.IOException: Stream Closed
> {code}
> I have attached the log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4834) Infinite loop if Exception occurs during the execution of karaf.shell.init.script
[
https://issues.apache.org/jira/browse/KARAF-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4834:
--
Description:
The while block between line 329 and line 352 in
https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
will never break if Exception other than EndOfFileException is thrown, e.g.
StreamClosed exception.
After executing a karaf command I happened to get the Interrupted error, then
the branding screen was shown, followed by infinite StreamClosedException.
Sorry I get this phenomenon only randomly and cannot provide stable steps to
reproce it.
{code}
karaf@root()
Error executing command: java.lang.InterruptedException
gogo: InterruptedException: null
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.0-SNAPSHOT)
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.io.IOException: Stream Closed
... hunderts lines with same content ignored here ...
karaf@root()> Error executing command: java.io.IOException: Stream Closed
{code}
was:The while block between line 329 and line 352 in
https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
will never break if Exception other than EndOfFileException is thrown, e.g.
StreamClosed exception.
> Infinite loop if Exception occurs during the execution of
> karaf.shell.init.script
> -
>
> Key: KARAF-4834
> URL: https://issues.apache.org/jira/browse/KARAF-4834
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
>
> The while block between line 329 and line 352 in
> https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java
> will never break if Exception other than EndOfFileException is thrown, e.g.
> StreamClosed exception.
> After executing a karaf command I happened to get the Interrupted error, then
> the branding screen was shown, followed by infinite StreamClosedException.
> Sorry I get this phenomenon only randomly and cannot provide stable steps to
> reproce it.
> {code}
> karaf@root()
> Error executing command: java.lang.InterruptedException
> gogo: InterruptedException: null
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.1.0-SNAPSHOT)
> 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.io.IOException: Stream Closed
> ... hunderts lines with same content ignored here ...
> karaf@root()> Error executing command: java.io.IOException: Stream Closed
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4834) Infinite loop if Exception occurs during the execution of karaf.shell.init.script
[ https://issues.apache.org/jira/browse/KARAF-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijun Liao updated KARAF-4834: -- Summary: Infinite loop if Exception occurs during the execution of karaf.shell.init.script (was: Endless loop if Exception occurs during the execution of karaf.shell.init.script) > Infinite loop if Exception occurs during the execution of > karaf.shell.init.script > - > > Key: KARAF-4834 > URL: https://issues.apache.org/jira/browse/KARAF-4834 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.1.0 >Reporter: Lijun Liao > Fix For: 4.1.0 > > > The while block between line 329 and line 352 in > https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java > will never break if Exception other than EndOfFileException is thrown, e.g. > StreamClosed exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4834) Endless loop if Exception occurs during the execution of karaf.shell.init.script
Lijun Liao created KARAF-4834: - Summary: Endless loop if Exception occurs during the execution of karaf.shell.init.script Key: KARAF-4834 URL: https://issues.apache.org/jira/browse/KARAF-4834 Project: Karaf Issue Type: Bug Components: karaf-shell Affects Versions: 4.1.0 Reporter: Lijun Liao Fix For: 4.1.0 The while block between line 329 and line 352 in https://github.com/apache/karaf/blob/master/shell/core/src/main/java/org/apache/karaf/shell/impl/console/ConsoleSessionImpl.java will never break if Exception other than EndOfFileException is thrown, e.g. StreamClosed exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4833) Incorrect behaviour of executing commands over multi lines via source
[
https://issues.apache.org/jira/browse/KARAF-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-4833:
--
Description:
Steps to reproduce the error:
1. Create a file demo.script with following text
{code}
feature:install \
"invalid-feature-name"
{code}
2. In karaf shell, enter source demo.script
You will get the following message:
{code}
karaf@root()> source tmp/demo.script
xx:xx:xx
gogo: IllegalArgumentException: No matching features for
invalid-feature-name/0.0.0
gogo: IllegalArgumentException: No matching features for
invalid-feature-name/0.0.0
Error executing command: No matching features for invalid-feature-name/0.0.0
{code}
Since the given feature does not exist, an IllegalArgumentException will be
thrown. The expected behavour is that the throw exception will be outputted
once.
was:
Steps to reproduce the error:
1. Create a file demo.script with following text
{code}
feature:install \
"invalid-feature-name"
{code}
2. In karaf shell, enter source demo.script
You will get the following message:
{code}
karaf@root()> source tmp/demo.script
09:41:34
gogo: IllegalArgumentException: No matching features for
invalid-feature-name/0.0.0
gogo: IllegalArgumentException: No matching features for
invalid-feature-name/0.0.0
Error executing command: No matching features for invalid-feature-name/0.0.0
{code}
Since the given feature does not exist, an IllegalArgumentException will be
thrown. The expected behavour is that the throw exception will be outputted
once.
> Incorrect behaviour of executing commands over multi lines via source
> -
>
> Key: KARAF-4833
> URL: https://issues.apache.org/jira/browse/KARAF-4833
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
> Fix For: 4.1.0
>
>
> Steps to reproduce the error:
> 1. Create a file demo.script with following text
> {code}
> feature:install \
> "invalid-feature-name"
> {code}
> 2. In karaf shell, enter source demo.script
> You will get the following message:
> {code}
> karaf@root()> source tmp/demo.script
>xx:xx:xx
> gogo: IllegalArgumentException: No matching features for
> invalid-feature-name/0.0.0
> gogo: IllegalArgumentException: No matching features for
> invalid-feature-name/0.0.0
> Error executing command: No matching features for invalid-feature-name/0.0.0
> {code}
> Since the given feature does not exist, an IllegalArgumentException will be
> thrown. The expected behavour is that the throw exception will be outputted
> once.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4833) Incorrect behaviour of executing commands over multi lines via source
Lijun Liao created KARAF-4833:
-
Summary: Incorrect behaviour of executing commands over multi
lines via source
Key: KARAF-4833
URL: https://issues.apache.org/jira/browse/KARAF-4833
Project: Karaf
Issue Type: Bug
Components: karaf-shell
Affects Versions: 4.1.0
Reporter: Lijun Liao
Fix For: 4.1.0
Steps to reproduce the error:
1. Create a file demo.script with following text
{code}
feature:install \
"invalid-feature-name"
{code}
2. In karaf shell, enter source demo.script
You will get the following message:
{code}
karaf@root()> source tmp/demo.script
09:41:34
gogo: IllegalArgumentException: No matching features for
invalid-feature-name/0.0.0
gogo: IllegalArgumentException: No matching features for
invalid-feature-name/0.0.0
Error executing command: No matching features for invalid-feature-name/0.0.0
{code}
Since the given feature does not exist, an IllegalArgumentException will be
thrown. The expected behavour is that the throw exception will be outputted
once.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4832) Cannot enter karaf command over multi lines
Lijun Liao created KARAF-4832:
-
Summary: Cannot enter karaf command over multi lines
Key: KARAF-4832
URL: https://issues.apache.org/jira/browse/KARAF-4832
Project: Karaf
Issue Type: Bug
Components: karaf-shell
Affects Versions: 4.1.0
Reporter: Lijun Liao
Fix For: 4.1.0
Steps to reproduce the problem:
1. In karaf shell, enter "echo \", then enter
2. In the new line, enter any text, then enter
You should get the following error text:
{code}
karaf@root()> echo \
xx:xx:xx
> demo-text
gogo: CommandNotFoundException: Command not found: demo-text
Command not found: demo-text
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (KARAF-4827) Cannot install feature depending on other 2+ levels of features with prerequisite="true"
[
https://issues.apache.org/jira/browse/KARAF-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15684385#comment-15684385
]
Lijun Liao edited comment on KARAF-4827 at 11/22/16 6:10 AM:
-
The configuration as described in the issue works in the fixed version.
Additionally it works also for the following configuration
{code:xml}
mvn:javax.interceptor/javax.interceptor-api/1.2
demo-a
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2
demo-b
mvn:javax.el/javax.el-api/3.0.0
{code}
But executing karaf command feature:install demo-c fails with following error
message
{code}
karaf@root()> feature:install demo-c
gogo: CircularPrerequisiteException: [demo-a/0.0.0]
Error executing command: [demo-a/0.0.0]
{code}
for all configurations below:
1. Version of prerequisite feature is not specified
{code:xml}
mvn:javax.interceptor/javax.interceptor-api/1.2
demo-a
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2
demo-b
mvn:javax.el/javax.el-api/3.0.0
{code}
2. Feature contains SNAPSHOT version
{code:xml}
mvn:javax.interceptor/javax.interceptor-api/1.2
demo-a
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2
demo-b
mvn:javax.el/javax.el-api/3.0.0
{code}
was (Author: lliao):
The configuration as described in the issue works in the fixed version.
Additionally it works also for the following configuration
{code:xml}
mvn:javax.interceptor/javax.interceptor-api/1.2
demo-a
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2
demo-b
mvn:javax.el/javax.el-api/3.0.0
{code}
But executing karaf command feature:install demo-c fails with following error
message
{code}
karaf@root()> feature:install demo-c
gogo: CircularPrerequisiteException: [demo-a/0.0.0]
Error executing command: [demo-a/0.0.0]
{code}
for all configurations below:
1. Version of prerequisite is not specified
{code:xml}
mvn:javax.interceptor/javax.interceptor-api/1.2
demo-a
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2
demo-b
mvn:javax.el/javax.el-api/3.0.0
{code}
2. Feature contains SNAPSHOT version
{code:xml}
mvn:javax.interceptor/javax.interceptor-api/1.2
demo-a
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2
demo-b
mvn:javax.el/javax.el-api/3.0.0
{code}
> Cannot install feature depending on other 2+ levels of features with
> prerequisite="true"
>
>
> Key: KARAF-4827
> URL: https://issues.apache.org/jira/browse/KARAF-4827
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
>Assignee: Guillaume Nodet
>Priority: Blocker
> Fix For: 4.1.0
>
>
> Steps to reproduce the error:
> 1. Unpack apache-karaf-4.1.0-SNAPSHOT.tar.gz
> 2. Add following block to the file
> "system/org/apache/karaf/features/enterprise/4.1.0-SNAPSHOT/enterprise-4.1.0-SNAPSHOT-features.xml"
> {code:xml}
>
> mvn:javax.interceptor/javax.interceptor-api/1.2
>
>
>
> demo-a
>
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2
>
>
>
> demo-b
> mvn:javax.el/javax.el-api/3.0.0
>
> {code}
> 3. Delete folder data and file lock if available
> 4. Start karaf (command "bin/karaf")
> 5. Execute command "feature:install demo-c" in karaf shell, you should get
> the following error message.
> {code}
> karaf@root()> feature:install demo-c
> xx:xx:xx
> gogo: CircularPrerequisiteException: [demo-a/0.0.0]
> Error executing command: [demo-a/0.0.0]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4831) Different behaviour of shell "sleep" between karaf 4.1.0 and 4.0.7
Lijun Liao created KARAF-4831: - Summary: Different behaviour of shell "sleep" between karaf 4.1.0 and 4.0.7 Key: KARAF-4831 URL: https://issues.apache.org/jira/browse/KARAF-4831 Project: Karaf Issue Type: Bug Components: karaf-shell Affects Versions: 4.1.0 Reporter: Lijun Liao Fix For: 4.1.0 In karaf 4.0.7 "sleep 1000" tells the system to sleep 1000 milli seconds, in karaf 4.1.0 it is 1000 seconds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4830) Karaf does not start with staged features in etc/org.apache.karaf.features.cfg
Lijun Liao created KARAF-4830:
-
Summary: Karaf does not start with staged features in
etc/org.apache.karaf.features.cfg
Key: KARAF-4830
URL: https://issues.apache.org/jira/browse/KARAF-4830
Project: Karaf
Issue Type: Bug
Components: karaf-feature
Affects Versions: 4.1.0
Reporter: Lijun Liao
Fix For: 4.1.0
The property featuresBoot in the file etc/org.apache.karaf.features.cfg
specifies the features to be started during the boot process.
As described in JIRA issue KARAF-4249, I have to stage the features to include
features containing wrapped bundle in the boot process. However, such
configuration prevents from the booting of karaf.
Steps to reproduce the problem:
1. Change the property featuresBoot
{code}
featuresBoot = \
instance, \
...
kar
{code}
to
{code}
featuresBoot = \
(instance, \
...
kar), transaction-api
{code}
2. Start karaf (bin/karaf)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (KARAF-4827) Cannot install feature depending on other 2+ levels of features with prerequisite="true"
[
https://issues.apache.org/jira/browse/KARAF-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15684385#comment-15684385
]
Lijun Liao edited comment on KARAF-4827 at 11/21/16 6:46 PM:
-
The configuration as described in the issue works in the fixed version.
Additionally it works also for the following configuration
{code:xml}
mvn:javax.interceptor/javax.interceptor-api/1.2
demo-a
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2
demo-b
mvn:javax.el/javax.el-api/3.0.0
{code}
But executing karaf command feature:install demo-c fails with following error
message
{code}
karaf@root()> feature:install demo-c
gogo: CircularPrerequisiteException: [demo-a/0.0.0]
Error executing command: [demo-a/0.0.0]
{code}
for all configurations below:
1. Version of prerequisite is not specified
{code:xml}
mvn:javax.interceptor/javax.interceptor-api/1.2
demo-a
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2
demo-b
mvn:javax.el/javax.el-api/3.0.0
{code}
2. Feature contains SNAPSHOT version
{code:xml}
mvn:javax.interceptor/javax.interceptor-api/1.2
demo-a
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2
demo-b
mvn:javax.el/javax.el-api/3.0.0
{code}
was (Author: lliao):
The configuration as described in the issue works in the fixed version.
Additionally it works also for the following configuration
{code:xml}
mvn:javax.interceptor/javax.interceptor-api/1.2
demo-a
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2
demo-b
mvn:javax.el/javax.el-api/3.0.0
{code}
But executing karaf command feature:install demo-c fails with following error
message
{code}
karaf@root()> feature:install demo-c
gogo: CircularPrerequisiteException: [demo-a/0.0.0]
Error executing command: [demo-a/0.0.0]
{code}
for all configuration below:
1. Version of prerequisite is not specified
{code:xml}
mvn:javax.interceptor/javax.interceptor-api/1.2
demo-a
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2
demo-b
mvn:javax.el/javax.el-api/3.0.0
{code}
2. Feature contains SNAPSHOT version
{code:xml}
mvn:javax.interceptor/javax.interceptor-api/1.2
demo-a
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2
demo-b
mvn:javax.el/javax.el-api/3.0.0
{code}
> Cannot install feature depending on other 2+ levels of features with
> prerequisite="true"
>
>
> Key: KARAF-4827
> URL: https://issues.apache.org/jira/browse/KARAF-4827
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
>Assignee: Guillaume Nodet
>Priority: Blocker
> Fix For: 4.1.0
>
>
> Steps to reproduce the error:
> 1. Unpack apache-karaf-4.1.0-SNAPSHOT.tar.gz
> 2. Add following block to the file
> "system/org/apache/karaf/features/enterprise/4.1.0-SNAPSHOT/enterprise-4.1.0-SNAPSHOT-features.xml"
> {code:xml}
>
> mvn:javax.interceptor/javax.interceptor-api/1.2
>
>
>
> demo-a
>
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2
>
>
>
> demo-b
> mvn:javax.el/javax.el-api/3.0.0
>
> {code}
> 3. Delete folder data and file lock if available
> 4. Start karaf (command "bin/karaf")
> 5. Execute command "feature:install demo-c" in karaf shell, you should get
> the following error message.
> {code}
> karaf@root()> feature:install demo-c
> xx:xx:xx
> gogo: CircularPrerequisiteException: [demo-a/0.0.0]
> Error executing command: [demo-a/0.0.0]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (KARAF-4827) Cannot install feature depending on other 2+ levels of features with prerequisite="true"
[
https://issues.apache.org/jira/browse/KARAF-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao reopened KARAF-4827:
---
The configuration as described in the issue works in the fixed version.
Additionally it works also for the following configuration
{code:xml}
mvn:javax.interceptor/javax.interceptor-api/1.2
demo-a
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2
demo-b
mvn:javax.el/javax.el-api/3.0.0
{code}
But executing karaf command feature:install demo-c fails with following error
message
{code}
karaf@root()> feature:install demo-c
gogo: CircularPrerequisiteException: [demo-a/0.0.0]
Error executing command: [demo-a/0.0.0]
{code}
for all configuration below:
1. Version of prerequisite is not specified
{code:xml}
mvn:javax.interceptor/javax.interceptor-api/1.2
demo-a
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2
demo-b
mvn:javax.el/javax.el-api/3.0.0
{code}
2. Feature contains SNAPSHOT version
{code:xml}
mvn:javax.interceptor/javax.interceptor-api/1.2
demo-a
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2
demo-b
mvn:javax.el/javax.el-api/3.0.0
{code}
> Cannot install feature depending on other 2+ levels of features with
> prerequisite="true"
>
>
> Key: KARAF-4827
> URL: https://issues.apache.org/jira/browse/KARAF-4827
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.1.0
>Reporter: Lijun Liao
>Assignee: Guillaume Nodet
>Priority: Blocker
> Fix For: 4.1.0
>
>
> Steps to reproduce the error:
> 1. Unpack apache-karaf-4.1.0-SNAPSHOT.tar.gz
> 2. Add following block to the file
> "system/org/apache/karaf/features/enterprise/4.1.0-SNAPSHOT/enterprise-4.1.0-SNAPSHOT-features.xml"
> {code:xml}
>
> mvn:javax.interceptor/javax.interceptor-api/1.2
>
>
>
> demo-a
>
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2
>
>
>
> demo-b
> mvn:javax.el/javax.el-api/3.0.0
>
> {code}
> 3. Delete folder data and file lock if available
> 4. Start karaf (command "bin/karaf")
> 5. Execute command "feature:install demo-c" in karaf shell, you should get
> the following error message.
> {code}
> karaf@root()> feature:install demo-c
> xx:xx:xx
> gogo: CircularPrerequisiteException: [demo-a/0.0.0]
> Error executing command: [demo-a/0.0.0]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
