[jira] [Assigned] (KARAF-5023) The serviceUrl property is changed unexpected when edit the rmiServerPort/rmiRegistryPort properties
[ https://issues.apache.org/jira/browse/KARAF-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-5023: --- Assignee: Jean-Baptiste Onofré > The serviceUrl property is changed unexpected when edit the > rmiServerPort/rmiRegistryPort properties > > > Key: KARAF-5023 > URL: https://issues.apache.org/jira/browse/KARAF-5023 > Project: Karaf > Issue Type: Bug > Components: karaf-config >Affects Versions: 4.1.0, 4.0.8 >Reporter: Xilai Dai >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.9, 4.1.1 > > > karaf@root()> config:edit --force org.apache.karaf.management > karaf@root()> config:property-set rmiRegistryPort 1100 > karaf@root()> config:property-set rmiServerPort 5 > karaf@root()> config:update > karaf@root()> Exception in thread "JMX Connector Thread > [service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-r > oot]" java.lang.RuntimeException: Could not start JMX connector server > at > org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:272) > Caused by: java.io.IOException: Cannot bind to URL > [rmi://127.0.0.1:1099/karaf-root]: javax.naming.CommunicationException > [Root exception is java.rmi.NoSuchObjectException: no such object in table] > at > javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:827) > at > javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:432) > at > org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:259) > Caused by: javax.naming.CommunicationException [Root exception is > java.rmi.NoSuchObjectException: no such object in tabl > e] > at > com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:161) > at > com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:228) > at javax.naming.InitialContext.bind(InitialContext.java:425) > at > javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:644) > at > javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427) > ... 1 more > Caused by: java.rmi.NoSuchObjectException: no such object in table > at > sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:276) > at > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:253) > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:379) > at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source) > at > com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:155) > ... 5 more > Looking into the etc/org.apache.karaf.management.cfg, the serviceUrl property > is changed to: > service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-root -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KARAF-5023) The serviceUrl property is changed unexpected when edit the rmiServerPort/rmiRegistryPort properties
[ https://issues.apache.org/jira/browse/KARAF-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5023: Fix Version/s: 4.1.1 4.0.9 > The serviceUrl property is changed unexpected when edit the > rmiServerPort/rmiRegistryPort properties > > > Key: KARAF-5023 > URL: https://issues.apache.org/jira/browse/KARAF-5023 > Project: Karaf > Issue Type: Bug > Components: karaf-config >Affects Versions: 4.1.0, 4.0.8 >Reporter: Xilai Dai >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.9, 4.1.1 > > > karaf@root()> config:edit --force org.apache.karaf.management > karaf@root()> config:property-set rmiRegistryPort 1100 > karaf@root()> config:property-set rmiServerPort 5 > karaf@root()> config:update > karaf@root()> Exception in thread "JMX Connector Thread > [service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-r > oot]" java.lang.RuntimeException: Could not start JMX connector server > at > org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:272) > Caused by: java.io.IOException: Cannot bind to URL > [rmi://127.0.0.1:1099/karaf-root]: javax.naming.CommunicationException > [Root exception is java.rmi.NoSuchObjectException: no such object in table] > at > javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:827) > at > javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:432) > at > org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:259) > Caused by: javax.naming.CommunicationException [Root exception is > java.rmi.NoSuchObjectException: no such object in tabl > e] > at > com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:161) > at > com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:228) > at javax.naming.InitialContext.bind(InitialContext.java:425) > at > javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:644) > at > javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427) > ... 1 more > Caused by: java.rmi.NoSuchObjectException: no such object in table > at > sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:276) > at > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:253) > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:379) > at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source) > at > com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:155) > ... 5 more > Looking into the etc/org.apache.karaf.management.cfg, the serviceUrl property > is changed to: > service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-root -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KARAF-5023) The serviceUrl property is changed unexpected when edit the rmiServerPort/rmiRegistryPort properties
Xilai Dai created KARAF-5023: Summary: The serviceUrl property is changed unexpected when edit the rmiServerPort/rmiRegistryPort properties Key: KARAF-5023 URL: https://issues.apache.org/jira/browse/KARAF-5023 Project: Karaf Issue Type: Bug Components: karaf-config Affects Versions: 4.0.8, 4.1.0 Reporter: Xilai Dai karaf@root()> config:edit --force org.apache.karaf.management karaf@root()> config:property-set rmiRegistryPort 1100 karaf@root()> config:property-set rmiServerPort 5 karaf@root()> config:update karaf@root()> Exception in thread "JMX Connector Thread [service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-r oot]" java.lang.RuntimeException: Could not start JMX connector server at org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:272) Caused by: java.io.IOException: Cannot bind to URL [rmi://127.0.0.1:1099/karaf-root]: javax.naming.CommunicationException [Root exception is java.rmi.NoSuchObjectException: no such object in table] at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:827) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:432) at org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:259) Caused by: javax.naming.CommunicationException [Root exception is java.rmi.NoSuchObjectException: no such object in tabl e] at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:161) at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:228) at javax.naming.InitialContext.bind(InitialContext.java:425) at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:644) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427) ... 1 more Caused by: java.rmi.NoSuchObjectException: no such object in table at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:276) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:253) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:379) at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source) at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:155) ... 5 more Looking into the etc/org.apache.karaf.management.cfg, the serviceUrl property is changed to: service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-root -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5021) Downgrade to Jetty 9.3.14
[ https://issues.apache.org/jira/browse/KARAF-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903984#comment-15903984 ] Achim Nierbeck commented on KARAF-5021: --- We need to upgrade to Pax-Web 6.0.3-SNAPSHOT to have this now ... > Downgrade to Jetty 9.3.14 > - > > Key: KARAF-5021 > URL: https://issues.apache.org/jira/browse/KARAF-5021 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.1 > > > Due to a bunch of breaking changes, and in order to smoothly work with CXF, > it would be better to downgrade to Jetty 9.3.14. > I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5021) Downgrade to Jetty 9.3.14
[ https://issues.apache.org/jira/browse/KARAF-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903434#comment-15903434 ] Daniel Kulp commented on KARAF-5021: Actually, its a bit different with CXF/camel/atmosphere as we call the constructor's directly, not via any service discovery. Thus, updating to 9.3.16 doesn't help. They didn't re-add the default constructors. They just removed the services file. Sticking with 9.3.14 is the only option at this point. > Downgrade to Jetty 9.3.14 > - > > Key: KARAF-5021 > URL: https://issues.apache.org/jira/browse/KARAF-5021 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.1 > > > Due to a bunch of breaking changes, and in order to smoothly work with CXF, > it would be better to downgrade to Jetty 9.3.14. > I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (KARAF-5021) Downgrade to Jetty 9.3.14
[ https://issues.apache.org/jira/browse/KARAF-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903425#comment-15903425 ] Achim Nierbeck edited comment on KARAF-5021 at 3/9/17 5:20 PM: --- Oh wait, we have an issue about that in Pax-Web with an upgrade to 9.3.16, that should also do Could you test if that also works for CXF? https://ops4j1.jira.com/browse/PAXWEB-1065 https://github.com/ops4j/org.ops4j.pax.web/commit/5d7650cb53516f945375a980aad780850c4404c7 that's already Pax-Web 6.0.3 we should check with that snapshot version was (Author: achim_nierbeck): Oh wait, we have an issue about that in Pax-Web with an upgrade to 9.3.16, that should also do Could you test if that also works for CXF? https://ops4j1.jira.com/browse/PAXWEB-1065 https://github.com/ops4j/org.ops4j.pax.web/commit/5d7650cb53516f945375a980aad780850c4404c7 > Downgrade to Jetty 9.3.14 > - > > Key: KARAF-5021 > URL: https://issues.apache.org/jira/browse/KARAF-5021 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.1 > > > Due to a bunch of breaking changes, and in order to smoothly work with CXF, > it would be better to downgrade to Jetty 9.3.14. > I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5021) Downgrade to Jetty 9.3.14
[ https://issues.apache.org/jira/browse/KARAF-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903363#comment-15903363 ] Achim Nierbeck commented on KARAF-5021: --- oh boy ... that's fubar ... so lets turn back the version ... need to change some other issues to re-opened than again :/ > Downgrade to Jetty 9.3.14 > - > > Key: KARAF-5021 > URL: https://issues.apache.org/jira/browse/KARAF-5021 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.1 > > > Due to a bunch of breaking changes, and in order to smoothly work with CXF, > it would be better to downgrade to Jetty 9.3.14. > I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5021) Downgrade to Jetty 9.3.14
[ https://issues.apache.org/jira/browse/KARAF-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903262#comment-15903262 ] Daniel Kulp commented on KARAF-5021: CXF's websocket support, camel-atmosphere-websocket, and atmosphere itself are all broken with Jetty 9.3.15 due to the same change that broke pax-web. CXF is now fixed on master for the direct jetty use cases (release needs to be made), but the atmosphere use cases are not fixed as the Atmosphere folks need to fix their code and release.See https://github.com/Atmosphere/atmosphere/issues/2242 At this point, sticking with 9.3.14 is about the only option to not break the various applications and such that are using atmosphere for their websocket stuff. (and CXF until 3.1.11 is released) > Downgrade to Jetty 9.3.14 > - > > Key: KARAF-5021 > URL: https://issues.apache.org/jira/browse/KARAF-5021 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.1 > > > Due to a bunch of breaking changes, and in order to smoothly work with CXF, > it would be better to downgrade to Jetty 9.3.14. > I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KARAF-5022) The repo defines an unnecessary dependency to pax web
Christian Schneider created KARAF-5022: -- Summary: The repo defines an unnecessary dependency to pax web Key: KARAF-5022 URL: https://issues.apache.org/jira/browse/KARAF-5022 Project: Karaf Issue Type: Bug Components: karaf-feature Affects Versions: 4.1.0 Reporter: Christian Schneider Assignee: Christian Schneider Fix For: 4.1.1 The spring repo defines a repo dependency to the standard repo and to pax web. As the standard repo depends on pax web anyway the spring repo does not need to also depend on it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5021) Downgrade to Jetty 9.3.14
[ https://issues.apache.org/jira/browse/KARAF-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903236#comment-15903236 ] Andrea Cosentino commented on KARAF-5021: - I wonder why in Jetty we have breaking changes in minor release (and it's not the first time). > Downgrade to Jetty 9.3.14 > - > > Key: KARAF-5021 > URL: https://issues.apache.org/jira/browse/KARAF-5021 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.1 > > > Due to a bunch of breaking changes, and in order to smoothly work with CXF, > it would be better to downgrade to Jetty 9.3.14. > I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (KARAF-5021) Downgrade to Jetty 9.3.14
[ https://issues.apache.org/jira/browse/KARAF-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903236#comment-15903236 ] Andrea Cosentino edited comment on KARAF-5021 at 3/9/17 3:41 PM: - I wonder why in Jetty we have breaking changes in minor releases (and it's not the first time). was (Author: ancosen): I wonder why in Jetty we have breaking changes in minor release (and it's not the first time). > Downgrade to Jetty 9.3.14 > - > > Key: KARAF-5021 > URL: https://issues.apache.org/jira/browse/KARAF-5021 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.1 > > > Due to a bunch of breaking changes, and in order to smoothly work with CXF, > it would be better to downgrade to Jetty 9.3.14. > I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5021) Downgrade to Jetty 9.3.14
[ https://issues.apache.org/jira/browse/KARAF-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903230#comment-15903230 ] Achim Nierbeck commented on KARAF-5021: --- Why is there a hard requirement for CXF on a certain Jetty version in the first place? That's creepy by itself already ... but if it has to ... I'm not going to block it ... but we should make sure we don't introduce some security issues by turning back to the old version. We loose functionality on the Websocket front ... people already are using ... :/ https://ops4j1.jira.com/browse/PAXWEB-1065 > Downgrade to Jetty 9.3.14 > - > > Key: KARAF-5021 > URL: https://issues.apache.org/jira/browse/KARAF-5021 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.1 > > > Due to a bunch of breaking changes, and in order to smoothly work with CXF, > it would be better to downgrade to Jetty 9.3.14. > I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5021) Downgrade to Jetty 9.3.14
[ https://issues.apache.org/jira/browse/KARAF-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903163#comment-15903163 ] Jean-Baptiste Onofré commented on KARAF-5021: - I know, but it means that CXF will use 9.3.14 and Karaf 9.3.15: it gonna be a mess and we will have potential a lot of outages. I just check with [~dkulp] and last CXF release won't update to 9.3.15. So, that's why I propose to align the version. Thoughts ? > Downgrade to Jetty 9.3.14 > - > > Key: KARAF-5021 > URL: https://issues.apache.org/jira/browse/KARAF-5021 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.1 > > > Due to a bunch of breaking changes, and in order to smoothly work with CXF, > it would be better to downgrade to Jetty 9.3.14. > I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5021) Downgrade to Jetty 9.3.14
[ https://issues.apache.org/jira/browse/KARAF-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903150#comment-15903150 ] Achim Nierbeck commented on KARAF-5021: --- we had a reason for bumping to that version ... > Downgrade to Jetty 9.3.14 > - > > Key: KARAF-5021 > URL: https://issues.apache.org/jira/browse/KARAF-5021 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.1 > > > Due to a bunch of breaking changes, and in order to smoothly work with CXF, > it would be better to downgrade to Jetty 9.3.14. > I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KARAF-5020) Unable to successfully start the simplest Camel CDI route in Karaf 4.1.0 or ServiceMix 7.0.0 (Karaf 4.0.8)
[
https://issues.apache.org/jira/browse/KARAF-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bob Blackard updated KARAF-5020:
Attachment: camel-osgi-cdi.zip
Maven project I'm trying to install in ServiceMix/Karaf. A full karaf.log is
included, as is a full bundle list and camel:context-list from Karaf Console.
> Unable to successfully start the simplest Camel CDI route in Karaf 4.1.0 or
> ServiceMix 7.0.0 (Karaf 4.0.8)
> --
>
> Key: KARAF-5020
> URL: https://issues.apache.org/jira/browse/KARAF-5020
> Project: Karaf
> Issue Type: Question
>Affects Versions: 4.1.0, 4.0.8
> Environment: Windows 10 and CentOS 7.3; Oracle Java 8
>Reporter: Bob Blackard
> Attachments: camel-osgi-cdi.zip
>
>
> I've been trying without success to build and deploy a simple route with
> Camel and CDI. I'm focused on deploying to ServiceMix 7.0.0, but have also
> tried this on a plane jane Karaf 4.1.0 and get precisely the same results.
> I built a very simple route based on the Camel CDI examples from both 2.16.4
> and 2.18.2. I'm excluding some of the testing stuff for now, just trying to
> get things to work when I deploy it in Karaf/ServiceMix.
> My RouteBuilder is:
> {code}
> public class DemoRouteBuilder extends RouteBuilder {
> Logger log = LoggerFactory.getLogger(DemoRouteBuilder.class);
> @Override
> public void configure() {
> log.info("Starting demo CDI route");
> from("timer://cdiTimer?period=5000")
> .routeId("com.omniprise.demo.cdi.route")
> .to("log:com.omniprise..demo.cdi.context")
> .to("mock:end");
> }
> }
> {code}
> I also have the requisite and content in my POM:
> {code}
> com.omniprise.demo.cdi.builder
> *
>
> osgi.extender; filter:="(osgi.extender=pax.cdi)",
> org.ops4j.pax.cdi.extension;
> filter:="(extension=camel-cdi-extension)"
>
> {code}
> Complete Java and POM code will be attached.
> Note that the camel-cdi feature will fail to install on ServiceMix 7.0.0 due
> to dependency conflicts:
> * ServiceMix 7.0.0 is using Camel 2.16.4
> * camel-cdi in 2.16.4 is looking for DeltaSpike [1.5.0,2.0)
> * camel-cdi in 2.16.4 is looking for pax-cdi 1.0.0.RC1
> * pax-cdi installs DeltaSpike 1.3.1
> * ... therefore a unresolved dependency error occurs if all that is done is:
> {code}
> feature:install pax-cdi pax-cdi-weld camel-cdi
> {code}
> Similar issues exist with newer versions of Camel as well when deploying into
> Karaf 4.1.0.
> Note, too, that even with the inclusion of updated DeltaSpike libraries,
> errors occur with pax-cdi 1.0.0.RC1, possibly due to an issue with Blueprint
> proxies.
> Therefore, these instructions install pax-cdi 1.0.0.RC2 and the latest
> DeltaSpike 1.7.2, along with camel-cdi (2.16.4 for ServiceMix 7.0.0 and
> 2.18.2 for Karaf 4.1.0).
> h2. To install and run in ServiceMix 7.0.0 (Karaf 4.0.8, Camel 2.16.4)
> Start ServiceMix, connect to Karaf Console and install:
> {code}
> feature:repo-add mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0.RC2/xml/features
> install mvn:org.apache.deltaspike.core/deltaspike-core-api/1.7.2
> install mvn:org.apache.deltaspike.core/deltaspike-core-impl/1.7.2
> feature:install pax-cdi/1.0.0.RC2
> feature:install pax-cdi-weld/1.0.0.RC2
> feature:install camel-cdi
> install -s mvn:com.omniprise.demo/camel-osgi-cdi/0.0.1-SNAPSHOT
> {code}
> h2. To install and run in a plain jane Karaf 4.x environment (Camel 2.18.2)
> Start Karaf, connect to Karaf Console and install:
> {code}
> feature:repo-add mvn:org.apache.camel.karaf/apache-camel/2.18.2/xml/features
> feature:repo-add mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0.RC2/xml/features
> install mvn:org.apache.deltaspike.core/deltaspike-core-api/1.7.2
> install mvn:org.apache.deltaspike.core/deltaspike-core-impl/1.7.2
> feature:install pax-cdi/1.0.0.RC2
> feature:install pax-cdi-weld/1.0.0.RC2
> feature:install camel/2.18.2
> feature:install camel-blueprint/2.18.2
> feature:install camel-cdi/2.18.2
> install -s mvn:com.omniprise.demo/camel-osgi-cdi/0.0.1-SNAPSHOT
> {code}
> In both cases, the packages are all installed and listed as running, but the
> Camel Context isn't started:
> {code}
> 70 | Active| 80 | 1.0.0.RC2 | OPS4J Pax CDI Bean Bundle API
> 71 | Active| 80 | 1.0.0.RC2 | OPS4J Pax CDI Extender for Bean
> Bundles
> 72 | Active| 80 | 1.0.0.RC2 | OPS4J Pax CDI Portable Extension for
> OSGi
> 73 | Active| 80 | 1.0.0.RC2 | OPS4J Pax CDI Service Provider
> Interface
> 74 | Active| 80 | 1.0.0.RC2 | OPS4J Pax CDI Weld Adapter
> ... content removed for brevity
> 83 | Active| 50 | 2.18.2 | camel-cdi
> ... content removed for brevity
> 92 |
[jira] [Created] (KARAF-5021) Downgrade to Jetty 9.3.14
Jean-Baptiste Onofré created KARAF-5021: --- Summary: Downgrade to Jetty 9.3.14 Key: KARAF-5021 URL: https://issues.apache.org/jira/browse/KARAF-5021 Project: Karaf Issue Type: Dependency upgrade Components: karaf-webcontainer Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.1.1 Due to a bunch of breaking changes, and in order to smoothly work with CXF, it would be better to downgrade to Jetty 9.3.14. I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KARAF-5020) Unable to successfully start the simplest Camel CDI route in Karaf 4.1.0 or ServiceMix 7.0.0 (Karaf 4.0.8)
[
https://issues.apache.org/jira/browse/KARAF-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bob Blackard updated KARAF-5020:
Description:
I've been trying without success to build and deploy a simple route with Camel
and CDI. I'm focused on deploying to ServiceMix 7.0.0, but have also tried this
on a plane jane Karaf 4.1.0 and get precisely the same results.
I built a very simple route based on the Camel CDI examples from both 2.16.4
and 2.18.2. I'm excluding some of the testing stuff for now, just trying to get
things to work when I deploy it in Karaf/ServiceMix.
My RouteBuilder is:
{code}
public class DemoRouteBuilder extends RouteBuilder {
Logger log = LoggerFactory.getLogger(DemoRouteBuilder.class);
@Override
public void configure() {
log.info("Starting demo CDI route");
from("timer://cdiTimer?period=5000")
.routeId("com.omniprise.demo.cdi.route")
.to("log:com.omniprise..demo.cdi.context")
.to("mock:end");
}
}
{code}
I also have the requisite and content in my POM:
{code}
com.omniprise.demo.cdi.builder
*
osgi.extender; filter:="(osgi.extender=pax.cdi)",
org.ops4j.pax.cdi.extension;
filter:="(extension=camel-cdi-extension)"
{code}
Complete Java and POM code will be attached.
Note that the camel-cdi feature will fail to install on ServiceMix 7.0.0 due to
dependency conflicts:
* ServiceMix 7.0.0 is using Camel 2.16.4
* camel-cdi in 2.16.4 is looking for DeltaSpike [1.5.0,2.0)
* camel-cdi in 2.16.4 is looking for pax-cdi 1.0.0.RC1
* pax-cdi installs DeltaSpike 1.3.1
* ... therefore a unresolved dependency error occurs if all that is done is:
{code}
feature:install pax-cdi pax-cdi-weld camel-cdi
{code}
Similar issues exist with newer versions of Camel as well when deploying into
Karaf 4.1.0.
Note, too, that even with the inclusion of updated DeltaSpike libraries, errors
occur with pax-cdi 1.0.0.RC1, possibly due to an issue with Blueprint proxies.
Therefore, these instructions install pax-cdi 1.0.0.RC2 and the latest
DeltaSpike 1.7.2, along with camel-cdi (2.16.4 for ServiceMix 7.0.0 and 2.18.2
for Karaf 4.1.0).
h2. To install and run in ServiceMix 7.0.0 (Karaf 4.0.8, Camel 2.16.4)
Start ServiceMix, connect to Karaf Console and install:
{code}
feature:repo-add mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0.RC2/xml/features
install mvn:org.apache.deltaspike.core/deltaspike-core-api/1.7.2
install mvn:org.apache.deltaspike.core/deltaspike-core-impl/1.7.2
feature:install pax-cdi/1.0.0.RC2
feature:install pax-cdi-weld/1.0.0.RC2
feature:install camel-cdi
install -s mvn:com.omniprise.demo/camel-osgi-cdi/0.0.1-SNAPSHOT
{code}
h2. To install and run in a plain jane Karaf 4.x environment (Camel 2.18.2)
Start Karaf, connect to Karaf Console and install:
{code}
feature:repo-add mvn:org.apache.camel.karaf/apache-camel/2.18.2/xml/features
feature:repo-add mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0.RC2/xml/features
install mvn:org.apache.deltaspike.core/deltaspike-core-api/1.7.2
install mvn:org.apache.deltaspike.core/deltaspike-core-impl/1.7.2
feature:install pax-cdi/1.0.0.RC2
feature:install pax-cdi-weld/1.0.0.RC2
feature:install camel/2.18.2
feature:install camel-blueprint/2.18.2
feature:install camel-cdi/2.18.2
install -s mvn:com.omniprise.demo/camel-osgi-cdi/0.0.1-SNAPSHOT
{code}
In both cases, the packages are all installed and listed as running, but the
Camel Context isn't started:
{code}
70 | Active| 80 | 1.0.0.RC2 | OPS4J Pax CDI Bean Bundle API
71 | Active| 80 | 1.0.0.RC2 | OPS4J Pax CDI Extender for Bean Bundles
72 | Active| 80 | 1.0.0.RC2 | OPS4J Pax CDI Portable Extension for
OSGi
73 | Active| 80 | 1.0.0.RC2 | OPS4J Pax CDI Service Provider Interface
74 | Active| 80 | 1.0.0.RC2 | OPS4J Pax CDI Weld Adapter
... content removed for brevity
83 | Active| 50 | 2.18.2 | camel-cdi
... content removed for brevity
92 | Active| 80 | 1.8.1 | OPS4J Pax Swissbox :: Tracker
93 | Active| 80 | 0.0.1.SNAPSHOT | Camel CDI OSGi Demo
addmin@root()> camel:context-list
addmin@root()>
{code}
The is only one error in the log associated with camel-cdi installing pax-cdi
1.0.0.RC1 even though pax-cdi 1.0.0.RC2 is already present, and therefore a CDI
provider is already registered. At the end of the log, it is clear that the CDI
binding is starting up, but there is no Context created, and the Route isn't
producing messages - there's nothing indicating there was a problem finding the
RouteBuilder or starting it:
{code}
2017-03-08T15:50:24,568 | INFO | pipe-feature:install camel-blueprint/2.18.2 |
CdiExtender | 71 - org.ops4j.pax.cdi.extender - 1.0.0.RC2
| creating CDI container for bean bundle camel-osgi-cdi [93] with extension
bundles [org.apache.camel.camel-cdi [83]]
2017-03-08T15:50:24,575
[jira] [Created] (KARAF-5020) Unable to successfully start the simplest Camel CDI route in Karaf 4.1.0 or ServiceMix 7.0.0 (Karaf 4.0.8)
Bob Blackard created KARAF-5020:
---
Summary: Unable to successfully start the simplest Camel CDI route
in Karaf 4.1.0 or ServiceMix 7.0.0 (Karaf 4.0.8)
Key: KARAF-5020
URL: https://issues.apache.org/jira/browse/KARAF-5020
Project: Karaf
Issue Type: Question
Affects Versions: 4.0.8, 4.1.0
Environment: Windows 10 and CentOS 7.3; Oracle Java 8
Reporter: Bob Blackard
I've been trying without success to build and deploy a simple route with Camel
and CDI. I'm focused on deploying to ServiceMix 7.0.0, but have also tried this
on a plane jane Karaf 4.1.0 and get precisely the same results.
I built a very simple route based on the Camel CDI examples from both 2.16.4
and 2.18.2. I'm excluding some of the testing stuff for now, just trying to get
things to work when I deploy it in Karaf/ServiceMix.
My RouteBuilder is:
{code}
public class DemoRouteBuilder extends RouteBuilder {
Logger log = LoggerFactory.getLogger(DemoRouteBuilder.class);
@Override
public void configure() {
log.info("Starting demo CDI route");
from("timer://cdiTimer?period=5000")
.routeId("com.omniprise.demo.cdi.route")
.to("log:com.omniprise..demo.cdi.context")
.to("mock:end");
}
}
{code}
I also have the requisite and content in my POM:
{code}
com.omniprise.demo.cdi.builder
*
osgi.extender; filter:="(osgi.extender=pax.cdi)",
org.ops4j.pax.cdi.extension;
filter:="(extension=camel-cdi-extension)"
{code}
Complete Java and POM code will be attached.
Note that the camel-cdi feature will fail to install on ServiceMix 7.0.0 due to
dependency conflicts:
* ServiceMix 7.0.0 is using Camel 2.16.4
* camel-cdi in 2.16.4 is looking for DeltaSpike [1.5.0,2.0)
* camel-cdi in 2.16.4 is looking for pax-cdi 1.0.0.RC1
* pax-cdi installs DeltaSpike 1.3.1
* ... therefore a unresolved dependency error occurs if all that is done is:
{code}
feature:install pax-cdi pax-cdi-weld camel-cdi
{code}
Similar issues exist with newer versions of Camel as well when deploying into
Karaf 4.1.0.
Note, too, that even with the inclusion of updated DeltaSpike libraries, errors
occur with pax-cdi 1.0.0.RC1, possibly due to an issue with Blueprint proxies.
Therefore, these instructions install pax-cdi 1.0.0.RC2 and the latest
DeltaSpike 1.7.2, along with camel-cdi (2.16.4 for ServiceMix 7.0.0 and 2.18.2
for Karaf 4.1.0).
h2. To install and run in ServiceMix 7.0.0 (Karaf 4.0.8, Camel 2.16.4)
Start ServiceMix, connect to Karaf Console and install:
{code}
feature:repo-add mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0.RC2/xml/features
install mvn:org.apache.deltaspike.core/deltaspike-core-api/1.7.2
install mvn:org.apache.deltaspike.core/deltaspike-core-impl/1.7.2
feature:install pax-cdi/1.0.0.RC2
feature:install pax-cdi-weld/1.0.0.RC2
feature:install camel-cdi
install -s mvn:com.omniprise.demo/camel-osgi-cdi/0.0.1-SNAPSHOT
{code}
h2. To install and run in a plain jane Karaf 4.x environment (Camel 2.18.1)
Start Karaf, connect to Karaf Console and install:
{code}
feature:repo-add mvn:org.apache.camel.karaf/apache-camel/2.18.2/xml/features
feature:repo-add mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0.RC2/xml/features
install mvn:org.apache.deltaspike.core/deltaspike-core-api/1.7.2
install mvn:org.apache.deltaspike.core/deltaspike-core-impl/1.7.2
feature:install pax-cdi/1.0.0.RC2
feature:install pax-cdi-weld/1.0.0.RC2
feature:install camel/2.18.2
feature:install camel-blueprint/2.18.2
feature:install camel-cdi/2.18.2
install -s mvn:com.omniprise.demo/camel-osgi-cdi/0.0.1-SNAPSHOT
{code}
In both cases, the packages are all installed and listed as running, but the
Camel Context isn't started:
{code}
70 | Active| 80 | 1.0.0.RC2 | OPS4J Pax CDI Bean Bundle API
71 | Active| 80 | 1.0.0.RC2 | OPS4J Pax CDI Extender for Bean Bundles
72 | Active| 80 | 1.0.0.RC2 | OPS4J Pax CDI Portable Extension for
OSGi
73 | Active| 80 | 1.0.0.RC2 | OPS4J Pax CDI Service Provider Interface
74 | Active| 80 | 1.0.0.RC2 | OPS4J Pax CDI Weld Adapter
... content removed for brevity
83 | Active| 50 | 2.18.2 | camel-cdi
... content removed for brevity
92 | Active| 80 | 1.8.1 | OPS4J Pax Swissbox :: Tracker
93 | Active| 80 | 0.0.1.SNAPSHOT | Camel CDI OSGi Demo
addmin@root()> camel:context-list
addmin@root()>
{code}
The is only one error in the log associated with camel-cdi installing pax-cdi
1.0.0.RC1 even though pax-cdi 1.0.0.RC2 is already present, and therefore a CDI
provider is already registered. At the end of the log, it is clear that the CDI
binding is starting up, but there is no Context created, and the Route isn't
producing messages - there's nothing indicating there was a problem finding the
RouteBuilder or starting it:
{code}
[jira] [Updated] (KARAF-4921) Expose more versions of slf4j api
[ https://issues.apache.org/jira/browse/KARAF-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4921: Fix Version/s: 4.1.1 4.0.9 > Expose more versions of slf4j api > - > > Key: KARAF-4921 > URL: https://issues.apache.org/jira/browse/KARAF-4921 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.0.8 >Reporter: Claus Ibsen >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.9, 4.1.1 > > > See CAMEL-10363 > This causes some 3rd party osgi bundles not be able to install and run in > karaf, because its shipped with too old slf4j api versions. > Please add newer versions of the slf4j api into karaf. See that CAMEL ticket > for more details. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-4921) Expose more versions of slf4j api
[ https://issues.apache.org/jira/browse/KARAF-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903092#comment-15903092 ] Jean-Baptiste Onofré commented on KARAF-4921: - Yes, thanks, gonna fix that for 4.1.1. > Expose more versions of slf4j api > - > > Key: KARAF-4921 > URL: https://issues.apache.org/jira/browse/KARAF-4921 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.0.8 >Reporter: Claus Ibsen >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.9, 4.1.1 > > > See CAMEL-10363 > This causes some 3rd party osgi bundles not be able to install and run in > karaf, because its shipped with too old slf4j api versions. > Please add newer versions of the slf4j api into karaf. See that CAMEL ticket > for more details. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-4921) Expose more versions of slf4j api
[ https://issues.apache.org/jira/browse/KARAF-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903087#comment-15903087 ] Claus Ibsen commented on KARAF-4921: This keeps being a problem even on latest 4.1.0 release. > Expose more versions of slf4j api > - > > Key: KARAF-4921 > URL: https://issues.apache.org/jira/browse/KARAF-4921 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.0.8 >Reporter: Claus Ibsen >Assignee: Jean-Baptiste Onofré > > See CAMEL-10363 > This causes some 3rd party osgi bundles not be able to install and run in > karaf, because its shipped with too old slf4j api versions. > Please add newer versions of the slf4j api into karaf. See that CAMEL ticket > for more details. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
