[jira] [Created] (CAMEL-7160) Throttling has problems with rate changes
Michael Pisula created CAMEL-7160: - Summary: Throttling has problems with rate changes Key: CAMEL-7160 URL: https://issues.apache.org/jira/browse/CAMEL-7160 Project: Camel Issue Type: Bug Reporter: Michael Pisula When using the throttler with the header expression for controlling the rate, changing the rate does not work reliably. Some more information can be found in the following mail thread: http://camel.465427.n5.nabble.com/Problems-with-dynamic-throttling-td5746613.html -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CAMEL-7161) camel-dozer - Can cause dead-lock in init when using spring
[
https://issues.apache.org/jira/browse/CAMEL-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-7161.
Resolution: Fixed
camel-dozer - Can cause dead-lock in init when using spring
---
Key: CAMEL-7161
URL: https://issues.apache.org/jira/browse/CAMEL-7161
Project: Camel
Issue Type: Bug
Affects Versions: 2.12.2
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.12.3, 2.13.0
When using spring with dozer, and we call init in the ctr, then spring can
cause a dead lock when it does its getBean stuff.
{code}
java.lang.Thread.State: BLOCKED (on object monitor)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:182)
- waiting to lock 0x0007d7c4ca38 (a
java.util.concurrent.ConcurrentHashMap)
at
org.springframework.beans.factory.support.AbstractBeanFactory.isTypeMatch(AbstractBeanFactory.java:468)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.doGetBeanNamesForType(DefaultListableBeanFactory.java:356)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanNamesForType(DefaultListableBeanFactory.java:334)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeansOfType(DefaultListableBeanFactory.java:434)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeansOfType(DefaultListableBeanFactory.java:428)
at
org.springframework.context.support.AbstractApplicationContext.getBeansOfType(AbstractApplicationContext.java:1182)
at
org.springframework.beans.factory.BeanFactoryUtils.beansOfTypeIncludingAncestors(BeanFactoryUtils.java:228)
at
org.apache.camel.spring.spi.ApplicationContextRegistry.findByTypeWithName(ApplicationContextRegistry.java:85)
at
org.apache.camel.impl.PropertyPlaceholderDelegateRegistry.findByTypeWithName(PropertyPlaceholderDelegateRegistry.java:70)
at
org.apache.camel.converter.dozer.DozerTypeConverterLoader.lookupDozerBeanMapperConfigurations(DozerTypeConverterLoader.java:228)
at
org.apache.camel.converter.dozer.DozerTypeConverterLoader.init(DozerTypeConverterLoader.java:155)
{code}
We should defer init to a bit later, and turn the loader into a service so
init is done like the others with start|stop methods.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (CAMEL-7160) Throttling has problems with rate changes
[ https://issues.apache.org/jira/browse/CAMEL-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Pisula updated CAMEL-7160: -- Attachment: (was: CAMEL-7160.patch) Throttling has problems with rate changes - Key: CAMEL-7160 URL: https://issues.apache.org/jira/browse/CAMEL-7160 Project: Camel Issue Type: Bug Reporter: Michael Pisula When using the throttler with the header expression for controlling the rate, changing the rate does not work reliably. Some more information can be found in the following mail thread: http://camel.465427.n5.nabble.com/Problems-with-dynamic-throttling-td5746613.html -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CAMEL-6555) camel-netty - Upgrade to Netty 4 or 5
[ https://issues.apache.org/jira/browse/CAMEL-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889352#comment-13889352 ] Claus Ibsen commented on CAMEL-6555: No its massive work and postponed for later when someone may get the time. We love contributions so you are much welcome to get started on this. I suggest to fork and work on a separate branch. And when ready we can merge to the master branch, or just .zip the code and we can add that. camel-netty - Upgrade to Netty 4 or 5 - Key: CAMEL-6555 URL: https://issues.apache.org/jira/browse/CAMEL-6555 Project: Camel Issue Type: Task Components: camel-netty Reporter: Claus Ibsen Fix For: Future Netty 4.0 has been released. We should upgrade, though it has new package names. So end users with custom codec need to migrate as well. So we could indicate that after Camel 2.12 we upgrade to give ppl amble time to adjust. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CAMEL-7162) [Bean Validator] Bean Validator should try to resolve ValidationProviderResolver reference
Henryk Konsek created CAMEL-7162:
Summary: [Bean Validator] Bean Validator should try to resolve
ValidationProviderResolver reference
Key: CAMEL-7162
URL: https://issues.apache.org/jira/browse/CAMEL-7162
Project: Camel
Issue Type: Improvement
Reporter: Henryk Konsek
Assignee: Henryk Konsek
Fix For: 2.13.0
Currently it is impossible to provide non-default
{{ValidationProviderResolver}} when creating Bean Validator endpoint. Component
should lookup for the {{ValidationProviderResolver}} the same way it looks up
for the {{MessageInterpolator}} or {{TraversableResolver}}.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Resolved] (CAMEL-7162) [Bean Validator] Bean Validator should try to resolve ValidationProviderResolver reference
[
https://issues.apache.org/jira/browse/CAMEL-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henryk Konsek resolved CAMEL-7162.
--
Resolution: Fixed
Fixed in 4c2150884f24e5d70d89066797465d690804b1c5.
[Bean Validator] Bean Validator should try to resolve
ValidationProviderResolver reference
--
Key: CAMEL-7162
URL: https://issues.apache.org/jira/browse/CAMEL-7162
Project: Camel
Issue Type: Improvement
Reporter: Henryk Konsek
Assignee: Henryk Konsek
Fix For: 2.13.0
Currently it is impossible to provide non-default
{{ValidationProviderResolver}} when creating Bean Validator endpoint.
Component should lookup for the {{ValidationProviderResolver}} the same way
it looks up for the {{MessageInterpolator}} or {{TraversableResolver}}.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (CAMEL-7160) Throttling has problems with rate changes
[ https://issues.apache.org/jira/browse/CAMEL-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-7160: --- Component/s: eip camel-core Affects Version/s: 2.12.2 Throttling has problems with rate changes - Key: CAMEL-7160 URL: https://issues.apache.org/jira/browse/CAMEL-7160 Project: Camel Issue Type: Bug Components: camel-core, eip Affects Versions: 2.12.2 Reporter: Michael Pisula Assignee: Claus Ibsen Fix For: 2.11.4, 2.12.3, 2.13.0 Attachments: CAMEL-7160.patch When using the throttler with the header expression for controlling the rate, changing the rate does not work reliably. Some more information can be found in the following mail thread: http://camel.465427.n5.nabble.com/Problems-with-dynamic-throttling-td5746613.html -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CAMEL-7160) Throttling has problems with rate changes
[ https://issues.apache.org/jira/browse/CAMEL-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-7160: -- Assignee: Claus Ibsen Throttling has problems with rate changes - Key: CAMEL-7160 URL: https://issues.apache.org/jira/browse/CAMEL-7160 Project: Camel Issue Type: Bug Components: camel-core, eip Affects Versions: 2.12.2 Reporter: Michael Pisula Assignee: Claus Ibsen Fix For: 2.11.4, 2.12.3, 2.13.0 Attachments: CAMEL-7160.patch When using the throttler with the header expression for controlling the rate, changing the rate does not work reliably. Some more information can be found in the following mail thread: http://camel.465427.n5.nabble.com/Problems-with-dynamic-throttling-td5746613.html -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CAMEL-7160) Throttling has problems with rate changes
[ https://issues.apache.org/jira/browse/CAMEL-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-7160: --- Fix Version/s: 2.13.0 2.12.3 2.11.4 Throttling has problems with rate changes - Key: CAMEL-7160 URL: https://issues.apache.org/jira/browse/CAMEL-7160 Project: Camel Issue Type: Bug Components: camel-core, eip Affects Versions: 2.12.2 Reporter: Michael Pisula Fix For: 2.11.4, 2.12.3, 2.13.0 Attachments: CAMEL-7160.patch When using the throttler with the header expression for controlling the rate, changing the rate does not work reliably. Some more information can be found in the following mail thread: http://camel.465427.n5.nabble.com/Problems-with-dynamic-throttling-td5746613.html -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CAMEL-7160) Throttling has problems with rate changes
[ https://issues.apache.org/jira/browse/CAMEL-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-7160. Resolution: Fixed Thanks for reporting and the patch. Throttling has problems with rate changes - Key: CAMEL-7160 URL: https://issues.apache.org/jira/browse/CAMEL-7160 Project: Camel Issue Type: Bug Components: camel-core, eip Affects Versions: 2.12.2 Reporter: Michael Pisula Assignee: Claus Ibsen Fix For: 2.11.4, 2.12.3, 2.13.0 Attachments: CAMEL-7160.patch When using the throttler with the header expression for controlling the rate, changing the rate does not work reliably. Some more information can be found in the following mail thread: http://camel.465427.n5.nabble.com/Problems-with-dynamic-throttling-td5746613.html -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CAMEL-7156) SpringCamelContext should shut down cleanly
[
https://issues.apache.org/jira/browse/CAMEL-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-7156:
---
Fix Version/s: Future
Issue Type: Improvement (was: Bug)
SpringCamelContext should shut down cleanly
---
Key: CAMEL-7156
URL: https://issues.apache.org/jira/browse/CAMEL-7156
Project: Camel
Issue Type: Improvement
Components: camel-spring
Affects Versions: 2.12.2
Environment: spring application context
Reporter: John Mark
Fix For: Future
The CamelContext does not shutdown properly when running inside a Spring
ApplicationContext. Upon shutdown I get a lot of the following errors:
{noformat}
org.apache.camel.RuntimeCamelException:
org.springframework.beans.factory.BeanCreationNotAllowedException: Error
creating bean with name 'someBean': Singleton bean creation not allowed while
the singletons of this factory are in destruction (Do not request a bean from
a BeanFactory in a destroy method implementation!)
at
org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1196)
at
org.apache.camel.impl.PropertyPlaceholderDelegateRegistry.lookup(PropertyPlaceholderDelegateRegistry.java:51)
at
org.apache.camel.component.bean.RegistryBean.lookupBean(RegistryBean.java:136)
at
org.apache.camel.component.bean.RegistryBean.getBean(RegistryBean.java:62)
at
org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:83)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:71)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:322)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:213)
at
org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:303)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:117)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:80)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.ChoiceProcessor.process(ChoiceProcessor.java:85)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:71)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:322)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:213)
at
org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:303)
at
[jira] [Commented] (CAMEL-7156) SpringCamelContext should shut down cleanly
[
https://issues.apache.org/jira/browse/CAMEL-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889486#comment-13889486
]
Claus Ibsen commented on CAMEL-7156:
Would require us to drop spring 3.1 support and spring 3.2 as minimum version.
I guess that would be acceptable from Camel 2.13 onwards.
SpringCamelContext should shut down cleanly
---
Key: CAMEL-7156
URL: https://issues.apache.org/jira/browse/CAMEL-7156
Project: Camel
Issue Type: Improvement
Components: camel-spring
Affects Versions: 2.12.2
Environment: spring application context
Reporter: John Mark
Fix For: Future
The CamelContext does not shutdown properly when running inside a Spring
ApplicationContext. Upon shutdown I get a lot of the following errors:
{noformat}
org.apache.camel.RuntimeCamelException:
org.springframework.beans.factory.BeanCreationNotAllowedException: Error
creating bean with name 'someBean': Singleton bean creation not allowed while
the singletons of this factory are in destruction (Do not request a bean from
a BeanFactory in a destroy method implementation!)
at
org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1196)
at
org.apache.camel.impl.PropertyPlaceholderDelegateRegistry.lookup(PropertyPlaceholderDelegateRegistry.java:51)
at
org.apache.camel.component.bean.RegistryBean.lookupBean(RegistryBean.java:136)
at
org.apache.camel.component.bean.RegistryBean.getBean(RegistryBean.java:62)
at
org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:83)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:71)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:322)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:213)
at
org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:303)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:117)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:80)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.ChoiceProcessor.process(ChoiceProcessor.java:85)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:71)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:322)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:213)
at
org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
[jira] [Commented] (CAMEL-7156) SpringCamelContext should shut down cleanly
[
https://issues.apache.org/jira/browse/CAMEL-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889490#comment-13889490
]
Claus Ibsen commented on CAMEL-7156:
Started discussion about dropping spring 3.1 support
http://camel.465427.n5.nabble.com/DISCUSS-Drop-Spring-3-1-support-in-Camel-2-13-onwards-tp5746724.html
SpringCamelContext should shut down cleanly
---
Key: CAMEL-7156
URL: https://issues.apache.org/jira/browse/CAMEL-7156
Project: Camel
Issue Type: Improvement
Components: camel-spring
Affects Versions: 2.12.2
Environment: spring application context
Reporter: John Mark
Fix For: Future
The CamelContext does not shutdown properly when running inside a Spring
ApplicationContext. Upon shutdown I get a lot of the following errors:
{noformat}
org.apache.camel.RuntimeCamelException:
org.springframework.beans.factory.BeanCreationNotAllowedException: Error
creating bean with name 'someBean': Singleton bean creation not allowed while
the singletons of this factory are in destruction (Do not request a bean from
a BeanFactory in a destroy method implementation!)
at
org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1196)
at
org.apache.camel.impl.PropertyPlaceholderDelegateRegistry.lookup(PropertyPlaceholderDelegateRegistry.java:51)
at
org.apache.camel.component.bean.RegistryBean.lookupBean(RegistryBean.java:136)
at
org.apache.camel.component.bean.RegistryBean.getBean(RegistryBean.java:62)
at
org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:83)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:71)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:322)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:213)
at
org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:303)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:117)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:80)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.ChoiceProcessor.process(ChoiceProcessor.java:85)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:71)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:322)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:213)
at
org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
[jira] [Resolved] (CAMEL-7159) camel-bindy not picking up @Link annotation items
[ https://issues.apache.org/jira/browse/CAMEL-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Anstey resolved CAMEL-7159. Resolution: Fixed camel-bindy not picking up @Link annotation items - Key: CAMEL-7159 URL: https://issues.apache.org/jira/browse/CAMEL-7159 Project: Camel Issue Type: Bug Affects Versions: 2.12.2 Reporter: Jonathan Anstey Assignee: Jonathan Anstey Fix For: 2.11.4, 2.12.3, 2.13.0 It works fine (like in the tests) when you provide bindy with a MapString, Object of model objects corresponding to the @Linked-ed classes. We should do better though and try to figure this out for users. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CAMEL-7155) Incorrect implementation of the method StringHelper.hasStartToken()
[
https://issues.apache.org/jira/browse/CAMEL-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889496#comment-13889496
]
Claus Ibsen commented on CAMEL-7155:
Thomas, are you working on a patch?
Incorrect implementation of the method StringHelper.hasStartToken()
---
Key: CAMEL-7155
URL: https://issues.apache.org/jira/browse/CAMEL-7155
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.12.2
Reporter: Tomas Rohovsky
Priority: Minor
From the semantic point of view the method hasStartToken() should return
false in case of an expression without language specified, i.e. starting with
${.
However, it is correct to return true in current usage of hasStartToken() in
camel-core, i.e. checking if an expression is in simple language, since if
the expression does not contain the language token, then it is a simple
expression.
The method calls for checking of simple language should be replaced with a
newly created method isSimpleLanguage(String expression) that would check if
the language is a simple expression, i.e. hasStartToken(expression, simple)
|| expression.indexOf(${) = 0.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Resolved] (CAMEL-7139) Problem with MvelExpression class visibility between camel bundles
[
https://issues.apache.org/jira/browse/CAMEL-7139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-7139.
Resolution: Fixed
Fix Version/s: 2.11.4
Thanks for the patch.
Problem with MvelExpression class visibility between camel bundles
--
Key: CAMEL-7139
URL: https://issues.apache.org/jira/browse/CAMEL-7139
Project: Camel
Issue Type: Bug
Components: osgi
Affects Versions: 2.12.2
Reporter: Andrzej Majewski
Assignee: Claus Ibsen
Fix For: 2.11.4, 2.12.3, 2.13.0
Attachments: CAMEL-7139.patch.txt, mvelItest.path.txt
http://camel.465427.n5.nabble.com/Problem-with-camel-routes-running-in-apache-karaf-2-3-3-td5745929.html
I am having problems with with class visibility between osgi bundles when
using camel 2.12 and 2.13-SNAPSHOT. I have created a showcase to reproduce
the problem based on camel example projects. I have tested the created
solution in camel 2.10 and problem does not exist.
I have created a sample application which is able to reproduce the problem.
Please pick it up from my forked repo:
https://github.com/andrzej-majewski/camel/tree/MvelExpression-class-visibility
The problem occurs when
- camel-example-osgi-domain - project containing only domain classes required
by different osgi projects ex.( org.apache.camel.example.osgi.domain.MyPojo )
- camel-example-osgi-mvel - example project which has dependency on
camel-example-osgi-domain
Now camel-example-osgi-mvel has following camel context.
{code}
?xml version=1.0 encoding=UTF-8?
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:camel=http://camel.apache.org/schema/spring;
xsi:schemaLocation=
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd;
camelContext xmlns=http://camel.apache.org/schema/spring;
route
from uri=timer://mytestTrigger?fixedRate=trueamp;period=1/
to uri=myTestFactory/
/route
route id=mvelTest
from uri=seda://myMvelTest?concurrentConsumers=2/
choice
when
mvelrequest.body instanceof
org.apache.camel.example.osgi.MyPojo/mvel
to uri=log:MvelRouter/
/when
/choice
/route
/camelContext
bean id=myTestFactory
class=org.apache.camel.example.osgi.MyTestFactory
property name=numberOfMessages value=2/
/bean
/beans
{code}
When I deploy both feature to karaf and place a message on seda://myMvelTest
queue I get following exception in karaf.
{code}
ERROR | eda://myMvelTest | DefaultErrorHandler |
rg.apache.camel.util.CamelLogger 215 | 73 - org.apache.camel.camel-core -
2.13.0.SNAPSHOT | Failed delivery for (MessageId:
ID-localhost-51000-1389691121739-1-56 on ExchangeId:
ID-localhost-51000-1389691121739-1-85). Exhausted after delivery attempt: 1
caught: org.apache.camel.ExpressionEvaluationException: [Error: could not
access: org; in class: org.apache.camel.language.mvel.RootObject]
[Near : {... est.body instanceof org.apache.camel.example.osgi. }]
^
[Line: 1, Column: 25]
Message History
---
RouteId ProcessorId Processor
Elapsed (ms)
[mvelTest ] [mvelTest ]
[seda://myMvelTest?concurrentConsumers=2
] [14]
[mvelTest ] [choice2 ] [when[mvel{Mvel[request.body
instanceof org.apache.camel.example.osgi.MyPojo]}]] [ 0]
Exchange
---
Exchange[
Id ID-localhost-51000-1389691121739-1-85
ExchangePattern InOut
Headers
{breadcrumbId=ID-localhost-51000-1389691121739-1-56, CamelRedelivered=false,
CamelRedeliveryCounter=0}
BodyTypeorg.apache.camel.example.osgi.MyPojo
Bodyorg.apache.camel.example.osgi.MyPojo@21093d9e
]
Stacktrace
---
org.apache.camel.ExpressionEvaluationException: [Error: could not access:
org; in class:
[jira] [Commented] (CAMEL-7146) NPE in Aggregator when completionSize = 1
[
https://issues.apache.org/jira/browse/CAMEL-7146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889552#comment-13889552
]
Stefan Burkard commented on CAMEL-7146:
---
I edited the description of the issue since I analyzed the issue in the Camel
code.
In the method doAggregation the aggregator evaluates if the aggregation is
complete. With completionSize = 1 this is the case on every Exchange. Therefore
the aggregator does not persist the Exchanges, but skips this part:
{code:title=AggregateProcessor.java|borderStyle=solid}
...
if (complete == null) {
doAggregationRepositoryAdd(newExchange.getContext(), key,
originalExchange, answer);
// we are not complete so the answer should be null
answer = null;
} else {
...
{code}
On the other hand does the method onCompletion no such evaluation and tries
to delete the Exchange in the Repository. Therefore the NPE.
NPE in Aggregator when completionSize = 1
-
Key: CAMEL-7146
URL: https://issues.apache.org/jira/browse/CAMEL-7146
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.12.2
Reporter: Stefan Burkard
Priority: Trivial
Labels: aggregator
Attachments: Camel-7146-example.tgz, Camel-7146-stacktrace.txt
A Camel aggregator with persistence repository cannot have a completionSize
of 1. If this is configured, every message produces a NPE with the attached
stacktrace.
I have also attached a small example project that shows the Exception. As
soon as the completionSize is 1, it runs fine.
This is just a minor flaw, since I cannot think about a really useful case
with completionSize 1, but it worked with earlier versions of Camel.
As an alternative (if completionSize 1 should not be used), Camel could throw
an error during Context startup when completionSize 2.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (CAMEL-7156) SpringCamelContext should shut down cleanly
[
https://issues.apache.org/jira/browse/CAMEL-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889738#comment-13889738
]
John Mark commented on CAMEL-7156:
--
Why would you need to drop support for Spring 3.1? SmartLifecycle has been
around since 3.0 (at least according to its javadocs).
SpringCamelContext should shut down cleanly
---
Key: CAMEL-7156
URL: https://issues.apache.org/jira/browse/CAMEL-7156
Project: Camel
Issue Type: Improvement
Components: camel-spring
Affects Versions: 2.12.2
Environment: spring application context
Reporter: John Mark
Fix For: Future
The CamelContext does not shutdown properly when running inside a Spring
ApplicationContext. Upon shutdown I get a lot of the following errors:
{noformat}
org.apache.camel.RuntimeCamelException:
org.springframework.beans.factory.BeanCreationNotAllowedException: Error
creating bean with name 'someBean': Singleton bean creation not allowed while
the singletons of this factory are in destruction (Do not request a bean from
a BeanFactory in a destroy method implementation!)
at
org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1196)
at
org.apache.camel.impl.PropertyPlaceholderDelegateRegistry.lookup(PropertyPlaceholderDelegateRegistry.java:51)
at
org.apache.camel.component.bean.RegistryBean.lookupBean(RegistryBean.java:136)
at
org.apache.camel.component.bean.RegistryBean.getBean(RegistryBean.java:62)
at
org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:83)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:71)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:322)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:213)
at
org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:303)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:117)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:80)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.ChoiceProcessor.process(ChoiceProcessor.java:85)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:71)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:322)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:213)
at
org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
[jira] [Created] (CAMEL-7163) BacklogDebugger - Should not change body/header type to string
Claus Ibsen created CAMEL-7163: -- Summary: BacklogDebugger - Should not change body/header type to string Key: CAMEL-7163 URL: https://issues.apache.org/jira/browse/CAMEL-7163 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.12.2 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.12.3, 2.13.0 When using the backlog debugger then updating the body/headers would currently force those to become string type. We should preserve existing type, and allow end users to specify a new type. And also make it possible to remove body/headers as well. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CAMEL-7163) BacklogDebugger - Should not change body/header type to string
[ https://issues.apache.org/jira/browse/CAMEL-7163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-7163. Resolution: Fixed BacklogDebugger - Should not change body/header type to string -- Key: CAMEL-7163 URL: https://issues.apache.org/jira/browse/CAMEL-7163 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.12.2 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.12.3, 2.13.0 When using the backlog debugger then updating the body/headers would currently force those to become string type. We should preserve existing type, and allow end users to specify a new type. And also make it possible to remove body/headers as well. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CAMEL-7092) Add camel-kafka component
[ https://issues.apache.org/jira/browse/CAMEL-7092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889981#comment-13889981 ] stephen samuel commented on CAMEL-7092: --- Is there still interest in this awesome contribution :) Add camel-kafka component - Key: CAMEL-7092 URL: https://issues.apache.org/jira/browse/CAMEL-7092 Project: Camel Issue Type: New Feature Affects Versions: 2.13.0 Reporter: Hadrian Zbarcea Assignee: Hadrian Zbarcea See thread request pull from github fork: http://camel.465427.n5.nabble.com/camel-pull-request-Added-Apache-Kafka-component-td5745174.html -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CAMEL-7164) TypeConverterRegistry - More JMX details
Claus Ibsen created CAMEL-7164: -- Summary: TypeConverterRegistry - More JMX details Key: CAMEL-7164 URL: https://issues.apache.org/jira/browse/CAMEL-7164 Project: Camel Issue Type: Improvement Components: camel-core, jmx Affects Versions: 2.12.2 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.12.3, 2.13.0 The type converter registry mbean has a little details today. But we should also include information on number of type converters in the registry, and allow end users to query if a converter exists, and as well browse the converters etc. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
