[jira] Created: (FELIX-1881) Add pax-web-extender required in the HTTP feature
Add pax-web-extender required in the HTTP feature
-
Key: FELIX-1881
URL: https://issues.apache.org/jira/browse/FELIX-1881
Project: Felix
Issue Type: New Feature
Components: Karaf
Reporter: Charles Moulliard
Attachments: features.xml
The feature file of Karaf proposes a HTTP feature containing the following
bundles.
{code}
feature name=http version=${version}
config name=org.ops4j.pax.web
org.osgi.service.http.port=8181
/config
bundlemvn:org.apache.geronimo.specs/geronimo-servlet_2.5_spec/${geronimo.servlet.version}/bundle
bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jetty-bundle/${jetty.bundle.version}/bundle
bundlemvn:org.ops4j.pax.web/pax-web-api/${pax.web.version}/bundle
bundlemvn:org.ops4j.pax.web/pax-web-spi/${pax.web.version}/bundle
bundlemvn:org.ops4j.pax.web/pax-web-runtime/${pax.web.version}/bundle
bundlemvn:org.ops4j.pax.web/pax-web-jetty/${pax.web.version}/bundle
/feature
{code}
This feafure is not complete as we need PAX-Web-Extender to deploy web projects
from WAR (ex : Wicket) or deploy an OSgi servlet (ex : CXF - Transport OSGI)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (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 ] Eoghan Glynn updated FELIX-1882: Component/s: Karaf Fix Version/s: karaf-1.2.0 karaf-1.0.2 Affects Version/s: karaf-1.0.0 [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 Fix For: karaf-1.0.2, karaf-1.2.0 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 down 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] Updated: (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 ] Eoghan Glynn updated FELIX-1882: Attachment: felix_1882.patch Can some committer please review this patch and apply if considered kosher? [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 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 down 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] Updated: (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 ] Eoghan Glynn updated FELIX-1882: Description: 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) was: 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 down 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) [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 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] 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] Created: (FELIX-1883) Karaf hangs and crash when several features are deployed
Karaf hangs and crash when several features are deployed
Key: FELIX-1883
URL: https://issues.apache.org/jira/browse/FELIX-1883
Project: Felix
Issue Type: Bug
Reporter: Charles Moulliard
Karaf hangs and crashes several times during installation of features startup
It seems that bundle refreshing is the origin of this problem
ex. Installation of camel-cxf feature (which includes a lot of cxf bundles)
{code}
ka...@root features:install camel-cxf
Refreshing bundles org.springframework.core (33),
org.apache.servicemix.bundles.cglib (44),
org.springframework.context.support (37), org.springframew
ork.context (36), org.apache.camel.camel-core (43)
Using an unsupported terminal: java.lang.UnsatisfiedLinkError: Native
Library C:\Documents and Settings\Charlesm.STREAMLINED\Local
Settings\Temp\jline
_.dll already loaded in another classloader
__ __
/ //_/ __ _/ __/
/ , / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Felix Karaf (1.1.0-SNAPSHOT)
Hit 'tab' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit 'ctrl-d' or 'osgi:shutdown' to shutdown Karaf.
D:\Temp\tutorial\part2\downloaded\reportincident.featuresjava -version
java version 1.6.0_16
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)
{code}
After killing the java process and restarting the server, here is what happens
{code}
ka...@root features:install camel-cxf
Refreshing bundles org.apache.camel.camel-core (43),
org.springframework.context (36), org.springframework.context.support
(37), org.apache.servicemix
.bundles.cglib (44), org.springframework.core (33)
ERROR: JarContent: Unable to read bytes.
(java.lang.IllegalStateException: zip file closed)
java.lang.IllegalStateException: zip file closed
at java.util.zip.ZipFile.ensureOpen(ZipFile.java:403)
at java.util.zip.ZipFile.getEntry(ZipFile.java:148)
at java.util.jar.JarFile.getEntry(JarFile.java:206)
at org.apache.felix.framework.util.JarFileX.getEntry(JarFileX.java:61)
at
org.apache.felix.framework.cache.JarContent.getEntryAsBytes(JarContent.java:120)
at
org.apache.felix.framework.ModuleImpl$ModuleClassLoader.findClass(ModuleImpl.java:1696)
at
org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(ModuleImpl.java:682)
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:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at
org.springframework.aop.framework.AdvisedSupport.getInterceptorsAndDynamicInterceptionAdvice(AdvisedSupport.java:462)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:190)
at $Proxy0.getServiceReference(Unknown Source)
at
org.springframework.osgi.service.importer.support.internal.collection.OsgiServiceCollection.destroy(OsgiServiceCollection.java:294)
at
org.springframework.osgi.service.importer.support.DisposableBeanRunnableAdapter.run(DisposableBeanRunnableAdapter.java:43)
at
org.springframework.osgi.service.importer.support.AbstractServiceImporterProxyFactoryBean.destroy(AbstractServiceImporterProxyFactoryBean.j
ava:67)
at
org.springframework.osgi.extender.internal.activator.ContextLoaderListener.shutdown(ContextLoaderListener.java:555)
at
org.springframework.osgi.extender.internal.activator.ContextLoaderListener.stop(ContextLoaderListener.java:433)
at
org.apache.felix.framework.util.SecureAction.stopActivator(SecureAction.java:661)
at org.apache.felix.framework.Felix.stopBundle(Felix.java:2071)
at org.apache.felix.framework.Felix$RefreshHelper.stop(Felix.java:4255)
at org.apache.felix.framework.Felix.refreshPackages(Felix.java:3405)
at
org.apache.felix.framework.PackageAdminImpl.run(PackageAdminImpl.java:329)
at java.lang.Thread.run(Thread.java:619)
ERROR: Error stopping bundle. (java.lang.NoClassDefFoundError:
org/springframework/aop/framework/AdvisedSupport$MethodCacheKey)
java.lang.NoClassDefFoundError:
org/springframework/aop/framework/AdvisedSupport$MethodCacheKey
at
org.springframework.aop.framework.AdvisedSupport.getInterceptorsAndDynamicInterceptionAdvice(AdvisedSupport.java:462)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:190)
at $Proxy0.getServiceReference(Unknown Source)
at
org.springframework.osgi.service.importer.support.internal.collection.OsgiServiceCollection.destroy(OsgiServiceCollection.java:294)
at
[jira] Resolved: (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 ] Guillaume Nodet resolved FELIX-1882. Resolution: Fixed Committing to https://svn.apache.org/repos/asf/felix/trunk ... M karaf/client/src/main/java/org/apache/felix/karaf/client/Main.java Committed r882582 [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] 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 ] Guillaume Nodet reassigned FELIX-1882: -- Assignee: Guillaume Nodet (was: 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: Guillaume Nodet 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] Resolved: (FELIX-1878) karaf.main.Main possible resource leaks and ignored exceptions from mkdirs().
[ https://issues.apache.org/jira/browse/FELIX-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved FELIX-1878. Resolution: Fixed Fix Version/s: karaf-1.2.0 karaf-1.0.2 Assignee: Guillaume Nodet Committing to https://svn.apache.org/repos/asf/felix/trunk ... M karaf/main/src/main/java/org/apache/felix/karaf/main/Main.java Committed r882590 karaf.main.Main possible resource leaks and ignored exceptions from mkdirs(). - Key: FELIX-1878 URL: https://issues.apache.org/jira/browse/FELIX-1878 Project: Felix Issue Type: Bug Components: Karaf Reporter: Jamie goodyear Assignee: Guillaume Nodet Priority: Minor Fix For: karaf-1.0.2, karaf-1.2.0 Attachments: felix-1778.patch karaf.main.Main possible resource leaks and ignored exceptions from mkdirs(). Resource leaks: org.apache.felix.karaf.main.Main line 361 org.apache.felix.karaf.main.Main line 383 org.apache.felix.karaf.main.Main line 367 Ignored exceptions: org.apache.felix.karaf.main.Main line 187 org.apache.felix.karaf.main.Main line 376 Issues detected during run of static analysis tool. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1601) Can't run in m2eclipse 0.9.9
[ https://issues.apache.org/jira/browse/FELIX-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12780656#action_12780656 ] Fernando Ribeiro commented on FELIX-1601: - Asked for confirmation in the M2Eclipse Developers list. Can't run in m2eclipse 0.9.9 Key: FELIX-1601 URL: https://issues.apache.org/jira/browse/FELIX-1601 Project: Felix Issue Type: Bug Affects Versions: maven-bundle-plugin-2.0.0, maven-bundle-plugin-2.0.1 Reporter: Fernando Ribeiro When running on m2eclipse 0.9.9, I get java.lang.NoSuchMethodError: org.apache.maven.project.MavenProject.getGoalConfiguration(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Lorg/codehaus/plexus/util/xml/Xpp3Dom. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1884) WebConsole should have a Services plugin
WebConsole should have a Services plugin Key: FELIX-1884 URL: https://issues.apache.org/jira/browse/FELIX-1884 Project: Felix Issue Type: New Feature Affects Versions: webconsole-2.0.2 Reporter: Justin Edelson Fix For: webconsole-2.0.4 Attachments: FELIX-1884.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1884) WebConsole should have a Services plugin
[ https://issues.apache.org/jira/browse/FELIX-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated FELIX-1884: -- Attachment: FELIX-1884.patch here's the patch WebConsole should have a Services plugin Key: FELIX-1884 URL: https://issues.apache.org/jira/browse/FELIX-1884 Project: Felix Issue Type: New Feature Affects Versions: webconsole-2.0.2 Reporter: Justin Edelson Fix For: webconsole-2.0.4 Attachments: FELIX-1884.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1884) WebConsole should have a Services plugin
[ https://issues.apache.org/jira/browse/FELIX-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated FELIX-1884: -- Attachment: FELIX-1884b.png FELIX-1884a.png here are some screenshots. WebConsole should have a Services plugin Key: FELIX-1884 URL: https://issues.apache.org/jira/browse/FELIX-1884 Project: Felix Issue Type: New Feature Affects Versions: webconsole-2.0.2 Reporter: Justin Edelson Fix For: webconsole-2.0.4 Attachments: FELIX-1884.patch, FELIX-1884a.png, FELIX-1884b.png -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
