[jira] [Updated] (KARAF-5283) Karaf in offline (no internet) environment - NamespaceHandler bugs
[ https://issues.apache.org/jira/browse/KARAF-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5283: Fix Version/s: 4.1.3 4.2.0 > Karaf in offline (no internet) environment - NamespaceHandler bugs > -- > > Key: KARAF-5283 > URL: https://issues.apache.org/jira/browse/KARAF-5283 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.1 >Reporter: Pointbreak > Fix For: 4.2.0, 4.1.3 > > > See https://issues.apache.org/jira/browse/ARIES-1723. This was previously > fixed in https://issues.apache.org/jira/browse/ARIES-1540, but the fix was > only applied to blueprint-core-1.6.2, not to later versions. > Karaf 4.x.x uses blueprint-core-1.8.x, which contains the exact same bug that > blueprint-core-1.6.1 had. > It would be really helpfull if this could be fixed in a karaf bugfix release. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5284) Karaf 4.1.2-SNAPSHOT bourne shell script doesn't start in cygwin
[
https://issues.apache.org/jira/browse/KARAF-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114427#comment-16114427
]
Jean-Baptiste Onofré commented on KARAF-5284:
-
The build was on Linux, and the test on Windows 7 VM with Cygwin. I will try
with a build on Windows.
> Karaf 4.1.2-SNAPSHOT bourne shell script doesn't start in cygwin
>
>
> Key: KARAF-5284
> URL: https://issues.apache.org/jira/browse/KARAF-5284
> Project: Karaf
> Issue Type: Bug
> Environment: Karaf 4.1.2-SNAPSHOT, zip file assembly, built from a
> fresh pull.
> JDK 1.8_141
> CYGWIN_NT-10.0 mccoy 2.5.2(0.297/5/3) 2016-06-23 14:29 x86_64 Cygwin
>Reporter: Steinar Bang
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Labels: karaf-shell
>
> Starting karaf unpacked from a zip file, from a cygwin terminal works in
> karaf 4.1.1 (starting from the karaf.bat file doesn't work there).
> Starting karaf 4.1.2-SNAPSHOT unpacked from a freshly build zip file, does
> not work, when using the bin/karaf sh file. It does, however, work to start
> karaf using the karaf.bat file.
> Since karaf is startable from the cygwin window, which is the important thing
> (better copy/paste and window resizing features than cmd.exe), this isn't
> very important.
> But I'm reporting it anyway, since it is a change in behaviour since 4.1.1.
> Starting karaf using bin/karaf gave this error message
> {noformat}
> sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$ bin/karaf
> bin/karaf: line 18: $'\r': command not found
> bin/karaf: line 19: syntax error near unexpected token `$'{\r''
> 'in/karaf: line 19: `realpath() {
> {noformat}
> Since this is recognizable as a "problem with CR-LF" error message, I edit
> the bin/karaf in emacs, changing CRLF to just LF, but then I got these error
> messages:
> {noformat}
> sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$ bin/karaf
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 18: $'\r':
> command not found
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 19: syntax
> error near unexpected token `$'{\r''
> 'cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 19:
> `warn() {
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 18:
> $'\r': command not found
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 26:
> $'\r': command not found
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 33:
> $'\r': command not found
> bin/karaf: line 109: detectOS: command not found
> bin/karaf: line 112: unlimitFD: command not found
> bin/karaf: line 115: locateHome: command not found
> bin/karaf: line 118: locateBase: command not found
> bin/karaf: line 121: locateData: command not found
> bin/karaf: line 124: locateEtc: command not found
> bin/karaf: line 127: setupNativePath: command not found
> bin/karaf: line 130: locateJava: command not found
> bin/karaf: line 133: detectJVM: command not found
> bin/karaf: line 136: checkJvmVersion: command not found
> bin/karaf: line 142: setupDefaults: command not found
> bin/karaf: line 148: setupDebugOptions: command not found
> bin/karaf: line 165: convertPaths: command not found
> bin/karaf: line 243: KARAF_HOME: parameter null or not set
> sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5284) Karaf 4.1.2-SNAPSHOT bourne shell script doesn't start in cygwin
[
https://issues.apache.org/jira/browse/KARAF-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114425#comment-16114425
]
Steinar Bang commented on KARAF-5284:
-
Was the karaf 4.1.2-SNAPSHOT where you couldn't reproduce built on windows? Or
was it built on linux/BSD/etc.?
The 4.1.2-SNAPSHOT that failed for me was built on windows (and that might
affect the line ending of the scripts).
> Karaf 4.1.2-SNAPSHOT bourne shell script doesn't start in cygwin
>
>
> Key: KARAF-5284
> URL: https://issues.apache.org/jira/browse/KARAF-5284
> Project: Karaf
> Issue Type: Bug
> Environment: Karaf 4.1.2-SNAPSHOT, zip file assembly, built from a
> fresh pull.
> JDK 1.8_141
> CYGWIN_NT-10.0 mccoy 2.5.2(0.297/5/3) 2016-06-23 14:29 x86_64 Cygwin
>Reporter: Steinar Bang
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Labels: karaf-shell
>
> Starting karaf unpacked from a zip file, from a cygwin terminal works in
> karaf 4.1.1 (starting from the karaf.bat file doesn't work there).
> Starting karaf 4.1.2-SNAPSHOT unpacked from a freshly build zip file, does
> not work, when using the bin/karaf sh file. It does, however, work to start
> karaf using the karaf.bat file.
> Since karaf is startable from the cygwin window, which is the important thing
> (better copy/paste and window resizing features than cmd.exe), this isn't
> very important.
> But I'm reporting it anyway, since it is a change in behaviour since 4.1.1.
> Starting karaf using bin/karaf gave this error message
> {noformat}
> sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$ bin/karaf
> bin/karaf: line 18: $'\r': command not found
> bin/karaf: line 19: syntax error near unexpected token `$'{\r''
> 'in/karaf: line 19: `realpath() {
> {noformat}
> Since this is recognizable as a "problem with CR-LF" error message, I edit
> the bin/karaf in emacs, changing CRLF to just LF, but then I got these error
> messages:
> {noformat}
> sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$ bin/karaf
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 18: $'\r':
> command not found
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 19: syntax
> error near unexpected token `$'{\r''
> 'cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 19:
> `warn() {
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 18:
> $'\r': command not found
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 26:
> $'\r': command not found
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 33:
> $'\r': command not found
> bin/karaf: line 109: detectOS: command not found
> bin/karaf: line 112: unlimitFD: command not found
> bin/karaf: line 115: locateHome: command not found
> bin/karaf: line 118: locateBase: command not found
> bin/karaf: line 121: locateData: command not found
> bin/karaf: line 124: locateEtc: command not found
> bin/karaf: line 127: setupNativePath: command not found
> bin/karaf: line 130: locateJava: command not found
> bin/karaf: line 133: detectJVM: command not found
> bin/karaf: line 136: checkJvmVersion: command not found
> bin/karaf: line 142: setupDefaults: command not found
> bin/karaf: line 148: setupDebugOptions: command not found
> bin/karaf: line 165: convertPaths: command not found
> bin/karaf: line 243: KARAF_HOME: parameter null or not set
> sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5023) The serviceUrl property is changed unexpected when edit the rmiServerPort/rmiRegistryPort properties
[
https://issues.apache.org/jira/browse/KARAF-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114390#comment-16114390
]
Jean-Baptiste Onofré commented on KARAF-5023:
-
The problem is that the {{ConnectorServerFactory}} uses the {{serviceUrl}}
provided by the {{Activator}}:
{code}
JMXServiceURL url = new JMXServiceURL(this.serviceUrl);
{code}
It's in the {{init()}} method. So, the {{serviceUrl}} is not updated in the
{{ConnectorServerFactory}}.
Actually, the {{ConnectorServerFactory}} should use a {{ManagedService}} to get
updated when the {{serviceUrl}} changes. It's not a minor change, so I prefer
to bump to 4.1.3 to have time to do it.
> The serviceUrl property is changed unexpected when edit the
> rmiServerPort/rmiRegistryPort properties
>
>
> Key: KARAF-5023
> URL: https://issues.apache.org/jira/browse/KARAF-5023
> Project: Karaf
> Issue Type: Bug
> Components: karaf-config
>Affects Versions: 4.1.0, 4.0.8
>Reporter: Xilai Dai
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.0.10, 4.1.3
>
>
> {code}
> karaf@root()> config:edit --force org.apache.karaf.management
> karaf@root()> config:property-set rmiRegistryPort 1100
> karaf@root()> config:property-set rmiServerPort 5
> karaf@root()> config:update
> karaf@root()> Exception in thread "JMX Connector Thread
> [service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-r
> oot]" java.lang.RuntimeException: Could not start JMX connector server
> at
> org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:272)
> Caused by: java.io.IOException: Cannot bind to URL
> [rmi://127.0.0.1:1099/karaf-root]: javax.naming.CommunicationException
> [Root exception is java.rmi.NoSuchObjectException: no such object in table]
> at
> javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:827)
> at
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:432)
> at
> org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:259)
> Caused by: javax.naming.CommunicationException [Root exception is
> java.rmi.NoSuchObjectException: no such object in tabl
> e]
> at
> com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:161)
> at
> com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:228)
> at javax.naming.InitialContext.bind(InitialContext.java:425)
> at
> javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:644)
> at
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
> ... 1 more
> Caused by: java.rmi.NoSuchObjectException: no such object in table
> at
> sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:276)
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:253)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:379)
> at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
> at
> com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:155)
> ... 5 more
> {code}
> Looking into the {{etc/org.apache.karaf.management.cfg}}, the {{serviceUrl}}
> property is changed to:
> {code}
> service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-root
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KARAF-5023) The serviceUrl property is changed unexpected when edit the rmiServerPort/rmiRegistryPort properties
[
https://issues.apache.org/jira/browse/KARAF-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-5023:
Fix Version/s: (was: 4.1.2)
4.1.3
> The serviceUrl property is changed unexpected when edit the
> rmiServerPort/rmiRegistryPort properties
>
>
> Key: KARAF-5023
> URL: https://issues.apache.org/jira/browse/KARAF-5023
> Project: Karaf
> Issue Type: Bug
> Components: karaf-config
>Affects Versions: 4.1.0, 4.0.8
>Reporter: Xilai Dai
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.0.10, 4.1.3
>
>
> {code}
> karaf@root()> config:edit --force org.apache.karaf.management
> karaf@root()> config:property-set rmiRegistryPort 1100
> karaf@root()> config:property-set rmiServerPort 5
> karaf@root()> config:update
> karaf@root()> Exception in thread "JMX Connector Thread
> [service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-r
> oot]" java.lang.RuntimeException: Could not start JMX connector server
> at
> org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:272)
> Caused by: java.io.IOException: Cannot bind to URL
> [rmi://127.0.0.1:1099/karaf-root]: javax.naming.CommunicationException
> [Root exception is java.rmi.NoSuchObjectException: no such object in table]
> at
> javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:827)
> at
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:432)
> at
> org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:259)
> Caused by: javax.naming.CommunicationException [Root exception is
> java.rmi.NoSuchObjectException: no such object in tabl
> e]
> at
> com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:161)
> at
> com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:228)
> at javax.naming.InitialContext.bind(InitialContext.java:425)
> at
> javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:644)
> at
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
> ... 1 more
> Caused by: java.rmi.NoSuchObjectException: no such object in table
> at
> sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:276)
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:253)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:379)
> at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
> at
> com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:155)
> ... 5 more
> {code}
> Looking into the {{etc/org.apache.karaf.management.cfg}}, the {{serviceUrl}}
> property is changed to:
> {code}
> service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-root
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5023) The serviceUrl property is changed unexpected when edit the rmiServerPort/rmiRegistryPort properties
[
https://issues.apache.org/jira/browse/KARAF-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114340#comment-16114340
]
Jean-Baptiste Onofré commented on KARAF-5023:
-
It's interesting to note:
1. The exception appears in the shell console but not in the log.
2. Same behavior happens if we change directly in
{{etc/org.apache.karaf.management.cfg}}, with also the exception only in the
shell console.
> The serviceUrl property is changed unexpected when edit the
> rmiServerPort/rmiRegistryPort properties
>
>
> Key: KARAF-5023
> URL: https://issues.apache.org/jira/browse/KARAF-5023
> Project: Karaf
> Issue Type: Bug
> Components: karaf-config
>Affects Versions: 4.1.0, 4.0.8
>Reporter: Xilai Dai
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2, 4.0.10
>
>
> {code}
> karaf@root()> config:edit --force org.apache.karaf.management
> karaf@root()> config:property-set rmiRegistryPort 1100
> karaf@root()> config:property-set rmiServerPort 5
> karaf@root()> config:update
> karaf@root()> Exception in thread "JMX Connector Thread
> [service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-r
> oot]" java.lang.RuntimeException: Could not start JMX connector server
> at
> org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:272)
> Caused by: java.io.IOException: Cannot bind to URL
> [rmi://127.0.0.1:1099/karaf-root]: javax.naming.CommunicationException
> [Root exception is java.rmi.NoSuchObjectException: no such object in table]
> at
> javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:827)
> at
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:432)
> at
> org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:259)
> Caused by: javax.naming.CommunicationException [Root exception is
> java.rmi.NoSuchObjectException: no such object in tabl
> e]
> at
> com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:161)
> at
> com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:228)
> at javax.naming.InitialContext.bind(InitialContext.java:425)
> at
> javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:644)
> at
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
> ... 1 more
> Caused by: java.rmi.NoSuchObjectException: no such object in table
> at
> sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:276)
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:253)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:379)
> at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
> at
> com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:155)
> ... 5 more
> {code}
> Looking into the {{etc/org.apache.karaf.management.cfg}}, the {{serviceUrl}}
> property is changed to:
> {code}
> service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-root
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5054) Default rmiRegistryPort 1099 is used always besides different configuration
[
https://issues.apache.org/jira/browse/KARAF-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114320#comment-16114320
]
Jean-Baptiste Onofré commented on KARAF-5054:
-
I just tried on Windows 7 VM and I'm not able to reproduce the issue.
Basically, I created two Karaf instances:
- a first one with the default configuration (and so default port numbers)
- a second one with {{etc/org.apache.karaf.management.cfg}} and
{{etc/org.apache.karaf.shell.cfg}} configuration files updated to use different
port.
I started the first instance, then the second one. Nothing in the second
instance log, and it starts without problem.
> Default rmiRegistryPort 1099 is used always besides different configuration
> ---
>
> Key: KARAF-5054
> URL: https://issues.apache.org/jira/browse/KARAF-5054
> Project: Karaf
> Issue Type: Bug
> Components: karaf-management
>Affects Versions: 4.1.0
> Environment: Windows 7 64bit, karaf 4.1.0 binary distribution, java
> 1.8.0_121, clean start
>Reporter: Jens Vagts
>Assignee: Jean-Baptiste Onofré
>
> When starting a _clean_ karaf instance (either very first first start or with
> {{clean}} command line parameter) the karaf management feature always tries
> to open the default port {{1099}} before opening the configured port
> resulting in a confusing exception in the {{karaf.log}}:
> {noformat}
> 2017-03-22T08:08:51,523 | WARN | pool-23-thread-1 | Activator
> | 38 - org.apache.karaf.management.server - 4.1.0 | Error starting
> activator
> java.rmi.server.ExportException: Port already in use: 1099; nested exception
> is:
> java.net.BindException: Address already in use: JVM_Bind
> at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:341)
> [?:?]
> at
> sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:249) [?:?]
> at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
> [?:?]
> at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147) [?:?]
> at
> sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:234) [?:?]
> at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:195) [?:?]
> at sun.rmi.registry.RegistryImpl.(RegistryImpl.java:180) [?:?]
> at
> java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:203) [?:?]
> at
> org.apache.karaf.management.RmiRegistryFactory.init(RmiRegistryFactory.java:128)
> [38:org.apache.karaf.management.server:4.1.0]
> at
> org.apache.karaf.management.internal.Activator.doStart(Activator.java:104)
> [38:org.apache.karaf.management.server:4.1.0]
> at
> org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.java:242)
> [38:org.apache.karaf.management.server:4.1.0]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [?:?]
> at java.lang.Thread.run(Thread.java:745) [?:?]
> Caused by: java.net.BindException: Address already in use: JVM_Bind
> at java.net.DualStackPlainSocketImpl.bind0(Native Method) ~[?:?]
> at
> java.net.DualStackPlainSocketImpl.socketBind(DualStackPlainSocketImpl.java:106)
> ~[?:?]
> at
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387) ~[?:?]
> at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:190) ~[?:?]
> at java.net.ServerSocket.bind(ServerSocket.java:375) ~[?:?]
> at java.net.ServerSocket.(ServerSocket.java:237) ~[?:?]
> at java.net.ServerSocket.(ServerSocket.java:128) ~[?:?]
> at
> sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:45)
> ~[?:?]
> at
> sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:345)
> ~[?:?]
> at
> sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:666) ~[?:?]
> at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:330)
> ~[?:?]
> ... 15 more
> {noformat}
> if the port is already used by another process (e.g. another karaf instance).
> The configured port {{rmiRegistryPort = 1100}} in the config file
> {{org.apache.karaf.management.cfg}} will be nevertheless applied afterwards.
> This can easily reproduced by creating two instances of the standard karaf
> {{4.1.0}} binary distributions and applying above configuration to the second
> instance.
> This occurs on _Windows_ (7 64 bit tested) only, and can *not* be reproduced
> on _Li
[jira] [Resolved] (KARAF-5054) Default rmiRegistryPort 1099 is used always besides different configuration
[
https://issues.apache.org/jira/browse/KARAF-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-5054.
-
Resolution: Cannot Reproduce
Fix Version/s: (was: 4.1.2)
> Default rmiRegistryPort 1099 is used always besides different configuration
> ---
>
> Key: KARAF-5054
> URL: https://issues.apache.org/jira/browse/KARAF-5054
> Project: Karaf
> Issue Type: Bug
> Components: karaf-management
>Affects Versions: 4.1.0
> Environment: Windows 7 64bit, karaf 4.1.0 binary distribution, java
> 1.8.0_121, clean start
>Reporter: Jens Vagts
>Assignee: Jean-Baptiste Onofré
>
> When starting a _clean_ karaf instance (either very first first start or with
> {{clean}} command line parameter) the karaf management feature always tries
> to open the default port {{1099}} before opening the configured port
> resulting in a confusing exception in the {{karaf.log}}:
> {noformat}
> 2017-03-22T08:08:51,523 | WARN | pool-23-thread-1 | Activator
> | 38 - org.apache.karaf.management.server - 4.1.0 | Error starting
> activator
> java.rmi.server.ExportException: Port already in use: 1099; nested exception
> is:
> java.net.BindException: Address already in use: JVM_Bind
> at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:341)
> [?:?]
> at
> sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:249) [?:?]
> at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
> [?:?]
> at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147) [?:?]
> at
> sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:234) [?:?]
> at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:195) [?:?]
> at sun.rmi.registry.RegistryImpl.(RegistryImpl.java:180) [?:?]
> at
> java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:203) [?:?]
> at
> org.apache.karaf.management.RmiRegistryFactory.init(RmiRegistryFactory.java:128)
> [38:org.apache.karaf.management.server:4.1.0]
> at
> org.apache.karaf.management.internal.Activator.doStart(Activator.java:104)
> [38:org.apache.karaf.management.server:4.1.0]
> at
> org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.java:242)
> [38:org.apache.karaf.management.server:4.1.0]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [?:?]
> at java.lang.Thread.run(Thread.java:745) [?:?]
> Caused by: java.net.BindException: Address already in use: JVM_Bind
> at java.net.DualStackPlainSocketImpl.bind0(Native Method) ~[?:?]
> at
> java.net.DualStackPlainSocketImpl.socketBind(DualStackPlainSocketImpl.java:106)
> ~[?:?]
> at
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387) ~[?:?]
> at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:190) ~[?:?]
> at java.net.ServerSocket.bind(ServerSocket.java:375) ~[?:?]
> at java.net.ServerSocket.(ServerSocket.java:237) ~[?:?]
> at java.net.ServerSocket.(ServerSocket.java:128) ~[?:?]
> at
> sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:45)
> ~[?:?]
> at
> sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:345)
> ~[?:?]
> at
> sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:666) ~[?:?]
> at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:330)
> ~[?:?]
> ... 15 more
> {noformat}
> if the port is already used by another process (e.g. another karaf instance).
> The configured port {{rmiRegistryPort = 1100}} in the config file
> {{org.apache.karaf.management.cfg}} will be nevertheless applied afterwards.
> This can easily reproduced by creating two instances of the standard karaf
> {{4.1.0}} binary distributions and applying above configuration to the second
> instance.
> This occurs on _Windows_ (7 64 bit tested) only, and can *not* be reproduced
> on _Linux_ OS!
> The same behavior (of using the default port before the differently
> configured one) has been observed for other ports as of: rmi server port
> ({{rmiServerPort}} in {{org.apache.karaf.management.cfg}}) and ssh
> ({{sshPort}} in {{org.apache.karaf.shell.cfg}}. Depending on the logging
> configuration the failing usage of the default ports can be seen before the
> configured ports are taken into account.
> Re-configuring the
[jira] [Commented] (KARAF-5100) Karaf maven plugin failed on karaf-assembly goal with StackOverflowException
[
https://issues.apache.org/jira/browse/KARAF-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114304#comment-16114304
]
Jean-Baptiste Onofré commented on KARAF-5100:
-
I can't reproduce this error. Can you provide your {{pom.xml}} and
{{features.xml}} ? Thanks !
> Karaf maven plugin failed on karaf-assembly goal with StackOverflowException
>
>
> Key: KARAF-5100
> URL: https://issues.apache.org/jira/browse/KARAF-5100
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
>Affects Versions: 4.1.1
> Environment: Apache Maven 3.3.9
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T19:41:47+03:00)
> Maven home: C:\Programs\apache-maven-3.3.9\bin\..
> Java version: 1.8.0_60, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_60\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
>Reporter: Vadim Melnikov
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.3
>
>
> [DEBUG] Resolved (org.apache.karaf.features:standard:xml:features:4.1.1) as
> C:\Users\vmm333\.m2\repository\org\apache\karaf\features\standard\4.1.1\standard-4.1.1-features.xml
> [DEBUG] Using manager PaxLocalRepositoryManager with priority 0.0 for
> C:\Users\vmm333\.m2\repository
> [DEBUG] Resolved (org.apache.karaf.features:framework:xml:features:4.1.1) as
> C:\Users\vmm333\.m2\repository\org\apache\karaf\features\framework\4.1.1\framework-4.1.1-features.xml
> [DEBUG] Resolved
> (com.mycompany.applications.product-mediation:product-mediation-karaf-features:xml:features:1.4.0)
> as
> C:\Users\vmm333\.m2\repository\com\mycompany\applications\product-mediation\product-mediation-karaf-features\1.4.0\product-mediation-karaf-features-1.4.0-features.xml
> [DEBUG] Resolved (org.ops4j.pax.web:pax-web-features:xml:features:6.0.3) as
> C:\Users\vmm333\.m2\repository\org\ops4j\pax\web\pax-web-features\6.0.3\pax-web-features-6.0.3-features.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.692 s
> [INFO] Finished at: 2017-04-21T11:34:37+03:00
> [INFO] Final Memory: 30M/332M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.karaf.tooling:karaf-maven-plugin:4.1.1:assembly (default-assembly)
> on project product-mediation-karaf-platform: Unable to build assembly: Error
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.karaf.tooling:karaf-maven-plugin:4.1.1:assembly
> (default-assembly) on project product-mediation-karaf-platform: Unable to
> build assembly
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to
[jira] [Updated] (KARAF-5100) Karaf maven plugin failed on karaf-assembly goal with StackOverflowException
[ https://issues.apache.org/jira/browse/KARAF-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5100: Fix Version/s: (was: 4.1.2) 4.1.3 > Karaf maven plugin failed on karaf-assembly goal with StackOverflowException > > > Key: KARAF-5100 > URL: https://issues.apache.org/jira/browse/KARAF-5100 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 4.1.1 > Environment: Apache Maven 3.3.9 > (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T19:41:47+03:00) > Maven home: C:\Programs\apache-maven-3.3.9\bin\.. > Java version: 1.8.0_60, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.8.0_60\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos" >Reporter: Vadim Melnikov >Assignee: Jean-Baptiste Onofré > Fix For: 4.2.0, 4.1.3 > > > [DEBUG] Resolved (org.apache.karaf.features:standard:xml:features:4.1.1) as > C:\Users\vmm333\.m2\repository\org\apache\karaf\features\standard\4.1.1\standard-4.1.1-features.xml > [DEBUG] Using manager PaxLocalRepositoryManager with priority 0.0 for > C:\Users\vmm333\.m2\repository > [DEBUG] Resolved (org.apache.karaf.features:framework:xml:features:4.1.1) as > C:\Users\vmm333\.m2\repository\org\apache\karaf\features\framework\4.1.1\framework-4.1.1-features.xml > [DEBUG] Resolved > (com.mycompany.applications.product-mediation:product-mediation-karaf-features:xml:features:1.4.0) > as > C:\Users\vmm333\.m2\repository\com\mycompany\applications\product-mediation\product-mediation-karaf-features\1.4.0\product-mediation-karaf-features-1.4.0-features.xml > [DEBUG] Resolved (org.ops4j.pax.web:pax-web-features:xml:features:6.0.3) as > C:\Users\vmm333\.m2\repository\org\ops4j\pax\web\pax-web-features\6.0.3\pax-web-features-6.0.3-features.xml > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 7.692 s > [INFO] Finished at: 2017-04-21T11:34:37+03:00 > [INFO] Final Memory: 30M/332M > [INFO] > > [ERROR] Failed to execute goal > org.apache.karaf.tooling:karaf-maven-plugin:4.1.1:assembly (default-assembly) > on project product-mediation-karaf-platform: Unable to build assembly: Error > -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.karaf.tooling:karaf-maven-plugin:4.1.1:assembly > (default-assembly) on project product-mediation-karaf-platform: Unable to > build assembly > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to build > assembly > at org.apache.karaf.tooling.AssemblyMojo.execute(AssemblyMojo.java
[jira] [Resolved] (KARAF-5286) Separate server key generation from key reading
[ https://issues.apache.org/jira/browse/KARAF-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved KARAF-5286. Resolution: Fixed > Separate server key generation from key reading > --- > > Key: KARAF-5286 > URL: https://issues.apache.org/jira/browse/KARAF-5286 > Project: Karaf > Issue Type: Improvement > Components: karaf-shell >Affects Versions: 4.2.0 >Reporter: Christian Schneider >Assignee: Christian Schneider > Fix For: 4.2.0 > > > Currently we use AbstractGeneratorHostKeyProvider to read server keys and > also generate them on the fly. According to the mina sshd team this class is > not meant for production use. > So I propose we create a separate classes for reading and writing keys. > I also propose we remove the hostKeyFormat config and only support OpenSSH > pem based keys. > For now we need a custom OpenSSHKeyPairProvider to read out keys as mina sshd > has a bug (SSHD-760). After the release of sshd 1.7.0 we can switch to the > standard FileKeyProvider from mina. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5286) Separate server key generation from key reading
[ https://issues.apache.org/jira/browse/KARAF-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114299#comment-16114299 ] ASF subversion and git services commented on KARAF-5286: Commit 033bfdf9604846ab586609a28ded83c845d714aa in karaf's branch refs/heads/OPENSSH from [~ch...@die-schneider.net] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=033bfdf ] [KARAF-5286] Separate server key generation from key reading. Only support openssh pem server keys > Separate server key generation from key reading > --- > > Key: KARAF-5286 > URL: https://issues.apache.org/jira/browse/KARAF-5286 > Project: Karaf > Issue Type: Improvement > Components: karaf-shell >Affects Versions: 4.2.0 >Reporter: Christian Schneider >Assignee: Christian Schneider > Fix For: 4.2.0 > > > Currently we use AbstractGeneratorHostKeyProvider to read server keys and > also generate them on the fly. According to the mina sshd team this class is > not meant for production use. > So I propose we create a separate classes for reading and writing keys. > I also propose we remove the hostKeyFormat config and only support OpenSSH > pem based keys. > For now we need a custom OpenSSHKeyPairProvider to read out keys as mina sshd > has a bug (SSHD-760). After the release of sshd 1.7.0 we can switch to the > standard FileKeyProvider from mina. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-4985) Karaf does not start with JDK 9 in Windows
[
https://issues.apache.org/jira/browse/KARAF-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114298#comment-16114298
]
ASF subversion and git services commented on KARAF-4985:
Commit b563c712ca95c8054b19817da05849c72f0a922a in karaf's branch
refs/heads/OPENSSH from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=b563c71 ]
[KARAF-4985] Add test on Java version on karaf.bat to use the correct startup
command
> Karaf does not start with JDK 9 in Windows
> ---
>
> Key: KARAF-4985
> URL: https://issues.apache.org/jira/browse/KARAF-4985
> Project: Karaf
> Issue Type: Bug
> Components: karaf-os-integration
>Affects Versions: 4.1.0
> Environment: Windows 7, Java 9 (JDK and JRE 9 - ea+156)
>Reporter: Lijun Liao
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
>
> Under JDK / JRE 9 (tested with ea+156) in Windows 7, karaf does not start
> Steps to reproduce the problem:
> 1. Start karaf {code}bin/karaf{code} and you will get the following error
> {code}
> -Djava.endorsed.dir=C:\Program Files\Java\jdk-9\jre\lib\endorsed:C:\Program
> Files\Java\jdk-9\lib\endorsed:D:\apache-karaf-4.1.0\bin\..\lib\endorsed is
> not supported. Endorsed standards and standalone APIs
> in modular form will be supported via the concept of upgradeable modules.
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5286) Separate server key generation from key reading
[ https://issues.apache.org/jira/browse/KARAF-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114296#comment-16114296 ] ASF subversion and git services commented on KARAF-5286: Commit 033bfdf9604846ab586609a28ded83c845d714aa in karaf's branch refs/heads/master from [~ch...@die-schneider.net] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=033bfdf ] [KARAF-5286] Separate server key generation from key reading. Only support openssh pem server keys > Separate server key generation from key reading > --- > > Key: KARAF-5286 > URL: https://issues.apache.org/jira/browse/KARAF-5286 > Project: Karaf > Issue Type: Improvement > Components: karaf-shell >Affects Versions: 4.2.0 >Reporter: Christian Schneider >Assignee: Christian Schneider > Fix For: 4.2.0 > > > Currently we use AbstractGeneratorHostKeyProvider to read server keys and > also generate them on the fly. According to the mina sshd team this class is > not meant for production use. > So I propose we create a separate classes for reading and writing keys. > I also propose we remove the hostKeyFormat config and only support OpenSSH > pem based keys. > For now we need a custom OpenSSHKeyPairProvider to read out keys as mina sshd > has a bug (SSHD-760). After the release of sshd 1.7.0 we can switch to the > standard FileKeyProvider from mina. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KARAF-5284) Karaf 4.1.2-SNAPSHOT bourne shell script doesn't start in cygwin
[
https://issues.apache.org/jira/browse/KARAF-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-5284.
-
Resolution: Cannot Reproduce
Fix Version/s: (was: 4.1.2)
(was: 4.2.0)
> Karaf 4.1.2-SNAPSHOT bourne shell script doesn't start in cygwin
>
>
> Key: KARAF-5284
> URL: https://issues.apache.org/jira/browse/KARAF-5284
> Project: Karaf
> Issue Type: Bug
> Environment: Karaf 4.1.2-SNAPSHOT, zip file assembly, built from a
> fresh pull.
> JDK 1.8_141
> CYGWIN_NT-10.0 mccoy 2.5.2(0.297/5/3) 2016-06-23 14:29 x86_64 Cygwin
>Reporter: Steinar Bang
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Labels: karaf-shell
>
> Starting karaf unpacked from a zip file, from a cygwin terminal works in
> karaf 4.1.1 (starting from the karaf.bat file doesn't work there).
> Starting karaf 4.1.2-SNAPSHOT unpacked from a freshly build zip file, does
> not work, when using the bin/karaf sh file. It does, however, work to start
> karaf using the karaf.bat file.
> Since karaf is startable from the cygwin window, which is the important thing
> (better copy/paste and window resizing features than cmd.exe), this isn't
> very important.
> But I'm reporting it anyway, since it is a change in behaviour since 4.1.1.
> Starting karaf using bin/karaf gave this error message
> {noformat}
> sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$ bin/karaf
> bin/karaf: line 18: $'\r': command not found
> bin/karaf: line 19: syntax error near unexpected token `$'{\r''
> 'in/karaf: line 19: `realpath() {
> {noformat}
> Since this is recognizable as a "problem with CR-LF" error message, I edit
> the bin/karaf in emacs, changing CRLF to just LF, but then I got these error
> messages:
> {noformat}
> sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$ bin/karaf
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 18: $'\r':
> command not found
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 19: syntax
> error near unexpected token `$'{\r''
> 'cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 19:
> `warn() {
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 18:
> $'\r': command not found
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 26:
> $'\r': command not found
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 33:
> $'\r': command not found
> bin/karaf: line 109: detectOS: command not found
> bin/karaf: line 112: unlimitFD: command not found
> bin/karaf: line 115: locateHome: command not found
> bin/karaf: line 118: locateBase: command not found
> bin/karaf: line 121: locateData: command not found
> bin/karaf: line 124: locateEtc: command not found
> bin/karaf: line 127: setupNativePath: command not found
> bin/karaf: line 130: locateJava: command not found
> bin/karaf: line 133: detectJVM: command not found
> bin/karaf: line 136: checkJvmVersion: command not found
> bin/karaf: line 142: setupDefaults: command not found
> bin/karaf: line 148: setupDebugOptions: command not found
> bin/karaf: line 165: convertPaths: command not found
> bin/karaf: line 243: KARAF_HOME: parameter null or not set
> sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5284) Karaf 4.1.2-SNAPSHOT bourne shell script doesn't start in cygwin
[
https://issues.apache.org/jira/browse/KARAF-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114295#comment-16114295
]
Jean-Baptiste Onofré commented on KARAF-5284:
-
I just tried on Windows 7 VM with Cygwin. With a freshly built Karaf
4.1.2-SNAPSHOT, in the Cygwin terminal, I did {{bin/karaf}} and {{cd bin &&
./karaf}}. Both worked for me. The only thing I noticed is a warning {{:
integer expression expected}} coming from the Java version check (not a big
deal).
> Karaf 4.1.2-SNAPSHOT bourne shell script doesn't start in cygwin
>
>
> Key: KARAF-5284
> URL: https://issues.apache.org/jira/browse/KARAF-5284
> Project: Karaf
> Issue Type: Bug
> Environment: Karaf 4.1.2-SNAPSHOT, zip file assembly, built from a
> fresh pull.
> JDK 1.8_141
> CYGWIN_NT-10.0 mccoy 2.5.2(0.297/5/3) 2016-06-23 14:29 x86_64 Cygwin
>Reporter: Steinar Bang
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Labels: karaf-shell
> Fix For: 4.2.0, 4.1.2
>
>
> Starting karaf unpacked from a zip file, from a cygwin terminal works in
> karaf 4.1.1 (starting from the karaf.bat file doesn't work there).
> Starting karaf 4.1.2-SNAPSHOT unpacked from a freshly build zip file, does
> not work, when using the bin/karaf sh file. It does, however, work to start
> karaf using the karaf.bat file.
> Since karaf is startable from the cygwin window, which is the important thing
> (better copy/paste and window resizing features than cmd.exe), this isn't
> very important.
> But I'm reporting it anyway, since it is a change in behaviour since 4.1.1.
> Starting karaf using bin/karaf gave this error message
> {noformat}
> sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$ bin/karaf
> bin/karaf: line 18: $'\r': command not found
> bin/karaf: line 19: syntax error near unexpected token `$'{\r''
> 'in/karaf: line 19: `realpath() {
> {noformat}
> Since this is recognizable as a "problem with CR-LF" error message, I edit
> the bin/karaf in emacs, changing CRLF to just LF, but then I got these error
> messages:
> {noformat}
> sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$ bin/karaf
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 18: $'\r':
> command not found
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 19: syntax
> error near unexpected token `$'{\r''
> 'cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/inc: line 19:
> `warn() {
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 18:
> $'\r': command not found
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 26:
> $'\r': command not found
> /cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT/bin/setenv: line 33:
> $'\r': command not found
> bin/karaf: line 109: detectOS: command not found
> bin/karaf: line 112: unlimitFD: command not found
> bin/karaf: line 115: locateHome: command not found
> bin/karaf: line 118: locateBase: command not found
> bin/karaf: line 121: locateData: command not found
> bin/karaf: line 124: locateEtc: command not found
> bin/karaf: line 127: setupNativePath: command not found
> bin/karaf: line 130: locateJava: command not found
> bin/karaf: line 133: detectJVM: command not found
> bin/karaf: line 136: checkJvmVersion: command not found
> bin/karaf: line 142: setupDefaults: command not found
> bin/karaf: line 148: setupDebugOptions: command not found
> bin/karaf: line 165: convertPaths: command not found
> bin/karaf: line 243: KARAF_HOME: parameter null or not set
> sb@mccoy:/cygdrive/c/ProgramFiles/apache-karaf-4.1.2-SNAPSHOT$
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KARAF-4261) Bundle start-level seems to be ignored at Karaf restart
[
https://issues.apache.org/jira/browse/KARAF-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-4261:
Fix Version/s: (was: 4.1.2)
4.1.3
> Bundle start-level seems to be ignored at Karaf restart
> ---
>
> Key: KARAF-4261
> URL: https://issues.apache.org/jira/browse/KARAF-4261
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core, karaf-kar
>Affects Versions: 4.0.3
>Reporter: Ralf Steppacher
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.0.10, 4.1.3
>
>
> AS a workaround for CAMEL-9483 I have set a start-level for my bundles
> deployed as part of my features. This works as expected during initial
> deployment (order of deployment is according to the start levels I set), but
> not during sub-sequent starts of Karaf. It appears the start-level of the
> bundles is ignored, meaning the order of deployment of my bundles is more or
> less random and I observe the issues described in CAMEL-9483 again.
> {{bundle:list}} shows my bundles with the start-levels they have been
> originally deployed with, though.
> As a workaround I set {{karaf.clean.all = true}} in system.properties.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KARAF-5210) Seemingly random NPEs from Aether resolver
[
https://issues.apache.org/jira/browse/KARAF-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-5210:
Fix Version/s: (was: 4.1.2)
4.1.3
> Seemingly random NPEs from Aether resolver
> --
>
> Key: KARAF-5210
> URL: https://issues.apache.org/jira/browse/KARAF-5210
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Windows
>Reporter: Peter Berkman
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.3
>
> Attachments: mvnsettings.xml, org.ops4j.pax.url.mvn.cfg
>
>
> We have an installer that automates much of our Karaf and product
> installation.
> since the upgrade to Karaf 4.1, I've been getting these about every 5th
> automated install. could be timing? Happens at random places and sometimes
> with dependencies that the target doesn't have.
> One thing is that we do turn OFF internet access for maven through settings
> in the org.ops4j.pax.url.mvn.cfg and provider our out mvnsettings.xml. I
> will try and attach them later, but these are the relevant settings:
> {code}
> org.ops4j.pax.url.mvn.settings=${karaf.etc}/mvnsettings.xml
> org.ops4j.pax.url.mvn.localRepository=${karaf.data}/repo
> org.ops4j.pax.url.mvn.useFallbackRepositories=false
> org.ops4j.pax.url.mvn.defaultRepositories=
> org.ops4j.pax.url.mvn.defaultLocalRepoAsRemote=true
> org.ops4j.pax.url.mvn.repositories= \
>
> file:${karaf.home}/${karaf.default.repository}@id=system.repository@snapshots,\
> file:${karaf.data}/kar@id=kar.repository@multi@snapshots
> {code}
> mvnsettings.xml:
> {code}
> http://maven.apache.org/SETTINGS/1.1.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.1.0
> http://maven.apache.org/xsd/settings-1.1.0.xsd";>
> data/repo
>
> {code}
> Here is what the stack looks like - note that the target bundle is almost
> always different on different failures.
> {code}
> 20170614 11:24:50.512 [INFO ] pipe-feature:install -v -r ngaudit |
> 10:org.apache.karaf.features.core |
> org.apache.karaf.features.internal.service.FeaturesServiceImpl | Adding
> features: ngaudit/[10.0.0.SNAPSHOT,10.0.0.SNAPSHOT]
> 20170614 11:24:50.531 [ERROR] Thread-85 | 69:org.apache.karaf.shell.core |
> org.apache.karaf.shell.support.ShellUtil | Exception caught while executing
> command
> org.apache.karaf.features.internal.util.MultiException: Error
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadManager$MavenDownloader.(MavenDownloadManager.java:84)[10:org.apache.karaf.features.core:4.1.1]
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadManager.createDownloader(MavenDownloadManager.java:72)[10:org.apache.karaf.features.core:4.1.1]
> at
> org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:375)[10:org.apache.karaf.features.core:4.1.1]
> at
> org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:372)[10:org.apache.karaf.features.core:4.1.1]
> at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:187)[10:org.apache.karaf.features.core:4.1.1]
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:285)[10:org.apache.karaf.features.core:4.1.1]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)[10:org.apache.karaf.features.core:4.1.1]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)[10:org.apache.karaf.features.core:4.1.1]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_92]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_92]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_92]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_92]
> Caused by: java.io.IOException: Error downloading
> mvn:org.apache.karaf.jndi/org.apache.karaf.jndi.core/4.1.1
> at
> org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:81)[10:org.apache.karaf.features.core:4.1.1]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_92]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_92]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_92]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_92]
> ... 3 more
> Caused by: java.lang.N
[jira] [Closed] (KARAF-4655) karaf-maven-plugin add-features-to-repo goal can't add Camel feature
[
https://issues.apache.org/jira/browse/KARAF-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider closed KARAF-4655.
--
Resolution: Cannot Reproduce
[~ilazebny] please reopen if you can still reproduce.
> karaf-maven-plugin add-features-to-repo goal can't add Camel feature
>
>
> Key: KARAF-4655
> URL: https://issues.apache.org/jira/browse/KARAF-4655
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
>Affects Versions: 4.0.5, 4.0.6
>Reporter: Igor Lazebny
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
> Attachments: pom.xml
>
>
> camel-restlet 2.17.3 feature contains bundle reference like this:
> {{ dependency="true">mvn:http://maven.restlet.org@id=restlet!org.restlet.osgi/org.restlet/2.3.6}}
> add-features-to-repo can't interpret it correctly trying to connect to
> "id=restlet" host:
> [ERROR] Failed to execute goal
> org.apache.karaf.tooling:karaf-maven-plugin:4.0.6-SNAPSHOT:features-add-to-repository
> (add-features-to-repo) on project karaf-maven-plugin-test: Error populating
> repository: Error resolving feature camel-restlet/2.17.3: Error resolving
> artifact
> mvn:http://maven.restlet.org@id=restlet!org.restlet.osgi/org.restlet/2.3.6:
> Can't resolve artifact org.restlet.osgi:org.restlet:jar:2.3.6: Could not
> transfer artifact org.restlet.osgi:org.restlet:jar:2.3.6 from/to
> http://maven.restlet.org@id=restlet (http://id=restlet): id=restlet: unknown
> error
> [ERROR] org.restlet.osgi:org.restlet:jar:2.3.6
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] http://maven.restlet.org@id=restlet (http://id=restlet,
> releases=true, snapshots=true): Unknown host id=restlet: unknown error
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5210) Seemingly random NPEs from Aether resolver
[
https://issues.apache.org/jira/browse/KARAF-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114238#comment-16114238
]
Christian Schneider commented on KARAF-5210:
Can you provide a small example project that reproduces the error?
We at least need the exact steps to reproduce.
> Seemingly random NPEs from Aether resolver
> --
>
> Key: KARAF-5210
> URL: https://issues.apache.org/jira/browse/KARAF-5210
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Windows
>Reporter: Peter Berkman
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
> Attachments: mvnsettings.xml, org.ops4j.pax.url.mvn.cfg
>
>
> We have an installer that automates much of our Karaf and product
> installation.
> since the upgrade to Karaf 4.1, I've been getting these about every 5th
> automated install. could be timing? Happens at random places and sometimes
> with dependencies that the target doesn't have.
> One thing is that we do turn OFF internet access for maven through settings
> in the org.ops4j.pax.url.mvn.cfg and provider our out mvnsettings.xml. I
> will try and attach them later, but these are the relevant settings:
> {code}
> org.ops4j.pax.url.mvn.settings=${karaf.etc}/mvnsettings.xml
> org.ops4j.pax.url.mvn.localRepository=${karaf.data}/repo
> org.ops4j.pax.url.mvn.useFallbackRepositories=false
> org.ops4j.pax.url.mvn.defaultRepositories=
> org.ops4j.pax.url.mvn.defaultLocalRepoAsRemote=true
> org.ops4j.pax.url.mvn.repositories= \
>
> file:${karaf.home}/${karaf.default.repository}@id=system.repository@snapshots,\
> file:${karaf.data}/kar@id=kar.repository@multi@snapshots
> {code}
> mvnsettings.xml:
> {code}
> http://maven.apache.org/SETTINGS/1.1.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.1.0
> http://maven.apache.org/xsd/settings-1.1.0.xsd";>
> data/repo
>
> {code}
> Here is what the stack looks like - note that the target bundle is almost
> always different on different failures.
> {code}
> 20170614 11:24:50.512 [INFO ] pipe-feature:install -v -r ngaudit |
> 10:org.apache.karaf.features.core |
> org.apache.karaf.features.internal.service.FeaturesServiceImpl | Adding
> features: ngaudit/[10.0.0.SNAPSHOT,10.0.0.SNAPSHOT]
> 20170614 11:24:50.531 [ERROR] Thread-85 | 69:org.apache.karaf.shell.core |
> org.apache.karaf.shell.support.ShellUtil | Exception caught while executing
> command
> org.apache.karaf.features.internal.util.MultiException: Error
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadManager$MavenDownloader.(MavenDownloadManager.java:84)[10:org.apache.karaf.features.core:4.1.1]
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadManager.createDownloader(MavenDownloadManager.java:72)[10:org.apache.karaf.features.core:4.1.1]
> at
> org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:375)[10:org.apache.karaf.features.core:4.1.1]
> at
> org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:372)[10:org.apache.karaf.features.core:4.1.1]
> at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:187)[10:org.apache.karaf.features.core:4.1.1]
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:285)[10:org.apache.karaf.features.core:4.1.1]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)[10:org.apache.karaf.features.core:4.1.1]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)[10:org.apache.karaf.features.core:4.1.1]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_92]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_92]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_92]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_92]
> Caused by: java.io.IOException: Error downloading
> mvn:org.apache.karaf.jndi/org.apache.karaf.jndi.core/4.1.1
> at
> org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:81)[10:org.apache.karaf.features.core:4.1.1]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_92]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_92]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_92]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$Sched
[jira] [Comment Edited] (KARAF-4367) "Module has been uninstalled" during installing the feature
[ https://issues.apache.org/jira/browse/KARAF-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112507#comment-16112507 ] Yi Yan edited comment on KARAF-4367 at 8/4/17 10:13 AM: Hi, I use JMX to install and uninstall two different features in Jconsole, I click one 'installFeature' button and quick click the 'uninstallFeature' button immediately, then I get the exception from the JConsole:Caused by: java.lang.IllegalStateException: Module has been uninstalled.. [^jconsole2.png] I'm using 4.0.5 Regards, Yi was (Author: yanbasic): Hi, I use JMX to uninstall two different features in two Jconsoles, I click one 'uninstallFeature' button and switch to another JConsole and click the other 'uninstallFeature' button immediately, then I got this exception from the JConsole:Caused by: java.lang.IllegalStateException: Module has been uninstalled.. [^jconsole.png] I'm using 4.0.5 Regards, Yi > "Module has been uninstalled" during installing the feature > --- > > Key: KARAF-4367 > URL: https://issues.apache.org/jira/browse/KARAF-4367 > Project: Karaf > Issue Type: Bug > Components: karaf-core, karaf-feature >Affects Versions: 4.0.4 >Reporter: Pavlo Vasylchenko > Attachments: jconsole2.png > > > Separately feature works fine, but if I try to install it just after > uninstalling another feature, I get exception. > Looks like karaf trying refresh something in this time. > my code: > featuresService.installFeature(feature, > EnumSet.of(Option.NoAutoRefreshBundles)); > ... > Caused by: java.lang.IllegalStateException: Module has been uninstalled. > at > org.eclipse.osgi.container.Module.checkValid(Module.java:526)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:] > at > org.eclipse.osgi.container.Module.getStartLevel(Module.java:243)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:] > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:480)[9:org.apache.karaf.features.core:4.0.4] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)[9:org.apache.karaf.features.core:4.0.4] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)[9:org.apache.karaf.features.core:4.0.4] > at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_60] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_60] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_60] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-4367) "Module has been uninstalled" during installing the feature
[ https://issues.apache.org/jira/browse/KARAF-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Yan updated KARAF-4367: -- Attachment: jconsole2.png > "Module has been uninstalled" during installing the feature > --- > > Key: KARAF-4367 > URL: https://issues.apache.org/jira/browse/KARAF-4367 > Project: Karaf > Issue Type: Bug > Components: karaf-core, karaf-feature >Affects Versions: 4.0.4 >Reporter: Pavlo Vasylchenko > Attachments: jconsole2.png > > > Separately feature works fine, but if I try to install it just after > uninstalling another feature, I get exception. > Looks like karaf trying refresh something in this time. > my code: > featuresService.installFeature(feature, > EnumSet.of(Option.NoAutoRefreshBundles)); > ... > Caused by: java.lang.IllegalStateException: Module has been uninstalled. > at > org.eclipse.osgi.container.Module.checkValid(Module.java:526)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:] > at > org.eclipse.osgi.container.Module.getStartLevel(Module.java:243)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:] > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:480)[9:org.apache.karaf.features.core:4.0.4] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)[9:org.apache.karaf.features.core:4.0.4] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)[9:org.apache.karaf.features.core:4.0.4] > at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_60] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_60] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_60] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-4367) "Module has been uninstalled" during installing the feature
[ https://issues.apache.org/jira/browse/KARAF-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Yan updated KARAF-4367: -- Attachment: (was: jconsole.png) > "Module has been uninstalled" during installing the feature > --- > > Key: KARAF-4367 > URL: https://issues.apache.org/jira/browse/KARAF-4367 > Project: Karaf > Issue Type: Bug > Components: karaf-core, karaf-feature >Affects Versions: 4.0.4 >Reporter: Pavlo Vasylchenko > > Separately feature works fine, but if I try to install it just after > uninstalling another feature, I get exception. > Looks like karaf trying refresh something in this time. > my code: > featuresService.installFeature(feature, > EnumSet.of(Option.NoAutoRefreshBundles)); > ... > Caused by: java.lang.IllegalStateException: Module has been uninstalled. > at > org.eclipse.osgi.container.Module.checkValid(Module.java:526)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:] > at > org.eclipse.osgi.container.Module.getStartLevel(Module.java:243)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:] > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:480)[9:org.apache.karaf.features.core:4.0.4] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)[9:org.apache.karaf.features.core:4.0.4] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)[9:org.apache.karaf.features.core:4.0.4] > at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_60] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_60] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_60] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-4655) karaf-maven-plugin add-features-to-repo goal can't add Camel feature
[
https://issues.apache.org/jira/browse/KARAF-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114203#comment-16114203
]
Jean-Baptiste Onofré commented on KARAF-4655:
-
As you can't reproduce the issue, I suggest to close this Jira. User will
reopen it if required.
> karaf-maven-plugin add-features-to-repo goal can't add Camel feature
>
>
> Key: KARAF-4655
> URL: https://issues.apache.org/jira/browse/KARAF-4655
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
>Affects Versions: 4.0.5, 4.0.6
>Reporter: Igor Lazebny
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
> Attachments: pom.xml
>
>
> camel-restlet 2.17.3 feature contains bundle reference like this:
> {{ dependency="true">mvn:http://maven.restlet.org@id=restlet!org.restlet.osgi/org.restlet/2.3.6}}
> add-features-to-repo can't interpret it correctly trying to connect to
> "id=restlet" host:
> [ERROR] Failed to execute goal
> org.apache.karaf.tooling:karaf-maven-plugin:4.0.6-SNAPSHOT:features-add-to-repository
> (add-features-to-repo) on project karaf-maven-plugin-test: Error populating
> repository: Error resolving feature camel-restlet/2.17.3: Error resolving
> artifact
> mvn:http://maven.restlet.org@id=restlet!org.restlet.osgi/org.restlet/2.3.6:
> Can't resolve artifact org.restlet.osgi:org.restlet:jar:2.3.6: Could not
> transfer artifact org.restlet.osgi:org.restlet:jar:2.3.6 from/to
> http://maven.restlet.org@id=restlet (http://id=restlet): id=restlet: unknown
> error
> [ERROR] org.restlet.osgi:org.restlet:jar:2.3.6
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] http://maven.restlet.org@id=restlet (http://id=restlet,
> releases=true, snapshots=true): Unknown host id=restlet: unknown error
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5233) LogService does not work with log4j2
[
https://issues.apache.org/jira/browse/KARAF-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114199#comment-16114199
]
Jean-Baptiste Onofré commented on KARAF-5233:
-
The {{LogServiceImpl}} now uses {{getDelegate()}} where it checks the property
and react accordingly:
{code}
private LogServiceInternal getDelegate(Dictionary config) {
if (config.get("log4j.rootLogger") != null) {
return new LogServiceLog4j1Impl(config);
}
else if (config.get("log4j2.rootLogger.level") != null) {
return new LogServiceLog4j2Impl(config);
}
else {
throw new IllegalStateException("Unrecognized configuration");
}
}
{code}
We now have two different log service depending of the log4j backend version.
> LogService does not work with log4j2
>
>
> Key: KARAF-5233
> URL: https://issues.apache.org/jira/browse/KARAF-5233
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
>Reporter: Fabian Lange
>Assignee: Jean-Baptiste Onofré
>
> log:get / log:set and similar do not work with log4j2.
> the reason is that the LogServiceImpl has hardcoded prefixes and assumes a
> certain property name convention.
> of course this totally changed with log4j2, making LogServiceImpl quite broken
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (KARAF-5233) LogService does not work with log4j2
[ https://issues.apache.org/jira/browse/KARAF-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-5233. - Resolution: Not A Problem Fix Version/s: (was: 4.1.2) > LogService does not work with log4j2 > > > Key: KARAF-5233 > URL: https://issues.apache.org/jira/browse/KARAF-5233 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.1 >Reporter: Fabian Lange >Assignee: Jean-Baptiste Onofré > > log:get / log:set and similar do not work with log4j2. > the reason is that the LogServiceImpl has hardcoded prefixes and assumes a > certain property name convention. > of course this totally changed with log4j2, making LogServiceImpl quite broken -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-5233) LogService does not work with log4j2
[ https://issues.apache.org/jira/browse/KARAF-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5233: Fix Version/s: (was: 4.2.0) > LogService does not work with log4j2 > > > Key: KARAF-5233 > URL: https://issues.apache.org/jira/browse/KARAF-5233 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.1 >Reporter: Fabian Lange >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.2 > > > log:get / log:set and similar do not work with log4j2. > the reason is that the LogServiceImpl has hardcoded prefixes and assumes a > certain property name convention. > of course this totally changed with log4j2, making LogServiceImpl quite broken -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KARAF-5144) java.lang.RuntimeException: Command name evaluates to null: $.jline.terminal
[
https://issues.apache.org/jira/browse/KARAF-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-5144.
-
Resolution: Fixed
With the last changes on the {{shell.init.script}}, it should work. Please
reopen the Jira if required.
> java.lang.RuntimeException: Command name evaluates to null: $.jline.terminal
>
>
> Key: KARAF-5144
> URL: https://issues.apache.org/jira/browse/KARAF-5144
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.1
>Reporter: Roland Hauser
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
>
> Method executeScript on class org.apache.karaf.shell.ssh.ShellCommand throws
> (and catches) this exception, when property karaf.shell.init.script in
> system.properties is set to "karaf.shell.init.script = etc/shell.init.script"
> to avoid KARAF-5143. This means that currently no command can be executed
> which is specified in the shell init-script, which makes it impossible for us
> to deploy our application on Karaf 4.1.1.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5144) java.lang.RuntimeException: Command name evaluates to null: $.jline.terminal
[
https://issues.apache.org/jira/browse/KARAF-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114183#comment-16114183
]
Christian Schneider commented on KARAF-5144:
I just checked the current shell init script:
jlineReader = $.reader
if { %(jlineReader != null) } {
# On 256 colors terminal, add a right prompt
max_colors = ($.jline.terminal getNumericCapability max_colors)
This should protect from $.jline.terminal being null too as it is a property of
the jline reader.
> java.lang.RuntimeException: Command name evaluates to null: $.jline.terminal
>
>
> Key: KARAF-5144
> URL: https://issues.apache.org/jira/browse/KARAF-5144
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.1
>Reporter: Roland Hauser
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
>
> Method executeScript on class org.apache.karaf.shell.ssh.ShellCommand throws
> (and catches) this exception, when property karaf.shell.init.script in
> system.properties is set to "karaf.shell.init.script = etc/shell.init.script"
> to avoid KARAF-5143. This means that currently no command can be executed
> which is specified in the shell init-script, which makes it impossible for us
> to deploy our application on Karaf 4.1.1.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5144) java.lang.RuntimeException: Command name evaluates to null: $.jline.terminal
[ https://issues.apache.org/jira/browse/KARAF-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114155#comment-16114155 ] Christian Schneider commented on KARAF-5144: Can you provide exact steps to reproduce this? Also your system might be important. Normally $.jline.terminal does not resolve to null. I think this is where the exception is caused: max_colors = ($.jline.terminal getNumericCapability max_colors) I think we can solve this in two ways. Either we make sure .jline.terminal is never null or we check for null in the script. > java.lang.RuntimeException: Command name evaluates to null: $.jline.terminal > > > Key: KARAF-5144 > URL: https://issues.apache.org/jira/browse/KARAF-5144 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.1.1 >Reporter: Roland Hauser >Assignee: Jean-Baptiste Onofré > Fix For: 4.2.0, 4.1.2 > > > Method executeScript on class org.apache.karaf.shell.ssh.ShellCommand throws > (and catches) this exception, when property karaf.shell.init.script in > system.properties is set to "karaf.shell.init.script = etc/shell.init.script" > to avoid KARAF-5143. This means that currently no command can be executed > which is specified in the shell init-script, which makes it impossible for us > to deploy our application on Karaf 4.1.1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-4655) karaf-maven-plugin add-features-to-repo goal can't add Camel feature
[
https://issues.apache.org/jira/browse/KARAF-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114053#comment-16114053
]
Christian Schneider commented on KARAF-4655:
The karaf version 4.0.6-SNAPSHOT referenced in the pom is not available.
I built the pom using several karaf versions (4.0.5, 4.0.6, 4.0.9, 4.1.1). All
builds worked fine. Can you check if upgrading the karaf version fixes the
issue for you?
> karaf-maven-plugin add-features-to-repo goal can't add Camel feature
>
>
> Key: KARAF-4655
> URL: https://issues.apache.org/jira/browse/KARAF-4655
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
>Affects Versions: 4.0.5, 4.0.6
>Reporter: Igor Lazebny
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
> Attachments: pom.xml
>
>
> camel-restlet 2.17.3 feature contains bundle reference like this:
> {{ dependency="true">mvn:http://maven.restlet.org@id=restlet!org.restlet.osgi/org.restlet/2.3.6}}
> add-features-to-repo can't interpret it correctly trying to connect to
> "id=restlet" host:
> [ERROR] Failed to execute goal
> org.apache.karaf.tooling:karaf-maven-plugin:4.0.6-SNAPSHOT:features-add-to-repository
> (add-features-to-repo) on project karaf-maven-plugin-test: Error populating
> repository: Error resolving feature camel-restlet/2.17.3: Error resolving
> artifact
> mvn:http://maven.restlet.org@id=restlet!org.restlet.osgi/org.restlet/2.3.6:
> Can't resolve artifact org.restlet.osgi:org.restlet:jar:2.3.6: Could not
> transfer artifact org.restlet.osgi:org.restlet:jar:2.3.6 from/to
> http://maven.restlet.org@id=restlet (http://id=restlet): id=restlet: unknown
> error
> [ERROR] org.restlet.osgi:org.restlet:jar:2.3.6
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] http://maven.restlet.org@id=restlet (http://id=restlet,
> releases=true, snapshots=true): Unknown host id=restlet: unknown error
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
