[jira] [Resolved] (CAMEL-11467) Camel-bindy tests fail depending on the locale
[
https://issues.apache.org/jira/browse/CAMEL-11467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved CAMEL-11467.
-
Resolution: Fixed
Fix Version/s: 2.20.0
> Camel-bindy tests fail depending on the locale
> --
>
> Key: CAMEL-11467
> URL: https://issues.apache.org/jira/browse/CAMEL-11467
> Project: Camel
> Issue Type: Bug
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 2.20.0
>
>
> I end up with the following:
> {code}
> [ERROR] Failures:
> [ERROR]
> org.apache.camel.dataformat.bindy.fixed.BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage(org.apache.camel.dataformat.bindy.fixed.BindyMarshallUnmarshallWithDefaultValueTest)
> [ERROR] Run 1:
> BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage:56
> mock://resultMarshal Body of message: 0. Expected: <10A9 JohnDoe
> ISINXD12345678BUYShare02500.45USD01-08-2009
> > but was: <10A9 JohnDoe ISINXD12345678BUYShare02500,45USD01-08-2009
> >
> >
> [ERROR] Run 2:
> BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage:56
> mock://resultMarshal Body of message: 0. Expected: <10A9 JohnDoe
> ISINXD12345678BUYShare02500.45USD01-08-2009
> > but was: <10A9 JohnDoe ISINXD12345678BUYShare02500,45USD01-08-2009
> >
> >
> [ERROR] Run 3:
> BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage:56
> mock://resultMarshal Body of message: 0. Expected: <10A9 JohnDoe
> ISINXD12345678BUYShare02500.45USD01-08-2009
> > but was: <10A9 JohnDoe ISINXD12345678BUYShare02500,45USD01-08-2009
> >
> >
> {code}
> My system decimal separator is set to ',' instead of '.' which causes the
> failures.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (CAMEL-11464) Upgrade to rhino 1.7.7.1
[ https://issues.apache.org/jira/browse/CAMEL-11464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved CAMEL-11464. - Resolution: Fixed > Upgrade to rhino 1.7.7.1 > > > Key: CAMEL-11464 > URL: https://issues.apache.org/jira/browse/CAMEL-11464 > Project: Camel > Issue Type: Improvement > Components: camel-script >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 2.20.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11459) Upgrade CXF to 3.2
[ https://issues.apache.org/jira/browse/CAMEL-11459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065558#comment-16065558 ] onder sezgin commented on CAMEL-11459: -- With the current 3.2.0 snaphot: [INFO] Results: [INFO] [WARNING] Tests run: 450, Failures: 0, Errors: 0, Skipped: 2 [INFO] [INFO] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 01:52 min [INFO] Finished at: 2017-06-28T01:08:54+03:00 [INFO] Final Memory: 45M/990M [INFO] > Upgrade CXF to 3.2 > -- > > Key: CAMEL-11459 > URL: https://issues.apache.org/jira/browse/CAMEL-11459 > Project: Camel > Issue Type: Improvement >Reporter: Guillaume Nodet > Fix For: 2.20.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11469) Camel-Hipchat - Configure via xml is broken
[
https://issues.apache.org/jira/browse/CAMEL-11469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065547#comment-16065547
]
ASF GitHub Bot commented on CAMEL-11469:
GitHub user w4tson opened a pull request:
https://github.com/apache/camel/pull/1793
CAMEL-11469 Use remainder of uri to parse config
The configuration now uses the remainder of the uri to parse out the
properties. This can now cope with a '//' or not and stops further string
manipulation where it isn't needed.
CAMEL-9495 was fixing parsing logic and seemed to knock it out. I'm not
super familiar with camel core but it looks like the 'remaining' URI is already
being passed in so it seems silly to attempt this again?
Also I had to work hard a bit not to introduce a dependency on spring in
order to reproduce this. My work around is to manually load in the route from
XML. It's quite clunky the way I've done it. If there's a smoother way, please
advise.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/w4tson/camel
CAMEL-11469-hipchat-endpoint-uri-problem
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1793.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1793
commit 202daa5f8145669880c0d7f61e01ae9a3308c249
Author: Paul Watson
Date: 2017-06-27T21:51:15Z
CAMEL-11469 Use remainder of uri to parse config
The configuration now uses the remainder of the uri to parse out the
properties. This can now cope with a '//' or not and stops further string
manipulation where it isn't needed
> Camel-Hipchat - Configure via xml is broken
> ---
>
> Key: CAMEL-11469
> URL: https://issues.apache.org/jira/browse/CAMEL-11469
> Project: Camel
> Issue Type: Bug
> Components: camel-hipcat
>Affects Versions: 2.19.1
>Reporter: Paul Watson
>Priority: Minor
>
> Declaring a hipchat endpoint in XML misconfigures the same component in the
> DSL. This seems to be because at some point via XML the component URI get's
> normalized and '//' is introduced.
> This means a component of
> {{}}
> Is actually configured to the default api.hipchat.com.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (CAMEL-11469) Camel-Hipchat - Configure via xml is broken
Paul Watson created CAMEL-11469:
---
Summary: Camel-Hipchat - Configure via xml is broken
Key: CAMEL-11469
URL: https://issues.apache.org/jira/browse/CAMEL-11469
Project: Camel
Issue Type: Bug
Components: camel-hipcat
Affects Versions: 2.19.1
Reporter: Paul Watson
Priority: Minor
Declaring a hipchat endpoint in XML misconfigures the same component in the
DSL. This seems to be because at some point via XML the component URI get's
normalized and '//' is introduced.
This means a component of
{{}}
Is actually configured to the default api.hipchat.com.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-11467) Camel-bindy tests fail depending on the locale
[
https://issues.apache.org/jira/browse/CAMEL-11467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065500#comment-16065500
]
Guillaume Nodet commented on CAMEL-11467:
-
Yes, and no. I have a fix to set the system properties, as they need to be set
for surefire VM. I'm just running the full build before committing.
> Camel-bindy tests fail depending on the locale
> --
>
> Key: CAMEL-11467
> URL: https://issues.apache.org/jira/browse/CAMEL-11467
> Project: Camel
> Issue Type: Bug
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Minor
>
> I end up with the following:
> {code}
> [ERROR] Failures:
> [ERROR]
> org.apache.camel.dataformat.bindy.fixed.BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage(org.apache.camel.dataformat.bindy.fixed.BindyMarshallUnmarshallWithDefaultValueTest)
> [ERROR] Run 1:
> BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage:56
> mock://resultMarshal Body of message: 0. Expected: <10A9 JohnDoe
> ISINXD12345678BUYShare02500.45USD01-08-2009
> > but was: <10A9 JohnDoe ISINXD12345678BUYShare02500,45USD01-08-2009
> >
> >
> [ERROR] Run 2:
> BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage:56
> mock://resultMarshal Body of message: 0. Expected: <10A9 JohnDoe
> ISINXD12345678BUYShare02500.45USD01-08-2009
> > but was: <10A9 JohnDoe ISINXD12345678BUYShare02500,45USD01-08-2009
> >
> >
> [ERROR] Run 3:
> BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage:56
> mock://resultMarshal Body of message: 0. Expected: <10A9 JohnDoe
> ISINXD12345678BUYShare02500.45USD01-08-2009
> > but was: <10A9 JohnDoe ISINXD12345678BUYShare02500,45USD01-08-2009
> >
> >
> {code}
> My system decimal separator is set to ',' instead of '.' which causes the
> failures.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (CAMEL-11468) locale setting should be ROOT to avoid different system complications
onder sezgin created CAMEL-11468: Summary: locale setting should be ROOT to avoid different system complications Key: CAMEL-11468 URL: https://issues.apache.org/jira/browse/CAMEL-11468 Project: Camel Issue Type: Improvement Components: camel-core Reporter: onder sezgin Assignee: onder sezgin Depending on the system settings locale may cause trouble in execution time, our code may fail even though it is actually correct. We can follow the suggestions here; https://dzone.com/articles/forbidden-apis-of-java -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11468) locale setting should be ROOT to avoid different system complications
[ https://issues.apache.org/jira/browse/CAMEL-11468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin updated CAMEL-11468: - Priority: Minor (was: Major) > locale setting should be ROOT to avoid different system complications > - > > Key: CAMEL-11468 > URL: https://issues.apache.org/jira/browse/CAMEL-11468 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: onder sezgin >Assignee: onder sezgin >Priority: Minor > > Depending on the system settings locale may cause trouble in execution time, > our code may fail even though it is actually correct. > We can follow the suggestions here; > https://dzone.com/articles/forbidden-apis-of-java -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11467) Camel-bindy tests fail depending on the locale
[
https://issues.apache.org/jira/browse/CAMEL-11467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065481#comment-16065481
]
onder sezgin commented on CAMEL-11467:
--
I suppose there is a workaround to set either system locale or jvm args to set.
eg:
https://stackoverflow.com/questions/8809098/how-do-i-set-the-default-locale-for-my-jvm
> Camel-bindy tests fail depending on the locale
> --
>
> Key: CAMEL-11467
> URL: https://issues.apache.org/jira/browse/CAMEL-11467
> Project: Camel
> Issue Type: Bug
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Minor
>
> I end up with the following:
> {code}
> [ERROR] Failures:
> [ERROR]
> org.apache.camel.dataformat.bindy.fixed.BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage(org.apache.camel.dataformat.bindy.fixed.BindyMarshallUnmarshallWithDefaultValueTest)
> [ERROR] Run 1:
> BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage:56
> mock://resultMarshal Body of message: 0. Expected: <10A9 JohnDoe
> ISINXD12345678BUYShare02500.45USD01-08-2009
> > but was: <10A9 JohnDoe ISINXD12345678BUYShare02500,45USD01-08-2009
> >
> >
> [ERROR] Run 2:
> BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage:56
> mock://resultMarshal Body of message: 0. Expected: <10A9 JohnDoe
> ISINXD12345678BUYShare02500.45USD01-08-2009
> > but was: <10A9 JohnDoe ISINXD12345678BUYShare02500,45USD01-08-2009
> >
> >
> [ERROR] Run 3:
> BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage:56
> mock://resultMarshal Body of message: 0. Expected: <10A9 JohnDoe
> ISINXD12345678BUYShare02500.45USD01-08-2009
> > but was: <10A9 JohnDoe ISINXD12345678BUYShare02500,45USD01-08-2009
> >
> >
> {code}
> My system decimal separator is set to ',' instead of '.' which causes the
> failures.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (CAMEL-11467) Camel-bindy tests fail depending on the locale
[
https://issues.apache.org/jira/browse/CAMEL-11467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
onder sezgin updated CAMEL-11467:
-
Priority: Minor (was: Major)
> Camel-bindy tests fail depending on the locale
> --
>
> Key: CAMEL-11467
> URL: https://issues.apache.org/jira/browse/CAMEL-11467
> Project: Camel
> Issue Type: Bug
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Minor
>
> I end up with the following:
> {code}
> [ERROR] Failures:
> [ERROR]
> org.apache.camel.dataformat.bindy.fixed.BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage(org.apache.camel.dataformat.bindy.fixed.BindyMarshallUnmarshallWithDefaultValueTest)
> [ERROR] Run 1:
> BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage:56
> mock://resultMarshal Body of message: 0. Expected: <10A9 JohnDoe
> ISINXD12345678BUYShare02500.45USD01-08-2009
> > but was: <10A9 JohnDoe ISINXD12345678BUYShare02500,45USD01-08-2009
> >
> >
> [ERROR] Run 2:
> BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage:56
> mock://resultMarshal Body of message: 0. Expected: <10A9 JohnDoe
> ISINXD12345678BUYShare02500.45USD01-08-2009
> > but was: <10A9 JohnDoe ISINXD12345678BUYShare02500,45USD01-08-2009
> >
> >
> [ERROR] Run 3:
> BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage:56
> mock://resultMarshal Body of message: 0. Expected: <10A9 JohnDoe
> ISINXD12345678BUYShare02500.45USD01-08-2009
> > but was: <10A9 JohnDoe ISINXD12345678BUYShare02500,45USD01-08-2009
> >
> >
> {code}
> My system decimal separator is set to ',' instead of '.' which causes the
> failures.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (CAMEL-11467) Camel-bindy tests fail depending on the locale
[
https://issues.apache.org/jira/browse/CAMEL-11467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet reassigned CAMEL-11467:
---
Assignee: Guillaume Nodet
> Camel-bindy tests fail depending on the locale
> --
>
> Key: CAMEL-11467
> URL: https://issues.apache.org/jira/browse/CAMEL-11467
> Project: Camel
> Issue Type: Bug
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>
> I end up with the following:
> {code}
> [ERROR] Failures:
> [ERROR]
> org.apache.camel.dataformat.bindy.fixed.BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage(org.apache.camel.dataformat.bindy.fixed.BindyMarshallUnmarshallWithDefaultValueTest)
> [ERROR] Run 1:
> BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage:56
> mock://resultMarshal Body of message: 0. Expected: <10A9 JohnDoe
> ISINXD12345678BUYShare02500.45USD01-08-2009
> > but was: <10A9 JohnDoe ISINXD12345678BUYShare02500,45USD01-08-2009
> >
> >
> [ERROR] Run 2:
> BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage:56
> mock://resultMarshal Body of message: 0. Expected: <10A9 JohnDoe
> ISINXD12345678BUYShare02500.45USD01-08-2009
> > but was: <10A9 JohnDoe ISINXD12345678BUYShare02500,45USD01-08-2009
> >
> >
> [ERROR] Run 3:
> BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage:56
> mock://resultMarshal Body of message: 0. Expected: <10A9 JohnDoe
> ISINXD12345678BUYShare02500.45USD01-08-2009
> > but was: <10A9 JohnDoe ISINXD12345678BUYShare02500,45USD01-08-2009
> >
> >
> {code}
> My system decimal separator is set to ',' instead of '.' which causes the
> failures.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (CAMEL-11467) Camel-bindy tests fail depending on the locale
Guillaume Nodet created CAMEL-11467:
---
Summary: Camel-bindy tests fail depending on the locale
Key: CAMEL-11467
URL: https://issues.apache.org/jira/browse/CAMEL-11467
Project: Camel
Issue Type: Bug
Reporter: Guillaume Nodet
I end up with the following:
{code}
[ERROR] Failures:
[ERROR]
org.apache.camel.dataformat.bindy.fixed.BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage(org.apache.camel.dataformat.bindy.fixed.BindyMarshallUnmarshallWithDefaultValueTest)
[ERROR] Run 1:
BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage:56
mock://resultMarshal Body of message: 0. Expected: <10A9 JohnDoe
ISINXD12345678BUYShare02500.45USD01-08-2009
> but was: <10A9 JohnDoe ISINXD12345678BUYShare02500,45USD01-08-2009
>
>
[ERROR] Run 2:
BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage:56
mock://resultMarshal Body of message: 0. Expected: <10A9 JohnDoe
ISINXD12345678BUYShare02500.45USD01-08-2009
> but was: <10A9 JohnDoe ISINXD12345678BUYShare02500,45USD01-08-2009
>
>
[ERROR] Run 3:
BindyMarshallUnmarshallWithDefaultValueTest.testMarshallMessage:56
mock://resultMarshal Body of message: 0. Expected: <10A9 JohnDoe
ISINXD12345678BUYShare02500.45USD01-08-2009
> but was: <10A9 JohnDoe ISINXD12345678BUYShare02500,45USD01-08-2009
>
>
{code}
My system decimal separator is set to ',' instead of '.' which causes the
failures.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-11466) camel-tarfile dataformat cannot remove successfully processed files
[ https://issues.apache.org/jira/browse/CAMEL-11466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065040#comment-16065040 ] ASF GitHub Bot commented on CAMEL-11466: GitHub user adioss opened a pull request: https://github.com/apache/camel/pull/1792 CAMEL-11466 align source code with camel-zipfile + add non regression unit test to test if resources correctly released after splitting tar see - https://github.com/apache/camel/pull/1785 - and jira ticket You can merge this pull request into a Git repository by running: $ git pull https://github.com/adioss/camel CAMEL-11466 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1792.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1792 commit f2ee3d6befe8e2ca50fbfb173cc7f67b9b1977de Author: Adrien PAILHES Date: 2017-06-27T16:10:12Z CAMEL-11466 align source code with camel-zipfile + add non regression unit test to test if resources correctly released after splitting tar > camel-tarfile dataformat cannot remove successfully processed files > --- > > Key: CAMEL-11466 > URL: https://issues.apache.org/jira/browse/CAMEL-11466 > Project: Camel > Issue Type: Improvement > Components: camel-tarfile >Affects Versions: 2.18.3 >Reporter: Adrien PAILHES >Priority: Minor > > According to https://issues.apache.org/jira/browse/CAMEL-11454, not releasing > resources (files) can prevent component to stop correctly. > Although Camel-tarfile is not sensitive to this pb, source code is very > similar to camel-zipfile so, according to associated camel-zipfile pull > request: > * code should be aligned > * non reg unittest can be written -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11466) camel-tarfile dataformat cannot remove successfully processed files
Adrien PAILHES created CAMEL-11466: -- Summary: camel-tarfile dataformat cannot remove successfully processed files Key: CAMEL-11466 URL: https://issues.apache.org/jira/browse/CAMEL-11466 Project: Camel Issue Type: Improvement Components: camel-tarfile Affects Versions: 2.18.3 Reporter: Adrien PAILHES Priority: Minor According to https://issues.apache.org/jira/browse/CAMEL-11454, not releasing correctly resources (files) can prevent component to stop correctly. Although Camel-tarfile is not sensitive to this pb, source code is very similar to camel-zipfile so, according to associated camel-zipfile pull request: * code should be aligned * non reg unittest can be written -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11466) camel-tarfile dataformat cannot remove successfully processed files
[ https://issues.apache.org/jira/browse/CAMEL-11466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien PAILHES updated CAMEL-11466: --- Description: According to https://issues.apache.org/jira/browse/CAMEL-11454, not releasing resources (files) can prevent component to stop correctly. Although Camel-tarfile is not sensitive to this pb, source code is very similar to camel-zipfile so, according to associated camel-zipfile pull request: * code should be aligned * non reg unittest can be written was: According to https://issues.apache.org/jira/browse/CAMEL-11454, not releasing correctly resources (files) can prevent component to stop correctly. Although Camel-tarfile is not sensitive to this pb, source code is very similar to camel-zipfile so, according to associated camel-zipfile pull request: * code should be aligned * non reg unittest can be written > camel-tarfile dataformat cannot remove successfully processed files > --- > > Key: CAMEL-11466 > URL: https://issues.apache.org/jira/browse/CAMEL-11466 > Project: Camel > Issue Type: Improvement > Components: camel-tarfile >Affects Versions: 2.18.3 >Reporter: Adrien PAILHES >Priority: Minor > > According to https://issues.apache.org/jira/browse/CAMEL-11454, not releasing > resources (files) can prevent component to stop correctly. > Although Camel-tarfile is not sensitive to this pb, source code is very > similar to camel-zipfile so, according to associated camel-zipfile pull > request: > * code should be aligned > * non reg unittest can be written -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11465) NPE caused by IrcMessage
James Netherton created CAMEL-11465:
---
Summary: NPE caused by IrcMessage
Key: CAMEL-11465
URL: https://issues.apache.org/jira/browse/CAMEL-11465
Project: Camel
Issue Type: Bug
Components: camel-irc
Reporter: James Netherton
The {{IrcEndpoint}} has a number of methods like {{createOnPrivmsgExchange}},
{{createOnNickExchange}} etc, where an instance of {{IrcMessage}} is created.
When the constructor is called, it results in:
{code}
16:49:55,426 ERROR [stderr] (Thread-97) Exception in thread "Thread-97"
java.lang.NullPointerException
16:49:55,427 ERROR [stderr] (Thread-97) at
org.apache.camel.impl.MessageSupport.setBody(MessageSupport.java:122)
16:49:55,427 ERROR [stderr] (Thread-97) at
org.apache.camel.component.irc.IrcMessage.(IrcMessage.java:50)
16:49:55,427 ERROR [stderr] (Thread-97) at
org.apache.camel.component.irc.IrcEndpoint.createOnPrivmsgExchange(IrcEndpoint.java:71)
16:49:55,427 ERROR [stderr] (Thread-97) at
org.apache.camel.component.irc.IrcConsumer$FilteredIRCEventAdapter.onPrivmsg(IrcConsumer.java:203)
16:49:55,427 ERROR [stderr] (Thread-97) at
org.schwering.irc.lib.IRCConnection.get(IRCConnection.java:430)
16:49:55,428 ERROR [stderr] (Thread-97) at
org.schwering.irc.lib.IRCConnection.run(IRCConnection.java:373)
{code}
Seems there's now a dependency on the CamelContext in
[MessageSupport.setBody|https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/camel/impl/MessageSupport.java#L122]
and the {{IrcMessage}} constructor calls {{setBody}} before the CamelContext
has been provided to it (it's currently set after the constructor is called).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-11463) back port CAMEL-11319 to 2.18
[ https://issues.apache.org/jira/browse/CAMEL-11463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065013#comment-16065013 ] ASF GitHub Bot commented on CAMEL-11463: GitHub user valdar opened a pull request: https://github.com/apache/camel/pull/1791 CAMEL-11463 (cherry picked from commit 239c7438a47ad8b93f75ba2de62e0580799aed69) CAMEL-11319: sql-stored - Add support for function You can merge this pull request into a Git repository by running: $ git pull https://github.com/valdar/camel CAMEL-11463 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1791.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1791 commit 7691cbd8bc81035de6234d53a30d700ea0250bc9 Author: Claus Ibsen Date: 2017-05-24T12:12:57Z CAMEL-11319: sql-stored - Add support for function CAMEL-11463 (cherry picked from commit 239c7438a47ad8b93f75ba2de62e0580799aed69) > back port CAMEL-11319 to 2.18 > - > > Key: CAMEL-11463 > URL: https://issues.apache.org/jira/browse/CAMEL-11463 > Project: Camel > Issue Type: Improvement > Components: camel-sql >Affects Versions: 2.18.0 >Reporter: Andrea Tarocchi > > Would be nice to also have this feature in 2.18 branch. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11464) Upgrade to rhino 1.7.7.1
Guillaume Nodet created CAMEL-11464: --- Summary: Upgrade to rhino 1.7.7.1 Key: CAMEL-11464 URL: https://issues.apache.org/jira/browse/CAMEL-11464 Project: Camel Issue Type: Improvement Components: camel-script Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 2.20.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11463) back port CAMEL-11319 to 2.18
Andrea Tarocchi created CAMEL-11463: --- Summary: back port CAMEL-11319 to 2.18 Key: CAMEL-11463 URL: https://issues.apache.org/jira/browse/CAMEL-11463 Project: Camel Issue Type: Improvement Components: camel-sql Affects Versions: 2.18.0 Reporter: Andrea Tarocchi Would be nice to also have this feature in 2.18 branch. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (CAMEL-11458) Avoid the use of the scriptengines libraries from google code
[ https://issues.apache.org/jira/browse/CAMEL-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved CAMEL-11458. - Resolution: Fixed https://github.com/apache/camel/commit/cc90cede2942fe751baa91d862b15eb0dcbf1f91 > Avoid the use of the scriptengines libraries from google code > - > > Key: CAMEL-11458 > URL: https://issues.apache.org/jira/browse/CAMEL-11458 > Project: Camel > Issue Type: Improvement > Components: camel-script, osgi >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 2.20.0 > > > Those libraries were needed when jsr223 was not ubiquitous, but since that > time, groovy offers a much better built-in support than the one from the > scriptengine libraries. > In particular, this library may cause memory leaks. > JRuby, BSH also has native support for jsr223. > Rhino has no public jsr223 implementation anymore, so it would make sense to > keep that one. However, when using jdk8, it may switch to nashorn instead... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (CAMEL-11462) Nashorn javascript library can not be found in OSGi
[ https://issues.apache.org/jira/browse/CAMEL-11462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved CAMEL-11462. - Resolution: Fixed Fix Version/s: 2.20.0 https://github.com/apache/camel/commit/a60fc014015cc8fbbc446660adf917e4774ce7ff > Nashorn javascript library can not be found in OSGi > > > Key: CAMEL-11462 > URL: https://issues.apache.org/jira/browse/CAMEL-11462 > Project: Camel > Issue Type: Bug > Components: camel-script, osgi >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 2.20.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (CAMEL-11456) Make the camel-grpc component more cloud service friendly
[ https://issues.apache.org/jira/browse/CAMEL-11456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin resolved CAMEL-11456. Resolution: Fixed > Make the camel-grpc component more cloud service friendly > - > > Key: CAMEL-11456 > URL: https://issues.apache.org/jira/browse/CAMEL-11456 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 2.20.0 > > > Change an URI to be able expose and call component in cloud service > infrastructure easy > Now, the component URI is looks like grpc:host:port/service instead of > passing host and port via parameters -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11456) Make the camel-grpc component more cloud service friendly
[ https://issues.apache.org/jira/browse/CAMEL-11456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-11456: --- Fix Version/s: 2.20.0 > Make the camel-grpc component more cloud service friendly > - > > Key: CAMEL-11456 > URL: https://issues.apache.org/jira/browse/CAMEL-11456 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 2.20.0 > > > Change an URI to be able expose and call component in cloud service > infrastructure easy > Now, the component URI is looks like grpc:host:port/service instead of > passing host and port via parameters -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11462) Nashorn javascript library can not be found in OSGi
[ https://issues.apache.org/jira/browse/CAMEL-11462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064788#comment-16064788 ] Guillaume Nodet commented on CAMEL-11462: - Well, that would be related, but different issue. > Nashorn javascript library can not be found in OSGi > > > Key: CAMEL-11462 > URL: https://issues.apache.org/jira/browse/CAMEL-11462 > Project: Camel > Issue Type: Bug > Components: camel-script, osgi >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11456) Make the camel-grpc component more cloud service friendly
[ https://issues.apache.org/jira/browse/CAMEL-11456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064786#comment-16064786 ] ASF GitHub Bot commented on CAMEL-11456: Github user asfgit closed the pull request at: https://github.com/apache/camel/pull/1787 > Make the camel-grpc component more cloud service friendly > - > > Key: CAMEL-11456 > URL: https://issues.apache.org/jira/browse/CAMEL-11456 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Minor > > Change an URI to be able expose and call component in cloud service > infrastructure easy > Now, the component URI is looks like grpc:host:port/service instead of > passing host and port via parameters -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11462) Nashorn javascript library can not be found in OSGi
[ https://issues.apache.org/jira/browse/CAMEL-11462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064777#comment-16064777 ] Andrea Cosentino commented on CAMEL-11462: -- Maybe this one too is related: https://issues.apache.org/jira/browse/KARAF-4603 > Nashorn javascript library can not be found in OSGi > > > Key: CAMEL-11462 > URL: https://issues.apache.org/jira/browse/CAMEL-11462 > Project: Camel > Issue Type: Bug > Components: camel-script, osgi >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11462) Nashorn javascript library can not be found in OSGi
[ https://issues.apache.org/jira/browse/CAMEL-11462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated CAMEL-11462: Component/s: osgi > Nashorn javascript library can not be found in OSGi > > > Key: CAMEL-11462 > URL: https://issues.apache.org/jira/browse/CAMEL-11462 > Project: Camel > Issue Type: Bug > Components: camel-script, osgi >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11462) Nashorn javascript library can not be found in OSGi
Guillaume Nodet created CAMEL-11462: --- Summary: Nashorn javascript library can not be found in OSGi Key: CAMEL-11462 URL: https://issues.apache.org/jira/browse/CAMEL-11462 Project: Camel Issue Type: Bug Components: camel-script Reporter: Guillaume Nodet Assignee: Guillaume Nodet -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (CAMEL-11440) Some attributes in spring camel xml can't be replaced by property placeholder when used in spring boot
[
https://issues.apache.org/jira/browse/CAMEL-11440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Tarocchi reopened CAMEL-11440:
-
> Some attributes in spring camel xml can't be replaced by property placeholder
> when used in spring boot
> --
>
> Key: CAMEL-11440
> URL: https://issues.apache.org/jira/browse/CAMEL-11440
> Project: Camel
> Issue Type: Bug
> Components: camel-spring, camel-spring-boot
>Affects Versions: 2.18.1
>Reporter: Andrea Tarocchi
>Assignee: Claus Ibsen
> Fix For: 2.19.1
>
> Attachments: reproducer2.zip, reproducer.zip
>
>
> Everything initialized in
> {{*org.apache.camel.core.xml.AbstractCamelContextFactoryBean.initCamelContext()*}}
> using a spring camel xml with spring boot, can not contain a property
> otherwise this is the exception thrown:
> {code}
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'camelMain': Invocation of init method failed; nested exception is
> java.lang.IllegalStateException:
> org.springframework.context.annotation.AnnotationConfigApplicationContext@1b99b9f8
> has not been refreshed yet
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1583)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
> at
> org.springframework.context.event.AbstractApplicationEventMulticaster.retrieveApplicationListeners(AbstractApplicationEventMulticaster.java:228)
> at
> org.springframework.context.event.AbstractApplicationEventMulticaster.getApplicationListeners(AbstractApplicationEventMulticaster.java:185)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:127)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:382)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:336)
> at
> org.springframework.boot.context.event.EventPublishingRunListener.finished(EventPublishingRunListener.java:93)
> at
> org.springframework.boot.SpringApplicationRunListeners.callFinishedListener(SpringApplicationRunListeners.java:79)
> at
> org.springframework.boot.SpringApplicationRunListeners.finished(SpringApplicationRunListeners.java:72)
> at
> org.springframework.boot.SpringApplication.handleRunFailure(SpringApplication.java:813)
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:326)
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1186)
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1175)
> at com.mycompany.Application.main(Application.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.springframework.boot.maven.AbstractRunMojo$LaunchRunner.run(AbstractRunMojo.java:506)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException:
> org.springframework.context.annotation.AnnotationConfigApplicationContext@1b99b9f8
> has not been refreshed yet
> at
> org.springframework.context.support.AbstractApplicationContext.assertBeanFactoryActive(AbstractApplicationContext.java:1063)
> at
> org.springframework.context.support.AbstractApplicationContext.getBeanNamesForType(AbstractApplicationContext.java:1177)
> at
> org.apache.camel.spring.CamelContextFactoryBean.getBeanForType(CamelContextFactoryBean.java:220)
> at
> org.apache.camel.core.xml.AbstractCamelContextFactoryBean.afterProperti
[jira] [Commented] (CAMEL-11440) Some attributes in spring camel xml can't be replaced by property placeholder when used in spring boot
[
https://issues.apache.org/jira/browse/CAMEL-11440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064642#comment-16064642
]
Andrea Tarocchi commented on CAMEL-11440:
-
Hi Claus,
running the reproducer bumping camel version to 2.19.1 seems to solve the issue;
but if I add a {{}} component (which was part of my original
issue, but I stripped down the reproducer to the bear minimum), it seems there
is another problem:
{code:java}
12:24:55.542 [main] DEBUG o.s.b.f.s.DefaultListableBeanFactory - Invoking
afterPropertiesSet() on bean with name 'camelMain'
12:24:55.551 [main] ERROR o.s.boot.SpringApplication - Error handling failed
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'camelMain': Invocation of init method failed; nested exception is
java.lang.IllegalStateException:
org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@1bd655b8
has not been refreshed yet
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1583)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:545)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
at
org.springframework.context.event.AbstractApplicationEventMulticaster.retrieveApplicationListeners(AbstractApplicationEventMulticaster.java:228)
at
org.springframework.context.event.AbstractApplicationEventMulticaster.getApplicationListeners(AbstractApplicationEventMulticaster.java:185)
at
org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:127)
at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:382)
at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:336)
at
org.springframework.boot.context.event.EventPublishingRunListener.finished(EventPublishingRunListener.java:100)
at
org.springframework.boot.SpringApplicationRunListeners.callFinishedListener(SpringApplicationRunListeners.java:79)
at
org.springframework.boot.SpringApplicationRunListeners.finished(SpringApplicationRunListeners.java:72)
at
org.springframework.boot.SpringApplication.handleRunFailure(SpringApplication.java:789)
at
org.springframework.boot.SpringApplication.run(SpringApplication.java:325)
at
org.springframework.boot.SpringApplication.run(SpringApplication.java:1162)
at
org.springframework.boot.SpringApplication.run(SpringApplication.java:1151)
at com.mycompany.Application.main(Application.java:35)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.springframework.boot.maven.AbstractRunMojo$LaunchRunner.run(AbstractRunMojo.java:506)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException:
org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@1bd655b8
has not been refreshed yet
at
org.springframework.context.support.AbstractApplicationContext.assertBeanFactoryActive(AbstractApplicationContext.java:1063)
at
org.springframework.context.support.AbstractApplicationContext.getBeanNamesForType(AbstractApplicationContext.java:1177)
at
org.apache.camel.spring.CamelContextFactoryBean.getBeanForType(CamelContextFactoryBean.java:234)
at
org.apache.camel.core.xml.AbstractCamelContextFactoryBean.afterPropertiesSet(AbstractCamelContextFactoryBean.java:166)
at
org.apache.camel.spring.CamelContextFactoryBean.afterPropertiesSet(CamelContextFactoryBean.java:289)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1642)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapable
[jira] [Updated] (CAMEL-11440) Some attributes in spring camel xml can't be replaced by property placeholder when used in spring boot
[
https://issues.apache.org/jira/browse/CAMEL-11440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Tarocchi updated CAMEL-11440:
Attachment: reproducer2.zip
> Some attributes in spring camel xml can't be replaced by property placeholder
> when used in spring boot
> --
>
> Key: CAMEL-11440
> URL: https://issues.apache.org/jira/browse/CAMEL-11440
> Project: Camel
> Issue Type: Bug
> Components: camel-spring, camel-spring-boot
>Affects Versions: 2.18.1
>Reporter: Andrea Tarocchi
>Assignee: Claus Ibsen
> Fix For: 2.19.1
>
> Attachments: reproducer2.zip, reproducer.zip
>
>
> Everything initialized in
> {{*org.apache.camel.core.xml.AbstractCamelContextFactoryBean.initCamelContext()*}}
> using a spring camel xml with spring boot, can not contain a property
> otherwise this is the exception thrown:
> {code}
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'camelMain': Invocation of init method failed; nested exception is
> java.lang.IllegalStateException:
> org.springframework.context.annotation.AnnotationConfigApplicationContext@1b99b9f8
> has not been refreshed yet
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1583)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
> at
> org.springframework.context.event.AbstractApplicationEventMulticaster.retrieveApplicationListeners(AbstractApplicationEventMulticaster.java:228)
> at
> org.springframework.context.event.AbstractApplicationEventMulticaster.getApplicationListeners(AbstractApplicationEventMulticaster.java:185)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:127)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:382)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:336)
> at
> org.springframework.boot.context.event.EventPublishingRunListener.finished(EventPublishingRunListener.java:93)
> at
> org.springframework.boot.SpringApplicationRunListeners.callFinishedListener(SpringApplicationRunListeners.java:79)
> at
> org.springframework.boot.SpringApplicationRunListeners.finished(SpringApplicationRunListeners.java:72)
> at
> org.springframework.boot.SpringApplication.handleRunFailure(SpringApplication.java:813)
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:326)
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1186)
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1175)
> at com.mycompany.Application.main(Application.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.springframework.boot.maven.AbstractRunMojo$LaunchRunner.run(AbstractRunMojo.java:506)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException:
> org.springframework.context.annotation.AnnotationConfigApplicationContext@1b99b9f8
> has not been refreshed yet
> at
> org.springframework.context.support.AbstractApplicationContext.assertBeanFactoryActive(AbstractApplicationContext.java:1063)
> at
> org.springframework.context.support.AbstractApplicationContext.getBeanNamesForType(AbstractApplicationContext.java:1177)
> at
> org.apache.camel.spring.CamelContextFactoryBean.getBeanForType(CamelContextFactoryBean.java:220)
> at
> org.apache.camel.core.xml.AbstractCamelCo
[jira] [Commented] (CAMEL-11461) SEDA - resolve references for concurrentConsumers, limitConcurrentConsumers
[ https://issues.apache.org/jira/browse/CAMEL-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064619#comment-16064619 ] ASF GitHub Bot commented on CAMEL-11461: GitHub user isavin opened a pull request: https://github.com/apache/camel/pull/1790 CAMEL-11461 Resolve concurrentConsumers and limitConcurrentConsumers … …from the registry. https://issues.apache.org/jira/browse/CAMEL-11461 You can merge this pull request into a Git repository by running: $ git pull https://github.com/isavin/camel CAMEL-11461-seda_resolve_consumer_args Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1790.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1790 commit bb125e3e6259e51f7137fb0085e39f4a3b35ad72 Author: Ion Savin Date: 2017-06-27T07:40:36Z CAMEL-11461 Resolve concurrentConsumers and limitConcurrentConsumers from the registry. > SEDA - resolve references for concurrentConsumers, limitConcurrentConsumers > --- > > Key: CAMEL-11461 > URL: https://issues.apache.org/jira/browse/CAMEL-11461 > Project: Camel > Issue Type: Improvement > Components: camel-core >Affects Versions: 2.19.1 >Reporter: Ion Savin > > SedaComponent doesn't currently resolve the references specified in uri for > the following parameters: > * concurrentConsumers > * limitConcurrentConsumers -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11461) SEDA - resolve references for concurrentConsumers, limitConcurrentConsumers
Ion Savin created CAMEL-11461: - Summary: SEDA - resolve references for concurrentConsumers, limitConcurrentConsumers Key: CAMEL-11461 URL: https://issues.apache.org/jira/browse/CAMEL-11461 Project: Camel Issue Type: Improvement Components: camel-core Affects Versions: 2.19.1 Reporter: Ion Savin SedaComponent doesn't currently resolve the references specified in uri for the following parameters: * concurrentConsumers * limitConcurrentConsumers -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (CAMEL-11460) Camel-Infinispan: If a Default Configuration is not provided then a DefaultCacheName must be provided
[ https://issues.apache.org/jira/browse/CAMEL-11460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-11460. -- Resolution: Fixed > Camel-Infinispan: If a Default Configuration is not provided then a > DefaultCacheName must be provided > - > > Key: CAMEL-11460 > URL: https://issues.apache.org/jira/browse/CAMEL-11460 > Project: Camel > Issue Type: Bug > Components: camel-infinispan >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino > Fix For: 2.20.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11460) Camel-Infinispan: If a Default Configuration is not provided then a DefaultCacheName must be provided
Andrea Cosentino created CAMEL-11460: Summary: Camel-Infinispan: If a Default Configuration is not provided then a DefaultCacheName must be provided Key: CAMEL-11460 URL: https://issues.apache.org/jira/browse/CAMEL-11460 Project: Camel Issue Type: Bug Components: camel-infinispan Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 2.20.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11214) FluentProducerTemplate - Should allow non default uri
[ https://issues.apache.org/jira/browse/CAMEL-11214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064563#comment-16064563 ] ASF GitHub Bot commented on CAMEL-11214: Github user asfgit closed the pull request at: https://github.com/apache/camel/pull/1789 > FluentProducerTemplate - Should allow non default uri > - > > Key: CAMEL-11214 > URL: https://issues.apache.org/jira/browse/CAMEL-11214 > Project: Camel > Issue Type: Improvement > Components: camel-core >Affects Versions: 2.19.0 >Reporter: Claus Ibsen > Fix For: 2.20.0 > > Attachments: > 0001-Fix-CAMEL-11214-FluentProducerTemplate-Should-allow-.patch > > > You get > Caused by: org.apache.camel.spring.GenericBeansException: Error post > processing bean: geoRestController; nested exception is > java.lang.NullPointerException > at > org.apache.camel.spring.CamelBeanPostProcessor.postProcessBeforeInitialization(CamelBeanPostProcessor.java:159) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:409) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1620) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555) > ... 21 more > Caused by: java.lang.NullPointerException > at java.util.Objects.requireNonNull(Objects.java:203) > at java.util.Optional.(Optional.java:96) > at java.util.Optional.of(Optional.java:108) > at > org.apache.camel.builder.DefaultFluentProducerTemplate.setDefaultEndpoint(DefaultFluentProducerTemplate.java:103) > at > org.apache.camel.impl.CamelPostProcessorHelper.createInjectionFluentProducerTemplate(CamelPostProcessorHelper.java:333) > at > org.apache.camel.impl.CamelPostProcessorHelper.getInjectionValue(CamelPostProcessorHelper.java:224) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor.injectField(DefaultCamelBeanPostProcessor.java:200) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor.injectField(DefaultCamelBeanPostProcessor.java:194) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor$1.doWith(DefaultCamelBeanPostProcessor.java:181) > at > org.apache.camel.util.ReflectionHelper.doWithFields(ReflectionHelper.java:73) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor.injectFields(DefaultCamelBeanPostProcessor.java:167) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor.postProcessBeforeInitialization(DefaultCamelBeanPostProcessor.java:82) > at > org.apache.camel.spring.CamelBeanPostProcessor.postProcessBeforeInitialization(CamelBeanPostProcessor.java:153) > ... 24 more > If you just have > @EndpointInject > private FluentProducerTemplate template; > So you need to set some dummy uri > @EndpointInject(uri = "log:foo") > private FluentProducerTemplate template; -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (CAMEL-11214) FluentProducerTemplate - Should allow non default uri
[ https://issues.apache.org/jira/browse/CAMEL-11214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-11214. - Resolution: Fixed Assignee: Claus Ibsen Thanks for the PR > FluentProducerTemplate - Should allow non default uri > - > > Key: CAMEL-11214 > URL: https://issues.apache.org/jira/browse/CAMEL-11214 > Project: Camel > Issue Type: Improvement > Components: camel-core >Affects Versions: 2.19.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen > Fix For: 2.20.0 > > Attachments: > 0001-Fix-CAMEL-11214-FluentProducerTemplate-Should-allow-.patch > > > You get > Caused by: org.apache.camel.spring.GenericBeansException: Error post > processing bean: geoRestController; nested exception is > java.lang.NullPointerException > at > org.apache.camel.spring.CamelBeanPostProcessor.postProcessBeforeInitialization(CamelBeanPostProcessor.java:159) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:409) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1620) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555) > ... 21 more > Caused by: java.lang.NullPointerException > at java.util.Objects.requireNonNull(Objects.java:203) > at java.util.Optional.(Optional.java:96) > at java.util.Optional.of(Optional.java:108) > at > org.apache.camel.builder.DefaultFluentProducerTemplate.setDefaultEndpoint(DefaultFluentProducerTemplate.java:103) > at > org.apache.camel.impl.CamelPostProcessorHelper.createInjectionFluentProducerTemplate(CamelPostProcessorHelper.java:333) > at > org.apache.camel.impl.CamelPostProcessorHelper.getInjectionValue(CamelPostProcessorHelper.java:224) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor.injectField(DefaultCamelBeanPostProcessor.java:200) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor.injectField(DefaultCamelBeanPostProcessor.java:194) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor$1.doWith(DefaultCamelBeanPostProcessor.java:181) > at > org.apache.camel.util.ReflectionHelper.doWithFields(ReflectionHelper.java:73) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor.injectFields(DefaultCamelBeanPostProcessor.java:167) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor.postProcessBeforeInitialization(DefaultCamelBeanPostProcessor.java:82) > at > org.apache.camel.spring.CamelBeanPostProcessor.postProcessBeforeInitialization(CamelBeanPostProcessor.java:153) > ... 24 more > If you just have > @EndpointInject > private FluentProducerTemplate template; > So you need to set some dummy uri > @EndpointInject(uri = "log:foo") > private FluentProducerTemplate template; -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (CAMEL-11458) Avoid the use of the scriptengines libraries from google code
[ https://issues.apache.org/jira/browse/CAMEL-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned CAMEL-11458: --- Assignee: Guillaume Nodet > Avoid the use of the scriptengines libraries from google code > - > > Key: CAMEL-11458 > URL: https://issues.apache.org/jira/browse/CAMEL-11458 > Project: Camel > Issue Type: Improvement > Components: camel-script, osgi >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 2.20.0 > > > Those libraries were needed when jsr223 was not ubiquitous, but since that > time, groovy offers a much better built-in support than the one from the > scriptengine libraries. > In particular, this library may cause memory leaks. > JRuby, BSH also has native support for jsr223. > Rhino has no public jsr223 implementation anymore, so it would make sense to > keep that one. However, when using jdk8, it may switch to nashorn instead... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11459) Upgrade CXF to 3.2
[ https://issues.apache.org/jira/browse/CAMEL-11459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated CAMEL-11459: Fix Version/s: 2.20.0 > Upgrade CXF to 3.2 > -- > > Key: CAMEL-11459 > URL: https://issues.apache.org/jira/browse/CAMEL-11459 > Project: Camel > Issue Type: Improvement >Reporter: Guillaume Nodet > Fix For: 2.20.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11458) Avoid the use of the scriptengines libraries from google code
[ https://issues.apache.org/jira/browse/CAMEL-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated CAMEL-11458: Fix Version/s: 2.20.0 > Avoid the use of the scriptengines libraries from google code > - > > Key: CAMEL-11458 > URL: https://issues.apache.org/jira/browse/CAMEL-11458 > Project: Camel > Issue Type: Improvement > Components: camel-script, osgi >Reporter: Guillaume Nodet > Fix For: 2.20.0 > > > Those libraries were needed when jsr223 was not ubiquitous, but since that > time, groovy offers a much better built-in support than the one from the > scriptengine libraries. > In particular, this library may cause memory leaks. > JRuby, BSH also has native support for jsr223. > Rhino has no public jsr223 implementation anymore, so it would make sense to > keep that one. However, when using jdk8, it may switch to nashorn instead... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11459) Upgrade CXF to 3.2
[ https://issues.apache.org/jira/browse/CAMEL-11459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064516#comment-16064516 ] Guillaume Nodet commented on CAMEL-11459: - This should incorporate https://github.com/jboss-fuse/camel/commit/e1478618c565d3206fa49355ea5a24b000690891 > Upgrade CXF to 3.2 > -- > > Key: CAMEL-11459 > URL: https://issues.apache.org/jira/browse/CAMEL-11459 > Project: Camel > Issue Type: Improvement >Reporter: Guillaume Nodet > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11459) Upgrade CXF to 3.2
Guillaume Nodet created CAMEL-11459: --- Summary: Upgrade CXF to 3.2 Key: CAMEL-11459 URL: https://issues.apache.org/jira/browse/CAMEL-11459 Project: Camel Issue Type: Improvement Reporter: Guillaume Nodet -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11214) FluentProducerTemplate - Should allow non default uri
[ https://issues.apache.org/jira/browse/CAMEL-11214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064509#comment-16064509 ] ASF GitHub Bot commented on CAMEL-11214: GitHub user vrlgohel opened a pull request: https://github.com/apache/camel/pull/1789 [CAMEL-11214] Restrict FluentProducerTemplate to include a dummy URI Fix for CAMEL-11214 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vrlgohel/camel-1 master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1789.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1789 commit 5697890857a7b13592c00f07ac053f0d4dcc6926 Author: Viral Gohel Date: 2017-06-27T09:03:14Z [CAMEL-11214] Restrict FluentProducerTemplate to include a dummy URI > FluentProducerTemplate - Should allow non default uri > - > > Key: CAMEL-11214 > URL: https://issues.apache.org/jira/browse/CAMEL-11214 > Project: Camel > Issue Type: Improvement > Components: camel-core >Affects Versions: 2.19.0 >Reporter: Claus Ibsen > Fix For: 2.20.0 > > Attachments: > 0001-Fix-CAMEL-11214-FluentProducerTemplate-Should-allow-.patch > > > You get > Caused by: org.apache.camel.spring.GenericBeansException: Error post > processing bean: geoRestController; nested exception is > java.lang.NullPointerException > at > org.apache.camel.spring.CamelBeanPostProcessor.postProcessBeforeInitialization(CamelBeanPostProcessor.java:159) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:409) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1620) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555) > ... 21 more > Caused by: java.lang.NullPointerException > at java.util.Objects.requireNonNull(Objects.java:203) > at java.util.Optional.(Optional.java:96) > at java.util.Optional.of(Optional.java:108) > at > org.apache.camel.builder.DefaultFluentProducerTemplate.setDefaultEndpoint(DefaultFluentProducerTemplate.java:103) > at > org.apache.camel.impl.CamelPostProcessorHelper.createInjectionFluentProducerTemplate(CamelPostProcessorHelper.java:333) > at > org.apache.camel.impl.CamelPostProcessorHelper.getInjectionValue(CamelPostProcessorHelper.java:224) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor.injectField(DefaultCamelBeanPostProcessor.java:200) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor.injectField(DefaultCamelBeanPostProcessor.java:194) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor$1.doWith(DefaultCamelBeanPostProcessor.java:181) > at > org.apache.camel.util.ReflectionHelper.doWithFields(ReflectionHelper.java:73) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor.injectFields(DefaultCamelBeanPostProcessor.java:167) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor.postProcessBeforeInitialization(DefaultCamelBeanPostProcessor.java:82) > at > org.apache.camel.spring.CamelBeanPostProcessor.postProcessBeforeInitialization(CamelBeanPostProcessor.java:153) > ... 24 more > If you just have > @EndpointInject > private FluentProducerTemplate template; > So you need to set some dummy uri > @EndpointInject(uri = "log:foo") > private FluentProducerTemplate template; -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11458) Avoid the use of the scriptengines libraries from google code
Guillaume Nodet created CAMEL-11458: --- Summary: Avoid the use of the scriptengines libraries from google code Key: CAMEL-11458 URL: https://issues.apache.org/jira/browse/CAMEL-11458 Project: Camel Issue Type: Improvement Components: camel-script, osgi Reporter: Guillaume Nodet Those libraries were needed when jsr223 was not ubiquitous, but since that time, groovy offers a much better built-in support than the one from the scriptengine libraries. In particular, this library may cause memory leaks. JRuby, BSH also has native support for jsr223. Rhino has no public jsr223 implementation anymore, so it would make sense to keep that one. However, when using jdk8, it may switch to nashorn instead... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11214) FluentProducerTemplate - Should allow non default uri
[ https://issues.apache.org/jira/browse/CAMEL-11214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064490#comment-16064490 ] Claus Ibsen commented on CAMEL-11214: - Hi Moumita How does it go with the github PR, do you have any luck with that? > FluentProducerTemplate - Should allow non default uri > - > > Key: CAMEL-11214 > URL: https://issues.apache.org/jira/browse/CAMEL-11214 > Project: Camel > Issue Type: Improvement > Components: camel-core >Affects Versions: 2.19.0 >Reporter: Claus Ibsen > Fix For: 2.20.0 > > Attachments: > 0001-Fix-CAMEL-11214-FluentProducerTemplate-Should-allow-.patch > > > You get > Caused by: org.apache.camel.spring.GenericBeansException: Error post > processing bean: geoRestController; nested exception is > java.lang.NullPointerException > at > org.apache.camel.spring.CamelBeanPostProcessor.postProcessBeforeInitialization(CamelBeanPostProcessor.java:159) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:409) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1620) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555) > ... 21 more > Caused by: java.lang.NullPointerException > at java.util.Objects.requireNonNull(Objects.java:203) > at java.util.Optional.(Optional.java:96) > at java.util.Optional.of(Optional.java:108) > at > org.apache.camel.builder.DefaultFluentProducerTemplate.setDefaultEndpoint(DefaultFluentProducerTemplate.java:103) > at > org.apache.camel.impl.CamelPostProcessorHelper.createInjectionFluentProducerTemplate(CamelPostProcessorHelper.java:333) > at > org.apache.camel.impl.CamelPostProcessorHelper.getInjectionValue(CamelPostProcessorHelper.java:224) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor.injectField(DefaultCamelBeanPostProcessor.java:200) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor.injectField(DefaultCamelBeanPostProcessor.java:194) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor$1.doWith(DefaultCamelBeanPostProcessor.java:181) > at > org.apache.camel.util.ReflectionHelper.doWithFields(ReflectionHelper.java:73) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor.injectFields(DefaultCamelBeanPostProcessor.java:167) > at > org.apache.camel.impl.DefaultCamelBeanPostProcessor.postProcessBeforeInitialization(DefaultCamelBeanPostProcessor.java:82) > at > org.apache.camel.spring.CamelBeanPostProcessor.postProcessBeforeInitialization(CamelBeanPostProcessor.java:153) > ... 24 more > If you just have > @EndpointInject > private FluentProducerTemplate template; > So you need to set some dummy uri > @EndpointInject(uri = "log:foo") > private FluentProducerTemplate template; -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (CAMEL-11440) Some attributes in spring camel xml can't be replaced by property placeholder when used in spring boot
[
https://issues.apache.org/jira/browse/CAMEL-11440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-11440.
-
Resolution: Fixed
Assignee: Claus Ibsen
Fix Version/s: 2.19.1
> Some attributes in spring camel xml can't be replaced by property placeholder
> when used in spring boot
> --
>
> Key: CAMEL-11440
> URL: https://issues.apache.org/jira/browse/CAMEL-11440
> Project: Camel
> Issue Type: Bug
> Components: camel-spring, camel-spring-boot
>Affects Versions: 2.18.1
>Reporter: Andrea Tarocchi
>Assignee: Claus Ibsen
> Fix For: 2.19.1
>
> Attachments: reproducer.zip
>
>
> Everything initialized in
> {{*org.apache.camel.core.xml.AbstractCamelContextFactoryBean.initCamelContext()*}}
> using a spring camel xml with spring boot, can not contain a property
> otherwise this is the exception thrown:
> {code}
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'camelMain': Invocation of init method failed; nested exception is
> java.lang.IllegalStateException:
> org.springframework.context.annotation.AnnotationConfigApplicationContext@1b99b9f8
> has not been refreshed yet
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1583)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
> at
> org.springframework.context.event.AbstractApplicationEventMulticaster.retrieveApplicationListeners(AbstractApplicationEventMulticaster.java:228)
> at
> org.springframework.context.event.AbstractApplicationEventMulticaster.getApplicationListeners(AbstractApplicationEventMulticaster.java:185)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:127)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:382)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:336)
> at
> org.springframework.boot.context.event.EventPublishingRunListener.finished(EventPublishingRunListener.java:93)
> at
> org.springframework.boot.SpringApplicationRunListeners.callFinishedListener(SpringApplicationRunListeners.java:79)
> at
> org.springframework.boot.SpringApplicationRunListeners.finished(SpringApplicationRunListeners.java:72)
> at
> org.springframework.boot.SpringApplication.handleRunFailure(SpringApplication.java:813)
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:326)
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1186)
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1175)
> at com.mycompany.Application.main(Application.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.springframework.boot.maven.AbstractRunMojo$LaunchRunner.run(AbstractRunMojo.java:506)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException:
> org.springframework.context.annotation.AnnotationConfigApplicationContext@1b99b9f8
> has not been refreshed yet
> at
> org.springframework.context.support.AbstractApplicationContext.assertBeanFactoryActive(AbstractApplicationContext.java:1063)
> at
> org.springframework.context.support.AbstractApplicationContext.getBeanNamesForType(AbstractApplicationContext.java:1177)
> at
> org.apache.camel.spring.CamelContextFactoryBean.getBeanForType(CamelContextFactoryBean.java:220)
> at
> org.apache.cam
[jira] [Commented] (CAMEL-11440) Some attributes in spring camel xml can't be replaced by property placeholder when used in spring boot
[
https://issues.apache.org/jira/browse/CAMEL-11440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064488#comment-16064488
]
Claus Ibsen commented on CAMEL-11440:
-
Hi
It works with Camel 2.19.1 etc.
Remember to set run controller to true if you want the JVM to keep running
camel.springboot.main-run-controller=true
> Some attributes in spring camel xml can't be replaced by property placeholder
> when used in spring boot
> --
>
> Key: CAMEL-11440
> URL: https://issues.apache.org/jira/browse/CAMEL-11440
> Project: Camel
> Issue Type: Bug
> Components: camel-spring, camel-spring-boot
>Affects Versions: 2.18.1
>Reporter: Andrea Tarocchi
> Fix For: 2.19.1
>
> Attachments: reproducer.zip
>
>
> Everything initialized in
> {{*org.apache.camel.core.xml.AbstractCamelContextFactoryBean.initCamelContext()*}}
> using a spring camel xml with spring boot, can not contain a property
> otherwise this is the exception thrown:
> {code}
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'camelMain': Invocation of init method failed; nested exception is
> java.lang.IllegalStateException:
> org.springframework.context.annotation.AnnotationConfigApplicationContext@1b99b9f8
> has not been refreshed yet
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1583)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
> at
> org.springframework.context.event.AbstractApplicationEventMulticaster.retrieveApplicationListeners(AbstractApplicationEventMulticaster.java:228)
> at
> org.springframework.context.event.AbstractApplicationEventMulticaster.getApplicationListeners(AbstractApplicationEventMulticaster.java:185)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:127)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:382)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:336)
> at
> org.springframework.boot.context.event.EventPublishingRunListener.finished(EventPublishingRunListener.java:93)
> at
> org.springframework.boot.SpringApplicationRunListeners.callFinishedListener(SpringApplicationRunListeners.java:79)
> at
> org.springframework.boot.SpringApplicationRunListeners.finished(SpringApplicationRunListeners.java:72)
> at
> org.springframework.boot.SpringApplication.handleRunFailure(SpringApplication.java:813)
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:326)
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1186)
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1175)
> at com.mycompany.Application.main(Application.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.springframework.boot.maven.AbstractRunMojo$LaunchRunner.run(AbstractRunMojo.java:506)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException:
> org.springframework.context.annotation.AnnotationConfigApplicationContext@1b99b9f8
> has not been refreshed yet
> at
> org.springframework.context.support.AbstractApplicationContext.assertBeanFactoryActive(AbstractApplicationContext.java:1063)
> at
> org.springframework.context.support.AbstractApplicationContext.getBeanNamesForType(AbstractApplicationContext.java:1177)
> at
> org.apache.camel.spring.CamelConte
[jira] [Updated] (CAMEL-8419) Camel StreamCache does not work with CXF consumer for InOut messages
[ https://issues.apache.org/jira/browse/CAMEL-8419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8419: --- Fix Version/s: 2.20.0 > Camel StreamCache does not work with CXF consumer for InOut messages > > > Key: CAMEL-8419 > URL: https://issues.apache.org/jira/browse/CAMEL-8419 > Project: Camel > Issue Type: Bug > Components: camel-cxf >Affects Versions: 2.14.1 >Reporter: Stephan Siano > Fix For: 2.20.0 > > Attachments: > 0001-CAMEL-8419-Camel-StreamCache-does-not-work-with-CXF-.patch > > > If a route that is started by a CXF consumer and has an InOut exchange > pattern (meaning that the CXF consumer is returning a response back to the > caller) contains a StreamCache as message object that is not in memory, > returning the payload will fail. > The reason for this is that an on-disk stream cache in Camel will be removed > when the LUW ends, but CXF will return the response afterwards. > See the two attached unit tests for details. > I don't like the actual patch too much, as it copies on-disk camel stream > caches into CXF stream caches when creating the CXF message object in camel > CXF, but this is about the last step before the LUW ends (and the file gets > deleted). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-8419) Camel StreamCache does not work with CXF consumer for InOut messages
[ https://issues.apache.org/jira/browse/CAMEL-8419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064463#comment-16064463 ] Claus Ibsen commented on CAMEL-8419: Thanks Sami for the PR. I think it looks good, but would just like a CXF committer to glace at the code before we do any merge. > Camel StreamCache does not work with CXF consumer for InOut messages > > > Key: CAMEL-8419 > URL: https://issues.apache.org/jira/browse/CAMEL-8419 > Project: Camel > Issue Type: Bug > Components: camel-cxf >Affects Versions: 2.14.1 >Reporter: Stephan Siano > Attachments: > 0001-CAMEL-8419-Camel-StreamCache-does-not-work-with-CXF-.patch > > > If a route that is started by a CXF consumer and has an InOut exchange > pattern (meaning that the CXF consumer is returning a response back to the > caller) contains a StreamCache as message object that is not in memory, > returning the payload will fail. > The reason for this is that an on-disk stream cache in Camel will be removed > when the LUW ends, but CXF will return the response afterwards. > See the two attached unit tests for details. > I don't like the actual patch too much, as it copies on-disk camel stream > caches into CXF stream caches when creating the CXF message object in camel > CXF, but this is about the last step before the LUW ends (and the file gets > deleted). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11457) camel-atomix - No new leader when all nodes are killed forcefully
[
https://issues.apache.org/jira/browse/CAMEL-11457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Burgazzoli updated CAMEL-11457:
Fix Version/s: 2.20.0
> camel-atomix - No new leader when all nodes are killed forcefully
> -
>
> Key: CAMEL-11457
> URL: https://issues.apache.org/jira/browse/CAMEL-11457
> Project: Camel
> Issue Type: Bug
> Components: camel-atomix
>Reporter: Nicola Ferraro
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.20.0
>
>
> I'm testing the leader service with the following scenario.
> Client mode with an external bootstrap service on Openshift. Using a
> spring-boot application.
> The service configuration is:
> {code}
> AtomixClusterClientService service = new AtomixClusterClientService();
> service.setId(InetAddress.getLocalHost().getHostName());
> service.setNodes(Collections.singletonList(new Address("atomix-boot-node",
> 8700)));
> {code}
> Steps:
> - I start 3 pods of the application, one is the leader.
> - Once started, I kill forcefully all three pods (calling
> "Runtime.getRuntime().halt(1)" from the JVM code) one after the other at
> short distance (few seconds)
> When all three pods become available again, the "leadershipChanged" callback
> is not called in any of the pods (waited > 1 hour). If I restart one pod
> after some time, that one become the leader. The other two pods receive the
> notification that there's a new leader.
> It seems that a timeout occurs, so that a new leader can be determined upon
> restart, but nobody participate in the election if pods are started before
> the timeout.
> [~lb] any idea?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Work started] (CAMEL-11457) camel-atomix - No new leader when all nodes are killed forcefully
[
https://issues.apache.org/jira/browse/CAMEL-11457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-11457 started by Luca Burgazzoli.
---
> camel-atomix - No new leader when all nodes are killed forcefully
> -
>
> Key: CAMEL-11457
> URL: https://issues.apache.org/jira/browse/CAMEL-11457
> Project: Camel
> Issue Type: Bug
> Components: camel-atomix
>Reporter: Nicola Ferraro
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.20.0
>
>
> I'm testing the leader service with the following scenario.
> Client mode with an external bootstrap service on Openshift. Using a
> spring-boot application.
> The service configuration is:
> {code}
> AtomixClusterClientService service = new AtomixClusterClientService();
> service.setId(InetAddress.getLocalHost().getHostName());
> service.setNodes(Collections.singletonList(new Address("atomix-boot-node",
> 8700)));
> {code}
> Steps:
> - I start 3 pods of the application, one is the leader.
> - Once started, I kill forcefully all three pods (calling
> "Runtime.getRuntime().halt(1)" from the JVM code) one after the other at
> short distance (few seconds)
> When all three pods become available again, the "leadershipChanged" callback
> is not called in any of the pods (waited > 1 hour). If I restart one pod
> after some time, that one become the leader. The other two pods receive the
> notification that there's a new leader.
> It seems that a timeout occurs, so that a new leader can be determined upon
> restart, but nobody participate in the election if pods are started before
> the timeout.
> [~lb] any idea?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (CAMEL-11454) camel-zipfile dataformat cannot remove successfully processed files
[
https://issues.apache.org/jira/browse/CAMEL-11454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-11454:
Fix Version/s: 2.20.0
2.19.2
2.18.5
> camel-zipfile dataformat cannot remove successfully processed files
> ---
>
> Key: CAMEL-11454
> URL: https://issues.apache.org/jira/browse/CAMEL-11454
> Project: Camel
> Issue Type: Bug
> Components: camel-zipfile
>Affects Versions: 2.18.3
> Environment: Windows 7 x64
>Reporter: Adrien PAILHES
>Assignee: onder sezgin
>Priority: Minor
> Fix For: 2.18.5, 2.19.2, 2.20.0
>
>
> When creating a route as follows:
> {code:xml}
>
> http://www.springframework.org/schema/beans";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:camel="http://camel.apache.org/schema/spring";
> xmlns:context="http://www.springframework.org/schema/context";
> xmlns:util="http://www.springframework.org/schema/util";
> xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-4.2.xsd
> http://www.springframework.org/schema/context
> http://www.springframework.org/schema/context/spring-context-4.2.xsd
> http://camel.apache.org/schema/spring
> http://camel.apache.org/schema/spring/camel-spring.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util-2.5.xsd";>
>class="org.apache.camel.dataformat.zipfile.ZipFileDataFormat">
>
>
> http://camel.apache.org/schema/spring";
> streamCache="true">
>
>
>
>
> ${body}
>
>
>
>
>
>
>
> {code}
> the renaming of the file fails with
> {code}
> Renaming file from 'C:\camelTest\in\20161201T0030Z_1D_BE00_EQ.zip' to
> 'C:\camelTest\in\.camel\20161201T0030Z_1D_BE00_EQ.zip' failed: Cannot delete
> file 'C:\camelTest\in\20161201T0030Z_1D_BE00_EQ.zip' after copy succeeded
> {code}
> The file stays in input folder and gets processed over and over again.
> h2. Investigation
> Problem only occurs if:
> * you try to move the file at the end of the exchange (not with noop but with
> delete, for example)
> * if ZipFile dataformat is used (not with ZipSplitter)
> * if usingIterator is true (not if false and Zip file with 1 entry)
> It's because in org.apache.camel.dataformat.zipfile.ZipIterator constructor:
> {code}
> InputStream inputStream = inputMessage.getBody(InputStream.class);
> {code}
> will create a new input stream instead of using the one already opened:
> inputStream parameter when using
> org.apache.camel.dataformat.zipfile.ZipFileDataFormat#unmarshal.
> This one won't be closed and you won't be able to release the resource unless
> you kill the process.
> So, two solutions:
> * close the inputStream parameter in
> org.apache.camel.dataformat.zipfile.ZipFileDataFormat#unmarshal before using
> ZipIterator constructor
> * use inputStream parameter instead of creating a new one when using
> dataformat (that's the implementation provided in the pull request)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (CAMEL-11455) Automatic transform String to DBObject after previous conversion error
[ https://issues.apache.org/jira/browse/CAMEL-11455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11455: Component/s: (was: camel-core) > Automatic transform String to DBObject after previous conversion error > -- > > Key: CAMEL-11455 > URL: https://issues.apache.org/jira/browse/CAMEL-11455 > Project: Camel > Issue Type: Bug > Components: camel-mongodb, camel-mongodb3 >Affects Versions: 2.19.1 >Reporter: Fabrizio Spataro > Fix For: 2.19.2, 2.20.0 > > Attachments: jsonFormatterDisappear.zip > > > Hello, > i found a bug. To reproduce it you can execute the code (see attachment file). > The bug is simple: > After an invalid conversion, the automatic String -> JSON transformation used > to put a document into MongoDB collection, fail! > Application flow: > # First document can be convert to JSON, Mongodb create a document (correct) > # Second document has an error, Mongodb cannot create a document (correct) > # Third document can be convert to JSON but Mongodb cannot create a document > into collection because automatic conversion is broken!!! (BUG) > Kings regards -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11455) Automatic transform String to DBObject after previous conversion error
[ https://issues.apache.org/jira/browse/CAMEL-11455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064459#comment-16064459 ] Claus Ibsen commented on CAMEL-11455: - Can you try to modify the type converters in camel-mongodb3 / camel-mongodb to not use try .. catch but throw an exception if conversion fails. They should not really do this. > Automatic transform String to DBObject after previous conversion error > -- > > Key: CAMEL-11455 > URL: https://issues.apache.org/jira/browse/CAMEL-11455 > Project: Camel > Issue Type: Bug > Components: camel-core, camel-mongodb, camel-mongodb3 >Affects Versions: 2.19.1 >Reporter: Fabrizio Spataro > Fix For: 2.19.2, 2.20.0 > > Attachments: jsonFormatterDisappear.zip > > > Hello, > i found a bug. To reproduce it you can execute the code (see attachment file). > The bug is simple: > After an invalid conversion, the automatic String -> JSON transformation used > to put a document into MongoDB collection, fail! > Application flow: > # First document can be convert to JSON, Mongodb create a document (correct) > # Second document has an error, Mongodb cannot create a document (correct) > # Third document can be convert to JSON but Mongodb cannot create a document > into collection because automatic conversion is broken!!! (BUG) > Kings regards -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11455) Automatic transform String to DBObject after previous conversion error
[ https://issues.apache.org/jira/browse/CAMEL-11455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11455: Fix Version/s: 2.20.0 2.19.2 > Automatic transform String to DBObject after previous conversion error > -- > > Key: CAMEL-11455 > URL: https://issues.apache.org/jira/browse/CAMEL-11455 > Project: Camel > Issue Type: Bug > Components: camel-core, camel-mongodb, camel-mongodb3 >Affects Versions: 2.19.1 >Reporter: Fabrizio Spataro > Fix For: 2.19.2, 2.20.0 > > Attachments: jsonFormatterDisappear.zip > > > Hello, > i found a bug. To reproduce it you can execute the code (see attachment file). > The bug is simple: > After an invalid conversion, the automatic String -> JSON transformation used > to put a document into MongoDB collection, fail! > Application flow: > # First document can be convert to JSON, Mongodb create a document (correct) > # Second document has an error, Mongodb cannot create a document (correct) > # Third document can be convert to JSON but Mongodb cannot create a document > into collection because automatic conversion is broken!!! (BUG) > Kings regards -- This message was sent by Atlassian JIRA (v6.4.14#64029)
