[jira] [Commented] (FELIX-3773) WebConsole uses library with ASL-incompatible licence
[ https://issues.apache.org/jira/browse/FELIX-3773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13502290#comment-13502290 ] Gert Vanthienen commented on FELIX-3773: According to http://www.apache.org/legal/resolved.html#json, it looks like the use of this library has been approved by the legal@ team WebConsole uses library with ASL-incompatible licence - Key: FELIX-3773 URL: https://issues.apache.org/jira/browse/FELIX-3773 Project: Felix Issue Type: Bug Components: Web Console Reporter: Neil Bartlett Priority: Critical WebConsole uses the JSON library from json.org that contains the following term in its licence (http://www.json.org/license.html): The Software shall be used for Good, not Evil. I believe that this restriction is incompatible with the ASL. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3752) Compilation failure in utils subproject on AIX
Gert Vanthienen created FELIX-3752: -- Summary: Compilation failure in utils subproject on AIX Key: FELIX-3752 URL: https://issues.apache.org/jira/browse/FELIX-3752 Project: Felix Issue Type: Bug Components: Utils Affects Versions: utils-1.2.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Priority: Minor Fix For: utils-1.2.2 When building the Felix Utils subproject on AIX, you bump into this compilation failure due to an unused com.sun import in PropertiesTest [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:testCompile (default-testCompile) on project org.apache.felix.utils: Compilation failure [ERROR] /home/hudson/workspace/felix-utils-7.1.x.fuse-stable-platform/jdk/jdk6/label/aix5/utils/src/test/java/org/apache/felix/utils/properties/PropertiesTest.java:[26,49] package com.sun.org.apache.xerces.internal.impl.dv does not exist [ERROR] - [Help 1] [ERROR] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (FELIX-3752) Compilation failure in utils subproject on AIX
[ https://issues.apache.org/jira/browse/FELIX-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved FELIX-3752. Resolution: Fixed Fixed in http://svn.apache.org/viewvc?view=revisionrevision=1408700 Compilation failure in utils subproject on AIX -- Key: FELIX-3752 URL: https://issues.apache.org/jira/browse/FELIX-3752 Project: Felix Issue Type: Bug Components: Utils Affects Versions: utils-1.2.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Priority: Minor Fix For: utils-1.2.2 When building the Felix Utils subproject on AIX, you bump into this compilation failure due to an unused com.sun import in PropertiesTest [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:testCompile (default-testCompile) on project org.apache.felix.utils: Compilation failure [ERROR] /home/hudson/workspace/felix-utils-7.1.x.fuse-stable-platform/jdk/jdk6/label/aix5/utils/src/test/java/org/apache/felix/utils/properties/PropertiesTest.java:[26,49] package com.sun.org.apache.xerces.internal.impl.dv does not exist [ERROR] - [Help 1] [ERROR] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3006) Please create a logout button for the web console screen
[ https://issues.apache.org/jira/browse/FELIX-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13102516#comment-13102516 ] Gert Vanthienen commented on FELIX-3006: The LogoutServlet plugin was added to avoid having to code addtional bits and pieces into the main OsgiManager class if we can have the logout code/ui/... done in a similar way as the other stuff. As Felix already pointed out, there's no use of sessions or cookies, so I just focused on getting the UI done and sending back the HTTP 401 authentication challenge so people have to provide their credentials again before they can continue working. That's the closest thing to 'logging out' that I could imagine, but I'm open to suggestions. Feel free to send along any suggestions/recommendations for improvement and I'll gladly alter the patch... Please create a logout button for the web console screen Key: FELIX-3006 URL: https://issues.apache.org/jira/browse/FELIX-3006 Project: Felix Issue Type: Improvement Components: Web Console Reporter: Susan Javurek Attachments: FELIX-3006.diff Please add a log out button on the web console to avoid sessions and cookies being retained. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3006) Please create a logout button for the web console screen
[ https://issues.apache.org/jira/browse/FELIX-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated FELIX-3006: --- Attachment: FELIX-3006.diff Attaching a first stab at a fix... Please create a logout button for the web console screen Key: FELIX-3006 URL: https://issues.apache.org/jira/browse/FELIX-3006 Project: Felix Issue Type: Improvement Components: Web Console Reporter: Susan Javurek Attachments: FELIX-3006.diff Please add a log out button on the web console to avoid sessions and cookies being retained. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FELIX-2419) UnsupportedOperationException while installing features
UnsupportedOperationException while installing features
---
Key: FELIX-2419
URL: https://issues.apache.org/jira/browse/FELIX-2419
Project: Felix
Issue Type: Bug
Components: Karaf
Affects Versions: karaf-1.6.2
Reporter: Gert Vanthienen
Fix For: karaf 1.8.0
I was trying to install a few features on the Karaf 1.6.2 release candidate
build and encountered UnsupportedOperationException
Here are the commands I used
{noformat}
features:addUrl mvn:org.apache.camel.karaf/apache-camel/2.2.0/xml/features
features:install camel-scala
features:install camel
{noformat}
This is the resulting exception's stack trace
{noformat}
10:46:07,342 | INFO | l Console Thread | Console |
araf.shell.console.jline.Console 198 | Exception caught while executing command
java.lang.UnsupportedOperationException
at java.util.AbstractList.remove(AbstractList.java:144)[:1.6.0_20]
at java.util.AbstractList$Itr.remove(AbstractList.java:360)[:1.6.0_20]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.findBundlesWithOptionalPackagesToRefresh(FeaturesServiceImpl.java:445)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.findBundlesToRefresh(FeaturesServiceImpl.java:389)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:252)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:222)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:218)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:51)[27:org.apache.felix.karaf.features.command:1.6.2]
at
org.apache.felix.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:39)[27:org.apache.felix.karaf.features.command:1.6.2]
at
org.apache.felix.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:41)[22:org.apache.felix.karaf.shell.console:1.6.2]
at
org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[22:org.apache.felix.karaf.shell.console:1.6.2]
at
org.apache.felix.gogo.runtime.shell.CommandProxy.execute(CommandProxy.java:50)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:229)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.executeStatement(Closure.java:162)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Pipe.run(Pipe.java:101)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:79)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.CommandSessionImpl.execute(CommandSessionImpl.java:71)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.karaf.shell.console.jline.Console.run(Console.java:180)[22:org.apache.felix.karaf.shell.console:1.6.2]
at java.lang.Thread.run(Thread.java:637)[:1.6.0_20]
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-2419) UnsupportedOperationException while installing features
[
https://issues.apache.org/jira/browse/FELIX-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated FELIX-2419:
---
Attachment: FELIX-2419.diff
UnsupportedOperationException while installing features
---
Key: FELIX-2419
URL: https://issues.apache.org/jira/browse/FELIX-2419
Project: Felix
Issue Type: Bug
Components: Karaf
Affects Versions: karaf-1.6.2
Reporter: Gert Vanthienen
Assignee: Guillaume Nodet
Fix For: karaf-1.6.2
Attachments: FELIX-2419.diff
I was trying to install a few features on the Karaf 1.6.2 release candidate
build and encountered UnsupportedOperationException
Here are the commands I used
{noformat}
features:addUrl mvn:org.apache.camel.karaf/apache-camel/2.2.0/xml/features
features:install camel-scala
features:install camel
{noformat}
This is the resulting exception's stack trace
{noformat}
10:46:07,342 | INFO | l Console Thread | Console |
araf.shell.console.jline.Console 198 | Exception caught while executing
command
java.lang.UnsupportedOperationException
at java.util.AbstractList.remove(AbstractList.java:144)[:1.6.0_20]
at java.util.AbstractList$Itr.remove(AbstractList.java:360)[:1.6.0_20]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.findBundlesWithOptionalPackagesToRefresh(FeaturesServiceImpl.java:445)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.findBundlesToRefresh(FeaturesServiceImpl.java:389)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:252)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:222)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:218)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:51)[27:org.apache.felix.karaf.features.command:1.6.2]
at
org.apache.felix.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:39)[27:org.apache.felix.karaf.features.command:1.6.2]
at
org.apache.felix.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:41)[22:org.apache.felix.karaf.shell.console:1.6.2]
at
org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[22:org.apache.felix.karaf.shell.console:1.6.2]
at
org.apache.felix.gogo.runtime.shell.CommandProxy.execute(CommandProxy.java:50)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:229)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.executeStatement(Closure.java:162)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Pipe.run(Pipe.java:101)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:79)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.CommandSessionImpl.execute(CommandSessionImpl.java:71)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.karaf.shell.console.jline.Console.run(Console.java:180)[22:org.apache.felix.karaf.shell.console:1.6.2]
at java.lang.Thread.run(Thread.java:637)[:1.6.0_20]
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2419) UnsupportedOperationException while installing features
[
https://issues.apache.org/jira/browse/FELIX-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved FELIX-2419.
Resolution: Fixed
Fixed in http://svn.apache.org/viewvc?view=revisionrevision=955727
UnsupportedOperationException while installing features
---
Key: FELIX-2419
URL: https://issues.apache.org/jira/browse/FELIX-2419
Project: Felix
Issue Type: Bug
Components: Karaf
Affects Versions: karaf-1.6.2
Reporter: Gert Vanthienen
Assignee: Guillaume Nodet
Fix For: karaf-1.6.2
Attachments: FELIX-2419.diff
I was trying to install a few features on the Karaf 1.6.2 release candidate
build and encountered UnsupportedOperationException
Here are the commands I used
{noformat}
features:addUrl mvn:org.apache.camel.karaf/apache-camel/2.2.0/xml/features
features:install camel-scala
features:install camel
{noformat}
This is the resulting exception's stack trace
{noformat}
10:46:07,342 | INFO | l Console Thread | Console |
araf.shell.console.jline.Console 198 | Exception caught while executing
command
java.lang.UnsupportedOperationException
at java.util.AbstractList.remove(AbstractList.java:144)[:1.6.0_20]
at java.util.AbstractList$Itr.remove(AbstractList.java:360)[:1.6.0_20]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.findBundlesWithOptionalPackagesToRefresh(FeaturesServiceImpl.java:445)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.findBundlesToRefresh(FeaturesServiceImpl.java:389)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:252)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:222)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:218)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:51)[27:org.apache.felix.karaf.features.command:1.6.2]
at
org.apache.felix.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:39)[27:org.apache.felix.karaf.features.command:1.6.2]
at
org.apache.felix.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:41)[22:org.apache.felix.karaf.shell.console:1.6.2]
at
org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[22:org.apache.felix.karaf.shell.console:1.6.2]
at
org.apache.felix.gogo.runtime.shell.CommandProxy.execute(CommandProxy.java:50)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:229)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.executeStatement(Closure.java:162)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Pipe.run(Pipe.java:101)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:79)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.CommandSessionImpl.execute(CommandSessionImpl.java:71)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.karaf.shell.console.jline.Console.run(Console.java:180)[22:org.apache.felix.karaf.shell.console:1.6.2]
at java.lang.Thread.run(Thread.java:637)[:1.6.0_20]
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2361) Unable to connect to admin:create'd instances from within the Karaf shell
[ https://issues.apache.org/jira/browse/FELIX-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12877950#action_12877950 ] Gert Vanthienen commented on FELIX-2361: This was apparently only happening on Ubuntu Linux -- it no longer ships with support for the Cipher implementations required for the SSH connection. This issue can be fixed by adding Bouncycastle as a security provider as explained in http://felix.apache.org/site/65-deploying-security-providers.html (or downloading and installing the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 6 from Sun) Unable to connect to admin:create'd instances from within the Karaf shell - Key: FELIX-2361 URL: https://issues.apache.org/jira/browse/FELIX-2361 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf 1.6.0 Reporter: Gert Vanthienen Assignee: Guillaume Nodet Fix For: karaf-1.6.2 When a child instance has been created with admin:create command, connecting to it with the admin:connect afterwards fails. The child instance itself is working correctly though and connecting with a plain ssh connection works fine. ka...@root admin:list Port State Pid Name [ 8101] [Started ] [20896] root [ 8102] [Started ] [19939] test ka...@root admin:connect test Connecting to host localhost on port 8102 Connected Error executing command: Session is closed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-2360) Error message from bin/karaf script
[ https://issues.apache.org/jira/browse/FELIX-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen reassigned FELIX-2360: -- Assignee: Gert Vanthienen Error message from bin/karaf script Key: FELIX-2360 URL: https://issues.apache.org/jira/browse/FELIX-2360 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf 1.6.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Priority: Trivial Fix For: karaf 1.8.0 When starting Karaf 1.6.0, an unnecessary error message appears on the console: ge...@ubuntu:~/opt/apache-felix-karaf-1.6.0$ bin/karaf bin/karaf: 326: [[: not found -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2360) Error message from bin/karaf script
Error message from bin/karaf script Key: FELIX-2360 URL: https://issues.apache.org/jira/browse/FELIX-2360 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf 1.6.0 Reporter: Gert Vanthienen Priority: Trivial Fix For: karaf 1.8.0 When starting Karaf 1.6.0, an unnecessary error message appears on the console: ge...@ubuntu:~/opt/apache-felix-karaf-1.6.0$ bin/karaf bin/karaf: 326: [[: not found -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2361) Unable to connect to admin:create'd instances from within the Karaf shell
Unable to connect to admin:create'd instances from within the Karaf shell - Key: FELIX-2361 URL: https://issues.apache.org/jira/browse/FELIX-2361 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf 1.6.0 Reporter: Gert Vanthienen Fix For: karaf 1.8.0 When a child instance has been created with admin:create command, connecting to it with the admin:connect afterwards fails. The child instance itself is working correctly though and connecting with a plain ssh connection works fine. ka...@root admin:list Port State Pid Name [ 8101] [Started ] [20896] root [ 8102] [Started ] [19939] test ka...@root admin:connect test Connecting to host localhost on port 8102 Connected Error executing command: Session is closed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2169) Improve dev:show-tree performance and avoid NPE for installed bundle
Improve dev:show-tree performance and avoid NPE for installed bundle Key: FELIX-2169 URL: https://issues.apache.org/jira/browse/FELIX-2169 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf-1.2.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.4.0 As reported in https://issues.apache.org/activemq/browse/SMX4-489, the current implementation of the dev:show-tree command has two problems: * for bundles with an extensive set of dependencies, calculating the dependency tree can take a long time (several seconds) * for installed bundles with imports for which no suitable export is available, the command fails with a NullPointerException -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-2169) Improve dev:show-tree performance and avoid NPE for installed bundle
[ https://issues.apache.org/jira/browse/FELIX-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated FELIX-2169: --- Affects Version/s: (was: karaf-1.2.0) karaf-1.4.0 Fix Version/s: (was: karaf-1.4.0) karaf 1.6.0 Improve dev:show-tree performance and avoid NPE for installed bundle Key: FELIX-2169 URL: https://issues.apache.org/jira/browse/FELIX-2169 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf-1.4.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf 1.6.0 As reported in https://issues.apache.org/activemq/browse/SMX4-489, the current implementation of the dev:show-tree command has two problems: * for bundles with an extensive set of dependencies, calculating the dependency tree can take a long time (several seconds) * for installed bundles with imports for which no suitable export is available, the command fails with a NullPointerException -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2169) Improve dev:show-tree performance and avoid NPE for installed bundle
[ https://issues.apache.org/jira/browse/FELIX-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved FELIX-2169. Resolution: Fixed Fixed in http://svn.apache.org/viewvc?view=revisionrevision=918963 Will ask Charles Mouillard to confirm that this fixes the issue he has reported. Improve dev:show-tree performance and avoid NPE for installed bundle Key: FELIX-2169 URL: https://issues.apache.org/jira/browse/FELIX-2169 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf-1.4.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf 1.6.0 As reported in https://issues.apache.org/activemq/browse/SMX4-489, the current implementation of the dev:show-tree command has two problems: * for bundles with an extensive set of dependencies, calculating the dependency tree can take a long time (several seconds) * for installed bundles with imports for which no suitable export is available, the command fails with a NullPointerException -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2061) [karaf] use waitForFrameworkStartup pax-exam option in the integration tests
[ https://issues.apache.org/jira/browse/FELIX-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen closed FELIX-2061. -- Resolution: Fixed Assignee: Gert Vanthienen Fixed in http://svn.apache.org/viewvc?view=revisionrevision=908120 Thanks to Eoghan for providing the patch! [karaf] use waitForFrameworkStartup pax-exam option in the integration tests Key: FELIX-2061 URL: https://issues.apache.org/jira/browse/FELIX-2061 Project: Felix Issue Type: Improvement Components: Karaf Affects Versions: karaf-1.2.0 Reporter: Eoghan Glynn Assignee: Gert Vanthienen Fix For: karaf-1.4.0 Attachments: felix_2061.patch I've seen the odd timeout in the Karaf integration tests, and I noticed that waitForFrameworkStartup pax-exam option was not being used. Now I'm not sure whether there's even any relationship there, but it probably wouldn't do any harm to add in this option. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2004) Update Configuring Failover Deployments doc to to include Oracle support
[ https://issues.apache.org/jira/browse/FELIX-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved FELIX-2004. Resolution: Fixed Fix Version/s: (was: karaf-1.0.0) karaf-1.2.0 Updated http://cwiki.apache.org/confluence/display/FELIX/6.7.+Configuring+Failover+Deployments with the content provided in the test space. @David: Thanks a lot for providing this new content! Could you quickly verify that the new content is in the correct place and close this issue if it is OK? Update Configuring Failover Deployments doc to to include Oracle support Key: FELIX-2004 URL: https://issues.apache.org/jira/browse/FELIX-2004 Project: Felix Issue Type: Bug Components: Documentation Affects Versions: karaf-1.0.0 Reporter: David Porter Fix For: karaf-1.2.0 I have made a number of changes to the Configuring Failover Deployments topic in the Karaf user's guide (http://felix.apache.org/site/67-configuring-failover-deployments.html) I have restructured the topic and added detail on the Oracle support added in FELIX-1975. I don't have rights to update the wiki page, so I have added the revised topic to a test wiki space here: http://cwiki.apache.org/confluence/display/test/6.7.+Configuring+Failover+Deployments I need someone to copy the contents of that page and overwrite the current page, which is here: http://cwiki.apache.org/confluence/display/FELIX/6.7.+Configuring+Failover+Deployments -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1975) [Karaf] Add oracle database support to Karaf jdbc locking feature.
[ https://issues.apache.org/jira/browse/FELIX-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12804567#action_12804567 ] Gert Vanthienen commented on FELIX-1975: Patch has been applied in http://svn.apache.org/viewvc?view=revisionrevision=902839 Thanks to Jamie Goodyear for yet another fine Karaf patch! [Karaf] Add oracle database support to Karaf jdbc locking feature. -- Key: FELIX-1975 URL: https://issues.apache.org/jira/browse/FELIX-1975 Project: Felix Issue Type: New Feature Components: Karaf Reporter: Jamie goodyear Assignee: Gert Vanthienen Attachments: felix-1975.patch Add oracle database support to Karaf jdbc locking feature. Current default JDBC class does not work well with Oracle databases, please add support for functionality with Oracle. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1975) [Karaf] Add oracle database support to Karaf jdbc locking feature.
[ https://issues.apache.org/jira/browse/FELIX-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved FELIX-1975. Resolution: Fixed Fix Version/s: karaf-1.4.0 [Karaf] Add oracle database support to Karaf jdbc locking feature. -- Key: FELIX-1975 URL: https://issues.apache.org/jira/browse/FELIX-1975 Project: Felix Issue Type: New Feature Components: Karaf Reporter: Jamie goodyear Assignee: Gert Vanthienen Fix For: karaf-1.4.0 Attachments: felix-1975.patch Add oracle database support to Karaf jdbc locking feature. Current default JDBC class does not work well with Oracle databases, please add support for functionality with Oracle. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-1843) Karaf shell doens't work properly under windows
[ https://issues.apache.org/jira/browse/FELIX-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen reassigned FELIX-1843: -- Assignee: Gert Vanthienen Karaf shell doens't work properly under windows --- Key: FELIX-1843 URL: https://issues.apache.org/jira/browse/FELIX-1843 Project: Felix Issue Type: Bug Components: Gogo, Karaf Affects Versions: karaf-1.2.0, gogo-0.2.0 Reporter: Stefan Weber Assignee: Gert Vanthienen When ever you try to complete a command the completion doesn't replace the prevoiusly typed characters but will be appended to them. Also backspace isn't working. Same behaviour if you use the up-key to get the last used command. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1932) Possible NullPointerException when itest fails
Possible NullPointerException when itest fails
--
Key: FELIX-1932
URL: https://issues.apache.org/jira/browse/FELIX-1932
Project: Felix
Issue Type: Bug
Components: Karaf
Affects Versions: karaf-1.2.0
Reporter: Gert Vanthienen
Assignee: Gert Vanthienen
Fix For: karaf-1.4.0
When a Karaf itest fails due to a missing service reference, the extra logging
that is being created can be interrupted by a NullPointException:
{noformat}
java.lang.NullPointerException
at
org.apache.felix.karaf.shell.itests.AbstractIntegrationTest.getOsgiService(AbstractIntegrationTest.java:76)
at
org.apache.felix.karaf.shell.itests.FeaturesTest.testFeatures(FeaturesTest.java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.injectContextAndInvoke(CallableTestMethodImpl.java:134)
at
org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.call(CallableTestMethodImpl.java:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.ops4j.pax.exam.rbc.internal.RemoteBundleContextImpl.remoteCall(RemoteBundleContextImpl.java:80)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
{noformat}
The bundle headers logging is also not very useful
{noformat}
Test bundle headers: [Ljava.lang.Object;@7f8922
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1932) Possible NullPointerException when itest fails
[
https://issues.apache.org/jira/browse/FELIX-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen closed FELIX-1932.
--
Resolution: Fixed
Fixed in http://svn.apache.org/viewvc?view=revisionrevision=888961
Possible NullPointerException when itest fails
--
Key: FELIX-1932
URL: https://issues.apache.org/jira/browse/FELIX-1932
Project: Felix
Issue Type: Bug
Components: Karaf
Affects Versions: karaf-1.2.0
Reporter: Gert Vanthienen
Assignee: Gert Vanthienen
Fix For: karaf-1.4.0
When a Karaf itest fails due to a missing service reference, the extra
logging that is being created can be interrupted by a NullPointException:
{noformat}
java.lang.NullPointerException
at
org.apache.felix.karaf.shell.itests.AbstractIntegrationTest.getOsgiService(AbstractIntegrationTest.java:76)
at
org.apache.felix.karaf.shell.itests.FeaturesTest.testFeatures(FeaturesTest.java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.injectContextAndInvoke(CallableTestMethodImpl.java:134)
at
org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.call(CallableTestMethodImpl.java:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.ops4j.pax.exam.rbc.internal.RemoteBundleContextImpl.remoteCall(RemoteBundleContextImpl.java:80)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
{noformat}
The bundle headers logging is also not very useful
{noformat}
Test bundle headers: [Ljava.lang.Object;@7f8922
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1914) Add a development subshell to ease troubleshooting classloading/resolution issues
[
https://issues.apache.org/jira/browse/FELIX-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12786674#action_12786674
]
Gert Vanthienen commented on FELIX-1914:
Add a *{{dev:dynamic-import}}* to enable/disable dynamic imports on a bundle in
http://svn.apache.org/viewvc?view=revisionrevision=887748
When disabling the bundle, the command will determine what packages have been
added.
Example:
{noformat}
ka...@root osgi:update 32
...
Caused by: java.lang.ClassNotFoundException: org.hsqldb.jdbcDriver
at
org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(ModuleImpl.java:738)
at org.apache.felix.framework.ModuleImpl.access$100(ModuleImpl.java:60)
at
org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1650)
at java.lang.ClassLoader.loadClass(ClassLoader.java:254)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:399)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at
org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1130)
... 26 more
ka...@root dev:dynamic-import 35
Enabling dynamic imports on bundle org.apache.servicemix.bundles.commons-dbcp
[35]
ka...@root osgi:update 32
ka...@root dev:dynamic-import 35
Disabling dynamic imports on bundle org.apache.servicemix.bundles.commons-dbcp
[35]
Additional packages wired since dynamic import was enabled:
- org.hsqldb
{noformat}
Add a development subshell to ease troubleshooting classloading/resolution
issues
-
Key: FELIX-1914
URL: https://issues.apache.org/jira/browse/FELIX-1914
Project: Felix
Issue Type: Improvement
Components: Karaf
Affects Versions: karaf-1.2.0
Reporter: Gert Vanthienen
Assignee: Gert Vanthienen
Fix For: karaf-1.4.0
At development time, people sometimes bump into classloading or bundle
resolution issues. Proposing to add a subshell with a few development tools
that can be used to troubleshoot these issues:
- To solve the unable to resolve due to constraint violation, we could
build a tool that discovers multiple bundles exporting the same package that
are needed to resolve the given bundle to give people a clue which
uses-constraints might be involved
- To solve a CNFE, we could build a tool that takes a snapshot of imports,
enabled dynamic imports and refreshes the bundle and then checks the imported
packages again to see which imports were added by the dynamic import
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1914) Add a development subshell to ease troubleshooting classloading/resolution issues
[ https://issues.apache.org/jira/browse/FELIX-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen closed FELIX-1914. -- Resolution: Fixed An initial set of 3 commands has been added to the dev: shell: - dev:show-tree id to show bundle wiring as dependency tree - dev:framework -(no)debug to enable/disable OSGi framework debug logging - dev:dynamic-import to enable/disable dynamic import on the fly Closing this issue - we can always create new issues if we think of new commands to add to the shell. Add a development subshell to ease troubleshooting classloading/resolution issues - Key: FELIX-1914 URL: https://issues.apache.org/jira/browse/FELIX-1914 Project: Felix Issue Type: Improvement Components: Karaf Affects Versions: karaf-1.2.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.4.0 At development time, people sometimes bump into classloading or bundle resolution issues. Proposing to add a subshell with a few development tools that can be used to troubleshoot these issues: - To solve the unable to resolve due to constraint violation, we could build a tool that discovers multiple bundles exporting the same package that are needed to resolve the given bundle to give people a clue which uses-constraints might be involved - To solve a CNFE, we could build a tool that takes a snapshot of imports, enabled dynamic imports and refreshes the bundle and then checks the imported packages again to see which imports were added by the dynamic import -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1914) Add a development subshell to ease troubleshooting classloading/resolution issues
[
https://issues.apache.org/jira/browse/FELIX-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12786473#action_12786473
]
Gert Vanthienen commented on FELIX-1914:
Added a *{{dev:framework}}* to enable/disable debug logging on the underlying
OSGi framework in http://svn.apache.org/viewvc?view=revisionrevision=887538.
* dev:framework -debug enables debug logging
* dev:framework -nodebug disables debug logging
Add a development subshell to ease troubleshooting classloading/resolution
issues
-
Key: FELIX-1914
URL: https://issues.apache.org/jira/browse/FELIX-1914
Project: Felix
Issue Type: Improvement
Components: Karaf
Affects Versions: karaf-1.2.0
Reporter: Gert Vanthienen
Assignee: Gert Vanthienen
Fix For: karaf-1.4.0
At development time, people sometimes bump into classloading or bundle
resolution issues. Proposing to add a subshell with a few development tools
that can be used to troubleshoot these issues:
- To solve the unable to resolve due to constraint violation, we could
build a tool that discovers multiple bundles exporting the same package that
are needed to resolve the given bundle to give people a clue which
uses-constraints might be involved
- To solve a CNFE, we could build a tool that takes a snapshot of imports,
enabled dynamic imports and refreshes the bundle and then checks the imported
packages again to see which imports were added by the dynamic import
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1914) Add a development subshell to ease troubleshooting classloading/resolution issues
[
https://issues.apache.org/jira/browse/FELIX-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12785971#action_12785971
]
Gert Vanthienen commented on FELIX-1914:
Added a *{{dev:show-tree}}* in
http://svn.apache.org/viewvc?view=revisionrevision=887233
This can be used to represent bundle dependencies 'graphically' and it will
also warn users if multiple bundles in the dependency graph are exporting the
same packages.
{noformat}
ka...@root dev:show-tree 36
Bundle wip.foobar [36] is currently INSTALLED
- using wip.bar2 [34] to resolve import org.wip.bar;version=2.0.0
- using wip.foo [35] to resolve import org.wip.foo
wip.foobar [36]
+- wip.bar2 [34]
+- wip.foo [35]
+- wip.bar1 [33]
WARNING: multiple bundles are exporting package org.wip.bar
- wip.bar1 [33]
- wip.bar2 [34]
{noformat}
Add a development subshell to ease troubleshooting classloading/resolution
issues
-
Key: FELIX-1914
URL: https://issues.apache.org/jira/browse/FELIX-1914
Project: Felix
Issue Type: Improvement
Components: Karaf
Affects Versions: karaf-1.2.0
Reporter: Gert Vanthienen
Assignee: Gert Vanthienen
Fix For: karaf-1.4.0
At development time, people sometimes bump into classloading or bundle
resolution issues. Proposing to add a subshell with a few development tools
that can be used to troubleshoot these issues:
- To solve the unable to resolve due to constraint violation, we could
build a tool that discovers multiple bundles exporting the same package that
are needed to resolve the given bundle to give people a clue which
uses-constraints might be involved
- To solve a CNFE, we could build a tool that takes a snapshot of imports,
enabled dynamic imports and refreshes the bundle and then checks the imported
packages again to see which imports were added by the dynamic import
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1914) Add a development subshell to ease troubleshooting classloading/resolution issues
Add a development subshell to ease troubleshooting classloading/resolution issues - Key: FELIX-1914 URL: https://issues.apache.org/jira/browse/FELIX-1914 Project: Felix Issue Type: Improvement Components: Karaf Affects Versions: karaf-1.2.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.4.0 At development time, people sometimes bump into classloading or bundle resolution issues. Proposing to add a subshell with a few development tools that can be used to troubleshoot these issues: - To solve the unable to resolve due to constraint violation, we could build a tool that discovers multiple bundles exporting the same package that are needed to resolve the given bundle to give people a clue which uses-constraints might be involved - To solve a CNFE, we could build a tool that takes a snapshot of imports, enabled dynamic imports and refreshes the bundle and then checks the imported packages again to see which imports were added by the dynamic import -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1899) Karaf itest (CoreTest) fails on slower CI machines
Karaf itest (CoreTest) fails on slower CI machines
---
Key: FELIX-1899
URL: https://issues.apache.org/jira/browse/FELIX-1899
Project: Felix
Issue Type: Bug
Components: Karaf
Affects Versions: karaf-1.0.0
Reporter: Gert Vanthienen
Assignee: Gert Vanthienen
Priority: Minor
Fix For: karaf-1.2.0
When running the Karaf build on a slower (CI) build machine, the CoreTest in
the itests fails because the commands have not been set up when the assertions
are being executed:
{noformat}
org.apache.felix.karaf.shell.itests.CoreTest.testInstallCommand [equinox] View
test details
java.lang.IllegalArgumentException: Command not found: log:display
at org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:208)
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1899) Karaf itest (CoreTest) fails on slower CI machines
[
https://issues.apache.org/jira/browse/FELIX-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved FELIX-1899.
Resolution: Fixed
Fixed in http://svn.apache.org/viewvc?view=revisionrevision=884537
Karaf itest (CoreTest) fails on slower CI machines
---
Key: FELIX-1899
URL: https://issues.apache.org/jira/browse/FELIX-1899
Project: Felix
Issue Type: Bug
Components: Karaf
Affects Versions: karaf-1.0.0
Reporter: Gert Vanthienen
Assignee: Gert Vanthienen
Priority: Minor
Fix For: karaf-1.2.0
When running the Karaf build on a slower (CI) build machine, the CoreTest in
the itests fails because the commands have not been set up when the
assertions are being executed:
{noformat}
org.apache.felix.karaf.shell.itests.CoreTest.testInstallCommand [equinox]
View test details
java.lang.IllegalArgumentException: Command not found: log:display
at org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:208)
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-1882) [karaf] karaf-client should have the option to retry connection establishment
[ https://issues.apache.org/jira/browse/FELIX-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen reassigned FELIX-1882: -- Assignee: Gert Vanthienen [karaf] karaf-client should have the option to retry connection establishment - Key: FELIX-1882 URL: https://issues.apache.org/jira/browse/FELIX-1882 Project: Felix Issue Type: Improvement Components: Karaf Affects Versions: karaf-1.0.0 Reporter: Eoghan Glynn Assignee: Gert Vanthienen Fix For: karaf-1.0.2, karaf-1.2.0 Attachments: felix_1882.patch When using the karaf-client to run some automated set-up commands on a newly started karaf instances, there's a slight race condition between the ssh server being ready to accept incoming connections and the point at which the karaf-client is run. This is especially apparent if the karaf instance has a long boot features list. To avoid having to artificially delay the client start-up, the karaf-client should accept two new command-line options to enable connection-establishment retry logic: -r [attempts] retry connection establishment (up to attempts times) -d [delay]intra-retry delay (defaults to 2 seconds) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1799) Hot-deployment does not work on admin:create'd instances
[ https://issues.apache.org/jira/browse/FELIX-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen closed FELIX-1799. -- Resolution: Fixed Fixed in http://svn.apache.org/viewvc?view=revisionrevision=829191 Hot-deployment does not work on admin:create'd instances Key: FELIX-1799 URL: https://issues.apache.org/jira/browse/FELIX-1799 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf-1.2.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.2.0 When using admin:create to create a new container instance, bundles copied to the hot-deployment folder for that instance are being deployed. The reason is that the etc/org.apache.felix.fileinstall-deploy.cfg file is missing from the instance which is required to configure Felix FileInstall -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1799) Hot-deployment does not work on admin:create'd instances
Hot-deployment does not work on admin:create'd instances Key: FELIX-1799 URL: https://issues.apache.org/jira/browse/FELIX-1799 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf-1.2.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.2.0 When using admin:create to create a new container instance, bundles copied to the hot-deployment folder for that instance are being deployed. The reason is that the etc/org.apache.felix.fileinstall-deploy.cfg file is missing from the instance which is required to configure Felix FileInstall -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1064) New goal for the features-maven-plugin: validate a features xml file
[ https://issues.apache.org/jira/browse/FELIX-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12767479#action_12767479 ] Gert Vanthienen commented on FELIX-1064: Improving the validate goal to deal with maven repositories specified in the bundle url cfr. http://svn.apache.org/viewvc?view=revisionrevision=826783 New goal for the features-maven-plugin: validate a features xml file Key: FELIX-1064 URL: https://issues.apache.org/jira/browse/FELIX-1064 Project: Felix Issue Type: Improvement Components: Karaf Reporter: Guillaume Nodet Assignee: Gert Vanthienen Fix For: karaf-1.0.2, karaf-1.2.0 We should add a goal to the features-maven-plugin to validate the features xml file: * do all the bundles exist? * are all the imports from the bundles resolved? Most of the code for reading manifest and looking up the bundles is already available in the features-maven-plugin' generate-features-xml Mojo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-1064) New goal for the features-maven-plugin: validate a features xml file
[ https://issues.apache.org/jira/browse/FELIX-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen reassigned FELIX-1064: -- Assignee: Gert Vanthienen New goal for the features-maven-plugin: validate a features xml file Key: FELIX-1064 URL: https://issues.apache.org/jira/browse/FELIX-1064 Project: Felix Issue Type: Improvement Components: Karaf Reporter: Guillaume Nodet Assignee: Gert Vanthienen We should add a goal to the features-maven-plugin to validate the features xml file: * do all the bundles exist? * are all the imports from the bundles resolved? Most of the code for reading manifest and looking up the bundles is already available in the features-maven-plugin' generate-features-xml Mojo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1064) New goal for the features-maven-plugin: validate a features xml file
[
https://issues.apache.org/jira/browse/FELIX-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved FELIX-1064.
Resolution: Fixed
Fix Version/s: karaf-1.2.0
karaf-1.0.2
The new plugin goal has been added in
http://svn.apache.org/viewvc?view=revisionrevision=826062
The new goal can be used by adding this plugin configuration to the build
section:
{code:xml}
plugin
groupIdorg.apache.felix.karaf.tooling/groupId
artifactIdfeatures-maven-plugin/artifactId
version1.1.0-SNAPSHOT/version
executions
execution
idvalidate/id
phaseprocess-resources/phase
goals
goalvalidate/goal
/goals
/execution
/executions
/plugin
{code
New goal for the features-maven-plugin: validate a features xml file
Key: FELIX-1064
URL: https://issues.apache.org/jira/browse/FELIX-1064
Project: Felix
Issue Type: Improvement
Components: Karaf
Reporter: Guillaume Nodet
Assignee: Gert Vanthienen
Fix For: karaf-1.0.2, karaf-1.2.0
We should add a goal to the features-maven-plugin to validate the features
xml file:
* do all the bundles exist?
* are all the imports from the bundles resolved?
Most of the code for reading manifest and looking up the bundles is already
available in the features-maven-plugin' generate-features-xml Mojo.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1749) Improve log:set command - add auto-completion for log levels and support lower case level
[ https://issues.apache.org/jira/browse/FELIX-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated FELIX-1749: --- Fix Version/s: (was: felix-2.0.1) Improve log:set command - add auto-completion for log levels and support lower case level - Key: FELIX-1749 URL: https://issues.apache.org/jira/browse/FELIX-1749 Project: Felix Issue Type: Improvement Components: Karaf Affects Versions: karaf-1.0.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Priority: Minor Fix For: karaf-1.0.2, karaf-1.2.0 Improve usability on the log:set command by: - adding a completer for the log level - allowing people to specify log levels in lower case too -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1749) Improve log:set command - add auto-completion for log levels and support lower case level
[ https://issues.apache.org/jira/browse/FELIX-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen closed FELIX-1749. -- Resolution: Fixed Fixed in http://svn.apache.org/viewvc?view=revrevision=824811 Improve log:set command - add auto-completion for log levels and support lower case level - Key: FELIX-1749 URL: https://issues.apache.org/jira/browse/FELIX-1749 Project: Felix Issue Type: Improvement Components: Karaf Affects Versions: karaf-1.0.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Priority: Minor Fix For: karaf-1.0.2, karaf-1.2.0 Improve usability on the log:set command by: - adding a completer for the log level - allowing people to specify log levels in lower case too -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1749) Improve log:set command - add auto-completion for log levels and support lower case level
Improve log:set command - add auto-completion for log levels and support lower case level - Key: FELIX-1749 URL: https://issues.apache.org/jira/browse/FELIX-1749 Project: Felix Issue Type: Improvement Components: Karaf Affects Versions: karaf-1.0.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Priority: Minor Fix For: felix-2.0.1, karaf-1.0.2, karaf-1.2.0 Improve usability on the log:set command by: - adding a completer for the log level - allowing people to specify log levels in lower case too -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1745) Unable to alter/unset a log level after it has been set from the console
Unable to alter/unset a log level after it has been set from the console Key: FELIX-1745 URL: https://issues.apache.org/jira/browse/FELIX-1745 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf-1.0.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.0.2, karaf-1.2.0 Once a log level has been set from the console, it seems impossible to alter/unset it. Cfr. this example ka...@root:/ log:get all ROOT: INFO org.apache.geronimo.gshell.remote: WARN ka...@root:/ log:set DEBUG com.foo ka...@root:/ log:set WARN com.foo.example ka...@root:/ log:get all ROOT: INFO com.foo: DEBUG com.foo.example: WARN org.apache.geronimo.gshell.remote: WARN ka...@root:/ log:set INFO com.foo ka...@root:/ log:get all ROOT: INFO com.foo: DEBUG com.foo.example: WARN org.apache.geronimo.gshell.remote: WARN ka...@root:/ log:set INFO com.foo ka...@root:/ log:get all ROOT: INFO com.foo: DEBUG com.foo.example: WARN org.apache.geronimo.gshell.remote: WARN ka...@root:/ log:set - com.foo ERROR - is not a valid option ka...@root:/ log:set WARN com.foo ka...@root:/ log:set - com.foo ERROR - is not a valid option ka...@root:/ log:get all ROOT: INFO com.foo: DEBUG com.foo.example: WARN org.apache.geronimo.gshell.remote: WARN -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1745) Unable to alter/unset a log level after it has been set from the console
[ https://issues.apache.org/jira/browse/FELIX-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen closed FELIX-1745. -- Resolution: Fixed Fixed in http://svn.apache.org/viewvc?view=revrevision=824488 Unable to alter/unset a log level after it has been set from the console Key: FELIX-1745 URL: https://issues.apache.org/jira/browse/FELIX-1745 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf-1.0.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.0.2, karaf-1.2.0 Once a log level has been set from the console, it seems impossible to alter/unset it. Cfr. this example ka...@root:/ log:get all ROOT: INFO org.apache.geronimo.gshell.remote: WARN ka...@root:/ log:set DEBUG com.foo ka...@root:/ log:set WARN com.foo.example ka...@root:/ log:get all ROOT: INFO com.foo: DEBUG com.foo.example: WARN org.apache.geronimo.gshell.remote: WARN ka...@root:/ log:set INFO com.foo ka...@root:/ log:get all ROOT: INFO com.foo: DEBUG com.foo.example: WARN org.apache.geronimo.gshell.remote: WARN ka...@root:/ log:set INFO com.foo ka...@root:/ log:get all ROOT: INFO com.foo: DEBUG com.foo.example: WARN org.apache.geronimo.gshell.remote: WARN ka...@root:/ log:set - com.foo ERROR - is not a valid option ka...@root:/ log:set WARN com.foo ka...@root:/ log:set - com.foo ERROR - is not a valid option ka...@root:/ log:get all ROOT: INFO com.foo: DEBUG com.foo.example: WARN org.apache.geronimo.gshell.remote: WARN -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1728) Karaf itest fail on IBM JDK due to Pax Exam annotations not found
Karaf itest fail on IBM JDK due to Pax Exam annotations not found - Key: FELIX-1728 URL: https://issues.apache.org/jira/browse/FELIX-1728 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf-1.0.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.0.2 Due to a difference in the way the IBM JDK handles annotations (it fails on annotations not on the classpath instead of ignoring them), the following tests fail: org.apache.felix.karaf.shell.itests.FeaturesTest.testFeatures [equinox] org.apache.felix.karaf.shell.itests.CoreTest.testHelp [equinox] org.apache.felix.karaf.shell.itests.CoreTest.testInstallCommand [equinox] Cfr. http://lists.ops4j.org/pipermail/general/2009q4/003296.html for background information the error looks like this: java.lang.TypeNotPresentException: Type org.ops4j.pax.exam.junit.Configuration not present at com.ibm.oti.reflect.AnnotationHelper.getAnnotation(AnnotationHelper.java:38) at com.ibm.oti.reflect.AnnotationHelper.getDeclaredAnnotations(AnnotationHelper.java:50) at com.ibm.oti.reflect.Method.getDeclaredAnnotations(Method.java:31) at java.lang.reflect.Method.getDeclaredAnnotations(Method.java:722) at java.lang.reflect.AccessibleObject.getAnnotations(AccessibleObject.java:191) at com.ibm.oti.reflect.Method.getAnnotation(Method.java:20) at java.lang.reflect.Method.getAnnotation(Method.java:711) at org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.getAnnotatedMethods(CallableTestMethodImpl.java:295) at org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.runBefores(CallableTestMethodImpl.java:162) at org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.injectContextAndInvoke(CallableTestMethodImpl.java:124) at org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.call(CallableTestMethodImpl.java:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.ops4j.pax.exam.rbc.internal.RemoteBundleContextImpl.remoteCall(RemoteBundleContextImpl.java:80) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:309) at sun.rmi.transport.Transport$1.run(Transport.java:168) at java.security.AccessController.doPrivileged(AccessController.java:279) at sun.rmi.transport.Transport.serviceCall(Transport.java:164) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:506) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.handleRequest(TCPTransport.java:838) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:912) at java.lang.Thread.run(Thread.java:810) Caused by: java.lang.ClassNotFoundException: org.ops4j.pax.exam.junit.Configuration at java.lang.Class.forName(Class.java:163) at com.ibm.oti.reflect.AnnotationHelper.getAnnotation(AnnotationHelper.java:33) ... 27 more The test launches okay, but the pax Configuration annotation class cannot be found. Adding the jar that contains the class, pax-exam-junit as a bundle in the test when we detect that we are using the ibm jdk allows the test to pass. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1728) Karaf itest fail on IBM JDK due to Pax Exam annotations not found
[ https://issues.apache.org/jira/browse/FELIX-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved FELIX-1728. Resolution: Fixed http://svn.apache.org/viewvc?view=revrevision=823510 adds the necessary jars to the classpath when running the tests on an IBM JDK Karaf itest fail on IBM JDK due to Pax Exam annotations not found - Key: FELIX-1728 URL: https://issues.apache.org/jira/browse/FELIX-1728 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf-1.0.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.0.2 Due to a difference in the way the IBM JDK handles annotations (it fails on annotations not on the classpath instead of ignoring them), the following tests fail: org.apache.felix.karaf.shell.itests.FeaturesTest.testFeatures [equinox] org.apache.felix.karaf.shell.itests.CoreTest.testHelp [equinox] org.apache.felix.karaf.shell.itests.CoreTest.testInstallCommand [equinox] Cfr. http://lists.ops4j.org/pipermail/general/2009q4/003296.html for background information the error looks like this: java.lang.TypeNotPresentException: Type org.ops4j.pax.exam.junit.Configuration not present at com.ibm.oti.reflect.AnnotationHelper.getAnnotation(AnnotationHelper.java:38) at com.ibm.oti.reflect.AnnotationHelper.getDeclaredAnnotations(AnnotationHelper.java:50) at com.ibm.oti.reflect.Method.getDeclaredAnnotations(Method.java:31) at java.lang.reflect.Method.getDeclaredAnnotations(Method.java:722) at java.lang.reflect.AccessibleObject.getAnnotations(AccessibleObject.java:191) at com.ibm.oti.reflect.Method.getAnnotation(Method.java:20) at java.lang.reflect.Method.getAnnotation(Method.java:711) at org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.getAnnotatedMethods(CallableTestMethodImpl.java:295) at org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.runBefores(CallableTestMethodImpl.java:162) at org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.injectContextAndInvoke(CallableTestMethodImpl.java:124) at org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.call(CallableTestMethodImpl.java:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.ops4j.pax.exam.rbc.internal.RemoteBundleContextImpl.remoteCall(RemoteBundleContextImpl.java:80) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:309) at sun.rmi.transport.Transport$1.run(Transport.java:168) at java.security.AccessController.doPrivileged(AccessController.java:279) at sun.rmi.transport.Transport.serviceCall(Transport.java:164) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:506) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.handleRequest(TCPTransport.java:838) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:912) at java.lang.Thread.run(Thread.java:810) Caused by: java.lang.ClassNotFoundException: org.ops4j.pax.exam.junit.Configuration at java.lang.Class.forName(Class.java:163) at com.ibm.oti.reflect.AnnotationHelper.getAnnotation(AnnotationHelper.java:33) ... 27 more The test launches okay, but the pax Configuration annotation class cannot be found. Adding the jar that contains the class, pax-exam-junit as a bundle in the test when we detect that we are using the ibm jdk allows the test to pass. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1641) Unable to connect to Karaf with ssh on Windows
Unable to connect to Karaf with ssh on Windows -- Key: FELIX-1641 URL: https://issues.apache.org/jira/browse/FELIX-1641 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf-1.0.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.0.0 When running Karaf on Windows, you can not connect to it with ssh. The connection is established, but authentication fails even with the default username and password right after installation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1641) Unable to connect to Karaf with ssh on Windows
[ https://issues.apache.org/jira/browse/FELIX-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved FELIX-1641. Resolution: Fixed The default blueprint converter for String - Properties uses the Properties.load() method which strips the \ from the Windows path names. Fixed in https://svn.apache.org/viewvc?view=revrevision=818650 by adding a custom converter to handle this particular use case. Unable to connect to Karaf with ssh on Windows -- Key: FELIX-1641 URL: https://issues.apache.org/jira/browse/FELIX-1641 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf-1.0.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.0.0 When running Karaf on Windows, you can not connect to it with ssh. The connection is established, but authentication fails even with the default username and password right after installation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1635) Find a way to improve handling optional imports in Karaf
Find a way to improve handling optional imports in Karaf Key: FELIX-1635 URL: https://issues.apache.org/jira/browse/FELIX-1635 Project: Felix Issue Type: Improvement Affects Versions: karaf-1.0.0 Reporter: Gert Vanthienen When installing a bundle, optional imports that unavailable at that time are ignored. However, if those ignored packages become available afterwards, users have to manually refresh the bundle to get the optional imports wired correctly. When a user is unaware of this, she'll probably experience a problem that gets fixed when the container is restarted (because bundles are being wired again), We should try to come up with a mechanism to improve this experience. One possible solution would be to improve the features mechanism to support refreshing existing bundles, so we can indicate that a given bundle needs to refreshed when a feature is being installed. Another way to handle it would be by keeping tracking of unwired optional imports and when automatically refreshing bundles when more imports become available. Probably needs a bit more investigation though to find a solution that works... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1624) Add a convenience start/stop script to start/stop karaf running in server mode
Add a convenience start/stop script to start/stop karaf running in server mode -- Key: FELIX-1624 URL: https://issues.apache.org/jira/browse/FELIX-1624 Project: Felix Issue Type: Improvement Affects Versions: karaf-1.0.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.0.0 Add two convenience scripts for starting/stopping karaf in server mode (without a local console) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1624) Add a convenience start/stop script to start/stop karaf running in server mode
[ https://issues.apache.org/jira/browse/FELIX-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated FELIX-1624: --- Attachment: FELIX-1624.diff First take on the *nix scripts -- still need to add the matching Windows scripts to this Add a convenience start/stop script to start/stop karaf running in server mode -- Key: FELIX-1624 URL: https://issues.apache.org/jira/browse/FELIX-1624 Project: Felix Issue Type: Improvement Affects Versions: karaf-1.0.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.0.0 Attachments: FELIX-1624.diff Add two convenience scripts for starting/stopping karaf in server mode (without a local console) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-1618) in spring-dm feature, optional imports in spring-context won't get resolved
[ https://issues.apache.org/jira/browse/FELIX-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen reassigned FELIX-1618: -- Assignee: Gert Vanthienen in spring-dm feature, optional imports in spring-context won't get resolved --- Key: FELIX-1618 URL: https://issues.apache.org/jira/browse/FELIX-1618 Project: Felix Issue Type: Bug Affects Versions: karaf-1.0.0 Reporter: Hans Couder Assignee: Gert Vanthienen Fix For: karaf-1.0.0 In the spring-dm feature, the spring-context bundle precedes spring-aop. This causes optional imports in the spring-context bundle won't get resolved resulting in: Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=org.apache.camel.camel-example-osgi, config=osgibundle:/META-INF/spring/*.xml)) java.lang.NoClassDefFoundError: org/springframework/aop/support/AopUtils at org.springframework.jmx.export.assembler.MetadataMBeanInfoAssembler.checkManagedBean(MetadataMBeanInfoAssembler.java:106) at org.springframework.jmx.export.assembler.AbstractMBeanInfoAssembler.getMBeanInfo(AbstractMBeanInfoAssembler.java:63) at org.apache.camel.management.DefaultManagementAgent.register(DefaultManagementAgent.java:202) at org.apache.camel.management.DefaultManagementAgent.register(DefaultManagementAgent.java:193) at org.apache.camel.management.ManagedManagementStrategy.manageNamedObject(ManagedManagementStrategy.java:68) at org.apache.camel.management.ManagedManagementStrategy.manageObject(ManagedManagementStrategy.java:61) at org.apache.camel.management.DefaultManagementLifecycleStrategy.onContextStart(DefaultManagementLifecycleStrategy.java:99) at org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:918) at org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:869) at org.apache.camel.spring.SpringCamelContext.maybeDoStart(SpringCamelContext.java:165) at org.apache.camel.spring.SpringCamelContext.doStart(SpringCamelContext.java:160) at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:52) at org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:832) at org.apache.camel.spring.SpringCamelContext.maybeStart(SpringCamelContext.java:99) at org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:119) at org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:516) at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78) at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49) at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76) at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736) at org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235) at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358) at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85) at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:136) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ClassNotFoundException: *** Class 'org.springframework.aop.support.AopUtils' was not found because bundle 38 does not import 'org.springframework.aop.support' even though bundle 39 does export it. To resolve this issue, add an import for 'org.springframework.aop.support' to bundle 38. *** at org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1645) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) ... 27 more Caused by: java.lang.ClassNotFoundException: org.springframework.aop.support.AopUtils at
[jira] Resolved: (FELIX-1618) in spring-dm feature, optional imports in spring-context won't get resolved
[ https://issues.apache.org/jira/browse/FELIX-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved FELIX-1618. Resolution: Fixed Reordering the bundles in the features descriptor should fix this, cfr. http://svn.apache.org/viewvc?view=revrevision=816629 @Hans: Can you close this issue if this fixes your problem? in spring-dm feature, optional imports in spring-context won't get resolved --- Key: FELIX-1618 URL: https://issues.apache.org/jira/browse/FELIX-1618 Project: Felix Issue Type: Bug Affects Versions: karaf-1.0.0 Reporter: Hans Couder Assignee: Gert Vanthienen Fix For: karaf-1.0.0 In the spring-dm feature, the spring-context bundle precedes spring-aop. This causes optional imports in the spring-context bundle won't get resolved resulting in: Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=org.apache.camel.camel-example-osgi, config=osgibundle:/META-INF/spring/*.xml)) java.lang.NoClassDefFoundError: org/springframework/aop/support/AopUtils at org.springframework.jmx.export.assembler.MetadataMBeanInfoAssembler.checkManagedBean(MetadataMBeanInfoAssembler.java:106) at org.springframework.jmx.export.assembler.AbstractMBeanInfoAssembler.getMBeanInfo(AbstractMBeanInfoAssembler.java:63) at org.apache.camel.management.DefaultManagementAgent.register(DefaultManagementAgent.java:202) at org.apache.camel.management.DefaultManagementAgent.register(DefaultManagementAgent.java:193) at org.apache.camel.management.ManagedManagementStrategy.manageNamedObject(ManagedManagementStrategy.java:68) at org.apache.camel.management.ManagedManagementStrategy.manageObject(ManagedManagementStrategy.java:61) at org.apache.camel.management.DefaultManagementLifecycleStrategy.onContextStart(DefaultManagementLifecycleStrategy.java:99) at org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:918) at org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:869) at org.apache.camel.spring.SpringCamelContext.maybeDoStart(SpringCamelContext.java:165) at org.apache.camel.spring.SpringCamelContext.doStart(SpringCamelContext.java:160) at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:52) at org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:832) at org.apache.camel.spring.SpringCamelContext.maybeStart(SpringCamelContext.java:99) at org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:119) at org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:516) at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78) at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49) at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76) at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736) at org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235) at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358) at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85) at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:136) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ClassNotFoundException: *** Class 'org.springframework.aop.support.AopUtils' was not found because bundle 38 does not import 'org.springframework.aop.support' even though bundle 39 does export it. To resolve this issue, add an import for 'org.springframework.aop.support' to bundle 38. *** at org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1645) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) ... 27 more Caused
[jira] Created: (FELIX-1602) Unable to configure boot features on admin:create-d instance
Unable to configure boot features on admin:create-d instance Key: FELIX-1602 URL: https://issues.apache.org/jira/browse/FELIX-1602 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf-1.0.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.0.0 When using admin:create to create a new Felix Karaf instance, you can not configure the boot features by just editing the etc/org.apache.felix.karaf.features.cfg file for that instance. To reproduce: - start karaf - from the console, create a new instance with admin:create myinstance - edit the karaf_home/instances/myinstance/etc/org.apache.felix.karaf.features.cfg file - start the instance from the console with admin:start myinstance You'll notice that the instance starts fine but the boot features have not been installed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1602) Unable to configure boot features on admin:create-d instance
[ https://issues.apache.org/jira/browse/FELIX-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved FELIX-1602. Resolution: Fixed Fixed in http://svn.apache.org/viewvc?view=revrevision=815332 Thanks to Guillaume for the pointer! Unable to configure boot features on admin:create-d instance Key: FELIX-1602 URL: https://issues.apache.org/jira/browse/FELIX-1602 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf-1.0.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.0.0 When using admin:create to create a new Felix Karaf instance, you can not configure the boot features by just editing the etc/org.apache.felix.karaf.features.cfg file for that instance. To reproduce: - start karaf - from the console, create a new instance with admin:create myinstance - edit the karaf_home/instances/myinstance/etc/org.apache.felix.karaf.features.cfg file - start the instance from the console with admin:start myinstance You'll notice that the instance starts fine but the boot features have not been installed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1485) Admin commands support in Karaf webconsole
[ https://issues.apache.org/jira/browse/FELIX-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved FELIX-1485. Resolution: Fixed Fix Version/s: karaf-1.0.0 Assignee: Gert Vanthienen Patch has been applied in http://svn.apache.org/viewvc?view=revrevision=804868! @Marcin: Thanks a lot for providing this patch! Could you double-check if everything works as you intended and then close the issue? Admin commands support in Karaf webconsole -- Key: FELIX-1485 URL: https://issues.apache.org/jira/browse/FELIX-1485 Project: Felix Issue Type: New Feature Components: Karaf Reporter: Marcin Wilkos Assignee: Gert Vanthienen Fix For: karaf-1.0.0 Attachments: FELIX-1485.patch We need a new tab in the console for the admin commands (create/destroy/start/stop). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1391) Unable to create new ConfigAdmin PID through karaf console
Unable to create new ConfigAdmin PID through karaf console -- Key: FELIX-1391 URL: https://issues.apache.org/jira/browse/FELIX-1391 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf-1.0.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.0.0 When creating a new PID through the the Karaf console, you get No configuration is being edited. Run the edit command first when trying to set a property value. ka...@root config:edit my.new.pid ka...@root config:propset key value No configuration is being edited. Run the edit command first -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1391) Unable to create new ConfigAdmin PID through karaf console
[ https://issues.apache.org/jira/browse/FELIX-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved FELIX-1391. Resolution: Fixed Fixed in http://svn.apache.org/viewvc?view=revrevision=796348 Unable to create new ConfigAdmin PID through karaf console -- Key: FELIX-1391 URL: https://issues.apache.org/jira/browse/FELIX-1391 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf-1.0.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.0.0 When creating a new PID through the the Karaf console, you get No configuration is being edited. Run the edit command first when trying to set a property value. ka...@root config:edit my.new.pid ka...@root config:propset key value No configuration is being edited. Run the edit command first -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1261) Install/Uninstall Karaf Features from Felix WebConsole
[ https://issues.apache.org/jira/browse/FELIX-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved FELIX-1261. Resolution: Fixed Fix Version/s: karaf-1.0.0 Assignee: Gert Vanthienen Thanks to Tim and Marcin for providing the patches! I have applied Tim's patch in http://svn.apache.org/viewvc?view=revrevision=790920 using the Blueprint descriptor that was already there to glue things together. Could you give it a spin and close this issue afterwards? Install/Uninstall Karaf Features from Felix WebConsole -- Key: FELIX-1261 URL: https://issues.apache.org/jira/browse/FELIX-1261 Project: Felix Issue Type: New Feature Components: Karaf Reporter: Marcin Wilkos Assignee: Gert Vanthienen Fix For: karaf-1.0.0 Attachments: FELIX-1261-ExtendedFeaturesPlugin.patch, webconsole.patch Currently we can't Install/Uninstall Karaf Features from Felix WebConsole. In my Google Summer of Code project I created an Extension Plugin for web console, which lists Karaf Features and gives admin ability to manage them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1200) Move features-maven-plugin into Karaf
[ https://issues.apache.org/jira/browse/FELIX-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12719957#action_12719957 ] Gert Vanthienen commented on FELIX-1200: Initial move in http://svn.apache.org/viewvc?view=revrevision=785091 Move features-maven-plugin into Karaf - Key: FELIX-1200 URL: https://issues.apache.org/jira/browse/FELIX-1200 Project: Felix Issue Type: Task Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.0.0 The ServiceMix Kernel features-maven-plugin should be moved to Karaf as well. cfr. http://www.nabble.com/-karaf--Maven-Features-Plugin-...--to23899256.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1200) Move features-maven-plugin into Karaf
[ https://issues.apache.org/jira/browse/FELIX-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen closed FELIX-1200. -- Resolution: Fixed Aligned it with the rest of Felix Karaf and removed some more references to servicemix kernel in http://svn.apache.org/viewvc?view=revrevision=785170 Move features-maven-plugin into Karaf - Key: FELIX-1200 URL: https://issues.apache.org/jira/browse/FELIX-1200 Project: Felix Issue Type: Task Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.0.0 The ServiceMix Kernel features-maven-plugin should be moved to Karaf as well. cfr. http://www.nabble.com/-karaf--Maven-Features-Plugin-...--to23899256.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1200) Move features-maven-plugin into Karaf
Move features-maven-plugin into Karaf - Key: FELIX-1200 URL: https://issues.apache.org/jira/browse/FELIX-1200 Project: Felix Issue Type: Task Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: karaf-1.0.0 The ServiceMix Kernel features-maven-plugin should be moved to Karaf as well. cfr. http://www.nabble.com/-karaf--Maven-Features-Plugin-...--to23899256.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1121) Add feature for installing Felix Web Console
[
https://issues.apache.org/jira/browse/FELIX-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved FELIX-1121.
Resolution: Fixed
Fix Version/s: karaf-1.0.0
Assignee: Gert Vanthienen
Thanks to Tim Moloney for providing the sample feature descriptor!
The new feature has been added to the main Karaf features file in
http://svn.apache.org/viewvc?view=revrevision=782239.
This will allow you to do a *{{features/install webconsole}}* to get the
console up and running.
Could you close this issue if this works for you, thanks?
Add feature for installing Felix Web Console
-
Key: FELIX-1121
URL: https://issues.apache.org/jira/browse/FELIX-1121
Project: Felix
Issue Type: Improvement
Components: Karaf
Reporter: Gert Vanthienen
Assignee: Gert Vanthienen
Fix For: karaf-1.0.0
Attachments: webconsole-feature.xml
The Felix Web Console can be installed on ServiceMix Kernel with these
commands:
- features/addUrl
mvn:org.apache.servicemix/apache-servicemix/4.0.0/xml/features
- features/install web
- osgi/install -s mvn:org.apache.felix/org.apache.felix.webconsole/1.2.8
We should make it easier for people to install it using a single command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1196) Felix Web Console can't list Karaf features
[
https://issues.apache.org/jira/browse/FELIX-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved FELIX-1196.
Resolution: Fixed
Fix Version/s: karaf-1.0.0
Assignee: Gert Vanthienen
Thanks to Marcin Wilkos for this patch!
It has been integrated in Karaf in
http://svn.apache.org/viewvc?view=revrevision=782261. I have also added this
bundle to the *{{webconsole}}* feature, so it is installed automatically when
you do a *{{features/install webconsole}}*.
Could you check if this fixes the issue for you and close this issue if it's
OK? Thanks!
Felix Web Console can't list Karaf features
---
Key: FELIX-1196
URL: https://issues.apache.org/jira/browse/FELIX-1196
Project: Felix
Issue Type: Improvement
Components: Karaf
Reporter: Marcin Wilkos
Assignee: Gert Vanthienen
Fix For: karaf-1.0.0
Attachments: webconsole.patch
Original Estimate: 24h
Remaining Estimate: 24h
Web console should be extended by plugin, which will make possible listing
Karaf features.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1125) features/list -i returns ERROR CommandLineExecutionFailed: org.apache.geronimo.gshell.command.CommandException: java.lang.ArrayStoreException: org.apache.servicemix.ke
[
https://issues.apache.org/jira/browse/FELIX-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved FELIX-1125.
Resolution: Fixed
Tim,
I think this bug was fixed just before ServiceMix Kernel became Apache Felix
Karaf (cfr. https://issues.apache.org/activemq/browse/SMX4KNL-266)
Regards,
Gert
features/list -i returns ERROR CommandLineExecutionFailed:
org.apache.geronimo.gshell.command.CommandException:
java.lang.ArrayStoreException:
org.apache.servicemix.kernel.gshell.features.internal.FeatureImpl
Key: FELIX-1125
URL: https://issues.apache.org/jira/browse/FELIX-1125
Project: Felix
Issue Type: Bug
Components: Karaf
Affects Versions: karaf-1.0.0
Environment: java version 1.6.0_13
Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
Java HotSpot(TM) Client VM (build 11.3-b02, mixed mode, sharing)
Reporter: Tim Moloney
The bug can be replicated as follows:
bash tar zxf apache-servicemix-kernel-1.1.0.tar.gz
bash cd apache-servicemix-kernel-1.1.0
bash cat webconsole-feature.xmlEOF
features
feature name=webconsole version=0.1.0-SNAPSHOT
bundlemvn:org.mortbay.jetty/jetty-util/6.1.11/jar/bundle
bundlemvn:org.mortbay.jetty/jetty-sslengine/6.1.11/jar/bundle
bundlemvn:org.mortbay.jetty/jetty/6.1.11/jar/bundle
bundlemvn:org.apache.felix/org.apache.felix.http.jetty/1.0.0/jar/bundle
config name=org.apache.felix.http
org.osgi.service.http.port=8080
/config
bundlemvn:org.apache.felix/org.apache.felix.webconsole/1.2.8/jar/bundle
config name=org.apache.felix.webconsole.internal.servlet.OsgiManager
username=tester
password=testing
/config
/feature
/features
EOF
bash bin/servicemix
_ __ __ _
/ ___| ___ _ _(_) ___ ___| \/ (_)_ __
\___ \ / _ \ '__\ \ / / |/ __/ _ \ |\/| | \ \/ /
___) | __/ | \ V /| | (_| __/ | | | |
|/ \___|_|\_/ |_|\___\___|_| |_|_/_/\_\
ServiceMix Kernel (1.1.0)
Type 'help' for more information.
---
s...@root:/ cp webconsole-feature.xml deploy
s...@root:/ features/list -i
ERROR CommandLineExecutionFailed:
org.apache.geronimo.gshell.command.CommandException:
java.lang.ArrayStoreException:
org.apache.servicemix.kernel.gshell.features.internal.FeatureImpl
s...@root:/ log/display-exception
s...@root:/ log/display
...
10:45:12,919 | INFO | localShell | CommandLineExecutorImpl |
om.shell.CommandLineExecutorImpl 64 | Executing (String): features/list -i
10:45:12,920 | INFO | localShell | CommandLineExecutorImpl |
om.shell.CommandLineExecutorImpl 104 | Executing (features/list): [-i]
10:46:19,302 | INFO | localShell | CommandLineExecutorImpl |
om.shell.CommandLineExecutorImpl 64 | Executing (String):
log/display-exception
10:46:19,303 | INFO | localShell | CommandLineExecutorImpl |
om.shell.CommandLineExecutorImpl 104 | Executing (log/display-exception): []
10:46:25,709 | INFO | localShell | CommandLineExecutorImpl |
om.shell.CommandLineExecutorImpl 64 | Executing (String): log/display
10:46:25,711 | INFO | localShell | CommandLineExecutorImpl |
om.shell.CommandLineExecutorImpl 104 | Executing (log/display): []
s...@root:/ osgi/shutdown
s...@root:/ bash
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1125) features/list -i returns ERROR CommandLineExecutionFailed: org.apache.geronimo.gshell.command.CommandException: java.lang.ArrayStoreException: org.apache.servicemix.ker
[
https://issues.apache.org/jira/browse/FELIX-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated FELIX-1125:
---
Fix Version/s: karaf-1.0.0
features/list -i returns ERROR CommandLineExecutionFailed:
org.apache.geronimo.gshell.command.CommandException:
java.lang.ArrayStoreException:
org.apache.servicemix.kernel.gshell.features.internal.FeatureImpl
Key: FELIX-1125
URL: https://issues.apache.org/jira/browse/FELIX-1125
Project: Felix
Issue Type: Bug
Components: Karaf
Affects Versions: karaf-1.0.0
Environment: java version 1.6.0_13
Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
Java HotSpot(TM) Client VM (build 11.3-b02, mixed mode, sharing)
Reporter: Tim Moloney
Fix For: karaf-1.0.0
The bug can be replicated as follows:
bash tar zxf apache-servicemix-kernel-1.1.0.tar.gz
bash cd apache-servicemix-kernel-1.1.0
bash cat webconsole-feature.xmlEOF
features
feature name=webconsole version=0.1.0-SNAPSHOT
bundlemvn:org.mortbay.jetty/jetty-util/6.1.11/jar/bundle
bundlemvn:org.mortbay.jetty/jetty-sslengine/6.1.11/jar/bundle
bundlemvn:org.mortbay.jetty/jetty/6.1.11/jar/bundle
bundlemvn:org.apache.felix/org.apache.felix.http.jetty/1.0.0/jar/bundle
config name=org.apache.felix.http
org.osgi.service.http.port=8080
/config
bundlemvn:org.apache.felix/org.apache.felix.webconsole/1.2.8/jar/bundle
config name=org.apache.felix.webconsole.internal.servlet.OsgiManager
username=tester
password=testing
/config
/feature
/features
EOF
bash bin/servicemix
_ __ __ _
/ ___| ___ _ _(_) ___ ___| \/ (_)_ __
\___ \ / _ \ '__\ \ / / |/ __/ _ \ |\/| | \ \/ /
___) | __/ | \ V /| | (_| __/ | | | |
|/ \___|_|\_/ |_|\___\___|_| |_|_/_/\_\
ServiceMix Kernel (1.1.0)
Type 'help' for more information.
---
s...@root:/ cp webconsole-feature.xml deploy
s...@root:/ features/list -i
ERROR CommandLineExecutionFailed:
org.apache.geronimo.gshell.command.CommandException:
java.lang.ArrayStoreException:
org.apache.servicemix.kernel.gshell.features.internal.FeatureImpl
s...@root:/ log/display-exception
s...@root:/ log/display
...
10:45:12,919 | INFO | localShell | CommandLineExecutorImpl |
om.shell.CommandLineExecutorImpl 64 | Executing (String): features/list -i
10:45:12,920 | INFO | localShell | CommandLineExecutorImpl |
om.shell.CommandLineExecutorImpl 104 | Executing (features/list): [-i]
10:46:19,302 | INFO | localShell | CommandLineExecutorImpl |
om.shell.CommandLineExecutorImpl 64 | Executing (String):
log/display-exception
10:46:19,303 | INFO | localShell | CommandLineExecutorImpl |
om.shell.CommandLineExecutorImpl 104 | Executing (log/display-exception): []
10:46:25,709 | INFO | localShell | CommandLineExecutorImpl |
om.shell.CommandLineExecutorImpl 64 | Executing (String): log/display
10:46:25,711 | INFO | localShell | CommandLineExecutorImpl |
om.shell.CommandLineExecutorImpl 104 | Executing (log/display): []
s...@root:/ osgi/shutdown
s...@root:/ bash
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1121) Add feature for installing Felix Web Console
Add feature for installing Felix Web Console
-
Key: FELIX-1121
URL: https://issues.apache.org/jira/browse/FELIX-1121
Project: Felix
Issue Type: Improvement
Components: Karaf
Reporter: Gert Vanthienen
The Felix Web Console can be installed on ServiceMix Kernel with these commands:
{noformat}
- features/addUrl mvn:org.apache.servicemix/apache-servicemix/4.0.0/xml/features
- features/install web
- osgi/install -s mvn:org.apache.felix/org.apache.felix.webconsole/1.2.8
{noformat}
We should make it easier for people to install it using a single command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1121) Add feature for installing Felix Web Console
[
https://issues.apache.org/jira/browse/FELIX-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated FELIX-1121:
---
Description:
The Felix Web Console can be installed on ServiceMix Kernel with these commands:
- features/addUrl mvn:org.apache.servicemix/apache-servicemix/4.0.0/xml/features
- features/install web
- osgi/install -s mvn:org.apache.felix/org.apache.felix.webconsole/1.2.8
We should make it easier for people to install it using a single command.
was:
The Felix Web Console can be installed on ServiceMix Kernel with these commands:
{noformat}
- features/addUrl mvn:org.apache.servicemix/apache-servicemix/4.0.0/xml/features
- features/install web
- osgi/install -s mvn:org.apache.felix/org.apache.felix.webconsole/1.2.8
{noformat}
We should make it easier for people to install it using a single command.
Add feature for installing Felix Web Console
-
Key: FELIX-1121
URL: https://issues.apache.org/jira/browse/FELIX-1121
Project: Felix
Issue Type: Improvement
Components: Karaf
Reporter: Gert Vanthienen
The Felix Web Console can be installed on ServiceMix Kernel with these
commands:
- features/addUrl
mvn:org.apache.servicemix/apache-servicemix/4.0.0/xml/features
- features/install web
- osgi/install -s mvn:org.apache.felix/org.apache.felix.webconsole/1.2.8
We should make it easier for people to install it using a single command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1116) Rename to Apache Felix Karaf
Rename to Apache Felix Karaf Key: FELIX-1116 URL: https://issues.apache.org/jira/browse/FELIX-1116 Project: Felix Issue Type: Task Components: Karaf Reporter: Gert Vanthienen Fix For: karaf-1.0.0 Now that the ServiceMix Kernel sources have been copied to Felix, we need to start renaming things: - package names should become org.apache.felix.karaf.* - POM group and artifact IDs should be changed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1116) Rename to Apache Felix Karaf
[ https://issues.apache.org/jira/browse/FELIX-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12705329#action_12705329 ] Gert Vanthienen commented on FELIX-1116: The bulk of the changes have been done in http://svn.apache.org/viewvc?limit_changes=0view=revrevision=770981. Some bits that remain are: - change the branding (the ascii art and the info that shows up when you start the product) - change the name of the commands in the bin folder Rename to Apache Felix Karaf Key: FELIX-1116 URL: https://issues.apache.org/jira/browse/FELIX-1116 Project: Felix Issue Type: Task Components: Karaf Reporter: Gert Vanthienen Fix For: karaf-1.0.0 Now that the ServiceMix Kernel sources have been copied to Felix, we need to start renaming things: - package names should become org.apache.felix.karaf.* - POM group and artifact IDs should be changed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-606) Exception when loading a class through DynamicImport-Package
[ https://issues.apache.org/jira/browse/FELIX-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12638530#action_12638530 ] Gert Vanthienen commented on FELIX-606: --- Richard, We recently came across this issue again in ServiceMix 4 and we fixed it by upgrading to Felix 1.2.1, so I guess your fix works. Feel free to mark this issue resolved. Regards, Gert Exception when loading a class through DynamicImport-Package Key: FELIX-606 URL: https://issues.apache.org/jira/browse/FELIX-606 Project: Felix Issue Type: Bug Components: Framework Affects Versions: felix-1.0.4 Reporter: Guillaume Nodet Assignee: Richard S. Hall Attachments: FELIX-606.patch ERROR: Unable to dynamically import package. (java.lang.ArrayStoreException) java.lang.ArrayStoreException at java.lang.System.arraycopy(Native Method) at org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.attemptDynamicImport(R4SearchPolicyCore.java:711) at org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.searchDynamicImports(R4SearchPolicyCore.java:526) at org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClassOrResource(R4SearchPolicyCore.java:480) at org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClass(R4SearchPolicyCore.java:187) at org.apache.felix.framework.searchpolicy.R4SearchPolicy.findClass(R4SearchPolicy.java:45) at org.apache.felix.moduleloader.ModuleImpl.getClass(ModuleImpl.java:146) at org.apache.felix.framework.Felix.loadBundleClass(Felix.java:1501) at org.apache.felix.framework.BundleImpl.loadClass(BundleImpl.java:358) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
