[jira] [Commented] (KARAF-4260) Setting karaf.clean.all = true breaks service wrapper service script
[
https://issues.apache.org/jira/browse/KARAF-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15939824#comment-15939824
]
ASF subversion and git services commented on KARAF-4260:
Commit 0d6be2201861f9c75ee8a542d6906f83a863c736 in karaf's branch
refs/heads/karaf-4.0.x from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=0d6be22 ]
[KARAF-4260] Use karaf.base to store the wrapper PID to avoid issue with
clean.all start
> Setting karaf.clean.all = true breaks service wrapper service script
>
>
> Key: KARAF-4260
> URL: https://issues.apache.org/jira/browse/KARAF-4260
> Project: Karaf
> Issue Type: Bug
> Components: karaf-config
>Affects Versions: 4.0.3
>Reporter: Ralf Steppacher
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.0.9, 4.1.1
>
>
> The Karaf service wrapper script is generated such that the PID file is
> created in {{$KARAF_HOME/data}}. When setting {{karaf.clean.all = true}} then
> the PID file created by the service script gets deleted together with the
> data directory. As a result of this the service script reports Karaf as not
> running and it is not possible to stop the process via the script.
> The PID file location probably should be outside the data directory by
> default.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (KARAF-4260) Setting karaf.clean.all = true breaks service wrapper service script
[
https://issues.apache.org/jira/browse/KARAF-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-4260.
-
Resolution: Fixed
> Setting karaf.clean.all = true breaks service wrapper service script
>
>
> Key: KARAF-4260
> URL: https://issues.apache.org/jira/browse/KARAF-4260
> Project: Karaf
> Issue Type: Bug
> Components: karaf-config
>Affects Versions: 4.0.3
>Reporter: Ralf Steppacher
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.0.9, 4.1.1
>
>
> The Karaf service wrapper script is generated such that the PID file is
> created in {{$KARAF_HOME/data}}. When setting {{karaf.clean.all = true}} then
> the PID file created by the service script gets deleted together with the
> data directory. As a result of this the service script reports Karaf as not
> running and it is not possible to stop the process via the script.
> The PID file location probably should be outside the data directory by
> default.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KARAF-4260) Setting karaf.clean.all = true breaks service wrapper service script
[
https://issues.apache.org/jira/browse/KARAF-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15939823#comment-15939823
]
ASF subversion and git services commented on KARAF-4260:
Commit 8e62450665d3f374fc791d1d0c4f96f210a9975d in karaf's branch
refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=8e62450 ]
[KARAF-4260] Use karaf.base to store the wrapper PID to avoid issue with
clean.all start
> Setting karaf.clean.all = true breaks service wrapper service script
>
>
> Key: KARAF-4260
> URL: https://issues.apache.org/jira/browse/KARAF-4260
> Project: Karaf
> Issue Type: Bug
> Components: karaf-config
>Affects Versions: 4.0.3
>Reporter: Ralf Steppacher
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.0.9, 4.1.1
>
>
> The Karaf service wrapper script is generated such that the PID file is
> created in {{$KARAF_HOME/data}}. When setting {{karaf.clean.all = true}} then
> the PID file created by the service script gets deleted together with the
> data directory. As a result of this the service script reports Karaf as not
> running and it is not possible to stop the process via the script.
> The PID file location probably should be outside the data directory by
> default.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KARAF-5057) doesn't bring up list of commands
[ https://issues.apache.org/jira/browse/KARAF-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5057: Fix Version/s: 4.1.1 > doesn't bring up list of commands > --- > > Key: KARAF-5057 > URL: https://issues.apache.org/jira/browse/KARAF-5057 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.1.0 > Environment: Windows 7, JDK 1.8 >Reporter: Terry Waldron >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (KARAF-5057) doesn't bring up list of commands
[ https://issues.apache.org/jira/browse/KARAF-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-5057: --- Assignee: Jean-Baptiste Onofré > doesn't bring up list of commands > --- > > Key: KARAF-5057 > URL: https://issues.apache.org/jira/browse/KARAF-5057 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 4.1.0 > Environment: Windows 7, JDK 1.8 >Reporter: Terry Waldron >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KARAF-5057) doesn't bring up list of commands
Terry Waldron created KARAF-5057: Summary: doesn't bring up list of commands Key: KARAF-5057 URL: https://issues.apache.org/jira/browse/KARAF-5057 Project: Karaf Issue Type: Bug Components: karaf-shell Affects Versions: 4.1.0 Environment: Windows 7, JDK 1.8 Reporter: Terry Waldron -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5018) Missing files in distribution created by instance:create
[
https://issues.apache.org/jira/browse/KARAF-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938661#comment-15938661
]
Jean-Baptiste Onofré commented on KARAF-5018:
-
(Actually, I already did the change, I'm rebasing/merging).
> Missing files in distribution created by instance:create
>
>
> Key: KARAF-5018
> URL: https://issues.apache.org/jira/browse/KARAF-5018
> Project: Karaf
> Issue Type: Bug
> Components: karaf-instance
>Affects Versions: 4.1.0
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 4.1.1
>
>
> When creating a node using instance:create -v test-01 I see a number of files
> are listed missing even though they are present in the main installation at
> the etc folder. Here is a sample output:
> {code}
> Creating new instance on SSH port 8104 and registry port 1102 / RMI server
> port 7 at: /opt/apache-karaf-4.1.0/instances/test-01
> Creating dir: /opt/apache-karaf-4.1.0/instances/test-01/bin
> Creating dir: /opt/apache-karaf-4.1.0/instances/test-01/etc
> Creating dir: /opt/apache-karaf-4.1.0/instances/test-01/system
> Creating dir: /opt/apache-karaf-4.1.0/instances/test-01/deploy
> Creating dir: /opt/apache-karaf-4.1.0/instances/test-01/data
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/all.policy
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/config.properties
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/custom.properties
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/distribution.info
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/equinox-debug.properties
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/java.util.logging.properties
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/jmx.acl.cfg
> WARNING: unable to find etc/jmx.acl.cfg
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/jre.properties
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/keys.properties
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.felix.fileinstall-deploy.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.features.repos.cfg
> WARNING: unable to find etc/org.apache.karaf.features.repos.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.jaas.cfg
> WARNING: unable to find etc/org.apache.karaf.jaas.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.kar.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.log.cfg
> WARNING: unable to find etc/org.apache.karaf.log.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.ops4j.pax.logging.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.ops4j.pax.url.mvn.cfg
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/shell.init.script
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/users.properties
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.features.cfg
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/system.properties
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.shell.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.management.cfg
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/bin/karaf
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/bin/start
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/bin/stop
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/bin/karaf.bat
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/bin/start.bat
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/bin/stop.bat
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KARAF-5018) Missing files in distribution created by instance:create
[
https://issues.apache.org/jira/browse/KARAF-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938658#comment-15938658
]
Jean-Baptiste Onofré commented on KARAF-5018:
-
As lot of config (most of) are now located in {{features.xml}}, the current
build is not really accurate, as it's using relative folder (to {{assemblies}}).
As a quick workaround, I will put default files set in the default instance
resources.
> Missing files in distribution created by instance:create
>
>
> Key: KARAF-5018
> URL: https://issues.apache.org/jira/browse/KARAF-5018
> Project: Karaf
> Issue Type: Bug
> Components: karaf-instance
>Affects Versions: 4.1.0
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 4.1.1
>
>
> When creating a node using instance:create -v test-01 I see a number of files
> are listed missing even though they are present in the main installation at
> the etc folder. Here is a sample output:
> {code}
> Creating new instance on SSH port 8104 and registry port 1102 / RMI server
> port 7 at: /opt/apache-karaf-4.1.0/instances/test-01
> Creating dir: /opt/apache-karaf-4.1.0/instances/test-01/bin
> Creating dir: /opt/apache-karaf-4.1.0/instances/test-01/etc
> Creating dir: /opt/apache-karaf-4.1.0/instances/test-01/system
> Creating dir: /opt/apache-karaf-4.1.0/instances/test-01/deploy
> Creating dir: /opt/apache-karaf-4.1.0/instances/test-01/data
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/all.policy
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/config.properties
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/custom.properties
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/distribution.info
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/equinox-debug.properties
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/java.util.logging.properties
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/jmx.acl.cfg
> WARNING: unable to find etc/jmx.acl.cfg
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/jre.properties
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/keys.properties
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.felix.fileinstall-deploy.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.features.repos.cfg
> WARNING: unable to find etc/org.apache.karaf.features.repos.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.jaas.cfg
> WARNING: unable to find etc/org.apache.karaf.jaas.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.kar.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.log.cfg
> WARNING: unable to find etc/org.apache.karaf.log.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.ops4j.pax.logging.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.ops4j.pax.url.mvn.cfg
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/shell.init.script
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/users.properties
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.features.cfg
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/system.properties
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.shell.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.management.cfg
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/bin/karaf
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/bin/start
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/bin/stop
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/bin/karaf.bat
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/bin/start.bat
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/bin/stop.bat
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Work started] (KARAF-5018) Missing files in distribution created by instance:create
[
https://issues.apache.org/jira/browse/KARAF-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KARAF-5018 started by Jean-Baptiste Onofré.
---
> Missing files in distribution created by instance:create
>
>
> Key: KARAF-5018
> URL: https://issues.apache.org/jira/browse/KARAF-5018
> Project: Karaf
> Issue Type: Bug
> Components: karaf-instance
>Affects Versions: 4.1.0
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 4.1.1
>
>
> When creating a node using instance:create -v test-01 I see a number of files
> are listed missing even though they are present in the main installation at
> the etc folder. Here is a sample output:
> {code}
> Creating new instance on SSH port 8104 and registry port 1102 / RMI server
> port 7 at: /opt/apache-karaf-4.1.0/instances/test-01
> Creating dir: /opt/apache-karaf-4.1.0/instances/test-01/bin
> Creating dir: /opt/apache-karaf-4.1.0/instances/test-01/etc
> Creating dir: /opt/apache-karaf-4.1.0/instances/test-01/system
> Creating dir: /opt/apache-karaf-4.1.0/instances/test-01/deploy
> Creating dir: /opt/apache-karaf-4.1.0/instances/test-01/data
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/all.policy
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/config.properties
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/custom.properties
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/distribution.info
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/equinox-debug.properties
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/java.util.logging.properties
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/jmx.acl.cfg
> WARNING: unable to find etc/jmx.acl.cfg
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/jre.properties
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/keys.properties
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.felix.fileinstall-deploy.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.features.repos.cfg
> WARNING: unable to find etc/org.apache.karaf.features.repos.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.jaas.cfg
> WARNING: unable to find etc/org.apache.karaf.jaas.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.kar.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.log.cfg
> WARNING: unable to find etc/org.apache.karaf.log.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.ops4j.pax.logging.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.ops4j.pax.url.mvn.cfg
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/shell.init.script
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/users.properties
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.features.cfg
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/etc/system.properties
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.shell.cfg
> Creating file:
> /opt/apache-karaf-4.1.0/instances/test-01/etc/org.apache.karaf.management.cfg
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/bin/karaf
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/bin/start
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/bin/stop
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/bin/karaf.bat
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/bin/start.bat
> Creating file: /opt/apache-karaf-4.1.0/instances/test-01/bin/stop.bat
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KARAF-4361) Allow dynamic config customization when embedding Karaf using the Main class
[
https://issues.apache.org/jira/browse/KARAF-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-4361:
Fix Version/s: (was: 4.1.1)
4.1.0
> Allow dynamic config customization when embedding Karaf using the Main class
>
>
> Key: KARAF-4361
> URL: https://issues.apache.org/jira/browse/KARAF-4361
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core
>Affects Versions: 4.1.0, 4.0.4
>Reporter: Serge Huber
>Assignee: Guillaume Nodet
> Fix For: 4.1.0, 4.0.9
>
> Attachments:
> KARAF_4361_Allow_dynamic_config_customization_when_embedding_Karaf_using_the_Main_class.patch
>
>
> We are using Karaf by embedding it and basically starting it like this :
> {code}
> // code to setup System properties
> main = new Main(new String[0]);
> main.launch();
> {code}
> The problem is that the ConfigProperties that are used to startup Karaf are
> directly created in the main.launch() method, like this:
> {code}
> public void launch() throws Exception {
> config = new ConfigProperties();
> {code}
> Ideally it would be great if we could either have a setter to provide the
> config value, so that we could manipulate it before launching. In an embedded
> environment this quickly becomes a necessity. For example we would like to
> make it possible to have retrieve properties coming from another framework
> such as Spring and use those to override config.properties settings in a
> dynamic way, without needing to dump them to a file at Karaf startup. I'm
> aware of the ${includes} and ${optionals} but those require files to be read
> from the disk where here I'm talking about being able to dynamically
> manipulate the properties once loaded.
> Basically something like this would be fantastic
> {code}
> // code to setup System properties
> main = new Main(new String[0]);
> ConfigProperties config = main.getConfig();
> if (config == null) {
>config = new ConfigProperties();
> }
> // manipulate config in any way desired
> main.setConfig(config)
> main.launch();
> {code}
> The main.launch could then simply be modified to something like this :
> {code}
> public void launch() throws Exception {
> if (config == null) {
> config = new ConfigProperties();
> }
> {code}
> Btw we are using Karaf 4.0.x so having this in both Karaf 4.1.0 and Karaf 4.0
> would be fantastic.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (KARAF-4361) Allow dynamic config customization when embedding Karaf using the Main class
[
https://issues.apache.org/jira/browse/KARAF-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-4361.
-
Resolution: Fixed
> Allow dynamic config customization when embedding Karaf using the Main class
>
>
> Key: KARAF-4361
> URL: https://issues.apache.org/jira/browse/KARAF-4361
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core
>Affects Versions: 4.1.0, 4.0.4
>Reporter: Serge Huber
>Assignee: Guillaume Nodet
> Fix For: 4.0.9, 4.1.0
>
> Attachments:
> KARAF_4361_Allow_dynamic_config_customization_when_embedding_Karaf_using_the_Main_class.patch
>
>
> We are using Karaf by embedding it and basically starting it like this :
> {code}
> // code to setup System properties
> main = new Main(new String[0]);
> main.launch();
> {code}
> The problem is that the ConfigProperties that are used to startup Karaf are
> directly created in the main.launch() method, like this:
> {code}
> public void launch() throws Exception {
> config = new ConfigProperties();
> {code}
> Ideally it would be great if we could either have a setter to provide the
> config value, so that we could manipulate it before launching. In an embedded
> environment this quickly becomes a necessity. For example we would like to
> make it possible to have retrieve properties coming from another framework
> such as Spring and use those to override config.properties settings in a
> dynamic way, without needing to dump them to a file at Karaf startup. I'm
> aware of the ${includes} and ${optionals} but those require files to be read
> from the disk where here I'm talking about being able to dynamically
> manipulate the properties once loaded.
> Basically something like this would be fantastic
> {code}
> // code to setup System properties
> main = new Main(new String[0]);
> ConfigProperties config = main.getConfig();
> if (config == null) {
>config = new ConfigProperties();
> }
> // manipulate config in any way desired
> main.setConfig(config)
> main.launch();
> {code}
> The main.launch could then simply be modified to something like this :
> {code}
> public void launch() throws Exception {
> if (config == null) {
> config = new ConfigProperties();
> }
> {code}
> Btw we are using Karaf 4.0.x so having this in both Karaf 4.1.0 and Karaf 4.0
> would be fantastic.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KARAF-4361) Allow dynamic config customization when embedding Karaf using the Main class
[
https://issues.apache.org/jira/browse/KARAF-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938541#comment-15938541
]
Jean-Baptiste Onofré commented on KARAF-4361:
-
It looks good to me on master:
https://github.com/apache/karaf/blob/master/main/src/main/java/org/apache/karaf/main/Main.java#L233
> Allow dynamic config customization when embedding Karaf using the Main class
>
>
> Key: KARAF-4361
> URL: https://issues.apache.org/jira/browse/KARAF-4361
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core
>Affects Versions: 4.1.0, 4.0.4
>Reporter: Serge Huber
>Assignee: Guillaume Nodet
> Fix For: 4.1.0, 4.0.9
>
> Attachments:
> KARAF_4361_Allow_dynamic_config_customization_when_embedding_Karaf_using_the_Main_class.patch
>
>
> We are using Karaf by embedding it and basically starting it like this :
> {code}
> // code to setup System properties
> main = new Main(new String[0]);
> main.launch();
> {code}
> The problem is that the ConfigProperties that are used to startup Karaf are
> directly created in the main.launch() method, like this:
> {code}
> public void launch() throws Exception {
> config = new ConfigProperties();
> {code}
> Ideally it would be great if we could either have a setter to provide the
> config value, so that we could manipulate it before launching. In an embedded
> environment this quickly becomes a necessity. For example we would like to
> make it possible to have retrieve properties coming from another framework
> such as Spring and use those to override config.properties settings in a
> dynamic way, without needing to dump them to a file at Karaf startup. I'm
> aware of the ${includes} and ${optionals} but those require files to be read
> from the disk where here I'm talking about being able to dynamically
> manipulate the properties once loaded.
> Basically something like this would be fantastic
> {code}
> // code to setup System properties
> main = new Main(new String[0]);
> ConfigProperties config = main.getConfig();
> if (config == null) {
>config = new ConfigProperties();
> }
> // manipulate config in any way desired
> main.setConfig(config)
> main.launch();
> {code}
> The main.launch could then simply be modified to something like this :
> {code}
> public void launch() throws Exception {
> if (config == null) {
> config = new ConfigProperties();
> }
> {code}
> Btw we are using Karaf 4.0.x so having this in both Karaf 4.1.0 and Karaf 4.0
> would be fantastic.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KARAF-5055) Service wrapper shutdown timeout is not taken into account when Karaf's JVM is 'Stopped'
[ https://issues.apache.org/jira/browse/KARAF-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938406#comment-15938406 ] John Poth commented on KARAF-5055: -- Thank you [~jbonofre] > Service wrapper shutdown timeout is not taken into account when Karaf's JVM > is 'Stopped' > > > Key: KARAF-5055 > URL: https://issues.apache.org/jira/browse/KARAF-5055 > Project: Karaf > Issue Type: Bug > Components: karaf-os-integration >Reporter: John Poth >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.9, 4.1.1 > > Attachments: wrapper-shutdown.xml > > > To reproduce, install the attached blueprint and start Karaf using the > Service Wrapper. Then: > \\ > * bin/karaf-service stop and then immediately > * kill -STOP $karaf_jvm_pid > You'll notice that the Karaf JVM will be killed using SIGTERM regardless of > the shutdown timeouts set in both the Service wrapper settings file > (karaf-wrapper.conf) and karaf. This doesn't allow for graceful shutdown. > I can provide a PR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5055) Service wrapper shutdown timeout is not taken into account when Karaf's JVM is 'Stopped'
[ https://issues.apache.org/jira/browse/KARAF-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938403#comment-15938403 ] ASF subversion and git services commented on KARAF-5055: Commit 3293f91b63f6abf30d2867972b3e5f075c24f3fe in karaf's branch refs/heads/karaf-4.0.x from [~jpoth] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=3293f91 ] [KARAF-5055] Use karaf shutdown timeout when notifying the service wrapper in Main > Service wrapper shutdown timeout is not taken into account when Karaf's JVM > is 'Stopped' > > > Key: KARAF-5055 > URL: https://issues.apache.org/jira/browse/KARAF-5055 > Project: Karaf > Issue Type: Bug > Components: karaf-os-integration >Reporter: John Poth >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.9, 4.1.1 > > Attachments: wrapper-shutdown.xml > > > To reproduce, install the attached blueprint and start Karaf using the > Service Wrapper. Then: > \\ > * bin/karaf-service stop and then immediately > * kill -STOP $karaf_jvm_pid > You'll notice that the Karaf JVM will be killed using SIGTERM regardless of > the shutdown timeouts set in both the Service wrapper settings file > (karaf-wrapper.conf) and karaf. This doesn't allow for graceful shutdown. > I can provide a PR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5055) Service wrapper shutdown timeout is not taken into account when Karaf's JVM is 'Stopped'
[ https://issues.apache.org/jira/browse/KARAF-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938395#comment-15938395 ] ASF subversion and git services commented on KARAF-5055: Commit 64d2ef60adb718655dee10d9e0bdc1d0a2e94a5c in karaf's branch refs/heads/master from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=64d2ef6 ] [KARAF-5055] This closes #290 > Service wrapper shutdown timeout is not taken into account when Karaf's JVM > is 'Stopped' > > > Key: KARAF-5055 > URL: https://issues.apache.org/jira/browse/KARAF-5055 > Project: Karaf > Issue Type: Bug > Components: karaf-os-integration >Reporter: John Poth >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.9, 4.1.1 > > Attachments: wrapper-shutdown.xml > > > To reproduce, install the attached blueprint and start Karaf using the > Service Wrapper. Then: > \\ > * bin/karaf-service stop and then immediately > * kill -STOP $karaf_jvm_pid > You'll notice that the Karaf JVM will be killed using SIGTERM regardless of > the shutdown timeouts set in both the Service wrapper settings file > (karaf-wrapper.conf) and karaf. This doesn't allow for graceful shutdown. > I can provide a PR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (KARAF-5055) Service wrapper shutdown timeout is not taken into account when Karaf's JVM is 'Stopped'
[ https://issues.apache.org/jira/browse/KARAF-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-5055. - Resolution: Fixed > Service wrapper shutdown timeout is not taken into account when Karaf's JVM > is 'Stopped' > > > Key: KARAF-5055 > URL: https://issues.apache.org/jira/browse/KARAF-5055 > Project: Karaf > Issue Type: Bug > Components: karaf-os-integration >Reporter: John Poth >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.9, 4.1.1 > > Attachments: wrapper-shutdown.xml > > > To reproduce, install the attached blueprint and start Karaf using the > Service Wrapper. Then: > \\ > * bin/karaf-service stop and then immediately > * kill -STOP $karaf_jvm_pid > You'll notice that the Karaf JVM will be killed using SIGTERM regardless of > the shutdown timeouts set in both the Service wrapper settings file > (karaf-wrapper.conf) and karaf. This doesn't allow for graceful shutdown. > I can provide a PR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5055) Service wrapper shutdown timeout is not taken into account when Karaf's JVM is 'Stopped'
[ https://issues.apache.org/jira/browse/KARAF-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938396#comment-15938396 ] ASF GitHub Bot commented on KARAF-5055: --- Github user asfgit closed the pull request at: https://github.com/apache/karaf/pull/290 > Service wrapper shutdown timeout is not taken into account when Karaf's JVM > is 'Stopped' > > > Key: KARAF-5055 > URL: https://issues.apache.org/jira/browse/KARAF-5055 > Project: Karaf > Issue Type: Bug > Components: karaf-os-integration >Reporter: John Poth >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.9, 4.1.1 > > Attachments: wrapper-shutdown.xml > > > To reproduce, install the attached blueprint and start Karaf using the > Service Wrapper. Then: > \\ > * bin/karaf-service stop and then immediately > * kill -STOP $karaf_jvm_pid > You'll notice that the Karaf JVM will be killed using SIGTERM regardless of > the shutdown timeouts set in both the Service wrapper settings file > (karaf-wrapper.conf) and karaf. This doesn't allow for graceful shutdown. > I can provide a PR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5055) Service wrapper shutdown timeout is not taken into account when Karaf's JVM is 'Stopped'
[ https://issues.apache.org/jira/browse/KARAF-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938394#comment-15938394 ] ASF subversion and git services commented on KARAF-5055: Commit e5f4f5c4852b3b825bdfe411665c37721ba921fb in karaf's branch refs/heads/master from [~jpoth] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=e5f4f5c ] [KARAF-5055] Use karaf shutdown timeout when notifying the service wrapper in Main > Service wrapper shutdown timeout is not taken into account when Karaf's JVM > is 'Stopped' > > > Key: KARAF-5055 > URL: https://issues.apache.org/jira/browse/KARAF-5055 > Project: Karaf > Issue Type: Bug > Components: karaf-os-integration >Reporter: John Poth >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.9, 4.1.1 > > Attachments: wrapper-shutdown.xml > > > To reproduce, install the attached blueprint and start Karaf using the > Service Wrapper. Then: > \\ > * bin/karaf-service stop and then immediately > * kill -STOP $karaf_jvm_pid > You'll notice that the Karaf JVM will be killed using SIGTERM regardless of > the shutdown timeouts set in both the Service wrapper settings file > (karaf-wrapper.conf) and karaf. This doesn't allow for graceful shutdown. > I can provide a PR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KARAF-4174) NullPointerException when running obr:info on a bundle served by cave
[ https://issues.apache.org/jira/browse/KARAF-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4174: Fix Version/s: (was: 4.1.1) 4.1.2 > NullPointerException when running obr:info on a bundle served by cave > - > > Key: KARAF-4174 > URL: https://issues.apache.org/jira/browse/KARAF-4174 > Project: Karaf > Issue Type: Bug > Components: cave-server, karaf-repository >Affects Versions: 4.0.4 >Reporter: Marton Papp >Assignee: Jean-Baptiste Onofré > Fix For: cave-4.0.1, 4.0.9, 4.1.2 > > > Hello, > I am using Cave 4.0.0 with Karaf 4.0.4-SNAPSHOT (after having the same > problem with 4.0.3) and I get a NullPointerException when running the > obr:info command on a bundle. > To reproduce: > __ __ >/ //_/ __ _/ __/ > / ,< / __ `/ ___/ __ `/ /_ > / /| |/ /_/ / / / /_/ / __/ > /_/ |_|\__,_/_/ \__,_/_/ > Apache Karaf (4.0.4-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()> feature:repo-add cave 4.0.0 > Adding feature url > mvn:org.apache.karaf.cave/apache-karaf-cave/4.0.0/xml/features > karaf@root()> feature:install cave-server > karaf@root()> cave:repository-create my-repository > karaf@root()> cave:repository-upload my-repository > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.ant/1.7.0_5 > karaf@root()> feature:install obr > karaf@root()> obr:url-add > http://localhost:8181/cave/http/my-repository-repository.xml > karaf@root()> obr:list > Name | Symbolic Name | Version > -- > | org.apache.servicemix.bundles.ant | 1.7.0.5 > karaf@root()> obr:info org.apache.servicemix.bundles.ant > Error executing command: java.lang.NullPointerException > karaf@root()> display -n 3 > 2015-12-05 18:40:26,319 | INFO | pool-50-thread-1 | bundle > | 56 - org.apache.aries.spifly.dynamic.bundle - 1.0.1 | No > 'SPI-Provider' Manifest header. Skipping bundle: org.apache.karaf.obr.core > 2015-12-05 18:40:26,319 | INFO | pool-50-thread-1 | FeaturesServiceImpl > | 9 - org.apache.karaf.features.core - 4.0.4.SNAPSHOT | Done. > 2015-12-05 18:40:40,518 | ERROR | nsole user karaf | ShellUtil > | 44 - org.apache.karaf.shell.core - 4.0.4.SNAPSHOT | Exception > caught while executing command > java.lang.NullPointerException > at > org.apache.karaf.obr.command.InfoCommand.printResource(InfoCommand.java:65)[118:org.apache.karaf.obr.core:4.0.4.SNAPSHOT] > at > org.apache.karaf.obr.command.InfoCommand.doExecute(InfoCommand.java:57)[118:org.apache.karaf.obr.core:4.0.4.SNAPSHOT] > at > org.apache.karaf.obr.command.ObrCommandSupport.execute(ObrCommandSupport.java:58)[118:org.apache.karaf.obr.core:4.0.4.SNAPSHOT] > at > org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:83)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at > org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:67)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at > org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:87)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at > org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:480)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at > org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:406)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at > org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at > org.apache.felix.gogo.runtime.Closure.execute(Closure.java:182)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at > org.apache.felix.gogo.runtime.Closure.execute(Closure.java:119)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at > org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:94)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at > org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:270)[44:org.apache.karaf.shell.core:4.0.4.SNAPSHOT] > at java.lang.Thread.run(Thread.java:745)[:1.8.0_60] > karaf@root()> > Regards -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KARAF-4235) Windows start script requires data dir
[ https://issues.apache.org/jira/browse/KARAF-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4235: Fix Version/s: (was: 4.1.1) 4.1.2 > Windows start script requires data dir > -- > > Key: KARAF-4235 > URL: https://issues.apache.org/jira/browse/KARAF-4235 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 >Reporter: Fabian Lange >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.9, 4.1.2 > > > I am observing the following problem > On linux, if I delete the data dir, it is recreated. > On Windows, if I run the start.bat, the output is: > karaf.bat: Ignoring predefined value for KARAF_HOME > karaf.bat: KARAF_DATA is not valid: > "C:\Users\Fabian\Downloads\apache-karaf-4.0.3\bin\..\data" > C:\Users\Fabian\Downloads\apache-karaf-4.0.3\bin> > I checked the difference, and right now I am actually wondering more why it > works on linux, rather than why it doesn't on windows, but I think also n > windows the data dir should be recreated. > STR: > Download Karaf 4.0.3 on windows. > unpack and delete data dir. > try to run start.bat > running karaf.bat will work however -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KARAF-4255) karaf-maven-plugin does include unused feature conditional dependencies in assembly
[
https://issues.apache.org/jira/browse/KARAF-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-4255:
Fix Version/s: (was: 4.1.1)
4.1.2
> karaf-maven-plugin does include unused feature conditional dependencies in
> assembly
> ---
>
> Key: KARAF-4255
> URL: https://issues.apache.org/jira/browse/KARAF-4255
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Fabian Lange
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.9, 4.1.2
>
>
> I am using karaf-maven-plugin to make a custom assembly.
> I do include SCR, but I do not include webconsole.
> When I look into the system folder of my generated assembly, I can see:
> {code}
> target/assembly/system/org/apache/felix/org.apache.felix.webconsole.plugins.ds/2.0.2/org.apache.felix.webconsole.plugins.ds-2.0.2.jar
> {code}
> this correlates to the maven output:
> {code}
> [INFO] Feature scr is defined as a boot feature
> [INFO] == Installing artifact
> mvn:org.apache.karaf.scr/org.apache.karaf.scr.command/4.0.3
> [INFO] == Installing artifact mvn:org.apache.felix/org.apache.felix.scr/2.0.2
> [INFO] == Installing artifact
> mvn:org.apache.felix/org.apache.felix.scr.compat/1.0.2
> [INFO] == Installing artifact
> mvn:org.apache.felix/org.apache.felix.webconsole.plugins.ds/2.0.2
> [INFO] == Installing artifact
> mvn:org.apache.felix/org.apache.felix.metatype/1.1.2
> [INFO] == Installing artifact
> mvn:org.apache.karaf.scr/org.apache.karaf.scr.management/4.0.3
> {code}
> however looking at:
> https://github.com/apache/karaf/blob/master/assemblies/features/standard/src/main/feature/feature.xml#L524
> you can see that this is an conditional dependency only.
> This is caused by the fact that assembly does not check if the conditional
> had been met:
> https://github.com/apache/karaf/blob/master/profile/src/main/java/org/apache/karaf/profile/assembly/Builder.java#L822
> I believe we need a check for the conditionals wether the condition is
> actually met.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KARAF-4188) Add support for Systemd's watchdog
[ https://issues.apache.org/jira/browse/KARAF-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4188: Fix Version/s: (was: 4.1.1) 4.1.2 > Add support for Systemd's watchdog > -- > > Key: KARAF-4188 > URL: https://issues.apache.org/jira/browse/KARAF-4188 > Project: Karaf > Issue Type: New Feature > Components: karaf-core >Reporter: Luca Burgazzoli >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.0.6, 4.0.9, 4.1.2 > > > Systemd has a watchdog feature that could help detecting freeze jvm, > integrating it in karaf would be possible via jna/jnr -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (KARAF-4124) feature config installer adds property to config
[
https://issues.apache.org/jira/browse/KARAF-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-4124.
-
Resolution: Won't Fix
This is a fix/improvement to do in Pax JDBC.
> feature config installer adds property to config
>
>
> Key: KARAF-4124
> URL: https://issues.apache.org/jira/browse/KARAF-4124
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.0.3
>Reporter: Markus Rathgeb
>Assignee: Jean-Baptiste Onofré
>
> The element in a feature XML allows a feature to create and/or
> populate a configuration (identified by a configuration PID).
> The "FeatureConfigInstaller" adds a custom property to the configuration.
> key = "org.apache.karaf.features.configKey"
> value = result of function call "createConfigurationKey(pid[0], pid[1])"
> There are bundles that cannot handle additional properties in the
> configuration.
> For example:
> * using Aries JPA + Hiberante + h2
> * the configuration is installed by a feature and a realted config entry
> * this will result in a non working setup
> {noformat}
> Caused by: org.h2.jdbc.JdbcSQLException: Unsupported connection setting
> "ORG.APACHE.KARAF.FEATURES.CONFIGKEY" [90113-172]
> at
> org.h2.message.DbException.getJdbcSQLException(DbException.java:329)
> at org.h2.message.DbException.get(DbException.java:169)
> at org.h2.message.DbException.get(DbException.java:146)
> at
> org.h2.engine.ConnectionInfo.readSettingsFromURL(ConnectionInfo.java:266)
> at org.h2.engine.ConnectionInfo.(ConnectionInfo.java:77)
> at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:90)
> at org.h2.Driver.connect(Driver.java:73)
> at
> org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:187)
> at
> org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:323)
> at
> org.apache.commons.dbcp2.managed.DataSourceXAConnectionFactory.createConnection(DataSourceXAConnectionFactory.java:112)
> at
> org.apache.commons.dbcp2.managed.PoolableManagedConnectionFactory.makeObject(PoolableManagedConnectionFactory.java:66)
> at
> org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:868)
> at
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:435)
> at
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:363)
> at
> org.apache.commons.dbcp2.managed.ManagedConnection.updateTransactionStatus(ManagedConnection.java:127)
> ... 132 more
> {noformat}
> There is a conditional branch in the "findExistingConfiguration" function to
> filter (find) the configuration using that property instead of the
> service.pid (this is another conditional branch).
> Is there any reason for using that property?
> I changed the "FeatureConfigInstaller" to not append that property and the
> above example is working now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KARAF-4162) Wrap deployer does not add default versions to exported packages
[ https://issues.apache.org/jira/browse/KARAF-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4162: Fix Version/s: (was: 4.1.1) (was: 4.0.9) > Wrap deployer does not add default versions to exported packages > > > Key: KARAF-4162 > URL: https://issues.apache.org/jira/browse/KARAF-4162 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 4.0.3 >Reporter: Aleksei Lissitsin > Attachments: export-package-actual.txt, export-package-expected.txt, > spring-beans-4.1.7.RELEASE.jar > > > Wrap deployer does not add default versions to exported packages but should. > Try, e.g., with the provided spring-beans jar. > My attempts to override this behaviour by using bundle:install with wrap url > containing '-nodefaultversion=false' failed too. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KARAF-3976) Broken compatibility with 3.x jdbc DataSources
[
https://issues.apache.org/jira/browse/KARAF-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3976:
Fix Version/s: (was: 4.1.1)
4.1.2
> Broken compatibility with 3.x jdbc DataSources
> --
>
> Key: KARAF-3976
> URL: https://issues.apache.org/jira/browse/KARAF-3976
> Project: Karaf
> Issue Type: Bug
> Components: karaf-jdbc
>Affects Versions: 4.0.1
>Reporter: Sergey
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.9, 4.1.2
>
>
> 1st of all, current documentaion is wrong, because command names was changed
> to jdbc:ds-info, for example, but
> http://karaf.apache.org/manual/latest/users-guide/jdbc.html still contains
> jdbc:info command names.
> Most important compatibility breaking change was another one: in karaf 3.x I
> was able to deploy DataSource using spring-dm xml or blueprint, and it was
> registered as a service and in jndi, and was listed using jdbc:datasources
> command. Right now no datasources are listed.
> {code}
> karaf@root()> jndi:names
> JNDI Name | Class Name
> --
> osgi:service/jdbc/zeusDataSource |
> net.sourceforge.jtds.jdbcx.JtdsDataSource
> osgi:service/jdbc/arenaDS |
> net.sourceforge.jtds.jdbcx.JtdsDataSource
> osgi:service/jdbc/tomsDS |
> net.sourceforge.jtds.jdbcx.JtdsDataSource
> osgi:service/jdbc/cofDS |
> com.sybase.jdbc3.jdbc.SybDataSource
> osgi:service/jdbc/fidbDataSource |
> net.sourceforge.jtds.jdbcx.JtdsDataSource
> osgi:service/jdbc/murexDS |
> com.sybase.jdbc3.jdbc.SybDataSource
> osgi:service/jdbc/gpDataSource|
> org.postgresql.ds.PGPoolingDataSource
> karaf@root()> jdbc:ds-info jdbc/fidbDataSource
> Property | Value
> -
> driver.version | 1.2.2
> db.version | 10.50.4000
> db.product | Microsoft SQL Server
> url| jdbc:jtds:sqlserver:
> driver.name| jTDS Type 4 JDBC Driver for MS SQL Server and Sybase
> username | ...
> karaf@root()> jdbc:ds-list
> Name | Product | Version | URL | Status
> ---
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KARAF-4124) feature config installer adds property to config
[
https://issues.apache.org/jira/browse/KARAF-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-4124:
Fix Version/s: (was: 4.1.1)
(was: 4.0.9)
> feature config installer adds property to config
>
>
> Key: KARAF-4124
> URL: https://issues.apache.org/jira/browse/KARAF-4124
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.0.3
>Reporter: Markus Rathgeb
>Assignee: Jean-Baptiste Onofré
>
> The element in a feature XML allows a feature to create and/or
> populate a configuration (identified by a configuration PID).
> The "FeatureConfigInstaller" adds a custom property to the configuration.
> key = "org.apache.karaf.features.configKey"
> value = result of function call "createConfigurationKey(pid[0], pid[1])"
> There are bundles that cannot handle additional properties in the
> configuration.
> For example:
> * using Aries JPA + Hiberante + h2
> * the configuration is installed by a feature and a realted config entry
> * this will result in a non working setup
> {noformat}
> Caused by: org.h2.jdbc.JdbcSQLException: Unsupported connection setting
> "ORG.APACHE.KARAF.FEATURES.CONFIGKEY" [90113-172]
> at
> org.h2.message.DbException.getJdbcSQLException(DbException.java:329)
> at org.h2.message.DbException.get(DbException.java:169)
> at org.h2.message.DbException.get(DbException.java:146)
> at
> org.h2.engine.ConnectionInfo.readSettingsFromURL(ConnectionInfo.java:266)
> at org.h2.engine.ConnectionInfo.(ConnectionInfo.java:77)
> at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:90)
> at org.h2.Driver.connect(Driver.java:73)
> at
> org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:187)
> at
> org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:323)
> at
> org.apache.commons.dbcp2.managed.DataSourceXAConnectionFactory.createConnection(DataSourceXAConnectionFactory.java:112)
> at
> org.apache.commons.dbcp2.managed.PoolableManagedConnectionFactory.makeObject(PoolableManagedConnectionFactory.java:66)
> at
> org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:868)
> at
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:435)
> at
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:363)
> at
> org.apache.commons.dbcp2.managed.ManagedConnection.updateTransactionStatus(ManagedConnection.java:127)
> ... 132 more
> {noformat}
> There is a conditional branch in the "findExistingConfiguration" function to
> filter (find) the configuration using that property instead of the
> service.pid (this is another conditional branch).
> Is there any reason for using that property?
> I changed the "FeatureConfigInstaller" to not append that property and the
> above example is working now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KARAF-3572) Override resources for instance:create in custom distributions
[
https://issues.apache.org/jira/browse/KARAF-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3572:
Fix Version/s: (was: 4.1.1)
4.1.2
> Override resources for instance:create in custom distributions
> --
>
> Key: KARAF-3572
> URL: https://issues.apache.org/jira/browse/KARAF-3572
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-instance
>Affects Versions: 3.0.3, 2.4.1, 4.0.0.M2
>Reporter: Krzysztof Sobkowiak
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.0.9, 4.1.2
>
>
> Currently the command {{instance:create}} creates a new instance using the
> resources included in {{org.apache.karaf.instance.core}} bundle. It would be
> resonable to allow people to override the resources in custom distributions,
> e.g. in the same way like branding bundles.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KARAF-3825) Add ability to shutdown Karaf with a disabled shutdown port
[ https://issues.apache.org/jira/browse/KARAF-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3825: Fix Version/s: (was: 4.1.1) 4.1.2 > Add ability to shutdown Karaf with a disabled shutdown port > --- > > Key: KARAF-3825 > URL: https://issues.apache.org/jira/browse/KARAF-3825 > Project: Karaf > Issue Type: Improvement > Components: karaf-core >Affects Versions: 3.0.3, 4.0.0 >Reporter: Dmitry Konstantinov >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.9, 4.0.9, 4.1.2 > > > Sometimes by security reasons listen ports are asked to disable. It would be > nice to provide an alternative way to trigger Karaf shutdown by touching a > special file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KARAF-2511) Review and update documentation
[ https://issues.apache.org/jira/browse/KARAF-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2511: Fix Version/s: (was: 4.1.1) 4.1.2 > Review and update documentation > --- > > Key: KARAF-2511 > URL: https://issues.apache.org/jira/browse/KARAF-2511 > Project: Karaf > Issue Type: Task > Components: karaf-documentation >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.9, 4.0.9, 4.1.2 > > > The documentation (manual) should be reviewed: > - The subshell part should be described (usage and configuration). > - The "code samples"/screenshots have to be updated with Karaf 3.0.0 use cases > - a global polishing, double read -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KARAF-3518) JDK9: endorsed directories not working any longer
[
https://issues.apache.org/jira/browse/KARAF-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3518:
Fix Version/s: (was: 4.1.1)
> JDK9: endorsed directories not working any longer
> -
>
> Key: KARAF-3518
> URL: https://issues.apache.org/jira/browse/KARAF-3518
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core, karaf-os-integration
>Affects Versions: 4.0.0.M3
> Environment: OS X,
> java version "1.9.0-ea"
> Java(TM) SE Runtime Environment (build 1.9.0-ea-b49)
> Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b49, mixed mode)
>Reporter: Achim Nierbeck
>Assignee: Guillaume Nodet
> Labels: java9
>
> following message is caught with JDK 1.9:
> {code}
> -Djava.endorsed.dirs=/Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/jre/lib/endorsed:/Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/lib/endorsed:/Users/anierbeck/Development/server/apache-karaf-4.0.0.M2/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.3.15#6346)
[jira] [Updated] (KARAF-201) Add post feature installation triggers
[
https://issues.apache.org/jira/browse/KARAF-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-201:
---
Fix Version/s: (was: 4.1.1)
> Add post feature installation triggers
> --
>
> Key: KARAF-201
> URL: https://issues.apache.org/jira/browse/KARAF-201
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-core, karaf-feature
>Reporter: Guillaume Nodet
>
> Something like:
> {code}
>
> // do anything using gogo commands
>
> {code}
> The result could be displayed to the user so that the installation could give
> him some information (manual steps, or whatever), though it may need a
> separate element.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KARAF-5034) readlink not found on HP-UX
[
https://issues.apache.org/jira/browse/KARAF-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-5034:
Summary: readlink not found on HP-UX (was: readlink not fund on HP-UX)
> readlink not found on HP-UX
> ---
>
> Key: KARAF-5034
> URL: https://issues.apache.org/jira/browse/KARAF-5034
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
>Affects Versions: 3.0.0
> Environment: HP-UX
>Reporter: Terrien Jean-Yves
>Assignee: Jean-Baptiste Onofré
>
> fail to start karaf readlink not found on HP-UX
> solved by addind this code on scripts
> {code}
> if ["" -eq $(whence readlink)]
> then
> DIRNAME=$(dirname "$0")
> PROGNAME=$(basename "$0")
> else
> REALNAME=$(readlink -e "$0" > /dev/null 2>&1)
> if [ $? != 0 ]; then
> REALNAME=$0
> fi
> DIRNAME=$(dirname "$REALNAME")
> PROGNAME=$(basename "$REALNAME")
> fi
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (KARAF-5056) Error executing command: [25] Inappropriate ioctl for device with Karaf-4.1.0 in ARM (BeagleBone)
[
https://issues.apache.org/jira/browse/KARAF-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned KARAF-5056:
---
Assignee: Jean-Baptiste Onofré
> Error executing command: [25] Inappropriate ioctl for device with Karaf-4.1.0
> in ARM (BeagleBone)
> -
>
> Key: KARAF-5056
> URL: https://issues.apache.org/jira/browse/KARAF-5056
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
> Environment: Beagle Bone Black (BeagleBoard.org Debian Image
> 2015-11-12) / (BeagleBoard.org Debian Image 2016-11-06),
> Java JDK 1.8.0_91 / 1.8.0_112
>Reporter: Alvaro Marco
>Assignee: Jean-Baptiste Onofré
>
> When starting a fresh distribution of apache-karaf-4.1.0 on the BeagleBone
> with bin/karaf, the following is displayed (after a while...):
> {code}
> root@beaglebone:~/sandbox/apache-karaf-4.1.0# bin/karaf
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.1.0)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> Error executing command: [25] Inappropriate ioctl for device
> root@beaglebone:~/sandbox/apache-karaf-4.1.0#
> {code}
> and returns to the shell
> The karaf.log register this exception:
> {code}
> ...
> 2017-03-23T06:25:18,543 | INFO | pool-13-thread-1 | core
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
> org.osgi.jmx.framework.PackageStateMBean to MBeanServer
> com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
> osgi.core:type=packageState,version=1.5,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
> 2017-03-23T06:25:18,576 | INFO | pool-13-thread-1 | core
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
> org.osgi.jmx.framework.wiring.BundleWiringStateMBean to MBeanServer
> com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
> osgi.core:type=wiringState,version=1.1,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
> 2017-03-23T06:25:18,453 | ERROR | Karaf local console user karaf | ShellUtil
> | 43 - org.apache.karaf.shell.core - 4.1.0 | Exception
> caught while executing command
> com.sun.jna.LastErrorException: [25] Inappropriate ioctl for device
> at com.sun.jna.Native.invokeVoid(Native Method) ~[?:?]
> at com.sun.jna.Function.invoke(Function.java:374) [?:?]
> at com.sun.jna.Function.invoke(Function.java:323) [?:?]
> at com.sun.jna.Library$Handler.invoke(Library.java:236) [?:?]
> at com.sun.proxy.$Proxy35.ioctl(Unknown Source) [50:org.jline:3.1.3]
> at
> org.jline.terminal.impl.jna.linux.LinuxNativePty.getSize(LinuxNativePty.java:82)
> [50:org.jline:3.1.3]
> at
> org.jline.terminal.impl.AbstractPosixTerminal.getSize(AbstractPosixTerminal.java:58)
> [50:org.jline:3.1.3]
> at
> org.apache.karaf.shell.impl.console.JLineTerminal.getSize(JLineTerminal.java:166)
> [43:org.apache.karaf.shell.core:4.1.0]
> at
> org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:477)
> [50:org.jline:3.1.3]
> at
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:332)
> [43:org.apache.karaf.shell.core:4.1.0]
> at java.lang.Thread.run(Thread.java:745) [?:?]
> 2017-03-23T06:25:19,236 | INFO | FelixShutdown| BlueprintExtender
> | 12 - org.apache.aries.blueprint.core - 1.7.1 | Destroying
> BlueprintContainer for bundle org.apache.karaf.jaas.blueprint.config/4.1.0
> 2017-03-23T06:25:19,455 | INFO | FelixShutdown| BlueprintExtender
> | 12 - org.apache.aries.blueprint.core - 1.7.1 | Destroying
> BlueprintContainer for bundle org.apache.karaf.shell.core/4.1.0
> 2017-03-23T06:25:19,482 | INFO | pool-3-thread-1 | CommandExtension
> | 43 - org.apache.karaf.shell.core - 4.1.0 | Registering commands for
> bundle org.apache.karaf.features.command/4.1.0
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KARAF-5046) Upgrade to maven-surefire-plugin 2.19.1
[
https://issues.apache.org/jira/browse/KARAF-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938234#comment-15938234
]
Jean-Baptiste Onofré commented on KARAF-5046:
-
This update introduce flaky tests with something such kind of error:
{code}
Error executing command:
org.jline.reader.LineReader.getBuffer()Lorg/jline/reader/impl/BufferImpl;
{code}
It could be a race condition/startup order on Pax Exam. I'm postponing this
update to give me time to investigate.
> Upgrade to maven-surefire-plugin 2.19.1
> ---
>
> Key: KARAF-5046
> URL: https://issues.apache.org/jira/browse/KARAF-5046
> Project: Karaf
> Issue Type: Dependency upgrade
> Components: karaf-core, karaf-test
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KARAF-5034) readlink not fund on HP-UX
[
https://issues.apache.org/jira/browse/KARAF-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938042#comment-15938042
]
Terrien Jean-Yves commented on KARAF-5034:
--
I'm running karaf 3.0.7
thank
> readlink not fund on HP-UX
> --
>
> Key: KARAF-5034
> URL: https://issues.apache.org/jira/browse/KARAF-5034
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
>Affects Versions: 3.0.0
> Environment: HP-UX
>Reporter: Terrien Jean-Yves
>Assignee: Jean-Baptiste Onofré
>
> fail to start karaf readlink not found on HP-UX
> solved by addind this code on scripts
> {code}
> if ["" -eq $(whence readlink)]
> then
> DIRNAME=$(dirname "$0")
> PROGNAME=$(basename "$0")
> else
> REALNAME=$(readlink -e "$0" > /dev/null 2>&1)
> if [ $? != 0 ]; then
> REALNAME=$0
> fi
> DIRNAME=$(dirname "$REALNAME")
> PROGNAME=$(basename "$REALNAME")
> fi
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KARAF-5046) Upgrade to maven-surefire-plugin 2.19.1
[ https://issues.apache.org/jira/browse/KARAF-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5046: Fix Version/s: (was: 4.1.1) (was: 4.0.9) > Upgrade to maven-surefire-plugin 2.19.1 > --- > > Key: KARAF-5046 > URL: https://issues.apache.org/jira/browse/KARAF-5046 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core, karaf-test >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KARAF-5056) Error executing command: [25] Inappropriate ioctl for device with Karaf-4.1.0 in ARM (BeagleBone)
[
https://issues.apache.org/jira/browse/KARAF-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alvaro Marco updated KARAF-5056:
Environment:
Beagle Bone Black (BeagleBoard.org Debian Image 2015-11-12) / (BeagleBoard.org
Debian Image 2016-11-06),
Java JDK 1.8.0_91 / 1.8.0_112
was:
Beagle Bone Black (BeagleBoard.org Debian Image 2015-11-12) / Green
(BeagleBoard.org Debian Image 2016-11-06),
Java JDK 1.8.0_91 / 1.8.0_112
> Error executing command: [25] Inappropriate ioctl for device with Karaf-4.1.0
> in ARM (BeagleBone)
> -
>
> Key: KARAF-5056
> URL: https://issues.apache.org/jira/browse/KARAF-5056
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
> Environment: Beagle Bone Black (BeagleBoard.org Debian Image
> 2015-11-12) / (BeagleBoard.org Debian Image 2016-11-06),
> Java JDK 1.8.0_91 / 1.8.0_112
>Reporter: Alvaro Marco
>
> When starting a fresh distribution of apache-karaf-4.1.0 on the BeagleBone
> with bin/karaf, the following is displayed (after a while...):
> {code}
> root@beaglebone:~/sandbox/apache-karaf-4.1.0# bin/karaf
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.1.0)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> Error executing command: [25] Inappropriate ioctl for device
> root@beaglebone:~/sandbox/apache-karaf-4.1.0#
> {code}
> and returns to the shell
> The karaf.log register this exception:
> {code}
> ...
> 2017-03-23T06:25:18,543 | INFO | pool-13-thread-1 | core
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
> org.osgi.jmx.framework.PackageStateMBean to MBeanServer
> com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
> osgi.core:type=packageState,version=1.5,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
> 2017-03-23T06:25:18,576 | INFO | pool-13-thread-1 | core
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
> org.osgi.jmx.framework.wiring.BundleWiringStateMBean to MBeanServer
> com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
> osgi.core:type=wiringState,version=1.1,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
> 2017-03-23T06:25:18,453 | ERROR | Karaf local console user karaf | ShellUtil
> | 43 - org.apache.karaf.shell.core - 4.1.0 | Exception
> caught while executing command
> com.sun.jna.LastErrorException: [25] Inappropriate ioctl for device
> at com.sun.jna.Native.invokeVoid(Native Method) ~[?:?]
> at com.sun.jna.Function.invoke(Function.java:374) [?:?]
> at com.sun.jna.Function.invoke(Function.java:323) [?:?]
> at com.sun.jna.Library$Handler.invoke(Library.java:236) [?:?]
> at com.sun.proxy.$Proxy35.ioctl(Unknown Source) [50:org.jline:3.1.3]
> at
> org.jline.terminal.impl.jna.linux.LinuxNativePty.getSize(LinuxNativePty.java:82)
> [50:org.jline:3.1.3]
> at
> org.jline.terminal.impl.AbstractPosixTerminal.getSize(AbstractPosixTerminal.java:58)
> [50:org.jline:3.1.3]
> at
> org.apache.karaf.shell.impl.console.JLineTerminal.getSize(JLineTerminal.java:166)
> [43:org.apache.karaf.shell.core:4.1.0]
> at
> org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:477)
> [50:org.jline:3.1.3]
> at
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:332)
> [43:org.apache.karaf.shell.core:4.1.0]
> at java.lang.Thread.run(Thread.java:745) [?:?]
> 2017-03-23T06:25:19,236 | INFO | FelixShutdown| BlueprintExtender
> | 12 - org.apache.aries.blueprint.core - 1.7.1 | Destroying
> BlueprintContainer for bundle org.apache.karaf.jaas.blueprint.config/4.1.0
> 2017-03-23T06:25:19,455 | INFO | FelixShutdown| BlueprintExtender
> | 12 - org.apache.aries.blueprint.core - 1.7.1 | Destroying
> BlueprintContainer for bundle org.apache.karaf.shell.core/4.1.0
> 2017-03-23T06:25:19,482 | INFO | pool-3-thread-1 | CommandExtension
> | 43 - org.apache.karaf.shell.core - 4.1.0 | Registering commands for
> bundle org.apache.karaf.features.command/4.1.0
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KARAF-5056) Error executing command: [25] Inappropriate ioctl for device with Karaf-4.1.0 in ARM (BeagleBone)
[
https://issues.apache.org/jira/browse/KARAF-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alvaro Marco updated KARAF-5056:
Description:
When starting a fresh distribution of apache-karaf-4.1.0 on the BeagleBone with
bin/karaf, the following is displayed (after a while...):
{code}
root@beaglebone:~/sandbox/apache-karaf-4.1.0# bin/karaf
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.0)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
Error executing command: [25] Inappropriate ioctl for device
root@beaglebone:~/sandbox/apache-karaf-4.1.0#
{code}
and returns to the shell
The karaf.log register this exception:
{code}
...
2017-03-23T06:25:18,543 | INFO | pool-13-thread-1 | core
| 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
org.osgi.jmx.framework.PackageStateMBean to MBeanServer
com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
osgi.core:type=packageState,version=1.5,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
2017-03-23T06:25:18,576 | INFO | pool-13-thread-1 | core
| 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
org.osgi.jmx.framework.wiring.BundleWiringStateMBean to MBeanServer
com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
osgi.core:type=wiringState,version=1.1,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
2017-03-23T06:25:18,453 | ERROR | Karaf local console user karaf | ShellUtil
| 43 - org.apache.karaf.shell.core - 4.1.0 | Exception
caught while executing command
com.sun.jna.LastErrorException: [25] Inappropriate ioctl for device
at com.sun.jna.Native.invokeVoid(Native Method) ~[?:?]
at com.sun.jna.Function.invoke(Function.java:374) [?:?]
at com.sun.jna.Function.invoke(Function.java:323) [?:?]
at com.sun.jna.Library$Handler.invoke(Library.java:236) [?:?]
at com.sun.proxy.$Proxy35.ioctl(Unknown Source) [50:org.jline:3.1.3]
at
org.jline.terminal.impl.jna.linux.LinuxNativePty.getSize(LinuxNativePty.java:82)
[50:org.jline:3.1.3]
at
org.jline.terminal.impl.AbstractPosixTerminal.getSize(AbstractPosixTerminal.java:58)
[50:org.jline:3.1.3]
at
org.apache.karaf.shell.impl.console.JLineTerminal.getSize(JLineTerminal.java:166)
[43:org.apache.karaf.shell.core:4.1.0]
at
org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:477)
[50:org.jline:3.1.3]
at
org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:332)
[43:org.apache.karaf.shell.core:4.1.0]
at java.lang.Thread.run(Thread.java:745) [?:?]
2017-03-23T06:25:19,236 | INFO | FelixShutdown| BlueprintExtender
| 12 - org.apache.aries.blueprint.core - 1.7.1 | Destroying
BlueprintContainer for bundle org.apache.karaf.jaas.blueprint.config/4.1.0
2017-03-23T06:25:19,455 | INFO | FelixShutdown| BlueprintExtender
| 12 - org.apache.aries.blueprint.core - 1.7.1 | Destroying
BlueprintContainer for bundle org.apache.karaf.shell.core/4.1.0
2017-03-23T06:25:19,482 | INFO | pool-3-thread-1 | CommandExtension
| 43 - org.apache.karaf.shell.core - 4.1.0 | Registering commands for
bundle org.apache.karaf.features.command/4.1.0
...
{code}
was:
When starting a fresh distribution of apache-karaf-4.1.0 on the BeagleBone with
bin/karaf, the following is displayed (after a while...):
{code}
root@beaglebone:~/sandbox/apache-karaf-4.1.0# bin/karaf
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.0)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
Error executing command: [25] Inappropriate ioctl for device
root@beaglebone:~/sandbox/apache-karaf-4.1.0#
{code}
and returns to the shell
The karaf.log register this:
{code}
...
2017-03-23T06:25:18,543 | INFO | pool-13-thread-1 | core
| 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
org.osgi.jmx.framework.PackageStateMBean to MBeanServer
com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
osgi.core:type=packageState,version=1.5,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
2017-03-23T06:25:18,576 | INFO | pool-13-thread-1 | core
| 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
org.osgi.jmx.framework.wiring.BundleWiringStateMBean to MBeanServer
[jira] [Updated] (KARAF-5056) Error executing command: [25] Inappropriate ioctl for device with Karaf-4.1.0 in ARM (BeagleBone)
[
https://issues.apache.org/jira/browse/KARAF-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alvaro Marco updated KARAF-5056:
Environment:
Beagle Bone Black (BeagleBoard.org Debian Image 2015-11-12) / Green
(BeagleBoard.org Debian Image 2016-11-06),
Java JDK 1.8.0_91 / 1.8.0_112
was:Beagle Bone Black / Green, Java 1.8.0_91 / 1.8.0_112
> Error executing command: [25] Inappropriate ioctl for device with Karaf-4.1.0
> in ARM (BeagleBone)
> -
>
> Key: KARAF-5056
> URL: https://issues.apache.org/jira/browse/KARAF-5056
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
> Environment: Beagle Bone Black (BeagleBoard.org Debian Image
> 2015-11-12) / Green (BeagleBoard.org Debian Image 2016-11-06),
> Java JDK 1.8.0_91 / 1.8.0_112
>Reporter: Alvaro Marco
>
> When starting a fresh distribution of apache-karaf-4.1.0 on the BeagleBone
> with bin/karaf, the following is displayed (after a while...):
> {code}
> root@beaglebone:~/sandbox/apache-karaf-4.1.0# bin/karaf
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.1.0)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> Error executing command: [25] Inappropriate ioctl for device
> {code}
> and returns to the shell
> The karaf.log register this:
> {code}
> ...
> 2017-03-23T06:25:18,543 | INFO | pool-13-thread-1 | core
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
> org.osgi.jmx.framework.PackageStateMBean to MBeanServer
> com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
> osgi.core:type=packageState,version=1.5,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
> 2017-03-23T06:25:18,576 | INFO | pool-13-thread-1 | core
> | 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
> org.osgi.jmx.framework.wiring.BundleWiringStateMBean to MBeanServer
> com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
> osgi.core:type=wiringState,version=1.1,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
> 2017-03-23T06:25:18,453 | ERROR | Karaf local console user karaf | ShellUtil
> | 43 - org.apache.karaf.shell.core - 4.1.0 | Exception
> caught while executing command
> com.sun.jna.LastErrorException: [25] Inappropriate ioctl for device
> at com.sun.jna.Native.invokeVoid(Native Method) ~[?:?]
> at com.sun.jna.Function.invoke(Function.java:374) [?:?]
> at com.sun.jna.Function.invoke(Function.java:323) [?:?]
> at com.sun.jna.Library$Handler.invoke(Library.java:236) [?:?]
> at com.sun.proxy.$Proxy35.ioctl(Unknown Source) [50:org.jline:3.1.3]
> at
> org.jline.terminal.impl.jna.linux.LinuxNativePty.getSize(LinuxNativePty.java:82)
> [50:org.jline:3.1.3]
> at
> org.jline.terminal.impl.AbstractPosixTerminal.getSize(AbstractPosixTerminal.java:58)
> [50:org.jline:3.1.3]
> at
> org.apache.karaf.shell.impl.console.JLineTerminal.getSize(JLineTerminal.java:166)
> [43:org.apache.karaf.shell.core:4.1.0]
> at
> org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:477)
> [50:org.jline:3.1.3]
> at
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:332)
> [43:org.apache.karaf.shell.core:4.1.0]
> at java.lang.Thread.run(Thread.java:745) [?:?]
> 2017-03-23T06:25:19,236 | INFO | FelixShutdown| BlueprintExtender
> | 12 - org.apache.aries.blueprint.core - 1.7.1 | Destroying
> BlueprintContainer for bundle org.apache.karaf.jaas.blueprint.config/4.1.0
> 2017-03-23T06:25:19,455 | INFO | FelixShutdown| BlueprintExtender
> | 12 - org.apache.aries.blueprint.core - 1.7.1 | Destroying
> BlueprintContainer for bundle org.apache.karaf.shell.core/4.1.0
> 2017-03-23T06:25:19,482 | INFO | pool-3-thread-1 | CommandExtension
> | 43 - org.apache.karaf.shell.core - 4.1.0 | Registering commands for
> bundle org.apache.karaf.features.command/4.1.0
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KARAF-5056) Error executing command: [25] Inappropriate ioctl for device with Karaf-4.1.0 in ARM (BeagleBone)
[
https://issues.apache.org/jira/browse/KARAF-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alvaro Marco updated KARAF-5056:
Description:
When starting a fresh distribution of apache-karaf-4.1.0 on the BeagleBone with
bin/karaf, the following is displayed (after a while...):
{code}
root@beaglebone:~/sandbox/apache-karaf-4.1.0# bin/karaf
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.0)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
Error executing command: [25] Inappropriate ioctl for device
root@beaglebone:~/sandbox/apache-karaf-4.1.0#
{code}
and returns to the shell
The karaf.log register this:
{code}
...
2017-03-23T06:25:18,543 | INFO | pool-13-thread-1 | core
| 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
org.osgi.jmx.framework.PackageStateMBean to MBeanServer
com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
osgi.core:type=packageState,version=1.5,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
2017-03-23T06:25:18,576 | INFO | pool-13-thread-1 | core
| 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
org.osgi.jmx.framework.wiring.BundleWiringStateMBean to MBeanServer
com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
osgi.core:type=wiringState,version=1.1,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
2017-03-23T06:25:18,453 | ERROR | Karaf local console user karaf | ShellUtil
| 43 - org.apache.karaf.shell.core - 4.1.0 | Exception
caught while executing command
com.sun.jna.LastErrorException: [25] Inappropriate ioctl for device
at com.sun.jna.Native.invokeVoid(Native Method) ~[?:?]
at com.sun.jna.Function.invoke(Function.java:374) [?:?]
at com.sun.jna.Function.invoke(Function.java:323) [?:?]
at com.sun.jna.Library$Handler.invoke(Library.java:236) [?:?]
at com.sun.proxy.$Proxy35.ioctl(Unknown Source) [50:org.jline:3.1.3]
at
org.jline.terminal.impl.jna.linux.LinuxNativePty.getSize(LinuxNativePty.java:82)
[50:org.jline:3.1.3]
at
org.jline.terminal.impl.AbstractPosixTerminal.getSize(AbstractPosixTerminal.java:58)
[50:org.jline:3.1.3]
at
org.apache.karaf.shell.impl.console.JLineTerminal.getSize(JLineTerminal.java:166)
[43:org.apache.karaf.shell.core:4.1.0]
at
org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:477)
[50:org.jline:3.1.3]
at
org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:332)
[43:org.apache.karaf.shell.core:4.1.0]
at java.lang.Thread.run(Thread.java:745) [?:?]
2017-03-23T06:25:19,236 | INFO | FelixShutdown| BlueprintExtender
| 12 - org.apache.aries.blueprint.core - 1.7.1 | Destroying
BlueprintContainer for bundle org.apache.karaf.jaas.blueprint.config/4.1.0
2017-03-23T06:25:19,455 | INFO | FelixShutdown| BlueprintExtender
| 12 - org.apache.aries.blueprint.core - 1.7.1 | Destroying
BlueprintContainer for bundle org.apache.karaf.shell.core/4.1.0
2017-03-23T06:25:19,482 | INFO | pool-3-thread-1 | CommandExtension
| 43 - org.apache.karaf.shell.core - 4.1.0 | Registering commands for
bundle org.apache.karaf.features.command/4.1.0
...
{code}
was:
When starting a fresh distribution of apache-karaf-4.1.0 on the BeagleBone with
bin/karaf, the following is displayed (after a while...):
{code}
root@beaglebone:~/sandbox/apache-karaf-4.1.0# bin/karaf
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.0)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
Error executing command: [25] Inappropriate ioctl for device
{code}
and returns to the shell
The karaf.log register this:
{code}
...
2017-03-23T06:25:18,543 | INFO | pool-13-thread-1 | core
| 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
org.osgi.jmx.framework.PackageStateMBean to MBeanServer
com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
osgi.core:type=packageState,version=1.5,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
2017-03-23T06:25:18,576 | INFO | pool-13-thread-1 | core
| 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
org.osgi.jmx.framework.wiring.BundleWiringStateMBean to MBeanServer
com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
[jira] [Updated] (KARAF-5056) Error executing command: [25] Inappropriate ioctl for device with Karaf-4.1.0 in ARM (BeagleBone)
[
https://issues.apache.org/jira/browse/KARAF-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alvaro Marco updated KARAF-5056:
Description:
When starting a fresh distribution of apache-karaf-4.1.0 on the BeagleBone with
bin/karaf, the following is displayed (after a while...):
{code}
root@beaglebone:~/sandbox/apache-karaf-4.1.0# bin/karaf
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.0)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
Error executing command: [25] Inappropriate ioctl for device
{code}
and returns to the shell
The karaf.log register this:
{code}
...
2017-03-23T06:25:18,543 | INFO | pool-13-thread-1 | core
| 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
org.osgi.jmx.framework.PackageStateMBean to MBeanServer
com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
osgi.core:type=packageState,version=1.5,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
2017-03-23T06:25:18,576 | INFO | pool-13-thread-1 | core
| 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
org.osgi.jmx.framework.wiring.BundleWiringStateMBean to MBeanServer
com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
osgi.core:type=wiringState,version=1.1,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
2017-03-23T06:25:18,453 | ERROR | Karaf local console user karaf | ShellUtil
| 43 - org.apache.karaf.shell.core - 4.1.0 | Exception
caught while executing command
com.sun.jna.LastErrorException: [25] Inappropriate ioctl for device
at com.sun.jna.Native.invokeVoid(Native Method) ~[?:?]
at com.sun.jna.Function.invoke(Function.java:374) [?:?]
at com.sun.jna.Function.invoke(Function.java:323) [?:?]
at com.sun.jna.Library$Handler.invoke(Library.java:236) [?:?]
at com.sun.proxy.$Proxy35.ioctl(Unknown Source) [50:org.jline:3.1.3]
at
org.jline.terminal.impl.jna.linux.LinuxNativePty.getSize(LinuxNativePty.java:82)
[50:org.jline:3.1.3]
at
org.jline.terminal.impl.AbstractPosixTerminal.getSize(AbstractPosixTerminal.java:58)
[50:org.jline:3.1.3]
at
org.apache.karaf.shell.impl.console.JLineTerminal.getSize(JLineTerminal.java:166)
[43:org.apache.karaf.shell.core:4.1.0]
at
org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:477)
[50:org.jline:3.1.3]
at
org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:332)
[43:org.apache.karaf.shell.core:4.1.0]
at java.lang.Thread.run(Thread.java:745) [?:?]
2017-03-23T06:25:19,236 | INFO | FelixShutdown| BlueprintExtender
| 12 - org.apache.aries.blueprint.core - 1.7.1 | Destroying
BlueprintContainer for bundle org.apache.karaf.jaas.blueprint.config/4.1.0
2017-03-23T06:25:19,455 | INFO | FelixShutdown| BlueprintExtender
| 12 - org.apache.aries.blueprint.core - 1.7.1 | Destroying
BlueprintContainer for bundle org.apache.karaf.shell.core/4.1.0
2017-03-23T06:25:19,482 | INFO | pool-3-thread-1 | CommandExtension
| 43 - org.apache.karaf.shell.core - 4.1.0 | Registering commands for
bundle org.apache.karaf.features.command/4.1.0
...
{code}
was:
When starting a fresh distribution of apache-karaf-4.1.0 on the BeagleBone with
bin/karaf, the following is displayed:
{code}
root@beaglebone:~/sandbox/apache-karaf-4.1.0# bin/karaf
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.0)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
Error executing command: [25] Inappropriate ioctl for device
{code}
and returns to the shell
The karaf.log register this:
{code}
...
2017-03-23T06:25:18,543 | INFO | pool-13-thread-1 | core
| 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
org.osgi.jmx.framework.PackageStateMBean to MBeanServer
com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
osgi.core:type=packageState,version=1.5,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
2017-03-23T06:25:18,576 | INFO | pool-13-thread-1 | core
| 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
org.osgi.jmx.framework.wiring.BundleWiringStateMBean to MBeanServer
com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
[jira] [Created] (KARAF-5056) Error executing command: [25] Inappropriate ioctl for device with Karaf-4.1.0 in ARM (BeagleBone)
Alvaro Marco created KARAF-5056:
---
Summary: Error executing command: [25] Inappropriate ioctl for
device with Karaf-4.1.0 in ARM (BeagleBone)
Key: KARAF-5056
URL: https://issues.apache.org/jira/browse/KARAF-5056
Project: Karaf
Issue Type: Bug
Components: karaf-shell
Affects Versions: 4.1.0
Environment: Beagle Bone Black / Green, Java 1.8.0_91 / 1.8.0_112
Reporter: Alvaro Marco
When starting a fresh distribution of apache-karaf-4.1.0 on the BeagleBone with
bin/karaf, the following is displayed:
{code}
root@beaglebone:~/sandbox/apache-karaf-4.1.0# bin/karaf
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.1.0)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
Error executing command: [25] Inappropriate ioctl for device
{code}
and returns to the shell
The karaf.log register this:
{code}
...
2017-03-23T06:25:18,543 | INFO | pool-13-thread-1 | core
| 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
org.osgi.jmx.framework.PackageStateMBean to MBeanServer
com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
osgi.core:type=packageState,version=1.5,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
2017-03-23T06:25:18,576 | INFO | pool-13-thread-1 | core
| 16 - org.apache.aries.jmx.core - 1.1.7 | Registering
org.osgi.jmx.framework.wiring.BundleWiringStateMBean to MBeanServer
com.sun.jmx.mbeanserver.JmxMBeanServer@481248 with name
osgi.core:type=wiringState,version=1.1,framework=org.apache.felix.framework,uuid=385edf94-736d-4596-99ef-60ac10d44e88
2017-03-23T06:25:18,453 | ERROR | Karaf local console user karaf | ShellUtil
| 43 - org.apache.karaf.shell.core - 4.1.0 | Exception
caught while executing command
com.sun.jna.LastErrorException: [25] Inappropriate ioctl for device
at com.sun.jna.Native.invokeVoid(Native Method) ~[?:?]
at com.sun.jna.Function.invoke(Function.java:374) [?:?]
at com.sun.jna.Function.invoke(Function.java:323) [?:?]
at com.sun.jna.Library$Handler.invoke(Library.java:236) [?:?]
at com.sun.proxy.$Proxy35.ioctl(Unknown Source) [50:org.jline:3.1.3]
at
org.jline.terminal.impl.jna.linux.LinuxNativePty.getSize(LinuxNativePty.java:82)
[50:org.jline:3.1.3]
at
org.jline.terminal.impl.AbstractPosixTerminal.getSize(AbstractPosixTerminal.java:58)
[50:org.jline:3.1.3]
at
org.apache.karaf.shell.impl.console.JLineTerminal.getSize(JLineTerminal.java:166)
[43:org.apache.karaf.shell.core:4.1.0]
at
org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:477)
[50:org.jline:3.1.3]
at
org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:332)
[43:org.apache.karaf.shell.core:4.1.0]
at java.lang.Thread.run(Thread.java:745) [?:?]
2017-03-23T06:25:19,236 | INFO | FelixShutdown| BlueprintExtender
| 12 - org.apache.aries.blueprint.core - 1.7.1 | Destroying
BlueprintContainer for bundle org.apache.karaf.jaas.blueprint.config/4.1.0
2017-03-23T06:25:19,455 | INFO | FelixShutdown| BlueprintExtender
| 12 - org.apache.aries.blueprint.core - 1.7.1 | Destroying
BlueprintContainer for bundle org.apache.karaf.shell.core/4.1.0
2017-03-23T06:25:19,482 | INFO | pool-3-thread-1 | CommandExtension
| 43 - org.apache.karaf.shell.core - 4.1.0 | Registering commands for
bundle org.apache.karaf.features.command/4.1.0
...
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
