[jira] [Commented] (CAMEL-15288) Camel OSGi: Allow for defining the Bean resolution order
[ https://issues.apache.org/jira/browse/CAMEL-15288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541278#comment-17541278 ] Martin Lichtin commented on CAMEL-15288: The behavior in 3.14 has changed and this may no longer be relevant.. > Camel OSGi: Allow for defining the Bean resolution order > > > Key: CAMEL-15288 > URL: https://issues.apache.org/jira/browse/CAMEL-15288 > Project: Camel > Issue Type: Improvement > Components: camel-osgi >Affects Versions: 2.24.3 >Reporter: Martin Lichtin >Assignee: Jean-Baptiste Onofré >Priority: Major > > Currently OsgiDefaultCamelContext updates the registry and inserts > OsgiServiceRegistry as the _first_ registry into the list. > This can lead to undesirable behaviour, so an option to define the resolution > order will be helpful. > For example, it can be more appropriate to lookup local beans first, only go > to lookup an OSGi service if no local bean is found. Or it could be desired > to not lookup OSGi services at all. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-18083) camel-karaf - ConcurrentModificationException during Karaf blueprint CamelContext startup
[
https://issues.apache.org/jira/browse/CAMEL-18083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17534235#comment-17534235
]
Martin Lichtin commented on CAMEL-18083:
But then the Karaf Blueprint integration is broken
> camel-karaf - ConcurrentModificationException during Karaf blueprint
> CamelContext startup
> -
>
> Key: CAMEL-18083
> URL: https://issues.apache.org/jira/browse/CAMEL-18083
> Project: Camel
> Issue Type: Bug
> Components: camel-karaf, osgi
>Affects Versions: 3.14.3
>Reporter: Martin Lichtin
>Priority: Minor
>
> Infrequently seeing a ConcurrentModificationException
> {noformat}
> 2022-05-08T22:14:54,999 | ERROR | rint Event Dispatcher: 1 |
> BlueprintCamelContext | .blueprint.BlueprintCamelContext 190 |
> 188 - org.apache.camel.karaf.camel-blueprint - 3.14.3 | Error occurred during
> starting CamelContext: my.test.CamelContext
> java.util.ConcurrentModificationException: null
> at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:911)
> ~[?:1.8.0_321]
> at java.util.ArrayList$Itr.next(ArrayList.java:861) ~[?:1.8.0_321]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:789)
> ~[!/:3.14.3]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:764)
> ~[!/:3.14.3]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2862)
> ~[!/:3.14.3]
> at org.apache.camel.support.service.BaseService.init(BaseService.java:83)
> ~[!/:3.14.3]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2568)
> ~[!/:3.14.3]
> at
> org.apache.camel.support.service.BaseService.start(BaseService.java:111)
> ~[!/:3.14.3]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2587)
> ~[!/:3.14.3]
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:253)
> ~[!/:3.14.3]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.start(BlueprintCamelContext.java:241)
> ~[!/:3.14.3]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.maybeStart(BlueprintCamelContext.java:283)
> ~[!/:3.14.3]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.blueprintEvent(BlueprintCamelContext.java:188)
> [!/:3.14.3]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$3.call(BlueprintEventDispatcher.java:197)
> [!/:1.10.3]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$3.call(BlueprintEventDispatcher.java:195)
> [!/:1.10.3]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_321]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [?:1.8.0_321]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_321]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [?:1.8.0_321]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_321]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [?:1.8.0_321]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [?:1.8.0_321]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [?:1.8.0_321]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [?:1.8.0_321]
> at java.lang.Thread.run(Thread.java:750) [?:1.8.0_321] {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (CAMEL-18083) ConcurrentModificationException during Karaf blueprint CamelContext startup
Martin Lichtin created CAMEL-18083:
--
Summary: ConcurrentModificationException during Karaf blueprint
CamelContext startup
Key: CAMEL-18083
URL: https://issues.apache.org/jira/browse/CAMEL-18083
Project: Camel
Issue Type: Bug
Affects Versions: 3.14.3
Reporter: Martin Lichtin
Infrequently seeing a ConcurrentModificationException
{noformat}
2022-05-08T22:14:54,999 | ERROR | rint Event Dispatcher: 1 |
BlueprintCamelContext | .blueprint.BlueprintCamelContext 190 | 188
- org.apache.camel.karaf.camel-blueprint - 3.14.3 | Error occurred during
starting CamelContext: my.test.CamelContext
java.util.ConcurrentModificationException: null
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:911)
~[?:1.8.0_321]
at java.util.ArrayList$Itr.next(ArrayList.java:861) ~[?:1.8.0_321]
at
org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:789)
~[!/:3.14.3]
at
org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:764)
~[!/:3.14.3]
at
org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2862)
~[!/:3.14.3]
at org.apache.camel.support.service.BaseService.init(BaseService.java:83)
~[!/:3.14.3]
at
org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2568)
~[!/:3.14.3]
at org.apache.camel.support.service.BaseService.start(BaseService.java:111)
~[!/:3.14.3]
at
org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2587)
~[!/:3.14.3]
at
org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:253)
~[!/:3.14.3]
at
org.apache.camel.blueprint.BlueprintCamelContext.start(BlueprintCamelContext.java:241)
~[!/:3.14.3]
at
org.apache.camel.blueprint.BlueprintCamelContext.maybeStart(BlueprintCamelContext.java:283)
~[!/:3.14.3]
at
org.apache.camel.blueprint.BlueprintCamelContext.blueprintEvent(BlueprintCamelContext.java:188)
[!/:3.14.3]
at
org.apache.aries.blueprint.container.BlueprintEventDispatcher$3.call(BlueprintEventDispatcher.java:197)
[!/:1.10.3]
at
org.apache.aries.blueprint.container.BlueprintEventDispatcher$3.call(BlueprintEventDispatcher.java:195)
[!/:1.10.3]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_321]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[?:1.8.0_321]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_321]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[?:1.8.0_321]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_321]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
[?:1.8.0_321]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
[?:1.8.0_321]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[?:1.8.0_321]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[?:1.8.0_321]
at java.lang.Thread.run(Thread.java:750) [?:1.8.0_321] {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (CAMEL-16888) [camel-karaf] xml-specs-api features should be updated to use woodstox.core and stax2-api
[
https://issues.apache.org/jira/browse/CAMEL-16888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531382#comment-17531382
]
Martin Lichtin commented on CAMEL-16888:
Point 3 would be good to fix as it causes
{noformat}
Caused by: java.lang.ClassNotFoundException: com.sun.istack.FinalArrayList not
found by org.apache.servicemix.bundles.jaxb-runtime [223]
at
org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1639)
~[?:?]
at
org.apache.felix.framework.BundleWiringImpl.access$200(BundleWiringImpl.java:80)
~[?:?]
at
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2053)
~[?:?]
at java.lang.ClassLoader.loadClass(ClassLoader.java:351) ~[?:1.8.0_321]
{noformat}
> [camel-karaf] xml-specs-api features should be updated to use woodstox.core
> and stax2-api
> -
>
> Key: CAMEL-16888
> URL: https://issues.apache.org/jira/browse/CAMEL-16888
> Project: Camel
> Issue Type: Improvement
> Components: karaf
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 3.x
>
>
> {{xml-specs-api}} should be updated with:
> # use dependency=true on stax2-api and update to stax2-api 4.2 (aligned with
> other camel features)
> # use woodstox-core instead of woodstox-core-asl and update to woodstox 6.2.4
> # update jaxb-runtime bundle to 2.3.2_1 to match CXF one
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (CAMEL-15288) Camel OSGi: Allow for defining the Bean resolution order
[ https://issues.apache.org/jira/browse/CAMEL-15288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527436#comment-17527436 ] Martin Lichtin commented on CAMEL-15288: Can this one be considered at some point? It is a performance hit to constantly lookup OSGi services. > Camel OSGi: Allow for defining the Bean resolution order > > > Key: CAMEL-15288 > URL: https://issues.apache.org/jira/browse/CAMEL-15288 > Project: Camel > Issue Type: Improvement > Components: camel-osgi >Affects Versions: 2.24.3 >Reporter: Martin Lichtin >Assignee: Jean-Baptiste Onofré >Priority: Major > > Currently OsgiDefaultCamelContext updates the registry and inserts > OsgiServiceRegistry as the _first_ registry into the list. > This can lead to undesirable behaviour, so an option to define the resolution > order will be helpful. > For example, it can be more appropriate to lookup local beans first, only go > to lookup an OSGi service if no local bean is found. Or it could be desired > to not lookup OSGi services at all. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-13072) In DefaultUnitOfWork:popRouteContext() avoid exception thrown
Martin Lichtin created CAMEL-13072:
--
Summary: In DefaultUnitOfWork:popRouteContext() avoid exception
thrown
Key: CAMEL-13072
URL: https://issues.apache.org/jira/browse/CAMEL-13072
Project: Camel
Issue Type: Improvement
Affects Versions: 2.21.4
Reporter: Martin Lichtin
Instead of
{noformat}
public RouteContext popRouteContext() {
try {
return routeContextStack.pop();
} catch (NoSuchElementException e) {
// ignore and return null
}
return null;
}
{noformat}
can just write
{noformat}
public RouteContext popRouteContext() {
return routeContextStack.pollFirst();
}
{noformat}
I understand the cost of an exception is low, but still it doesn't look nice to
see zillions of exceptions in a flight recording caused by Camel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12308) Upgrade to CXF 3.2.2
[ https://issues.apache.org/jira/browse/CAMEL-12308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16576387#comment-16576387 ] Martin Lichtin commented on CAMEL-12308: That's true of course. Staying with Karaf 4.0.x we cannot go beyond 2.20.x (2.21 requires a newer Jetty that is only in newer Karafs). Guess we're stuck with Camel 2.19 then for that Karaf version. > Upgrade to CXF 3.2.2 > > > Key: CAMEL-12308 > URL: https://issues.apache.org/jira/browse/CAMEL-12308 > Project: Camel > Issue Type: Improvement > Components: camel-cxf >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 2.21.0 > > > There is a newer version and it also fixes a problem on JDK9 in the > camel-itests -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-12308) Upgrade to CXF 3.2.2
[
https://issues.apache.org/jira/browse/CAMEL-12308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574985#comment-16574985
]
Martin Lichtin edited comment on CAMEL-12308 at 8/9/18 9:09 PM:
Can this upgrade be back-ported to 2.20?
Camel 2.20.4 is still on CXF 3.2.1 and this CXF version contains a strange
version range that confuses Karaf assembly.
{noformat}
apache-cxf-3.2.1-features.xml:
mvn:org.ops4j.pax.cdi/pax-cdi-features/[1.0.0.RC1,2)/xml/features
vs
apache-cxf-3.2.2-features.xml:
mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0.RC2/xml/features
{noformat}
CXF 3.2.2 has this fixed. CXF-7567
was (Author: lichtin):
Can this upgrade be back-ported to 2.20?
Camel 2.20.4 is still on CXF 3.2.1 and this CXF version contains a strange
version range that confuses Karaf assembly.
{noformat}
apache-cxf-3.2.1-features.xml:
mvn:org.ops4j.pax.cdi/pax-cdi-features/[1.0.0.RC1,2)/xml/features
vs
apache-cxf-3.2.2-features.xml:
mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0.RC2/xml/features
{noformat}
CXF 3.2.2 has this fixed.
> Upgrade to CXF 3.2.2
>
>
> Key: CAMEL-12308
> URL: https://issues.apache.org/jira/browse/CAMEL-12308
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 2.21.0
>
>
> There is a newer version and it also fixes a problem on JDK9 in the
> camel-itests
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12308) Upgrade to CXF 3.2.2
[
https://issues.apache.org/jira/browse/CAMEL-12308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574985#comment-16574985
]
Martin Lichtin commented on CAMEL-12308:
Can this upgrade be back-ported to 2.20?
Camel 2.20.4 is still on CXF 3.2.1 and this CXF version contains a strange
version range that confuses Karaf assembly.
{noformat}
apache-cxf-3.2.1-features.xml:
mvn:org.ops4j.pax.cdi/pax-cdi-features/[1.0.0.RC1,2)/xml/features
vs
apache-cxf-3.2.2-features.xml:
mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0.RC2/xml/features
{noformat}
CXF 3.2.2 has this fixed.
> Upgrade to CXF 3.2.2
>
>
> Key: CAMEL-12308
> URL: https://issues.apache.org/jira/browse/CAMEL-12308
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 2.21.0
>
>
> There is a newer version and it also fixes a problem on JDK9 in the
> camel-itests
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-9856) RestSwaggerProcessor fails with "Provider org.apache.xalan.processor.TransformerFactoryImpl not found"
[
https://issues.apache.org/jira/browse/CAMEL-9856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182279#comment-16182279
]
Martin Lichtin commented on CAMEL-9856:
---
2.18.5 exhibits the same issue.
However what solves it, is to (re-) add the following system properties to
Karaf:
{noformat}
javax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
javax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl
{noformat}
Earlier releases of Karaf had these settings, but for some reason they were
removed.
> RestSwaggerProcessor fails with "Provider
> org.apache.xalan.processor.TransformerFactoryImpl not found"
> --
>
> Key: CAMEL-9856
> URL: https://issues.apache.org/jira/browse/CAMEL-9856
> Project: Camel
> Issue Type: Bug
> Components: camel-core, karaf
>Affects Versions: 2.16.3
> Environment: Karaf 4.0.3, Java 8
>Reporter: Ralf Steppacher
>Assignee: Claus Ibsen
> Fix For: 2.18.0
>
>
> When I try to query the Swagger API output for my REST routes, which are
> defined in a Blueprint context with the XML DSL, any request to a path that I
> think should return API information yields an empty response body (status
> 200) on the client and this error on the server. The error is raised by
> {{RestSwaggerSupport::getRestDefinitions(String)}} (line 147).
> {noformat}
> 2016-04-11 16:45:29,136 | WARN | qtp215489304-167 | RestSwaggerProcessor
> | 78 - org.apache.camel.camel-swagger-java - 2.16.3 | | Error
> rendering Swagger API due RuntimeException thrown in RequiredModelMBean while
> trying to invoke operation dumpRestsAsXml
> javax.management.MBeanException: RuntimeException thrown in
> RequiredModelMBean while trying to invoke operation dumpRestsAsXml
> at
> javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1285)[:1.8.0_77]
> at
> javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:1085)[:1.8.0_77]
> at
> org.apache.camel.management.MixinRequiredModelMBean.invoke(MixinRequiredModelMBean.java:70)[71:org.apache.camel.camel-core:2.16.3]
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)[:1.8.0_77]
> at
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)[:1.8.0_77]
> at
> org.apache.camel.swagger.RestSwaggerSupport.getRestDefinitions(RestSwaggerSupport.java:147)[78:org.apache.camel.camel-swagger-java:2.16.3]
> at
> org.apache.camel.swagger.RestSwaggerSupport.renderResourceListing(RestSwaggerSupport.java:198)[78:org.apache.camel.camel-swagger-java:2.16.3]
> at
> org.apache.camel.swagger.RestSwaggerProcessor.process(RestSwaggerProcessor.java:95)[78:org.apache.camel.camel-swagger-java:2.16.3]
> at
> org.apache.camel.component.rest.RestApiProducer.process(RestApiProducer.java:36)[71:org.apache.camel.camel-core:2.16.3]
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[71:org.apache.camel.camel-core:2.16.3]
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145)[71:org.apache.camel.camel-core:2.16.3]
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)[71:org.apache.camel.camel-core:2.16.3]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:460)[71:org.apache.camel.camel-core:2.16.3]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)[71:org.apache.camel.camel-core:2.16.3]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)[71:org.apache.camel.camel-core:2.16.3]
> at
> org.apache.camel.component.jetty.CamelContinuationServlet.service(CamelContinuationServlet.java:191)[74:org.apache.camel.camel-jetty-common:2.16.3]
> at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790)[63:javax.servlet-api:3.1.0]
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808)[122:org.eclipse.jetty.servlet:9.2.10.v20150310]
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)[122:org.eclipse.jetty.servlet:9.2.10.v20150310]
> at
> org.eclipse.jetty.servlets.MultiPartFilter.doFilter(MultiPartFilter.java:146)[123:org.eclipse.jetty.servlets:9.2.10.v20150310]
> at
> org.apache.camel.component.jetty.CamelFilterWrapper.doFilter(CamelFilterWrapper.java:43)[74:org.apache.camel.camel-jetty-common:2.16.3]
> at
>
[jira] [Commented] (CAMEL-9856) RestSwaggerProcessor fails with "Provider org.apache.xalan.processor.TransformerFactoryImpl not found"
[
https://issues.apache.org/jira/browse/CAMEL-9856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177972#comment-16177972
]
Martin Lichtin commented on CAMEL-9856:
---
Running into the same issue with Camel 2.18.4.
The problem appears as soon as one documents a query param.
E.g. this works:
{noformat}
{noformat}
and one can retrieve the Swagger JSON.
But when adding a the Swagger interface does no longer work:
{noformat}
{noformat}
The full exception is:
{noformat}
2017-09-23 22:38:48,911 | WARN | qtp1862576107-269|
RestSwaggerProcessor | mel.swagger.RestSwaggerProcessor 122 | 240
- org.apache.camel.camel-swagger-java - 2.18.4 | Error rendering Swagger API
due Error occurred in RequiredModelMBean while trying to invoke operation
dumpRestsAsXml
javax.management.RuntimeErrorException: Error occurred in RequiredModelMBean
while trying to invoke operation dumpRestsAsXml
at
javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1289)[:1.8.0_141]
at
javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:1085)[:1.8.0_141]
at
org.apache.camel.management.MixinRequiredModelMBean.invoke(MixinRequiredModelMBean.java:70)[233:org.apache.camel.camel-core:2.18.4]
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)[:1.8.0_141]
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)[:1.8.0_141]
at
org.apache.camel.swagger.RestSwaggerSupport.getRestDefinitions(RestSwaggerSupport.java:153)[240:org.apache.camel.camel-swagger-java:2.18.4]
at
org.apache.camel.swagger.RestSwaggerSupport.renderResourceListing(RestSwaggerSupport.java:202)[240:org.apache.camel.camel-swagger-java:2.18.4]
at
org.apache.camel.swagger.RestSwaggerProcessor.process(RestSwaggerProcessor.java:118)[240:org.apache.camel.camel-swagger-java:2.18.4]
at
org.apache.camel.component.rest.RestApiProducer.process(RestApiProducer.java:36)[233:org.apache.camel.camel-core:2.18.4]
at
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[233:org.apache.camel.camel-core:2.18.4]
at
org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145)[233:org.apache.camel.camel-core:2.18.4]
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)[233:org.apache.camel.camel-core:2.18.4]
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)[233:org.apache.camel.camel-core:2.18.4]
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)[233:org.apache.camel.camel-core:2.18.4]
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)[233:org.apache.camel.camel-core:2.18.4]
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:97)[233:org.apache.camel.camel-core:2.18.4]
at
org.apache.camel.http.common.CamelServlet.doService(CamelServlet.java:195)[234:org.apache.camel.camel-http-common:2.18.4]
at
org.apache.camel.http.common.CamelServlet.service(CamelServlet.java:74)[234:org.apache.camel.camel-http-common:2.18.4]
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:790)[220:javax.servlet-api:3.1.0]
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)[330:org.eclipse.jetty.servlet:9.2.19.v20160908]
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)[330:org.eclipse.jetty.servlet:9.2.19.v20160908]
at
org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71)[372:org.ops4j.pax.web.pax-web-jetty:4.3.0]
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)[329:org.eclipse.jetty.server:9.2.19.v20160908]
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)[328:org.eclipse.jetty.security:9.2.19.v20160908]
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)[329:org.eclipse.jetty.server:9.2.19.v20160908]
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)[329:org.eclipse.jetty.server:9.2.19.v20160908]
at
org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:287)[372:org.ops4j.pax.web.pax-web-jetty:4.3.0]
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)[330:org.eclipse.jetty.servlet:9.2.19.v20160908]
at
[jira] [Commented] (CAMEL-10913) CORS header Access-Control-Allow-Credentials not managed correctly
[
https://issues.apache.org/jira/browse/CAMEL-10913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170537#comment-16170537
]
Martin Lichtin commented on CAMEL-10913:
Hi Nicola, would it be possible to make this change available for 2.18.x?
I seem to also run into this issue and unfortunately cannot upgrade to 2.19.
> CORS header Access-Control-Allow-Credentials not managed correctly
> --
>
> Key: CAMEL-10913
> URL: https://issues.apache.org/jira/browse/CAMEL-10913
> Project: Camel
> Issue Type: Bug
> Components: camel-http-common
>Reporter: Nicola Ferraro
>Assignee: Nicola Ferraro
> Fix For: 2.19.0
>
>
> When a browser uses the "withCredentials" flag (not visible in HTTP request
> headers), it accepts the response only if the
> "Access-Control-Allow-Credentials" header returned by the server is set to
> "true".
> That header is not part of Camel standard cors headers, but it can be set in
> the route. The problem is that when "Access-Control-Allow-Credentials" is set
> to "true", the "Access-Control-Allow-Origin" header cannot be set to "*",
> which is our default (https://www.w3.org/TR/cors/ - section 6.1, point 3).
> Setting a value for the "Access-Control-Allow-Origin" header equals to the
> "Origin" header of the request makes the trick, but this must be set
> per-route, and *CORS must be disabled*.
> Eg.
> {code}
> // do not enable cors
> rest().get("/hello")
> .route()
> .to("direct:handle")
> .setHeader("Access-Control-Allow-Credentials", constant("true"))
> .setHeader("Access-Control-Allow-Origin", header("Origin"));
> {code}
> Otherwise the only option is setting a fixed allowed origin if you know it in
> advance.
> I wonder if we should add e.g. a ".corsAllowCredentials(boolean)"
> configuration to handle this situation correctly, or another flag to reflect
> the origin instead of returning "*".
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (CAMEL-11783) Updates to http://camel.apache.org/rest-dsl.html
Martin Lichtin created CAMEL-11783: -- Summary: Updates to http://camel.apache.org/rest-dsl.html Key: CAMEL-11783 URL: https://issues.apache.org/jira/browse/CAMEL-11783 Project: Camel Issue Type: Improvement Reporter: Martin Lichtin The page http://camel.apache.org/rest-dsl.html is a bit out of date. Specifically, "corsHeaderProperty" is now called "corsHeaders". Also there's a new "apiProperty" not yet documented. In addition it'd be good to clarify that for PUT and POST, the request body will by default be also the HTTP response. It's sort of normal with Camel, but not what one would expect when using the Rest DSL. Might want to show an example of how to empty the body for a . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11408) Camel Servlet Web Page http://camel.apache.org/servlet.html
Martin Lichtin created CAMEL-11408: -- Summary: Camel Servlet Web Page http://camel.apache.org/servlet.html Key: CAMEL-11408 URL: https://issues.apache.org/jira/browse/CAMEL-11408 Project: Camel Issue Type: Task Reporter: Martin Lichtin On page http://camel.apache.org/servlet.html the section "Sample when using OSGi" is missing the code snippets. Can these examples be put back in and, if possible, be verified? Thanks much! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-9695) OSGi - During shutdown, Camel cannot unregister error handler
[
https://issues.apache.org/jira/browse/CAMEL-9695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351199#comment-15351199
]
Martin Lichtin commented on CAMEL-9695:
---
Confirmed it no longer appears using 2.16.3.
> OSGi - During shutdown, Camel cannot unregister error handler
> -
>
> Key: CAMEL-9695
> URL: https://issues.apache.org/jira/browse/CAMEL-9695
> Project: Camel
> Issue Type: Bug
> Components: karaf
>Affects Versions: 2.15.5
> Environment: Karaf 3.0.3
>Reporter: Martin Lichtin
>Assignee: Claus Ibsen
>Priority: Minor
>
> According to http://camel.apache.org/redeliverypolicy.html
> my camel context is like
> {code:xml}
> http://camel.apache.org/schema/blueprint;
> xsi:schemaLocation="http://camel.apache.org/schema/blueprint
> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd;
> id="myIdxt" messageHistory="false">
>redeliveryPolicyRef="myRedeliveryPolicy" />
>
>
>
>
> etc.etc.
>
>
> {code}
> During shutdown, the following is output:
> {noformat}
> 2016-03-10 12:33:44,649 | WARN | FelixStartLevel |
> faultManagementLifecycleStrategy | faultManagementLifecycleStrategy 640 |
> 130 - org.apache.camel.camel-core - 2.15.5 | Could not unregister error
> handler: org.apache.camel.management.mbean.ManagedErrorHandler@72c1
> e7c3 as ErrorHandler MBean.
> org.apache.camel.NoSuchBeanException: No bean could be found in the registry
> for: myErrorHandler of type: org.apache.camel.builder.ErrorHandlerBuilder
> at
> org.apache.camel.util.CamelContextHelper.mandatoryLookup(CamelContextHelper.java:159)
> at
> org.apache.camel.impl.DefaultRouteContext.mandatoryLookup(DefaultRouteContext.java:151)
> at
> org.apache.camel.builder.ErrorHandlerBuilderRef.lookupErrorHandlerBuilder(ErrorHandlerBuilderRef.java:137)
> at
> org.apache.camel.management.DefaultManagementNamingStrategy.getObjectNameForErrorHandler(DefaultManagementNamingStrategy.java:154)
> at
> org.apache.camel.management.ManagedManagementStrategy.getManagedObjectName(ManagedManagementStrategy.java:104)
> at
> org.apache.camel.management.ManagedManagementStrategy.unmanageObject(ManagedManagementStrategy.java:143)
> at
> org.apache.camel.management.DefaultManagementLifecycleStrategy.unmanageObject(DefaultManagementLifecycleStrategy.java:839)
> at
> org.apache.camel.management.DefaultManagementLifecycleStrategy.onErrorHandlerRemove(DefaultManagementLifecycleStrategy.java:638)
> at
> org.apache.camel.impl.RouteService.stopChildService(RouteService.java:351)
> at org.apache.camel.impl.RouteService.doStop(RouteService.java:237)
> at
> org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:77)
> at
> org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:101)
> at
> org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:141)
> at
> org.apache.camel.util.ServiceHelper.stopAndShutdownService(ServiceHelper.java:204)
> at
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2843)
> at
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2868)
> at
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2856)
> at
> org.apache.camel.impl.DefaultCamelContext.doStop(DefaultCamelContext.java:2691)
> at
> org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
> at
> org.apache.camel.blueprint.BlueprintCamelContext.destroy(BlueprintCamelContext.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)[:1.8.0_66]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_66]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_66]
> at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_66]
> at
> org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:297)[15:org.apache.aries.blueprint.core:1.4.2]
> at
> org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:958)[15:org.apache.aries.blueprint.core:1.4.2]
> etc..
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-9695) OSGi - During shutdown, Camel cannot unregister error handler
[
https://issues.apache.org/jira/browse/CAMEL-9695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209998#comment-15209998
]
Martin Lichtin commented on CAMEL-9695:
---
Thanks for the info. We will be ugprading Camel as soon as possible.
> OSGi - During shutdown, Camel cannot unregister error handler
> -
>
> Key: CAMEL-9695
> URL: https://issues.apache.org/jira/browse/CAMEL-9695
> Project: Camel
> Issue Type: Bug
> Components: karaf
>Affects Versions: 2.15.5
> Environment: Karaf 3.0.3
>Reporter: Martin Lichtin
>Priority: Minor
>
> According to http://camel.apache.org/redeliverypolicy.html
> my camel context is like
> {code:xml}
> http://camel.apache.org/schema/blueprint;
> xsi:schemaLocation="http://camel.apache.org/schema/blueprint
> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd;
> id="myIdxt" messageHistory="false">
>redeliveryPolicyRef="myRedeliveryPolicy" />
>
>
>
>
> etc.etc.
>
>
> {code}
> During shutdown, the following is output:
> {noformat}
> 2016-03-10 12:33:44,649 | WARN | FelixStartLevel |
> faultManagementLifecycleStrategy | faultManagementLifecycleStrategy 640 |
> 130 - org.apache.camel.camel-core - 2.15.5 | Could not unregister error
> handler: org.apache.camel.management.mbean.ManagedErrorHandler@72c1
> e7c3 as ErrorHandler MBean.
> org.apache.camel.NoSuchBeanException: No bean could be found in the registry
> for: myErrorHandler of type: org.apache.camel.builder.ErrorHandlerBuilder
> at
> org.apache.camel.util.CamelContextHelper.mandatoryLookup(CamelContextHelper.java:159)
> at
> org.apache.camel.impl.DefaultRouteContext.mandatoryLookup(DefaultRouteContext.java:151)
> at
> org.apache.camel.builder.ErrorHandlerBuilderRef.lookupErrorHandlerBuilder(ErrorHandlerBuilderRef.java:137)
> at
> org.apache.camel.management.DefaultManagementNamingStrategy.getObjectNameForErrorHandler(DefaultManagementNamingStrategy.java:154)
> at
> org.apache.camel.management.ManagedManagementStrategy.getManagedObjectName(ManagedManagementStrategy.java:104)
> at
> org.apache.camel.management.ManagedManagementStrategy.unmanageObject(ManagedManagementStrategy.java:143)
> at
> org.apache.camel.management.DefaultManagementLifecycleStrategy.unmanageObject(DefaultManagementLifecycleStrategy.java:839)
> at
> org.apache.camel.management.DefaultManagementLifecycleStrategy.onErrorHandlerRemove(DefaultManagementLifecycleStrategy.java:638)
> at
> org.apache.camel.impl.RouteService.stopChildService(RouteService.java:351)
> at org.apache.camel.impl.RouteService.doStop(RouteService.java:237)
> at
> org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:77)
> at
> org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:101)
> at
> org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:141)
> at
> org.apache.camel.util.ServiceHelper.stopAndShutdownService(ServiceHelper.java:204)
> at
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2843)
> at
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2868)
> at
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2856)
> at
> org.apache.camel.impl.DefaultCamelContext.doStop(DefaultCamelContext.java:2691)
> at
> org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
> at
> org.apache.camel.blueprint.BlueprintCamelContext.destroy(BlueprintCamelContext.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)[:1.8.0_66]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_66]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_66]
> at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_66]
> at
> org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:297)[15:org.apache.aries.blueprint.core:1.4.2]
> at
> org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:958)[15:org.apache.aries.blueprint.core:1.4.2]
> etc..
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-9695) OSGi - During shutdown, Camel cannot unregister error handler
[
https://issues.apache.org/jira/browse/CAMEL-9695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15193382#comment-15193382
]
Martin Lichtin commented on CAMEL-9695:
---
I'm trying to upgrade to 2.16.2, but something with Camel http servlet support
seems to have changed and my servlets which used to be accessible at
localhost:8181/camel/services/MYSERVLET no longer work... sorry.
> OSGi - During shutdown, Camel cannot unregister error handler
> -
>
> Key: CAMEL-9695
> URL: https://issues.apache.org/jira/browse/CAMEL-9695
> Project: Camel
> Issue Type: Bug
> Components: karaf
>Affects Versions: 2.15.5
> Environment: Karaf 3.0.3
>Reporter: Martin Lichtin
>Priority: Minor
>
> According to http://camel.apache.org/redeliverypolicy.html
> my camel context is like
> {code:xml}
> http://camel.apache.org/schema/blueprint;
> xsi:schemaLocation="http://camel.apache.org/schema/blueprint
> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd;
> id="myIdxt" messageHistory="false">
>redeliveryPolicyRef="myRedeliveryPolicy" />
>
>
>
>
> etc.etc.
>
>
> {code}
> During shutdown, the following is output:
> {noformat}
> 2016-03-10 12:33:44,649 | WARN | FelixStartLevel |
> faultManagementLifecycleStrategy | faultManagementLifecycleStrategy 640 |
> 130 - org.apache.camel.camel-core - 2.15.5 | Could not unregister error
> handler: org.apache.camel.management.mbean.ManagedErrorHandler@72c1
> e7c3 as ErrorHandler MBean.
> org.apache.camel.NoSuchBeanException: No bean could be found in the registry
> for: myErrorHandler of type: org.apache.camel.builder.ErrorHandlerBuilder
> at
> org.apache.camel.util.CamelContextHelper.mandatoryLookup(CamelContextHelper.java:159)
> at
> org.apache.camel.impl.DefaultRouteContext.mandatoryLookup(DefaultRouteContext.java:151)
> at
> org.apache.camel.builder.ErrorHandlerBuilderRef.lookupErrorHandlerBuilder(ErrorHandlerBuilderRef.java:137)
> at
> org.apache.camel.management.DefaultManagementNamingStrategy.getObjectNameForErrorHandler(DefaultManagementNamingStrategy.java:154)
> at
> org.apache.camel.management.ManagedManagementStrategy.getManagedObjectName(ManagedManagementStrategy.java:104)
> at
> org.apache.camel.management.ManagedManagementStrategy.unmanageObject(ManagedManagementStrategy.java:143)
> at
> org.apache.camel.management.DefaultManagementLifecycleStrategy.unmanageObject(DefaultManagementLifecycleStrategy.java:839)
> at
> org.apache.camel.management.DefaultManagementLifecycleStrategy.onErrorHandlerRemove(DefaultManagementLifecycleStrategy.java:638)
> at
> org.apache.camel.impl.RouteService.stopChildService(RouteService.java:351)
> at org.apache.camel.impl.RouteService.doStop(RouteService.java:237)
> at
> org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:77)
> at
> org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:101)
> at
> org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:141)
> at
> org.apache.camel.util.ServiceHelper.stopAndShutdownService(ServiceHelper.java:204)
> at
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2843)
> at
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2868)
> at
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2856)
> at
> org.apache.camel.impl.DefaultCamelContext.doStop(DefaultCamelContext.java:2691)
> at
> org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
> at
> org.apache.camel.blueprint.BlueprintCamelContext.destroy(BlueprintCamelContext.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)[:1.8.0_66]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_66]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_66]
> at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_66]
> at
> org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:297)[15:org.apache.aries.blueprint.core:1.4.2]
> at
> org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:958)[15:org.apache.aries.blueprint.core:1.4.2]
> etc..
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-9695) OSGi - During shutdown, Camel cannot unregister error handler
[
https://issues.apache.org/jira/browse/CAMEL-9695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Lichtin updated CAMEL-9695:
--
Environment: Karaf 3.0.3
> OSGi - During shutdown, Camel cannot unregister error handler
> -
>
> Key: CAMEL-9695
> URL: https://issues.apache.org/jira/browse/CAMEL-9695
> Project: Camel
> Issue Type: Bug
> Components: karaf
>Affects Versions: 2.15.5
> Environment: Karaf 3.0.3
>Reporter: Martin Lichtin
>Priority: Minor
>
> According to http://camel.apache.org/redeliverypolicy.html
> my camel context is like
> {code:xml}
> http://camel.apache.org/schema/blueprint;
> xsi:schemaLocation="http://camel.apache.org/schema/blueprint
> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd;
> id="myIdxt" messageHistory="false">
>redeliveryPolicyRef="myRedeliveryPolicy" />
>
>
>
>
> etc.etc.
>
>
> {code}
> During shutdown, the following is output:
> {noformat}
> 2016-03-10 12:33:44,649 | WARN | FelixStartLevel |
> faultManagementLifecycleStrategy | faultManagementLifecycleStrategy 640 |
> 130 - org.apache.camel.camel-core - 2.15.5 | Could not unregister error
> handler: org.apache.camel.management.mbean.ManagedErrorHandler@72c1
> e7c3 as ErrorHandler MBean.
> org.apache.camel.NoSuchBeanException: No bean could be found in the registry
> for: myErrorHandler of type: org.apache.camel.builder.ErrorHandlerBuilder
> at
> org.apache.camel.util.CamelContextHelper.mandatoryLookup(CamelContextHelper.java:159)
> at
> org.apache.camel.impl.DefaultRouteContext.mandatoryLookup(DefaultRouteContext.java:151)
> at
> org.apache.camel.builder.ErrorHandlerBuilderRef.lookupErrorHandlerBuilder(ErrorHandlerBuilderRef.java:137)
> at
> org.apache.camel.management.DefaultManagementNamingStrategy.getObjectNameForErrorHandler(DefaultManagementNamingStrategy.java:154)
> at
> org.apache.camel.management.ManagedManagementStrategy.getManagedObjectName(ManagedManagementStrategy.java:104)
> at
> org.apache.camel.management.ManagedManagementStrategy.unmanageObject(ManagedManagementStrategy.java:143)
> at
> org.apache.camel.management.DefaultManagementLifecycleStrategy.unmanageObject(DefaultManagementLifecycleStrategy.java:839)
> at
> org.apache.camel.management.DefaultManagementLifecycleStrategy.onErrorHandlerRemove(DefaultManagementLifecycleStrategy.java:638)
> at
> org.apache.camel.impl.RouteService.stopChildService(RouteService.java:351)
> at org.apache.camel.impl.RouteService.doStop(RouteService.java:237)
> at
> org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:77)
> at
> org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:101)
> at
> org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:141)
> at
> org.apache.camel.util.ServiceHelper.stopAndShutdownService(ServiceHelper.java:204)
> at
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2843)
> at
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2868)
> at
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2856)
> at
> org.apache.camel.impl.DefaultCamelContext.doStop(DefaultCamelContext.java:2691)
> at
> org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
> at
> org.apache.camel.blueprint.BlueprintCamelContext.destroy(BlueprintCamelContext.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)[:1.8.0_66]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_66]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_66]
> at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_66]
> at
> org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:297)[15:org.apache.aries.blueprint.core:1.4.2]
> at
> org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:958)[15:org.apache.aries.blueprint.core:1.4.2]
> etc..
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-9695) During shutdown, Camel cannot unregister error handler
Martin Lichtin created CAMEL-9695:
-
Summary: During shutdown, Camel cannot unregister error handler
Key: CAMEL-9695
URL: https://issues.apache.org/jira/browse/CAMEL-9695
Project: Camel
Issue Type: Bug
Affects Versions: 2.15.5
Reporter: Martin Lichtin
According to http://camel.apache.org/redeliverypolicy.html
my camel context is like
{code:xml}
http://camel.apache.org/schema/blueprint;
xsi:schemaLocation="http://camel.apache.org/schema/blueprint
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd;
id="myIdxt" messageHistory="false">
etc.etc.
{code}
During shutdown, the following is output:
{noformat}
2016-03-10 12:33:44,649 | WARN | FelixStartLevel |
faultManagementLifecycleStrategy | faultManagementLifecycleStrategy 640 | 130
- org.apache.camel.camel-core - 2.15.5 | Could not unregister error handler:
org.apache.camel.management.mbean.ManagedErrorHandler@72c1
e7c3 as ErrorHandler MBean.
org.apache.camel.NoSuchBeanException: No bean could be found in the registry
for: myErrorHandler of type: org.apache.camel.builder.ErrorHandlerBuilder
at
org.apache.camel.util.CamelContextHelper.mandatoryLookup(CamelContextHelper.java:159)
at
org.apache.camel.impl.DefaultRouteContext.mandatoryLookup(DefaultRouteContext.java:151)
at
org.apache.camel.builder.ErrorHandlerBuilderRef.lookupErrorHandlerBuilder(ErrorHandlerBuilderRef.java:137)
at
org.apache.camel.management.DefaultManagementNamingStrategy.getObjectNameForErrorHandler(DefaultManagementNamingStrategy.java:154)
at
org.apache.camel.management.ManagedManagementStrategy.getManagedObjectName(ManagedManagementStrategy.java:104)
at
org.apache.camel.management.ManagedManagementStrategy.unmanageObject(ManagedManagementStrategy.java:143)
at
org.apache.camel.management.DefaultManagementLifecycleStrategy.unmanageObject(DefaultManagementLifecycleStrategy.java:839)
at
org.apache.camel.management.DefaultManagementLifecycleStrategy.onErrorHandlerRemove(DefaultManagementLifecycleStrategy.java:638)
at
org.apache.camel.impl.RouteService.stopChildService(RouteService.java:351)
at org.apache.camel.impl.RouteService.doStop(RouteService.java:237)
at
org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:77)
at
org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:101)
at
org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:141)
at
org.apache.camel.util.ServiceHelper.stopAndShutdownService(ServiceHelper.java:204)
at
org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2843)
at
org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2868)
at
org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2856)
at
org.apache.camel.impl.DefaultCamelContext.doStop(DefaultCamelContext.java:2691)
at org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
at
org.apache.camel.blueprint.BlueprintCamelContext.destroy(BlueprintCamelContext.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)[:1.8.0_66]
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_66]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_66]
at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_66]
at
org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:297)[15:org.apache.aries.blueprint.core:1.4.2]
at
org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:958)[15:org.apache.aries.blueprint.core:1.4.2]
etc..
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8770) Camel Blueprint - depends-on does not work
[
https://issues.apache.org/jira/browse/CAMEL-8770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725938#comment-14725938
]
Martin Lichtin commented on CAMEL-8770:
---
Hi Willem thanks for the fix. Something definitely changed with 2.15.3 :)
I've so far been referring to several beans with depends-on="beanA,beanB"
However, this (obviously) no longer works. It seems depends-on does not support
a list (unlike the depends-on in Aries Blueprint).
How then can one make the CamelContext depend on more than one bean?
> Camel Blueprint - depends-on does not work
> --
>
> Key: CAMEL-8770
> URL: https://issues.apache.org/jira/browse/CAMEL-8770
> Project: Camel
> Issue Type: Bug
> Components: camel-blueprint
>Affects Versions: 2.14.2, 2.15.2
>Reporter: Willem Jiang
>Assignee: Willem Jiang
> Fix For: 2.14.3, 2.15.3, 2.16.0
>
>
> Attribute depends-on does not work for camelContext element in blueprint
> container. When bean XXX does not exist then an exception should be thrown
> like in spring container.
> {code}
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-9068) Log output to show which route is shutdown and has a pending message
Martin Lichtin created CAMEL-9068:
-
Summary: Log output to show which route is shutdown and has a
pending message
Key: CAMEL-9068
URL: https://issues.apache.org/jira/browse/CAMEL-9068
Project: Camel
Issue Type: Improvement
Affects Versions: 2.15.1
Reporter: Martin Lichtin
Priority: Minor
It'd be great to see in the log output which route is shutdown and has a
pending message:
{noformat}
2015-08-06 09:11:45,312 | INFO | FelixDispatchQueue |
DefaultShutdownStrategy | mel.impl.DefaultShutdownStrategy 184 | 94 -
org.apache.camel.camel-core - 2.15.1 | Starting to graceful shutdown 1 routes
(timeout 300 seconds)
2015-08-06 09:11:45,318 | INFO | hread #23 - ShutdownTask |
DefaultShutdownStrategy | ultShutdownStrategy$ShutdownTask 606 | 94 -
org.apache.camel.camel-core - 2.15.1 | Waiting as there are still 1 inflight
and pending exchanges to complete, timeout in 300 seconds.
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-9068) Log output to show which route is shutdown and has a pending message
[
https://issues.apache.org/jira/browse/CAMEL-9068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14680128#comment-14680128
]
Martin Lichtin commented on CAMEL-9068:
---
Setting log level to DEBUG for org.apache.camel.impl.DefaultShutdownStrategy
would be an approach, thanks.
I still think above mentioned INFO messages would become useful once they
contain route name(s).
Currently one reads them and cannot deduce anything meaningful without knowing
which route is affected.
Log output to show which route is shutdown and has a pending message
Key: CAMEL-9068
URL: https://issues.apache.org/jira/browse/CAMEL-9068
Project: Camel
Issue Type: Improvement
Affects Versions: 2.15.1
Reporter: Martin Lichtin
Priority: Minor
It'd be great to see in the log output which route is shutdown and has a
pending message:
{noformat}
2015-08-06 09:11:45,312 | INFO | FelixDispatchQueue |
DefaultShutdownStrategy | mel.impl.DefaultShutdownStrategy 184 | 94
- org.apache.camel.camel-core - 2.15.1 | Starting to graceful shutdown 1
routes (timeout 300 seconds)
2015-08-06 09:11:45,318 | INFO | hread #23 - ShutdownTask |
DefaultShutdownStrategy | ultShutdownStrategy$ShutdownTask 606 | 94
- org.apache.camel.camel-core - 2.15.1 | Waiting as there are still 1
inflight and pending exchanges to complete, timeout in 300 seconds.
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8891) MVEL link on page http://camel.apache.org/mvel.html outdated
Martin Lichtin created CAMEL-8891: - Summary: MVEL link on page http://camel.apache.org/mvel.html outdated Key: CAMEL-8891 URL: https://issues.apache.org/jira/browse/CAMEL-8891 Project: Camel Issue Type: Improvement Components: documentation Reporter: Martin Lichtin Priority: Minor The MVEL link on page http://camel.apache.org/mvel.html is outdated. Can you update link to where MVEL is documented? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8841) camel:context-inflight returns 'Object name cannot be null'
[
https://issues.apache.org/jira/browse/CAMEL-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Lichtin updated CAMEL-8841:
--
Attachment: patchfile.txt
camel:context-inflight returns 'Object name cannot be null'
---
Key: CAMEL-8841
URL: https://issues.apache.org/jira/browse/CAMEL-8841
Project: Camel
Issue Type: Bug
Components: karaf, tooling
Affects Versions: 2.15.1, 2.15.2
Environment: Karaf 3.0.3
Reporter: Martin Lichtin
Fix For: 2.16.0, 2.15.3
Attachments: patchfile.txt
{noformat}
karaf camel:context-inflight myCamelContext
Error executing command: Object name cannot be null
karaf log:exception-display
javax.management.RuntimeOperationsException: Object name cannot be null
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered(DefaultMBeanServerInterceptor.java:569)[:1.8.0_45]
at
com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java:638)[:1.8.0_45]
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_45]
at
org.apache.karaf.management.boot.KarafMBeanServerBuilder$MBeanInvocationHandler.invoke(KarafMBeanServerBuilder.java:80)[karaf-jmx-boot.jar:]
at com.sun.proxy.$Proxy0.isRegistered(Unknown Source)[:]
at
org.apache.camel.commands.AbstractLocalCamelController.browseInflightExchanges(AbstractLocalCamelController.java:186)
at
org.apache.camel.commands.ContextInflightCommand.performContextCommand(ContextInflightCommand.java:56)
at
org.apache.camel.commands.AbstractContextCommand.executeLocal(AbstractContextCommand.java:74)
at
org.apache.camel.commands.AbstractContextCommand.execute(AbstractContextCommand.java:42)
at
org.apache.camel.karaf.commands.ContextInflight.doExecute(ContextInflight.java:40)
at
org.apache.karaf.shell.console.AbstractAction.execute(AbstractAction.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:39)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.commands.basic.AbstractCommand.execute(AbstractCommand.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:92)
at
org.apache.karaf.shell.console.impl.jline.ConsoleImpl.run(ConsoleImpl.java:208)
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.runConsole(ShellFactoryImpl.java:158)[52:org.apache.karaf.shell.ssh:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1$1.run(ShellFactoryImpl.java:133)
at java.security.AccessController.doPrivileged(Native
Method)[:1.8.0_45]
at
org.apache.karaf.jaas.modules.JaasHelper.doAs(JaasHelper.java:57)[26:org.apache.karaf.jaas.modules:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.run(ShellFactoryImpl.java:129)[52:org.apache.karaf.shell.ssh:3.0.3]
Caused by: java.lang.IllegalArgumentException: Object name cannot be null
... 30 more
{noformat}
I think when combining the object name
SetObjectName set = mBeanServer.queryNames(new
ObjectName(agent.getMBeanObjectDomainName() +
:type=services,name=DefaultInflightRepository,*), null);
The :context=context-name part seems missing.
The query should be something like
org.apache.camel:context=context-name,type=services,name=DefaultInflightRepository
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8841) camel:context-inflight returns 'Object name cannot be null'
[
https://issues.apache.org/jira/browse/CAMEL-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14585620#comment-14585620
]
Martin Lichtin commented on CAMEL-8841:
---
BTW, I see a regression in 2.16-SNAPSHOT with regards to Blueprint config files.
For example:
{noformat}
camelContext id=myContext
xmlns=http://camel.apache.org/schema/blueprint;
xsi:schemaLocation=http://camel.apache.org/schema/blueprint
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd;
depends-on=jms,PROPAGATION_REQUIRED
{noformat}
gives
{noformat}
org.osgi.service.blueprint.container.ComponentDefinitionException: Unresolved
ref/idref to component: jms,PROPAGATION_REQUIRED
{noformat}
It no longer seems to understand the depends-on in case of more than one
reference mentioned.
As far as I remember, the separator could be comma or space.
camel:context-inflight returns 'Object name cannot be null'
---
Key: CAMEL-8841
URL: https://issues.apache.org/jira/browse/CAMEL-8841
Project: Camel
Issue Type: Bug
Components: karaf, tooling
Affects Versions: 2.15.1, 2.15.2
Environment: Karaf 3.0.3
Reporter: Martin Lichtin
Fix For: 2.16.0, 2.15.3
Attachments: patchfile.txt
{noformat}
karaf camel:context-inflight myCamelContext
Error executing command: Object name cannot be null
karaf log:exception-display
javax.management.RuntimeOperationsException: Object name cannot be null
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered(DefaultMBeanServerInterceptor.java:569)[:1.8.0_45]
at
com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java:638)[:1.8.0_45]
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_45]
at
org.apache.karaf.management.boot.KarafMBeanServerBuilder$MBeanInvocationHandler.invoke(KarafMBeanServerBuilder.java:80)[karaf-jmx-boot.jar:]
at com.sun.proxy.$Proxy0.isRegistered(Unknown Source)[:]
at
org.apache.camel.commands.AbstractLocalCamelController.browseInflightExchanges(AbstractLocalCamelController.java:186)
at
org.apache.camel.commands.ContextInflightCommand.performContextCommand(ContextInflightCommand.java:56)
at
org.apache.camel.commands.AbstractContextCommand.executeLocal(AbstractContextCommand.java:74)
at
org.apache.camel.commands.AbstractContextCommand.execute(AbstractContextCommand.java:42)
at
org.apache.camel.karaf.commands.ContextInflight.doExecute(ContextInflight.java:40)
at
org.apache.karaf.shell.console.AbstractAction.execute(AbstractAction.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:39)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.commands.basic.AbstractCommand.execute(AbstractCommand.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:92)
at
org.apache.karaf.shell.console.impl.jline.ConsoleImpl.run(ConsoleImpl.java:208)
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.runConsole(ShellFactoryImpl.java:158)[52:org.apache.karaf.shell.ssh:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1$1.run(ShellFactoryImpl.java:133)
at java.security.AccessController.doPrivileged(Native
Method)[:1.8.0_45]
at
org.apache.karaf.jaas.modules.JaasHelper.doAs(JaasHelper.java:57)[26:org.apache.karaf.jaas.modules:3.0.3]
at
[jira] [Commented] (CAMEL-8841) camel:context-inflight returns 'Object name cannot be null'
[
https://issues.apache.org/jira/browse/CAMEL-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14585036#comment-14585036
]
Martin Lichtin commented on CAMEL-8841:
---
Yes, I'll give it a whirl.
camel:context-inflight returns 'Object name cannot be null'
---
Key: CAMEL-8841
URL: https://issues.apache.org/jira/browse/CAMEL-8841
Project: Camel
Issue Type: Bug
Components: karaf, tooling
Affects Versions: 2.15.1, 2.15.2
Environment: Karaf 3.0.3
Reporter: Martin Lichtin
Fix For: 2.16.0, 2.15.3
{noformat}
karaf camel:context-inflight myCamelContext
Error executing command: Object name cannot be null
karaf log:exception-display
javax.management.RuntimeOperationsException: Object name cannot be null
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered(DefaultMBeanServerInterceptor.java:569)[:1.8.0_45]
at
com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java:638)[:1.8.0_45]
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_45]
at
org.apache.karaf.management.boot.KarafMBeanServerBuilder$MBeanInvocationHandler.invoke(KarafMBeanServerBuilder.java:80)[karaf-jmx-boot.jar:]
at com.sun.proxy.$Proxy0.isRegistered(Unknown Source)[:]
at
org.apache.camel.commands.AbstractLocalCamelController.browseInflightExchanges(AbstractLocalCamelController.java:186)
at
org.apache.camel.commands.ContextInflightCommand.performContextCommand(ContextInflightCommand.java:56)
at
org.apache.camel.commands.AbstractContextCommand.executeLocal(AbstractContextCommand.java:74)
at
org.apache.camel.commands.AbstractContextCommand.execute(AbstractContextCommand.java:42)
at
org.apache.camel.karaf.commands.ContextInflight.doExecute(ContextInflight.java:40)
at
org.apache.karaf.shell.console.AbstractAction.execute(AbstractAction.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:39)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.commands.basic.AbstractCommand.execute(AbstractCommand.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:92)
at
org.apache.karaf.shell.console.impl.jline.ConsoleImpl.run(ConsoleImpl.java:208)
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.runConsole(ShellFactoryImpl.java:158)[52:org.apache.karaf.shell.ssh:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1$1.run(ShellFactoryImpl.java:133)
at java.security.AccessController.doPrivileged(Native
Method)[:1.8.0_45]
at
org.apache.karaf.jaas.modules.JaasHelper.doAs(JaasHelper.java:57)[26:org.apache.karaf.jaas.modules:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.run(ShellFactoryImpl.java:129)[52:org.apache.karaf.shell.ssh:3.0.3]
Caused by: java.lang.IllegalArgumentException: Object name cannot be null
... 30 more
{noformat}
I think when combining the object name
SetObjectName set = mBeanServer.queryNames(new
ObjectName(agent.getMBeanObjectDomainName() +
:type=services,name=DefaultInflightRepository,*), null);
The :context=context-name part seems missing.
The query should be something like
org.apache.camel:context=context-name,type=services,name=DefaultInflightRepository
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8841) camel:context-inflight returns 'Object name cannot be null'
[
https://issues.apache.org/jira/browse/CAMEL-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14585063#comment-14585063
]
Martin Lichtin commented on CAMEL-8841:
---
Following http://camel.apache.org/contributing.html
{noformat}
git clone https://git-wip-us.apache.org/repos/asf/camel.git
cd camel
mvn eclipse:eclipse
{noformat}
unfortunately fails with
{noformat}
[ERROR] Failed to execute goal on project camel-gae: Could not resolve
dependencies for project org.apache.camel:camel-gae:bundle:2.16-SNAPSHOT: The
following artifacts could not be resolved:
com.google.gdata:gdata-contacts-3.0:jar:1.41.5,
com.google.gdata:gdata-calendar-2.0:jar:1.41.5,
com.google.gdata:gdata-client-1.0:jar:1.41.5,
com.google.gdata:gdata-core-1.0:jar:1.41.5: Could not find artifact
com.google.gdata:gdata-contacts-3.0:jar:1.41.5 in bbp-repo
(http://repo.bbp.ch/artifactory/repo) - [Help 1]
{noformat}
camel:context-inflight returns 'Object name cannot be null'
---
Key: CAMEL-8841
URL: https://issues.apache.org/jira/browse/CAMEL-8841
Project: Camel
Issue Type: Bug
Components: karaf, tooling
Affects Versions: 2.15.1, 2.15.2
Environment: Karaf 3.0.3
Reporter: Martin Lichtin
Fix For: 2.16.0, 2.15.3
{noformat}
karaf camel:context-inflight myCamelContext
Error executing command: Object name cannot be null
karaf log:exception-display
javax.management.RuntimeOperationsException: Object name cannot be null
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered(DefaultMBeanServerInterceptor.java:569)[:1.8.0_45]
at
com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java:638)[:1.8.0_45]
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_45]
at
org.apache.karaf.management.boot.KarafMBeanServerBuilder$MBeanInvocationHandler.invoke(KarafMBeanServerBuilder.java:80)[karaf-jmx-boot.jar:]
at com.sun.proxy.$Proxy0.isRegistered(Unknown Source)[:]
at
org.apache.camel.commands.AbstractLocalCamelController.browseInflightExchanges(AbstractLocalCamelController.java:186)
at
org.apache.camel.commands.ContextInflightCommand.performContextCommand(ContextInflightCommand.java:56)
at
org.apache.camel.commands.AbstractContextCommand.executeLocal(AbstractContextCommand.java:74)
at
org.apache.camel.commands.AbstractContextCommand.execute(AbstractContextCommand.java:42)
at
org.apache.camel.karaf.commands.ContextInflight.doExecute(ContextInflight.java:40)
at
org.apache.karaf.shell.console.AbstractAction.execute(AbstractAction.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:39)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.commands.basic.AbstractCommand.execute(AbstractCommand.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:92)
at
org.apache.karaf.shell.console.impl.jline.ConsoleImpl.run(ConsoleImpl.java:208)
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.runConsole(ShellFactoryImpl.java:158)[52:org.apache.karaf.shell.ssh:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1$1.run(ShellFactoryImpl.java:133)
at java.security.AccessController.doPrivileged(Native
Method)[:1.8.0_45]
at
org.apache.karaf.jaas.modules.JaasHelper.doAs(JaasHelper.java:57)[26:org.apache.karaf.jaas.modules:3.0.3]
at
[jira] [Commented] (CAMEL-8841) camel:context-inflight returns 'Object name cannot be null'
[
https://issues.apache.org/jira/browse/CAMEL-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14585269#comment-14585269
]
Martin Lichtin commented on CAMEL-8841:
---
Right. Just wanted to report that I cannot build Camel given the instructions.
mvn clean install -Dtest=false fails the same way. But anyways.. don't need
to for this JIRA.
What's confusing is that the context names listed by camel:context-list don't
match what is expected by JMX as the 'context' name.
There is a so-called ManagementName expected when composing the object name.
Not a problem, just one more thing.
camel:context-inflight returns 'Object name cannot be null'
---
Key: CAMEL-8841
URL: https://issues.apache.org/jira/browse/CAMEL-8841
Project: Camel
Issue Type: Bug
Components: karaf, tooling
Affects Versions: 2.15.1, 2.15.2
Environment: Karaf 3.0.3
Reporter: Martin Lichtin
Fix For: 2.16.0, 2.15.3
{noformat}
karaf camel:context-inflight myCamelContext
Error executing command: Object name cannot be null
karaf log:exception-display
javax.management.RuntimeOperationsException: Object name cannot be null
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered(DefaultMBeanServerInterceptor.java:569)[:1.8.0_45]
at
com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java:638)[:1.8.0_45]
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_45]
at
org.apache.karaf.management.boot.KarafMBeanServerBuilder$MBeanInvocationHandler.invoke(KarafMBeanServerBuilder.java:80)[karaf-jmx-boot.jar:]
at com.sun.proxy.$Proxy0.isRegistered(Unknown Source)[:]
at
org.apache.camel.commands.AbstractLocalCamelController.browseInflightExchanges(AbstractLocalCamelController.java:186)
at
org.apache.camel.commands.ContextInflightCommand.performContextCommand(ContextInflightCommand.java:56)
at
org.apache.camel.commands.AbstractContextCommand.executeLocal(AbstractContextCommand.java:74)
at
org.apache.camel.commands.AbstractContextCommand.execute(AbstractContextCommand.java:42)
at
org.apache.camel.karaf.commands.ContextInflight.doExecute(ContextInflight.java:40)
at
org.apache.karaf.shell.console.AbstractAction.execute(AbstractAction.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:39)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.commands.basic.AbstractCommand.execute(AbstractCommand.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:92)
at
org.apache.karaf.shell.console.impl.jline.ConsoleImpl.run(ConsoleImpl.java:208)
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.runConsole(ShellFactoryImpl.java:158)[52:org.apache.karaf.shell.ssh:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1$1.run(ShellFactoryImpl.java:133)
at java.security.AccessController.doPrivileged(Native
Method)[:1.8.0_45]
at
org.apache.karaf.jaas.modules.JaasHelper.doAs(JaasHelper.java:57)[26:org.apache.karaf.jaas.modules:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.run(ShellFactoryImpl.java:129)[52:org.apache.karaf.shell.ssh:3.0.3]
Caused by: java.lang.IllegalArgumentException: Object name cannot be null
... 30 more
{noformat}
I think when combining the object name
SetObjectName set = mBeanServer.queryNames(new
ObjectName(agent.getMBeanObjectDomainName() +
[jira] [Created] (CAMEL-8841) camel:context-inflight returns 'Object name cannot be null'
Martin Lichtin created CAMEL-8841:
-
Summary: camel:context-inflight returns 'Object name cannot be
null'
Key: CAMEL-8841
URL: https://issues.apache.org/jira/browse/CAMEL-8841
Project: Camel
Issue Type: Bug
Affects Versions: 2.15.2, 2.15.1
Environment: Karaf 3.0.3
Reporter: Martin Lichtin
{noformat}
karaf camel:context-inflight myCamelContext
Error executing command: Object name cannot be null
karaf log:exception-display
javax.management.RuntimeOperationsException: Object name cannot be null
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered(DefaultMBeanServerInterceptor.java:569)[:1.8.0_45]
at
com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java:638)[:1.8.0_45]
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_45]
at
org.apache.karaf.management.boot.KarafMBeanServerBuilder$MBeanInvocationHandler.invoke(KarafMBeanServerBuilder.java:80)[karaf-jmx-boot.jar:]
at com.sun.proxy.$Proxy0.isRegistered(Unknown Source)[:]
at
org.apache.camel.commands.AbstractLocalCamelController.browseInflightExchanges(AbstractLocalCamelController.java:186)
at
org.apache.camel.commands.ContextInflightCommand.performContextCommand(ContextInflightCommand.java:56)
at
org.apache.camel.commands.AbstractContextCommand.executeLocal(AbstractContextCommand.java:74)
at
org.apache.camel.commands.AbstractContextCommand.execute(AbstractContextCommand.java:42)
at
org.apache.camel.karaf.commands.ContextInflight.doExecute(ContextInflight.java:40)
at
org.apache.karaf.shell.console.AbstractAction.execute(AbstractAction.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:39)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.commands.basic.AbstractCommand.execute(AbstractCommand.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown Source)[:]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown Source)[:]
at
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:92)
at
org.apache.karaf.shell.console.impl.jline.ConsoleImpl.run(ConsoleImpl.java:208)
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.runConsole(ShellFactoryImpl.java:158)[52:org.apache.karaf.shell.ssh:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1$1.run(ShellFactoryImpl.java:133)
at java.security.AccessController.doPrivileged(Native Method)[:1.8.0_45]
at
org.apache.karaf.jaas.modules.JaasHelper.doAs(JaasHelper.java:57)[26:org.apache.karaf.jaas.modules:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.run(ShellFactoryImpl.java:129)[52:org.apache.karaf.shell.ssh:3.0.3]
Caused by: java.lang.IllegalArgumentException: Object name cannot be null
... 30 more
{noformat}
I think when combining the object name
SetObjectName set = mBeanServer.queryNames(new
ObjectName(agent.getMBeanObjectDomainName() +
:type=services,name=DefaultInflightRepository,*), null);
The :context=context-name part seems missing.
The query should be something like
org.apache.camel:context=context-name,type=services,name=DefaultInflightRepository
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8631) Allow use of Spring 4 in Karaf environment
Martin Lichtin created CAMEL-8631: - Summary: Allow use of Spring 4 in Karaf environment Key: CAMEL-8631 URL: https://issues.apache.org/jira/browse/CAMEL-8631 Project: Camel Issue Type: Improvement Affects Versions: 2.15.1 Environment: Karaf 3.0.3 Reporter: Martin Lichtin It's currently not possible to use Camel with Spring version 4. When first installing Spring 4: feature:install -v spring/4.1.2.RELEASE_1 and then installing Camel: feature:repo-add mvn:org.apache.camel.karaf/apache-camel/2.15.1/xml/features feature:install camel The Camel feature file will actually install Spring 3 and not use the version 4 that is already installed. One can verify this with bundle:requirements camel-spring to see that it resolved the 'spring' packages with 3.2.11.RELEASE and not version 4. E.g.: osgi.wiring.package; ((osgi.wiring.package=org.springframework.beans)(version=3.2.0)(!(version=5.0.0))) resolved by: osgi.wiring.package; org.springframework.beans 3.2.11.RELEASE from org.apache.servicemix.bundles.spring-beans [83] I believe the Camel features file needs to be modified to support Spring 4. It currently has range restrictions that exclude version 4. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8593) JmsEndpoint.configureListenerContainer() some debug logs miss {}
Martin Lichtin created CAMEL-8593:
-
Summary: JmsEndpoint.configureListenerContainer() some debug logs
miss {}
Key: CAMEL-8593
URL: https://issues.apache.org/jira/browse/CAMEL-8593
Project: Camel
Issue Type: Improvement
Affects Versions: 2.13.3
Reporter: Martin Lichtin
Priority: Trivial
In method JmsEndpoint.configureListenerContainer()
there are a few debug logs that miss the second {}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-7623) Camel is blocked while trying to shutdown a JMS consumer
[
https://issues.apache.org/jira/browse/CAMEL-7623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14113886#comment-14113886
]
Martin Lichtin commented on CAMEL-7623:
---
Just wanted to report that this issue seems to have been caused by ActiveMQ
prefetch=0 setting.
Camel is blocked while trying to shutdown a JMS consumer
Key: CAMEL-7623
URL: https://issues.apache.org/jira/browse/CAMEL-7623
Project: Camel
Issue Type: Bug
Components: camel-jms
Affects Versions: 2.12.3
Environment: Karaf 2.3.4, Camel 2.12.3, spring-jms 3.2.5.RELEASE
Reporter: Martin Lichtin
Assignee: Claus Ibsen
Camel is blocked while trying to shutdown a JMS consumer.
{noformat}
FelixStartLevel daemon prio=10 tid=0x2aaab03d2000 nid=0x6803 in
Object.wait() [0x405cd000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on 0x00079b473700 (a java.lang.Object)
at java.lang.Object.wait(Object.java:503)
at
org.springframework.jms.listener.DefaultMessageListenerContainer.doShutdown(DefaultMessageListenerContainer.java:545)
- locked 0x00079b473700 (a java.lang.Object)
at
org.springframework.jms.listener.AbstractJmsListeningContainer.shutdown(AbstractJmsListeningContainer.java:233)
at
org.springframework.jms.listener.AbstractJmsListeningContainer.destroy(AbstractJmsListeningContainer.java:173)
at
org.apache.camel.component.jms.DefaultJmsMessageListenerContainer.destroy(DefaultJmsMessageListenerContainer.java:100)
at
org.apache.camel.component.jms.JmsConsumer.stopAndDestroyListenerContainer(JmsConsumer.java:179)
at
org.apache.camel.component.jms.JmsConsumer.doStop(JmsConsumer.java:217)
at
org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
at
org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:141)
at
org.apache.camel.impl.DefaultShutdownStrategy.shutdownNow(DefaultShutdownStrategy.java:336)
at
org.apache.camel.impl.DefaultShutdownStrategy.shutdownRoutesNow(DefaultShutdownStrategy.java:310)
at
org.apache.camel.impl.DefaultShutdownStrategy.doShutdown(DefaultShutdownStrategy.java:204)
at
org.apache.camel.impl.DefaultShutdownStrategy.shutdownForced(DefaultShutdownStrategy.java:131)
at
org.apache.camel.impl.DefaultCamelContext.doStop(DefaultCamelContext.java:1753)
- locked 0x00079b1cb208 (a
org.apache.camel.blueprint.BlueprintCamelContext)
at
org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
at
org.apache.camel.blueprint.BlueprintCamelContext.destroy(BlueprintCamelContext.java:119)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:297)
at
org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:958)
at
org.apache.aries.blueprint.container.BeanRecipe.destroy(BeanRecipe.java:863)
at
org.apache.aries.blueprint.container.BlueprintRepository.destroy(BlueprintRepository.java:320)
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.destroyComponents(BlueprintContainerImpl.java:722)
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.tidyupComponents(BlueprintContainerImpl.java:916)
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.destroy(BlueprintContainerImpl.java:866)
at
org.apache.aries.blueprint.container.BlueprintExtender$3.run(BlueprintExtender.java:301)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
org.apache.aries.blueprint.container.BlueprintExtender.destroyContainer(BlueprintExtender.java:322)
at
org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:218)
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)
at
[jira] [Created] (CAMEL-7623) Camel is blocked while trying to shutdown a JMS consumer
Martin Lichtin created CAMEL-7623:
-
Summary: Camel is blocked while trying to shutdown a JMS consumer
Key: CAMEL-7623
URL: https://issues.apache.org/jira/browse/CAMEL-7623
Project: Camel
Issue Type: Bug
Components: camel-jms
Affects Versions: 2.12.3
Environment: Karaf 2.3.4, Camel 2.12.3, spring-jms 3.2.5.RELEASE
Reporter: Martin Lichtin
Camel is blocked while trying to shutdown a JMS consumer.
{noformat}
FelixStartLevel daemon prio=10 tid=0x2aaab03d2000 nid=0x6803 in
Object.wait() [0x405cd000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on 0x00079b473700 (a java.lang.Object)
at java.lang.Object.wait(Object.java:503)
at
org.springframework.jms.listener.DefaultMessageListenerContainer.doShutdown(DefaultMessageListenerContainer.java:545)
- locked 0x00079b473700 (a java.lang.Object)
at
org.springframework.jms.listener.AbstractJmsListeningContainer.shutdown(AbstractJmsListeningContainer.java:233)
at
org.springframework.jms.listener.AbstractJmsListeningContainer.destroy(AbstractJmsListeningContainer.java:173)
at
org.apache.camel.component.jms.DefaultJmsMessageListenerContainer.destroy(DefaultJmsMessageListenerContainer.java:100)
at
org.apache.camel.component.jms.JmsConsumer.stopAndDestroyListenerContainer(JmsConsumer.java:179)
at
org.apache.camel.component.jms.JmsConsumer.doStop(JmsConsumer.java:217)
at org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
at
org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:141)
at
org.apache.camel.impl.DefaultShutdownStrategy.shutdownNow(DefaultShutdownStrategy.java:336)
at
org.apache.camel.impl.DefaultShutdownStrategy.shutdownRoutesNow(DefaultShutdownStrategy.java:310)
at
org.apache.camel.impl.DefaultShutdownStrategy.doShutdown(DefaultShutdownStrategy.java:204)
at
org.apache.camel.impl.DefaultShutdownStrategy.shutdownForced(DefaultShutdownStrategy.java:131)
at
org.apache.camel.impl.DefaultCamelContext.doStop(DefaultCamelContext.java:1753)
- locked 0x00079b1cb208 (a
org.apache.camel.blueprint.BlueprintCamelContext)
at org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
at
org.apache.camel.blueprint.BlueprintCamelContext.destroy(BlueprintCamelContext.java:119)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:297)
at
org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:958)
at
org.apache.aries.blueprint.container.BeanRecipe.destroy(BeanRecipe.java:863)
at
org.apache.aries.blueprint.container.BlueprintRepository.destroy(BlueprintRepository.java:320)
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.destroyComponents(BlueprintContainerImpl.java:722)
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.tidyupComponents(BlueprintContainerImpl.java:916)
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.destroy(BlueprintContainerImpl.java:866)
at
org.apache.aries.blueprint.container.BlueprintExtender$3.run(BlueprintExtender.java:301)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
org.apache.aries.blueprint.container.BlueprintExtender.destroyContainer(BlueprintExtender.java:322)
at
org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:218)
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)
at
org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1103)
at
org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:695)
at
[jira] [Reopened] (CAMEL-7623) Camel is blocked while trying to shutdown a JMS consumer
[
https://issues.apache.org/jira/browse/CAMEL-7623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Lichtin reopened CAMEL-7623:
---
Sorry this wasn't clear, but the thread is in this state since an hour. Async
shutdown wouldn't help, afaics.
Camel is blocked while trying to shutdown a JMS consumer
Key: CAMEL-7623
URL: https://issues.apache.org/jira/browse/CAMEL-7623
Project: Camel
Issue Type: Bug
Components: camel-jms
Affects Versions: 2.12.3
Environment: Karaf 2.3.4, Camel 2.12.3, spring-jms 3.2.5.RELEASE
Reporter: Martin Lichtin
Assignee: Claus Ibsen
Camel is blocked while trying to shutdown a JMS consumer.
{noformat}
FelixStartLevel daemon prio=10 tid=0x2aaab03d2000 nid=0x6803 in
Object.wait() [0x405cd000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on 0x00079b473700 (a java.lang.Object)
at java.lang.Object.wait(Object.java:503)
at
org.springframework.jms.listener.DefaultMessageListenerContainer.doShutdown(DefaultMessageListenerContainer.java:545)
- locked 0x00079b473700 (a java.lang.Object)
at
org.springframework.jms.listener.AbstractJmsListeningContainer.shutdown(AbstractJmsListeningContainer.java:233)
at
org.springframework.jms.listener.AbstractJmsListeningContainer.destroy(AbstractJmsListeningContainer.java:173)
at
org.apache.camel.component.jms.DefaultJmsMessageListenerContainer.destroy(DefaultJmsMessageListenerContainer.java:100)
at
org.apache.camel.component.jms.JmsConsumer.stopAndDestroyListenerContainer(JmsConsumer.java:179)
at
org.apache.camel.component.jms.JmsConsumer.doStop(JmsConsumer.java:217)
at
org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
at
org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:141)
at
org.apache.camel.impl.DefaultShutdownStrategy.shutdownNow(DefaultShutdownStrategy.java:336)
at
org.apache.camel.impl.DefaultShutdownStrategy.shutdownRoutesNow(DefaultShutdownStrategy.java:310)
at
org.apache.camel.impl.DefaultShutdownStrategy.doShutdown(DefaultShutdownStrategy.java:204)
at
org.apache.camel.impl.DefaultShutdownStrategy.shutdownForced(DefaultShutdownStrategy.java:131)
at
org.apache.camel.impl.DefaultCamelContext.doStop(DefaultCamelContext.java:1753)
- locked 0x00079b1cb208 (a
org.apache.camel.blueprint.BlueprintCamelContext)
at
org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
at
org.apache.camel.blueprint.BlueprintCamelContext.destroy(BlueprintCamelContext.java:119)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:297)
at
org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:958)
at
org.apache.aries.blueprint.container.BeanRecipe.destroy(BeanRecipe.java:863)
at
org.apache.aries.blueprint.container.BlueprintRepository.destroy(BlueprintRepository.java:320)
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.destroyComponents(BlueprintContainerImpl.java:722)
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.tidyupComponents(BlueprintContainerImpl.java:916)
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.destroy(BlueprintContainerImpl.java:866)
at
org.apache.aries.blueprint.container.BlueprintExtender$3.run(BlueprintExtender.java:301)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
org.apache.aries.blueprint.container.BlueprintExtender.destroyContainer(BlueprintExtender.java:322)
at
org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:218)
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)
at
[jira] [Commented] (CAMEL-6094) Cannot specify which converter to use when several can do the same conversion
[ https://issues.apache.org/jira/browse/CAMEL-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14003155#comment-14003155 ] Martin Lichtin commented on CAMEL-6094: --- Is there a workaround available to get rid of these warnings? They still appear with Camel 2.12.3. Cannot specify which converter to use when several can do the same conversion - Key: CAMEL-6094 URL: https://issues.apache.org/jira/browse/CAMEL-6094 Project: Camel Issue Type: Improvement Components: camel-http, camel-jetty Reporter: Nicolas Lebreton Fix For: Future I use both Camel-Jetty and Camel-http4 components in many routes. Each time a route is started the following messages appear in logs : 15:16:01,496 | WARN | xtenderThread-32 | DefaultTypeConverter | 68 - org.apache.camel.camel-core - 2.6.0.fuse-01-09 | Overriding type converter from: StaticMethodTypeConverter: public static java.io.InputStream org.apache.camel.component.http.HttpConverter.toInputStream(javax.servlet.http.HttpServletRequest,org.apache.camel.Exchange) throws java.io.IOException to: StaticMethodTypeConverter: public static java.io.InputStream org.apache.camel.component.http4.HttpConverter.toInputStream(javax.servlet.http.HttpServletRequest,org.apache.camel.Exchange) throws java.io.IOException 15:16:01,497 | WARN | xtenderThread-32 | DefaultTypeConverter | 68 - org.apache.camel.camel-core - 2.6.0.fuse-01-09 | Overriding type converter from: StaticMethodTypeConverter: public static javax.servlet.http.HttpServletRequest org.apache.camel.component.http.HttpConverter.toServletRequest(org.apache.camel.Message) to: StaticMethodTypeConverter: public static javax.servlet.http.HttpServletRequest org.apache.camel.component.http4.HttpConverter.toServletRequest(org.apache.camel.Message) 15:16:01,498 | WARN | xtenderThread-32 | DefaultTypeConverter | 68 - org.apache.camel.camel-core - 2.6.0.fuse-01-09 | Overriding type converter from: StaticMethodTypeConverter: public static javax.servlet.http.HttpServletResponse org.apache.camel.component.http.HttpConverter.toServletResponse(org.apache.camel.Message) to: StaticMethodTypeConverter: public static javax.servlet.http.HttpServletResponse org.apache.camel.component.http4.HttpConverter.toServletResponse(org.apache.camel.Message) Even if these are warnings, even if the impact is clearly documented, my customers can not understand why there are so many messages with keywords like IOExceptions and can think this is linked to my product since they appear each time a route is started. This is why I have chosen Major as a priority. I cannot uninstall neither camel-http4 nor camel-http (which is the most quoted solution on forums). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7392) Unable to resolve bundle revision org.apache.camel.camel-servlet
[ https://issues.apache.org/jira/browse/CAMEL-7392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13980794#comment-13980794 ] Martin Lichtin commented on CAMEL-7392: --- Unfortunately that didn't make a difference. To reproduce, it's sufficient to first load hawtio-core, then load camel-servlet into a cleanly started Karaf: karaf@root features:addurl mvn:io.hawt/hawtio-karaf/1.3.1/xml/features karaf@root features:install hawtio karaf@root features:install camel-servlet Error executing command: Could not start bundle mvn:org.apache.camel/camel-servlet/2.13.0 in feature(s) camel-servlet-2.13.0: Uses constraint violation. Unable to resolve bundle revision org.apache.camel.camel-servlet [99.0] because it is exposed to package 'javax.servlet' from bundle revisions org.apache.geronimo.specs.geronimo-servlet_2.5_spec [55.0] and org.apache.geronimo.specs.geronimo-servlet_3.0_spec [97.0] via two dependency chains. Chain 1: org.apache.camel.camel-servlet [99.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_2.5_spec [55.0] Chain 2: org.apache.camel.camel-servlet [99.0] import: ((osgi.wiring.package=org.apache.camel.component.http)(version=2.13.0)(!(version=2.14.0))) | export: osgi.wiring.package=org.apache.camel.component.http; uses:=javax.servlet org.apache.camel.camel-http [98.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_3.0_spec [97.0] karaf@root Unable to resolve bundle revision org.apache.camel.camel-servlet - Key: CAMEL-7392 URL: https://issues.apache.org/jira/browse/CAMEL-7392 Project: Camel Issue Type: Bug Affects Versions: 2.13.0 Environment: Karaf 2.3.4 Reporter: Martin Lichtin When loading features repositorymvn:org.apache.activemq/activemq-karaf/5.7.0/xml/features/repository repositorymvn:org.apache.camel.karaf/apache-camel/2.13.0/xml/features/repository repositorymvn:io.hawt/hawtio-karaf/1.2.3/xml/features/repository featureactivemq/feature featurecamel/feature featurecamel-jms/feature featurecamel-mvel/feature featurecamel-groovy/feature featurehawtio-core/feature featurecamel-cache/feature featurecxf/feature featurecamel-cxf/feature featurecamel-http/feature featurecamel-http4/feature featurecamel-servlet/feature the following issue occurs: Error executing command: Could not start bundle mvn:org.apache.camel/camel-servlet/2.13.0 in feature(s) camel-servlet-2.13.0: Uses constraint violation. Unable to resolve bundle revision org.apache.camel.camel-servlet [243.0] because it is exposed to package 'javax.servlet' from bundle revisions org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] and org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] via two dependency chains. Chain 1: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] Chain 2: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=org.apache.camel.component.http)(version=2.13.0)(!(version=2.14.0))) | export: osgi.wiring.package=org.apache.camel.component.http; uses:=javax.servlet org.apache.camel.camel-http [239.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7392) Unable to resolve bundle revision org.apache.camel.camel-servlet
Martin Lichtin created CAMEL-7392: - Summary: Unable to resolve bundle revision org.apache.camel.camel-servlet Key: CAMEL-7392 URL: https://issues.apache.org/jira/browse/CAMEL-7392 Project: Camel Issue Type: Bug Affects Versions: 2.13.0 Environment: Karaf 2.3.4 Reporter: Martin Lichtin When loading features featureactivemq/feature featurecamel/feature featurecamel-jms/feature featurecamel-mvel/feature featurecamel-groovy/feature featurehawtio-core/feature featurecamel-cache/feature featurecxf/feature featurecamel-cxf/feature featurecamel-http/feature featurecamel-http4/feature featurecamel-servlet/feature the following issue occurs: Error executing command: Could not start bundle mvn:org.apache.camel/camel-servlet/2.13.0 in feature(s) camel-servlet-2.13.0: Uses constraint violation. Unable to resolve bundle revision org.apache.camel.camel-servlet [243.0] because it is exposed to package 'javax.servlet' from bundle revisions org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] and org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] via two dependency chains. Chain 1: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] Chain 2: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=org.apache.camel.component.http)(version=2.13.0)(!(version=2.14.0))) | export: osgi.wiring.package=org.apache.camel.component.http; uses:=javax.servlet org.apache.camel.camel-http [239.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7392) Unable to resolve bundle revision org.apache.camel.camel-servlet
[ https://issues.apache.org/jira/browse/CAMEL-7392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Lichtin updated CAMEL-7392: -- Description: When loading features repositorymvn:org.apache.activemq/activemq-karaf/5.7.0/xml/features/repository repositorymvn:org.apache.camel.karaf/apache-camel/2.13.0/xml/features/repository repositorymvn:io.hawt/hawtio-karaf/1.2.3/xml/features/repository featureactivemq/feature featurecamel/feature featurecamel-jms/feature featurecamel-mvel/feature featurecamel-groovy/feature featurehawtio-core/feature featurecamel-cache/feature featurecxf/feature featurecamel-cxf/feature featurecamel-http/feature featurecamel-http4/feature featurecamel-servlet/feature the following issue occurs: Error executing command: Could not start bundle mvn:org.apache.camel/camel-servlet/2.13.0 in feature(s) camel-servlet-2.13.0: Uses constraint violation. Unable to resolve bundle revision org.apache.camel.camel-servlet [243.0] because it is exposed to package 'javax.servlet' from bundle revisions org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] and org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] via two dependency chains. Chain 1: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] Chain 2: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=org.apache.camel.component.http)(version=2.13.0)(!(version=2.14.0))) | export: osgi.wiring.package=org.apache.camel.component.http; uses:=javax.servlet org.apache.camel.camel-http [239.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] was: When loading features featureactivemq/feature featurecamel/feature featurecamel-jms/feature featurecamel-mvel/feature featurecamel-groovy/feature featurehawtio-core/feature featurecamel-cache/feature featurecxf/feature featurecamel-cxf/feature featurecamel-http/feature featurecamel-http4/feature featurecamel-servlet/feature the following issue occurs: Error executing command: Could not start bundle mvn:org.apache.camel/camel-servlet/2.13.0 in feature(s) camel-servlet-2.13.0: Uses constraint violation. Unable to resolve bundle revision org.apache.camel.camel-servlet [243.0] because it is exposed to package 'javax.servlet' from bundle revisions org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] and org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] via two dependency chains. Chain 1: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] Chain 2: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=org.apache.camel.component.http)(version=2.13.0)(!(version=2.14.0))) | export: osgi.wiring.package=org.apache.camel.component.http; uses:=javax.servlet org.apache.camel.camel-http [239.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] Unable to resolve bundle revision org.apache.camel.camel-servlet - Key: CAMEL-7392 URL: https://issues.apache.org/jira/browse/CAMEL-7392 Project: Camel Issue Type: Bug Affects Versions: 2.13.0 Environment: Karaf 2.3.4 Reporter: Martin Lichtin When loading features repositorymvn:org.apache.activemq/activemq-karaf/5.7.0/xml/features/repository repositorymvn:org.apache.camel.karaf/apache-camel/2.13.0/xml/features/repository repositorymvn:io.hawt/hawtio-karaf/1.2.3/xml/features/repository featureactivemq/feature featurecamel/feature featurecamel-jms/feature featurecamel-mvel/feature featurecamel-groovy/feature featurehawtio-core/feature featurecamel-cache/feature featurecxf/feature featurecamel-cxf/feature
[jira] [Commented] (CAMEL-7392) Unable to resolve bundle revision org.apache.camel.camel-servlet
[ https://issues.apache.org/jira/browse/CAMEL-7392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13979820#comment-13979820 ] Martin Lichtin commented on CAMEL-7392: --- Thanks for the info. Actually we happily run with ActiveMQ 5.7 (client-side only) and Camel 2.13.0. What seems to be causing the problem here is hawtio. Camel and the camel-servlet feature come up fine when I do not load the hawtio-core feature. Unable to resolve bundle revision org.apache.camel.camel-servlet - Key: CAMEL-7392 URL: https://issues.apache.org/jira/browse/CAMEL-7392 Project: Camel Issue Type: Bug Affects Versions: 2.13.0 Environment: Karaf 2.3.4 Reporter: Martin Lichtin When loading features repositorymvn:org.apache.activemq/activemq-karaf/5.7.0/xml/features/repository repositorymvn:org.apache.camel.karaf/apache-camel/2.13.0/xml/features/repository repositorymvn:io.hawt/hawtio-karaf/1.2.3/xml/features/repository featureactivemq/feature featurecamel/feature featurecamel-jms/feature featurecamel-mvel/feature featurecamel-groovy/feature featurehawtio-core/feature featurecamel-cache/feature featurecxf/feature featurecamel-cxf/feature featurecamel-http/feature featurecamel-http4/feature featurecamel-servlet/feature the following issue occurs: Error executing command: Could not start bundle mvn:org.apache.camel/camel-servlet/2.13.0 in feature(s) camel-servlet-2.13.0: Uses constraint violation. Unable to resolve bundle revision org.apache.camel.camel-servlet [243.0] because it is exposed to package 'javax.servlet' from bundle revisions org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] and org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] via two dependency chains. Chain 1: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] Chain 2: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=org.apache.camel.component.http)(version=2.13.0)(!(version=2.14.0))) | export: osgi.wiring.package=org.apache.camel.component.http; uses:=javax.servlet org.apache.camel.camel-http [239.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7367) ClassNotFoundException: groovy.lang.Script
Martin Lichtin created CAMEL-7367: - Summary: ClassNotFoundException: groovy.lang.Script Key: CAMEL-7367 URL: https://issues.apache.org/jira/browse/CAMEL-7367 Project: Camel Issue Type: Bug Components: camel-groovy Affects Versions: 2.13.0 Reporter: Martin Lichtin When trying to upgrade from 2.11.4 to either 2.12.3 or 2.13.0 a problem with using Groovy pops up. The symptom is: java.lang.ClassNotFoundException: groovy.lang.Script at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:648) at groovy.lang.GroovyClassLoader$InnerLoader.loadClass(GroovyClassLoader.java:401) at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:758) at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:746) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:800) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at groovy.lang.GroovyClassLoader.access$300(GroovyClassLoader.java:55) at groovy.lang.GroovyClassLoader$ClassCollector.createClass(GroovyClassLoader.java:471) at groovy.lang.GroovyClassLoader$ClassCollector.onClassNode(GroovyClassLoader.java:488) at groovy.lang.GroovyClassLoader$ClassCollector.call(GroovyClassLoader.java:492) at org.codehaus.groovy.control.CompilationUnit$15.call(CompilationUnit.java:803) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1036) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:572) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:550) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:527) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:279) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:258) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:244) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:202) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:212) at org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:65) at org.apache.camel.language.groovy.GroovyExpression.evaluate(GroovyExpression.java:50) at org.apache.camel.processor.SetBodyProcessor.process(SetBodyProcessor.java:46) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72) at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:398) at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191) at org.apache.camel.processor.Pipeline.process(Pipeline.java:118) at org.apache.camel.processor.Pipeline.process(Pipeline.java:80) at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191) at org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:51) at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191) at org.apache.camel.processor.UnitOfWorkProducer.process(UnitOfWorkProducer.java:73) at org.apache.camel.impl.ProducerCache$2.doInProducer(ProducerCache.java:378) at org.apache.camel.impl.ProducerCache$2.doInProducer(ProducerCache.java:346) at org.apache.camel.impl.ProducerCache.doInProducer(ProducerCache.java:242) at org.apache.camel.impl.ProducerCache.sendExchange(ProducerCache.java:346) at org.apache.camel.impl.ProducerCache.send(ProducerCache.java:184) at org.apache.camel.impl.DefaultProducerTemplate.send(DefaultProducerTemplate.java:124) ... This runs inside a Karaf 2.3.4 with features featurecamel/feature featurecamel-groovy/feature loaded. groovy.lang.Script comes from the groovy-all/2.2.2 bundle. The bundle is loaded by the camel-groovy feature. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7365) Camel versus Karaf versions
Martin Lichtin created CAMEL-7365: - Summary: Camel versus Karaf versions Key: CAMEL-7365 URL: https://issues.apache.org/jira/browse/CAMEL-7365 Project: Camel Issue Type: Improvement Components: documentation Reporter: Martin Lichtin Priority: Minor Can page http://camel.apache.org/karaf.html be brought up to date? For example, I'd like to upgrade to Karaf 3.0.1 and it's not clear which version (or version range) would be suitable. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7049) Cannot set JMSReplyTo with a topic destination when sending a message to a queue
[ https://issues.apache.org/jira/browse/CAMEL-7049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13883839#comment-13883839 ] Martin Lichtin commented on CAMEL-7049: --- ActiveMQ 5.7.0 (however, from what I can see, no message broker code is involved, it's happening in JmsProducer) Cannot set JMSReplyTo with a topic destination when sending a message to a queue Key: CAMEL-7049 URL: https://issues.apache.org/jira/browse/CAMEL-7049 Project: Camel Issue Type: Bug Components: camel-jms Affects Versions: 2.11.1 Reporter: Martin Lichtin Assignee: Claus Ibsen Fix For: 2.11.4, 2.12.3, 2.13.0 The use case is about using Camel to communicate with the ActiveMQ StatisticsPlugin: Need to send a message and set 'JMSReplyTo' with a destination for the response message(s). Doing this as part of a Camel processor: in.setHeader(JMSReplyTo, topic://mydest); This, however, results in the broker (ie. the statistics plugin) returning messages to the mydest queue, as opposed to the topic. The issue is that Camel starts fiddling with the 'JMSReplyTo' header. Enabling trace level shows how Camel coerces the topic into a queue: JmsProducer | amel.component.jms.JmsProducer$2 315 | 126 - org.apache.camel.camel-jms - 2.11.1 | Normalized JMSReplyTo destination name topic://jmsqueuemonitor - jmsqueuemonitor JmsProducer | amel.component.jms.JmsProducer$2 315 | 126 - org.apache.camel.camel-jms - 2.11.1 | Normalized JMSReplyTo destination name topic://jmsqueuemonitor - jmsqueuemonitor JmsProducer | amel.component.jms.JmsProducer$2 331 | 126 - org.apache.camel.camel-jms - 2.11.1 | Creating JMSReplyTo queue: jmsqueuemonitor JmsProducer | amel.component.jms.JmsProducer$2 331 | 126 - org.apache.camel.camel-jms - 2.11.1 | Creating JMSReplyTo queue: jmsqueuemonitor JmsProducer | amel.component.jms.JmsProducer$2 343 | 126 - org.apache.camel.camel-jms - 2.11.1 | Using JMSReplyTo destination: queue://jmsqueuemonitor JmsProducer | amel.component.jms.JmsProducer$2 343 | 126 - org.apache.camel.camel-jms - 2.11.1 | Using JMSReplyTo destination: queue://jmsqueuemonitor Camel seems to apply some logic that is faulty in this circumstance. Just want to send a message to a queue and have that message carry a 'JMSReplyTo' value that should be left untouched. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Reopened] (CAMEL-7049) Cannot set JMSReplyTo with a topic destination when sending a message to a queue
[
https://issues.apache.org/jira/browse/CAMEL-7049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Lichtin reopened CAMEL-7049:
---
Unfortunately it doesn't seem to be fixed, at least not in 2.11.3.
I still see how it the 'normalization' switches from topic to queue:
JmsProducer | amel.component.jms.JmsProducer$2 328 | 126
- org.apache.camel.camel-jms - 2.11.3 | Normalized JMSReplyTo destination name
topic://xxx - xxx
JmsProducer | amel.component.jms.JmsProducer$2 344 | 126
- org.apache.camel.camel-jms - 2.11.3 | Creating JMSReplyTo queue: xxx
JmsProducer | amel.component.jms.JmsProducer$2 356 | 126
- org.apache.camel.camel-jms - 2.11.3 | Using JMSReplyTo destination:
queue://xxx
JmsProducer | amel.component.jms.JmsProducer$2 364 | 126
- org.apache.camel.camel-jms - 2.11.3 | Created javax.jms.Message:
ActiveMQMessage {commandId = 0, responseRequired = false, messageId = null,
originalDestination = null, originalTransactionId = null, producerId = null,
destination = null, transactionId = null, expiration = 0, timestamp = 0,
arrival = 0, brokerInTime = 0, brokerOutTime = 0, correlationId = null, replyTo
= queue://xxx, persistent = true, type = null, priority = 0, groupID = null,
groupSequence = 0, targetConsumerId = null, compressed = false, userID = null,
content = null, marshalledProperties = null, dataStructure = null,
redeliveryCounter = 0, size = 0, properties =
{breadcrumbId=ID-mlipc-54383-1390388987563-0-1, firedTime=Wed Jan 22 12:09:49
CET 2014}, readOnlyProperties = false, readOnlyBody = false, droppable = false}
Cannot set JMSReplyTo with a topic destination when sending a message to a
queue
Key: CAMEL-7049
URL: https://issues.apache.org/jira/browse/CAMEL-7049
Project: Camel
Issue Type: Bug
Components: camel-jms
Affects Versions: 2.11.1
Reporter: Martin Lichtin
Assignee: Claus Ibsen
Fix For: 2.11.3, 2.12.3, 2.13.0
The use case is about using Camel to communicate with the ActiveMQ
StatisticsPlugin:
Need to send a message and set 'JMSReplyTo' with a destination for the
response message(s). Doing this as part of a Camel processor:
in.setHeader(JMSReplyTo, topic://mydest);
This, however, results in the broker (ie. the statistics plugin) returning
messages to the mydest queue, as opposed to the topic.
The issue is that Camel starts fiddling with the 'JMSReplyTo' header.
Enabling trace level shows how Camel coerces the topic into a queue:
JmsProducer | amel.component.jms.JmsProducer$2 315 | 126 -
org.apache.camel.camel-jms - 2.11.1 | Normalized JMSReplyTo destination name
topic://jmsqueuemonitor - jmsqueuemonitor
JmsProducer | amel.component.jms.JmsProducer$2 315 | 126 -
org.apache.camel.camel-jms - 2.11.1 | Normalized JMSReplyTo destination name
topic://jmsqueuemonitor - jmsqueuemonitor
JmsProducer | amel.component.jms.JmsProducer$2 331 | 126 -
org.apache.camel.camel-jms - 2.11.1 | Creating JMSReplyTo queue:
jmsqueuemonitor
JmsProducer | amel.component.jms.JmsProducer$2 331 | 126 -
org.apache.camel.camel-jms - 2.11.1 | Creating JMSReplyTo queue:
jmsqueuemonitor
JmsProducer | amel.component.jms.JmsProducer$2 343 | 126 -
org.apache.camel.camel-jms - 2.11.1 | Using JMSReplyTo destination:
queue://jmsqueuemonitor
JmsProducer | amel.component.jms.JmsProducer$2 343 | 126 -
org.apache.camel.camel-jms - 2.11.1 | Using JMSReplyTo destination:
queue://jmsqueuemonitor
Camel seems to apply some logic that is faulty in this circumstance.
Just want to send a message to a queue and have that message carry a
'JMSReplyTo' value that should be left untouched.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (CAMEL-7049) Cannot set JMSReplyTo with a topic destination when sending a message to a queue
Martin Lichtin created CAMEL-7049: - Summary: Cannot set JMSReplyTo with a topic destination when sending a message to a queue Key: CAMEL-7049 URL: https://issues.apache.org/jira/browse/CAMEL-7049 Project: Camel Issue Type: Bug Components: camel-jms Affects Versions: 2.11.1 Reporter: Martin Lichtin The use case is about using Camel to communicate with the ActiveMQ StatisticsPlugin: Need to send a message and set 'JMSReplyTo' with a destination for the response message(s). Doing this as part of a Camel processor: in.setHeader(JMSReplyTo, topic://mydest); This, however, results in the broker (ie. the statistics plugin) returning messages to the mydest queue, as opposed to the topic. The issue is that Camel starts fiddling with the 'JMSReplyTo' header. Enabling trace level shows how Camel coerces the topic into a queue: JmsProducer | amel.component.jms.JmsProducer$2 315 | 126 - org.apache.camel.camel-jms - 2.11.1 | Normalized JMSReplyTo destination name topic://jmsqueuemonitor - jmsqueuemonitor JmsProducer | amel.component.jms.JmsProducer$2 315 | 126 - org.apache.camel.camel-jms - 2.11.1 | Normalized JMSReplyTo destination name topic://jmsqueuemonitor - jmsqueuemonitor JmsProducer | amel.component.jms.JmsProducer$2 331 | 126 - org.apache.camel.camel-jms - 2.11.1 | Creating JMSReplyTo queue: jmsqueuemonitor JmsProducer | amel.component.jms.JmsProducer$2 331 | 126 - org.apache.camel.camel-jms - 2.11.1 | Creating JMSReplyTo queue: jmsqueuemonitor JmsProducer | amel.component.jms.JmsProducer$2 343 | 126 - org.apache.camel.camel-jms - 2.11.1 | Using JMSReplyTo destination: queue://jmsqueuemonitor JmsProducer | amel.component.jms.JmsProducer$2 343 | 126 - org.apache.camel.camel-jms - 2.11.1 | Using JMSReplyTo destination: queue://jmsqueuemonitor Camel seems to apply some logic that is faulty in this circumstance. Just want to send a message to a queue and have that message carry a 'JMSReplyTo' value that should be left untouched. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
