[jira] [Comment Edited] (CAMEL-12976) cxf route calling rest api service throws exception
[ https://issues.apache.org/jira/browse/CAMEL-12976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708317#comment-16708317 ] Willem Jiang edited comment on CAMEL-12976 at 12/4/18 7:42 AM: --- It looks like you use the http producer to send the request. 405 error means " Method Not Allowed " My suggestion is you log the request message to check if you set a wrong HTTP method. was (Author: njiang): It looks like you use the http producer to send the request. My suggestion is you log the request message to check if you miss anything in the request. > cxf route calling rest api service throws exception > --- > > Key: CAMEL-12976 > URL: https://issues.apache.org/jira/browse/CAMEL-12976 > Project: Camel > Issue Type: Bug > Components: camel-http-common >Affects Versions: 2.22.2 >Reporter: Matthias Fricke >Priority: Major > Attachments: HapWsProcessor.java, servertrace.txt > > > Hello, > I create a cxf route which exposes a soap ws. > Inside the route I call a rest service using a second route. (Its just a soap > proxy for a rest call) > However, the rest service call gives back a http 405. > If I call the rest service directly from SoapUI, everything works as expected. > I have attached the trace of my camel server. > i have also attached my camel processor class. > It has two routes, one "direct:getOperatorsProviderRequestAll" works just > fine. > The second route "direct:getOperatorsProviderRequestByID" is producing the > error. > I read about the ticket https://issues.apache.org/jira/browse/CAMEL-11951 > I thought it might be a similar problem? > Thanks and regards > Matthias > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12944) camel-ribbon : Avoid potentially conflicting jetty port during test execution
[ https://issues.apache.org/jira/browse/CAMEL-12944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Önder Sezgin resolved CAMEL-12944. -- Resolution: Fixed > camel-ribbon : Avoid potentially conflicting jetty port during test execution > - > > Key: CAMEL-12944 > URL: https://issues.apache.org/jira/browse/CAMEL-12944 > Project: Camel > Issue Type: Improvement >Reporter: Önder Sezgin >Assignee: Önder Sezgin >Priority: Minor > Fix For: 3.0.0, 2.24.0 > > > Would be good to read ports from properties files or some other option etc... > See PR > https://github.com/apache/camel/pull/2549 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12944) camel-ribbon : Avoid potentially conflicting jetty port during test execution
[
https://issues.apache.org/jira/browse/CAMEL-12944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708323#comment-16708323
]
ASF GitHub Bot commented on CAMEL-12944:
onderson closed pull request #2651: CAMEL-12944 - externalize configs as PR
#2549 tried
URL: https://github.com/apache/camel/pull/2651
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/components/camel-ribbon/src/test/java/org/apache/camel/component/ribbon/cloud/SpringRibbonServiceCallRouteTest.java
b/components/camel-ribbon/src/test/java/org/apache/camel/component/ribbon/cloud/SpringRibbonServiceCallRouteTest.java
index 0ca03f8edba..a83e2103a8d 100644
---
a/components/camel-ribbon/src/test/java/org/apache/camel/component/ribbon/cloud/SpringRibbonServiceCallRouteTest.java
+++
b/components/camel-ribbon/src/test/java/org/apache/camel/component/ribbon/cloud/SpringRibbonServiceCallRouteTest.java
@@ -21,6 +21,7 @@
import org.apache.camel.Navigate;
import org.apache.camel.Processor;
+import org.apache.camel.PropertyInject;
import org.apache.camel.Route;
import org.apache.camel.impl.cloud.DefaultServiceCallProcessor;
import org.apache.camel.test.spring.CamelSpringTestSupport;
@@ -30,16 +31,23 @@
@DirtiesContext
public abstract class SpringRibbonServiceCallRouteTest extends
CamelSpringTestSupport {
+
+@PropertyInject("firstPort")
+private String firstPort;
+
+@PropertyInject("secondPort")
+private String secondPort;
+
@Test
public void testServiceCall() throws Exception {
-getMockEndpoint("mock:9090").expectedMessageCount(1);
-getMockEndpoint("mock:9091").expectedMessageCount(1);
+getMockEndpoint("mock:{{firstPort}}").expectedMessageCount(1);
+getMockEndpoint("mock:{{secondPort}}").expectedMessageCount(1);
getMockEndpoint("mock:result").expectedMessageCount(2);
String out = template.requestBody("direct:start", null, String.class);
String out2 = template.requestBody("direct:start", null, String.class);
-assertEquals("9091", out);
-assertEquals("9090", out2);
+assertEquals(secondPort, out);
+assertEquals(firstPort, out2);
assertMockEndpointsSatisfied();
}
diff --git
a/components/camel-ribbon/src/test/resources/org/apache/camel/component/ribbon/cloud/SpringBeanRibbonServiceCallRouteTest.xml
b/components/camel-ribbon/src/test/resources/org/apache/camel/component/ribbon/cloud/SpringBeanRibbonServiceCallRouteTest.xml
index 55654bf47c0..692bd689d16 100644
---
a/components/camel-ribbon/src/test/resources/org/apache/camel/component/ribbon/cloud/SpringBeanRibbonServiceCallRouteTest.xml
+++
b/components/camel-ribbon/src/test/resources/org/apache/camel/component/ribbon/cloud/SpringBeanRibbonServiceCallRouteTest.xml
@@ -24,10 +24,14 @@
http://www.springframework.org/schema/beans/spring-beans.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd;>
+
+
+
+
-
+
@@ -48,18 +52,18 @@
- http://localhost:9090"/>
-
+ http://localhost:{{firstPort}}"/>
+
-9090
+{{firstPort}}
- http://localhost:9091"/>
-
+ http://localhost:{{secondPort}}"/>
+
-9091
+{{secondPort}}
diff --git
a/components/camel-ribbon/src/test/resources/org/apache/camel/component/ribbon/cloud/SpringDslRibbonPropertiesServiceCallRouteTest.xml
b/components/camel-ribbon/src/test/resources/org/apache/camel/component/ribbon/cloud/SpringDslRibbonPropertiesServiceCallRouteTest.xml
index 6fb2da3cf56..368833e3e62 100644
---
a/components/camel-ribbon/src/test/resources/org/apache/camel/component/ribbon/cloud/SpringDslRibbonPropertiesServiceCallRouteTest.xml
+++
b/components/camel-ribbon/src/test/resources/org/apache/camel/component/ribbon/cloud/SpringDslRibbonPropertiesServiceCallRouteTest.xml
@@ -25,31 +25,35 @@
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd;>
+
+
+
+
http://camel.apache.org/schema/spring;>
-
+
- http://localhost:9090"/>
-
+ http://localhost:{{firstPort}}"/>
+
-9090
+{{firstPort}}
- http://localhost:9091"/>
-
+ http://localhost:{{secondPort}}"/>
+
-9091
+{{secondPort}}
diff --git
[jira] [Commented] (CAMEL-12976) cxf route calling rest api service throws exception
[ https://issues.apache.org/jira/browse/CAMEL-12976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708317#comment-16708317 ] Willem Jiang commented on CAMEL-12976: -- It looks like you use the http producer to send the request. My suggestion is you log the request message to check if you miss anything in the request. > cxf route calling rest api service throws exception > --- > > Key: CAMEL-12976 > URL: https://issues.apache.org/jira/browse/CAMEL-12976 > Project: Camel > Issue Type: Bug > Components: camel-http-common >Affects Versions: 2.22.2 >Reporter: Matthias Fricke >Priority: Major > Attachments: HapWsProcessor.java, servertrace.txt > > > Hello, > I create a cxf route which exposes a soap ws. > Inside the route I call a rest service using a second route. (Its just a soap > proxy for a rest call) > However, the rest service call gives back a http 405. > If I call the rest service directly from SoapUI, everything works as expected. > I have attached the trace of my camel server. > i have also attached my camel processor class. > It has two routes, one "direct:getOperatorsProviderRequestAll" works just > fine. > The second route "direct:getOperatorsProviderRequestByID" is producing the > error. > I read about the ticket https://issues.apache.org/jira/browse/CAMEL-11951 > I thought it might be a similar problem? > Thanks and regards > Matthias > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12976) cxf route calling rest api service throws exception
[ https://issues.apache.org/jira/browse/CAMEL-12976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708303#comment-16708303 ] Andrea Cosentino commented on CAMEL-12976: -- Nobody will be cruzified here. Simply, it is much easier to get some feedback on the mailing list from users community than in the JIRA. Maybe someone already experienced something like this. > cxf route calling rest api service throws exception > --- > > Key: CAMEL-12976 > URL: https://issues.apache.org/jira/browse/CAMEL-12976 > Project: Camel > Issue Type: Bug > Components: camel-http-common >Affects Versions: 2.22.2 >Reporter: Matthias Fricke >Priority: Major > Attachments: HapWsProcessor.java, servertrace.txt > > > Hello, > I create a cxf route which exposes a soap ws. > Inside the route I call a rest service using a second route. (Its just a soap > proxy for a rest call) > However, the rest service call gives back a http 405. > If I call the rest service directly from SoapUI, everything works as expected. > I have attached the trace of my camel server. > i have also attached my camel processor class. > It has two routes, one "direct:getOperatorsProviderRequestAll" works just > fine. > The second route "direct:getOperatorsProviderRequestByID" is producing the > error. > I read about the ticket https://issues.apache.org/jira/browse/CAMEL-11951 > I thought it might be a similar problem? > Thanks and regards > Matthias > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12976) cxf route calling rest api service throws exception
[ https://issues.apache.org/jira/browse/CAMEL-12976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708300#comment-16708300 ] Matthias Fricke commented on CAMEL-12976: - No, and İ hope İ wont get cruzified for not having done that first. Best Matthias > cxf route calling rest api service throws exception > --- > > Key: CAMEL-12976 > URL: https://issues.apache.org/jira/browse/CAMEL-12976 > Project: Camel > Issue Type: Bug > Components: camel-http-common >Affects Versions: 2.22.2 >Reporter: Matthias Fricke >Priority: Major > Attachments: HapWsProcessor.java, servertrace.txt > > > Hello, > I create a cxf route which exposes a soap ws. > Inside the route I call a rest service using a second route. (Its just a soap > proxy for a rest call) > However, the rest service call gives back a http 405. > If I call the rest service directly from SoapUI, everything works as expected. > I have attached the trace of my camel server. > i have also attached my camel processor class. > It has two routes, one "direct:getOperatorsProviderRequestAll" works just > fine. > The second route "direct:getOperatorsProviderRequestByID" is producing the > error. > I read about the ticket https://issues.apache.org/jira/browse/CAMEL-11951 > I thought it might be a similar problem? > Thanks and regards > Matthias > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12944) camel-ribbon : Avoid potentially conflicting jetty port during test execution
[ https://issues.apache.org/jira/browse/CAMEL-12944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707874#comment-16707874 ] ASF GitHub Bot commented on CAMEL-12944: onderson opened a new pull request #2651: CAMEL-12944 - externalize configs as PR #2549 tried URL: https://github.com/apache/camel/pull/2651 to avoid potentially conflicting jetty port during test execution This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > camel-ribbon : Avoid potentially conflicting jetty port during test execution > - > > Key: CAMEL-12944 > URL: https://issues.apache.org/jira/browse/CAMEL-12944 > Project: Camel > Issue Type: Improvement >Reporter: Önder Sezgin >Assignee: Önder Sezgin >Priority: Minor > Fix For: 3.0.0, 2.24.0 > > > Would be good to read ports from properties files or some other option etc... > See PR > https://github.com/apache/camel/pull/2549 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-12944) camel-ribbon : Avoid potentially conflicting jetty port during test execution
[ https://issues.apache.org/jira/browse/CAMEL-12944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Önder Sezgin reassigned CAMEL-12944: Assignee: Önder Sezgin > camel-ribbon : Avoid potentially conflicting jetty port during test execution > - > > Key: CAMEL-12944 > URL: https://issues.apache.org/jira/browse/CAMEL-12944 > Project: Camel > Issue Type: Improvement >Reporter: Önder Sezgin >Assignee: Önder Sezgin >Priority: Minor > Fix For: 3.0.0, 2.24.0 > > > Would be good to read ports from properties files or some other option etc... > See PR > https://github.com/apache/camel/pull/2549 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-12968) DefaultFluentProducerTemplate is not thread safe (endpoint, etc.)
[
https://issues.apache.org/jira/browse/CAMEL-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707753#comment-16707753
]
Paul D Johe edited comment on CAMEL-12968 at 12/3/18 8:42 PM:
--
We have worked around this issue by no longer using the FluentTemplateProducer
that is produced in the CamelAutoConfiguration, but instead using
{code:java}
@EndpointInject(uri=...)
private FluentTemplateProducer templateProducer;{code}
Thus we avoid the 'FluentTemplateProducer.to(...)' call that was giving us
trouble.
Perhaps consider removing the FluentTemplateProducer from the camel autoconfig,
or perhaps change the API altogether and have
fluentTemplateProducer.createBuilder().to(...).body(...).header(...).send();
where createBuilder() always returns a new object instance that does not affect
the state of the main fluentTemplateProducer object instance:
{code:java}
public DefaultFluentProducerTemplate {
public FluentTemplateProducerBuilder createBuilder() {
return new FluentTemplateProducerBuilder(this);
}
public static class FluentTemplateProducerBuilder {
// This class contains state (endpoint, processor, body, headers)
// That is, all 'fluent methods' as well as the send methods.
// It can have a reference to its DefaultFluentProducerTemplate parent
// so when needed it can call objects there (ProducerTemplate, etc.)
}
}{code}
was (Author: pdjohe):
We have worked around this issue by no longer using the FluentTemplateProducer
that is produced in the CamelAutoConfiguration, but instead using
{code:java}
@EndpointInject(uri=...)
private FluentTemplateProducer templateProducer;{code}
Thus we avoid the 'FluentTemplateProducer.to(...)' call that was giving us
trouble.
Perhaps consider removing the FluentTemplateProducer from the camel autoconfig,
or perhaps change the API altogether and have
fluentTemplateProducer.createBuilder().to(...).body(...).header(...).send();
where createBuilder() always returns a new object instance that does not affect
the state of the main fluentTemplateProducer object instance:
{code:java}
public DefaultFluentProducerTemplate {
public FluentTemplateProducerBuilder createBuilder() {
return new FluentTemplateProducerBuilder(this);
}
public static class FluentTemplateProducerBuilder {
// This class contains state (endpoint, processor, body, headers)
// That is, all 'fluent methods' as well as the send methods.
// It can have a reference to it's DefaultFluentProducerTemplate parent
// So when needed it can call objects there (ProducerTemplate, etc.)
}
}{code}
> DefaultFluentProducerTemplate is not thread safe (endpoint, etc.)
> -
>
> Key: CAMEL-12968
> URL: https://issues.apache.org/jira/browse/CAMEL-12968
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.22.1, 2.23.0
>Reporter: Paul D Johe
>Priority: Major
>
> The DefaultFluentProducerTemplate saves state between method calls. This
> leads to unexpected behavior when the javadoc specifies that it should be
> thread safe.
> For example:
> # thread 1 calls fluentProducerTemplate.to("direct:a").send("message1");
> # thread 2 calls fluentProducerTemplate.to("direct:b").send("message2");
> If these are run in parallel, the sequence of calls can be:
> # thread 1 calls to("direct:a") - endpoint in the object is direct:a
> # thread 2 calls to("direct:b") - endpoint in the object is direct:b
> # *thread 1 calls send("message1") - this gets sent incorrectly to direct:b*
> # thread 2 calls send("message2") - this gets sent correctly to direct:b
> Endpoint is one example, but almost all fields in this class share this
> behavior. It should be clearly documented which fields can be used fluently
> over multiple threads, and which cannot. As the API is today, all methods
> returning 'this' should be made thread-safe (state is only local to the
> caller) so that the fluent interface works as expected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-12968) DefaultFluentProducerTemplate is not thread safe (endpoint, etc.)
[
https://issues.apache.org/jira/browse/CAMEL-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707753#comment-16707753
]
Paul D Johe edited comment on CAMEL-12968 at 12/3/18 8:41 PM:
--
We have worked around this issue by no longer using the FluentTemplateProducer
that is produced in the CamelAutoConfiguration, but instead using
{code:java}
@EndpointInject(uri=...)
private FluentTemplateProducer templateProducer;{code}
Thus we avoid the 'FluentTemplateProducer.to(...)' call that was giving us
trouble.
Perhaps consider removing the FluentTemplateProducer from the camel autoconfig,
or perhaps change the API altogether and have
fluentTemplateProducer.createBuilder().to(...).body(...).header(...).send();
where createBuilder() always returns a new object instance that does not affect
the state of the main fluentTemplateProducer object instance:
{code:java}
public DefaultFluentProducerTemplate {
public FluentTemplateProducerBuilder createBuilder() {
return new FluentTemplateProducerBuilder(this);
}
public static class FluentTemplateProducerBuilder {
// This class contains state (endpoint, processor, body, headers)
// That is, all 'fluent methods' as well as the send methods.
// It can have a reference to it's DefaultFluentProducerTemplate parent
// So when needed it can call objects there (ProducerTemplate, etc.)
}
}{code}
was (Author: pdjohe):
We have worked around this issue by no longer using the FluentTemplateProducer
this is produced in the CamelAutoConfiguration, but instead using
@EndpointInject(uri=...) FluentTemplateProducer fields everywhere, thus
avoiding the 'FluentTemplateProducer.to(...)' call.
Perhaps consider removing the FluentTemplateProducer from the camel autoconfig,
or perhaps change the API altogether and have
fluentTemplateProducer.createBuilder().to(...).body(...).header(...).send();
where createBuilder() always returns a new object instance that does not affect
the state of the main fluentTemplateProducer object instance.
> DefaultFluentProducerTemplate is not thread safe (endpoint, etc.)
> -
>
> Key: CAMEL-12968
> URL: https://issues.apache.org/jira/browse/CAMEL-12968
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.22.1, 2.23.0
>Reporter: Paul D Johe
>Priority: Major
>
> The DefaultFluentProducerTemplate saves state between method calls. This
> leads to unexpected behavior when the javadoc specifies that it should be
> thread safe.
> For example:
> # thread 1 calls fluentProducerTemplate.to("direct:a").send("message1");
> # thread 2 calls fluentProducerTemplate.to("direct:b").send("message2");
> If these are run in parallel, the sequence of calls can be:
> # thread 1 calls to("direct:a") - endpoint in the object is direct:a
> # thread 2 calls to("direct:b") - endpoint in the object is direct:b
> # *thread 1 calls send("message1") - this gets sent incorrectly to direct:b*
> # thread 2 calls send("message2") - this gets sent correctly to direct:b
> Endpoint is one example, but almost all fields in this class share this
> behavior. It should be clearly documented which fields can be used fluently
> over multiple threads, and which cannot. As the API is today, all methods
> returning 'this' should be made thread-safe (state is only local to the
> caller) so that the fluent interface works as expected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12968) DefaultFluentProducerTemplate is not thread safe (endpoint, etc.)
[
https://issues.apache.org/jira/browse/CAMEL-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707753#comment-16707753
]
Paul D Johe commented on CAMEL-12968:
-
We have worked around this issue by no longer using the FluentTemplateProducer
this is produced in the CamelAutoConfiguration, but instead using
@EndpointInject(uri=...) FluentTemplateProducer fields everywhere, thus
avoiding the 'FluentTemplateProducer.to(...)' call.
Perhaps consider removing the FluentTemplateProducer from the camel autoconfig,
or perhaps change the API altogether and have
fluentTemplateProducer.createBuilder().to(...).body(...).header(...).send();
where createBuilder() always returns a new object instance that does not affect
the state of the main fluentTemplateProducer object instance.
> DefaultFluentProducerTemplate is not thread safe (endpoint, etc.)
> -
>
> Key: CAMEL-12968
> URL: https://issues.apache.org/jira/browse/CAMEL-12968
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.22.1, 2.23.0
>Reporter: Paul D Johe
>Priority: Major
>
> The DefaultFluentProducerTemplate saves state between method calls. This
> leads to unexpected behavior when the javadoc specifies that it should be
> thread safe.
> For example:
> # thread 1 calls fluentProducerTemplate.to("direct:a").send("message1");
> # thread 2 calls fluentProducerTemplate.to("direct:b").send("message2");
> If these are run in parallel, the sequence of calls can be:
> # thread 1 calls to("direct:a") - endpoint in the object is direct:a
> # thread 2 calls to("direct:b") - endpoint in the object is direct:b
> # *thread 1 calls send("message1") - this gets sent incorrectly to direct:b*
> # thread 2 calls send("message2") - this gets sent correctly to direct:b
> Endpoint is one example, but almost all fields in this class share this
> behavior. It should be clearly documented which fields can be used fluently
> over multiple threads, and which cannot. As the API is today, all methods
> returning 'this' should be made thread-safe (state is only local to the
> caller) so that the fluent interface works as expected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12605) Enhance the AS2 Component to send and receive encrypted AS2 messages
[ https://issues.apache.org/jira/browse/CAMEL-12605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707636#comment-16707636 ] ASF GitHub Bot commented on CAMEL-12605: punkhorn opened a new pull request #2650: [CAMEL-12605] Added further tests and fixes for compression URL: https://github.com/apache/camel/pull/2650 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Enhance the AS2 Component to send and receive encrypted AS2 messages > > > Key: CAMEL-12605 > URL: https://issues.apache.org/jira/browse/CAMEL-12605 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.23.0 >Reporter: William Collins >Assignee: William Collins >Priority: Major > > Enhance the AS2 Component to support encrypted AS2 messages per RFC4130 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12976) cxf route calling rest api service throws exception
[ https://issues.apache.org/jira/browse/CAMEL-12976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707586#comment-16707586 ] Andrea Cosentino commented on CAMEL-12976: -- Did you post this question on the users mailing list first? > cxf route calling rest api service throws exception > --- > > Key: CAMEL-12976 > URL: https://issues.apache.org/jira/browse/CAMEL-12976 > Project: Camel > Issue Type: Bug > Components: camel-http-common >Affects Versions: 2.22.2 >Reporter: Matthias Fricke >Priority: Major > Attachments: HapWsProcessor.java, servertrace.txt > > > Hello, > I create a cxf route which exposes a soap ws. > Inside the route I call a rest service using a second route. (Its just a soap > proxy for a rest call) > However, the rest service call gives back a http 405. > If I call the rest service directly from SoapUI, everything works as expected. > I have attached the trace of my camel server. > i have also attached my camel processor class. > It has two routes, one "direct:getOperatorsProviderRequestAll" works just > fine. > The second route "direct:getOperatorsProviderRequestByID" is producing the > error. > I read about the ticket https://issues.apache.org/jira/browse/CAMEL-11951 > I thought it might be a similar problem? > Thanks and regards > Matthias > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12976) cxf route calling rest api service throws exception
Matthias Fricke created CAMEL-12976: --- Summary: cxf route calling rest api service throws exception Key: CAMEL-12976 URL: https://issues.apache.org/jira/browse/CAMEL-12976 Project: Camel Issue Type: Bug Components: camel-http-common Affects Versions: 2.22.2 Reporter: Matthias Fricke Attachments: HapWsProcessor.java, servertrace.txt Hello, I create a cxf route which exposes a soap ws. Inside the route I call a rest service using a second route. (Its just a soap proxy for a rest call) However, the rest service call gives back a http 405. If I call the rest service directly from SoapUI, everything works as expected. I have attached the trace of my camel server. i have also attached my camel processor class. It has two routes, one "direct:getOperatorsProviderRequestAll" works just fine. The second route "direct:getOperatorsProviderRequestByID" is producing the error. I read about the ticket https://issues.apache.org/jira/browse/CAMEL-11951 I thought it might be a similar problem? Thanks and regards Matthias -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12975) WARN: No CamelContext defined yet so cannot inject into bean: org.apache.camel.converter.jaxb.FallbackTypeConverter
Pascal Schumacher created CAMEL-12975:
-
Summary: WARN: No CamelContext defined yet so cannot inject into
bean: org.apache.camel.converter.jaxb.FallbackTypeConverter
Key: CAMEL-12975
URL: https://issues.apache.org/jira/browse/CAMEL-12975
Project: Camel
Issue Type: Bug
Components: camel-jaxb, camel-spring-boot-starters
Affects Versions: 2.23.0
Reporter: Pascal Schumacher
I'm using camel-jaxb-starter 2.23.0 in combination with Spring Boot 2.1.1.
During start-up this warning is displayed:
{{WARN 15204 --- [ main] o.a.c.i.DefaultCamelBeanPostProcessor:
No CamelContext defined yet so cannot inject into bean:
org.apache.camel.converter.jaxb.FallbackTypeConverter}}
Otherwise everything is working fine (as far as I can tell).
I created a minimal project that allows reproducing this warning:
https://github.com/PascalSchumacher/CamelJaxbStartupWarning
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12974) Route coverage: When and otherwise are not marked as covered
[
https://issues.apache.org/jira/browse/CAMEL-12974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aurélien Pupier updated CAMEL-12974:
Description:
- use a route with a choice with when and otherwise inside.
- launch mvn test camel:route-coverage
- when and otherwise are marked with a 0 count even if they were used
examples of the CBR examples available in Eclipse Fuse Tooling:
{noformat}Route:cbr-route
Line # Count Route
-- - -
33 5 from
34 5 log
35 5 choice
36 0 when
38 2 log
39 2 to
41 0 when
43 2 log
44 2 to
46 0 otherwise
47 1 log
48 1 to
51 5 log
Coverage: 10 out of 13 (76.9%){noformat}
we can notice that elements inside when and otherwise are well counted but when
and otherwise are at 0
was:
- use a route with a choice with when and otherwise inside.
- launch mvn test camel:route-coverage
- when and otherwise are marked with a 0 count even if they were used
examples of the CBR examples available in Eclipse Fuse Tooling:
{quote}Route: cbr-route
Line # Count Route
-- - -
33 5 from
34 5 log
35 5 choice
36 0 when
38 2 log
39 2 to
41 0 when
43 2 log
44 2 to
46 0 otherwise
47 1 log
48 1 to
51 5 log
Coverage: 10 out of 13 (76.9%){quote}
we can notice that elements inside when and otherwise are well counted but when
and otherwise are at 0
> Route coverage: When and otherwise are not marked as covered
>
>
> Key: CAMEL-12974
> URL: https://issues.apache.org/jira/browse/CAMEL-12974
> Project: Camel
> Issue Type: Bug
> Components: tooling
>Affects Versions: 2.21.0
>Reporter: Aurélien Pupier
>Priority: Major
>
> - use a route with a choice with when and otherwise inside.
> - launch mvn test camel:route-coverage
> - when and otherwise are marked with a 0 count even if they were used
> examples of the CBR examples available in Eclipse Fuse Tooling:
> {noformat}Route: cbr-route
> Line # Count Route
> -- - -
> 33 5 from
> 34 5 log
> 35 5 choice
> 36 0 when
> 38 2 log
> 39 2 to
> 41 0 when
> 43 2 log
> 44 2 to
> 46 0 otherwise
> 47 1 log
> 48 1 to
> 51 5 log
> Coverage: 10 out of 13 (76.9%){noformat}
> we can notice that elements inside when and otherwise are well counted but
> when and otherwise are at 0
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12974) Route coverage: When and otherwise are not marked as covered
[
https://issues.apache.org/jira/browse/CAMEL-12974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aurélien Pupier updated CAMEL-12974:
Component/s: tooling
> Route coverage: When and otherwise are not marked as covered
>
>
> Key: CAMEL-12974
> URL: https://issues.apache.org/jira/browse/CAMEL-12974
> Project: Camel
> Issue Type: Bug
> Components: tooling
>Affects Versions: 2.21.0
>Reporter: Aurélien Pupier
>Priority: Major
>
> - use a route with a choice with when and otherwise inside.
> - launch mvn test camel:route-coverage
> - when and otherwise are marked with a 0 count even if they were used
> examples of the CBR examples available in Eclipse Fuse Tooling:
> {quote}Route: cbr-route
> Line # Count Route
> -- - -
> 33 5 from
> 34 5 log
> 35 5 choice
> 36 0 when
> 38 2 log
> 39 2 to
> 41 0 when
> 43 2 log
> 44 2 to
> 46 0 otherwise
> 47 1 log
> 48 1 to
> 51 5 log
> Coverage: 10 out of 13 (76.9%){quote}
> we can notice that elements inside when and otherwise are well counted but
> when and otherwise are at 0
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12974) Route coverage: When and otherwise are not marked as covered
Aurélien Pupier created CAMEL-12974:
---
Summary: Route coverage: When and otherwise are not marked as
covered
Key: CAMEL-12974
URL: https://issues.apache.org/jira/browse/CAMEL-12974
Project: Camel
Issue Type: Bug
Affects Versions: 2.21.0
Reporter: Aurélien Pupier
- use a route with a choice with when and otherwise inside.
- launch mvn test camel:route-coverage
- when and otherwise are marked with a 0 count even if they were used
examples of the CBR examples available in Eclipse Fuse Tooling:
{quote}Route: cbr-route
Line # Count Route
-- - -
33 5 from
34 5 log
35 5 choice
36 0 when
38 2 log
39 2 to
41 0 when
43 2 log
44 2 to
46 0 otherwise
47 1 log
48 1 to
51 5 log
Coverage: 10 out of 13 (76.9%){quote}
we can notice that elements inside when and otherwise are well counted but when
and otherwise are at 0
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12964) Create new CamelWIH to integrate with recently added Camel support in jBPM/KIE-Server
[
https://issues.apache.org/jira/browse/CAMEL-12964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707041#comment-16707041
]
ASF GitHub Bot commented on CAMEL-12964:
oscerd closed pull request #2644: CAMEL-12964: Initial import of jBPM CamelWIH
and Command.
URL: https://github.com/apache/camel/pull/2644
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/components/camel-jbpm/pom.xml b/components/camel-jbpm/pom.xml
index 2a5a161e5db..02b4540db60 100644
--- a/components/camel-jbpm/pom.xml
+++ b/components/camel-jbpm/pom.xml
@@ -92,6 +92,15 @@
true
+
+
+ org.jbpm
+ jbpm-workitems-core
+ ${jbpm-version}
+ provided
+ true
+
+
org.jboss.logging
jboss-logging
@@ -128,6 +137,24 @@
camel-test
test
+
+ org.mockito
+ mockito-core
+ test
+
+
+org.jbpm
+jbpm-workitems-core
+${jbpm-version}
+test-jar
+test
+
+
+ xml-apis
+ xml-apis
+
+
+
diff --git
a/components/camel-jbpm/src/main/java/org/apache/camel/component/jbpm/JBPMConstants.java
b/components/camel-jbpm/src/main/java/org/apache/camel/component/jbpm/JBPMConstants.java
index 8341cfd619c..94ff0ca77ba 100644
---
a/components/camel-jbpm/src/main/java/org/apache/camel/component/jbpm/JBPMConstants.java
+++
b/components/camel-jbpm/src/main/java/org/apache/camel/component/jbpm/JBPMConstants.java
@@ -43,4 +43,12 @@
String JBPM_TASK_EVENT_LISTENER = "task";
String JBPM_CASE_EVENT_LISTENER = "case";
String JBPM_EVENT_EMITTER = "emitter";
+
+String GLOBAL_CAMEL_CONTEXT_SERVICE_KEY = "GlobalCamelService";
+String DEPLOYMENT_CAMEL_CONTEXT_SERVICE_KEY_POSTFIX = "_CamelService";
+String CAMEL_ENDPOINT_ID_WI_PARAM = "CamelEndpointId";
+String RESPONSE_WI_PARAM = "Response";
+String MESSAGE_WI_PARAM = "Message";
+
+
}
diff --git
a/components/camel-jbpm/src/main/java/org/apache/camel/component/jbpm/server/CamelKieServerExtension.java
b/components/camel-jbpm/src/main/java/org/apache/camel/component/jbpm/server/CamelKieServerExtension.java
index 0e297bece0f..659a498c2db 100644
---
a/components/camel-jbpm/src/main/java/org/apache/camel/component/jbpm/server/CamelKieServerExtension.java
+++
b/components/camel-jbpm/src/main/java/org/apache/camel/component/jbpm/server/CamelKieServerExtension.java
@@ -23,6 +23,7 @@
import java.util.List;
import java.util.Map;
+import org.apache.camel.component.jbpm.JBPMConstants;
import org.apache.camel.impl.DefaultCamelContext;
import org.apache.camel.model.FromDefinition;
import org.apache.camel.model.RouteDefinition;
@@ -85,7 +86,7 @@ public void init(KieServerImpl kieServer, KieServerRegistry
registry) {
}
}
-ServiceRegistry.get().register("GlobalCamelService", this.camel);
+
ServiceRegistry.get().register(JBPMConstants.GLOBAL_CAMEL_CONTEXT_SERVICE_KEY,
this.camel);
}
@Override
@@ -117,7 +118,7 @@ public void createContainer(String id, KieContainerInstance
kieContainerInstance
context.start();
camelContexts.put(id, context);
-ServiceRegistry.get().register(id + "_CamelService", context);
+ServiceRegistry.get().register(id +
JBPMConstants.DEPLOYMENT_CAMEL_CONTEXT_SERVICE_KEY_POSTFIX, context);
}
} catch (Exception e) {
diff --git
a/components/camel-jbpm/src/main/java/org/apache/camel/component/jbpm/workitem/AbstractCamelCommand.java
b/components/camel-jbpm/src/main/java/org/apache/camel/component/jbpm/workitem/AbstractCamelCommand.java
new file mode 100644
index 000..a26aa321710
--- /dev/null
+++
b/components/camel-jbpm/src/main/java/org/apache/camel/component/jbpm/workitem/AbstractCamelCommand.java
@@ -0,0 +1,85 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the
[jira] [Commented] (CAMEL-12973) AbstractCamelWorkItemHandler init fails when WIH is loaded before CamelContext is created.
[ https://issues.apache.org/jira/browse/CAMEL-12973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16706991#comment-16706991 ] ASF GitHub Bot commented on CAMEL-12973: DuncanDoyle opened a new pull request #2649: CAMEL-12973: Init deferred to first call when WIH uses Deployment-sco… URL: https://github.com/apache/camel/pull/2649 …ped context in combination with Singleton RuntimeStrategy. Removed redundant double slash from 'direct' URL. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > AbstractCamelWorkItemHandler init fails when WIH is loaded before > CamelContext is created. > -- > > Key: CAMEL-12973 > URL: https://issues.apache.org/jira/browse/CAMEL-12973 > Project: Camel > Issue Type: Bug > Components: camel-jbpm >Affects Versions: 2.23.0 >Reporter: Duncan Doyle >Assignee: Maciej Swiderski >Priority: Major > > When the AbstractCamelWorkItemHandler is created before the referenced > CamelContext is created and registered, deployment of a KJAR fails with an > IllegalArgumentException. > This can happen when the deployment uses a combination of a Singleton > RuntimeStrategy and a Deployment-scoped CamelContext. This is due to the fact > that the jBPM KIE-Server extension runs after the jBPM extension. > In such a situation we need to defer the creation of the ProducerTemplate > until the first call to WIH.execute. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12973) AbstractCamelWorkItemHandler init fails when WIH is loaded before CamelContext is created.
[ https://issues.apache.org/jira/browse/CAMEL-12973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-12973: - Affects Version/s: (was: 2.23.1) 2.23.0 > AbstractCamelWorkItemHandler init fails when WIH is loaded before > CamelContext is created. > -- > > Key: CAMEL-12973 > URL: https://issues.apache.org/jira/browse/CAMEL-12973 > Project: Camel > Issue Type: Bug > Components: camel-jbpm >Affects Versions: 2.23.0 >Reporter: Duncan Doyle >Assignee: Maciej Swiderski >Priority: Major > > When the AbstractCamelWorkItemHandler is created before the referenced > CamelContext is created and registered, deployment of a KJAR fails with an > IllegalArgumentException. > This can happen when the deployment uses a combination of a Singleton > RuntimeStrategy and a Deployment-scoped CamelContext. This is due to the fact > that the jBPM KIE-Server extension runs after the jBPM extension. > In such a situation we need to defer the creation of the ProducerTemplate > until the first call to WIH.execute. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12973) AbstractCamelWorkItemHandler init fails when WIH is loaded before CamelContext is created.
Duncan Doyle created CAMEL-12973: Summary: AbstractCamelWorkItemHandler init fails when WIH is loaded before CamelContext is created. Key: CAMEL-12973 URL: https://issues.apache.org/jira/browse/CAMEL-12973 Project: Camel Issue Type: Bug Components: camel-jbpm Affects Versions: 2.23.1 Reporter: Duncan Doyle Assignee: Maciej Swiderski When the AbstractCamelWorkItemHandler is created before the referenced CamelContext is created and registered, deployment of a KJAR fails with an IllegalArgumentException. This can happen when the deployment uses a combination of a Singleton RuntimeStrategy and a Deployment-scoped CamelContext. This is due to the fact that the jBPM KIE-Server extension runs after the jBPM extension. In such a situation we need to defer the creation of the ProducerTemplate until the first call to WIH.execute. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12948) Camel-Box: Download file version
[ https://issues.apache.org/jira/browse/CAMEL-12948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16706914#comment-16706914 ] Vladimir commented on CAMEL-12948: -- I can't setup environment to test this. I am doing something wrong but... > Camel-Box: Download file version > > > Key: CAMEL-12948 > URL: https://issues.apache.org/jira/browse/CAMEL-12948 > Project: Camel > Issue Type: Bug > Components: camel-box >Affects Versions: 2.22.1 >Reporter: Vladimir >Assignee: Andrea Cosentino >Priority: Major > Fix For: 2.24.0 > > > Provided endpoint is not functional. > Exception : Failed to resolve endpoint: box://files/downloadVersion due to: > No matching method for files/downloadVersion, with arguments []. > The issue is explained here : > [http://camel.465427.n5.nabble.com/Camel-box-download-file-version-td5825974.html] > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12971) SJMS Component javax.jms.JMSException: Unmatched acknowledge: MessageAck when transactionBatchTimeout expired
[
https://issues.apache.org/jira/browse/CAMEL-12971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kachalov updated CAMEL-12971:
Description:
We use Apache ActiveMQ 5.15.2 and Camel 2.20.2.
When we switched to use camel-sjms instead of camel-jms we sometimes get this
error:
{code:java}
2018-11-30 20:39:33,264 +0300 INFO 19 [TransactionContext] commit failed for
transaction TX:ID:a-kachalov-61507-1543599563462-1:1:2
javax.jms.JMSException: COMMIT FAILED: Transaction marked rollback only
xaErrorCode:100
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54)
~[activemq-client-5.15.2.jar:5.15.2]
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1399)
~[activemq-client-5.15.2.jar:?]
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1428)
~[activemq-client-5.15.2.jar:?]
at
org.apache.activemq.BatchSynchronizationReproduceTest$2.answer(BatchSynchronizationReproduceTest.java:66)
~[classes/:?]
at
org.apache.activemq.TransactionContext.commit(TransactionContext.java:330)
~[activemq-client-5.15.2.jar:?]
at org.apache.activemq.ActiveMQSession.commit(ActiveMQSession.java:582)
[activemq-client-5.15.2.jar:?]
at
org.apache.camel.component.sjms.tx.SessionBatchTransactionSynchronization$TimeoutTask.run(SessionBatchTransactionSynchronization.java:135)
[camel-sjms-2.20.2.jar:2.20.2]
at java.util.TimerThread.mainLoop(Timer.java:555) [?:1.8.0_73]
at java.util.TimerThread.run(Timer.java:505) [?:1.8.0_73]
Caused by: javax.transaction.xa.XAException: COMMIT FAILED: Transaction marked
rollback only xaErrorCode:100
at
org.apache.activemq.transaction.Transaction.newXAException(Transaction.java:213)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.transaction.Transaction.prePrepare(Transaction.java:115)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.transaction.LocalTransaction.commit(LocalTransaction.java:54)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.broker.TransactionBroker.commitTransaction(TransactionBroker.java:252)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.broker.BrokerFilter.commitTransaction(BrokerFilter.java:114)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.broker.TransportConnection.processCommitTransactionOnePhase(TransportConnection.java:529)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.command.TransactionInfo.visit(TransactionInfo.java:100)
~[activemq-client-5.15.2.jar:5.15.2]
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:330)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:194)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
~[activemq-client-5.15.2.jar:5.15.2]
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:125)
~[activemq-client-5.15.2.jar:5.15.2]
at
org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:301)
~[activemq-client-5.15.2.jar:5.15.2]
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
~[activemq-client-5.15.2.jar:5.15.2]
at
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:235)
~[activemq-client-5.15.2.jar:5.15.2]
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:216)
~[activemq-client-5.15.2.jar:5.15.2]
at java.lang.Thread.run(Thread.java:745) ~[?:1.8.0_73]
Caused by: javax.jms.TransactionRolledBackException: COMMIT FAILED: Transaction
marked rollback only xaErrorCode:100
at
org.apache.activemq.transaction.Transaction.prePrepare(Transaction.java:116)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.transaction.LocalTransaction.commit(LocalTransaction.java:54)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.broker.TransactionBroker.commitTransaction(TransactionBroker.java:252)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.broker.BrokerFilter.commitTransaction(BrokerFilter.java:114)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.broker.TransportConnection.processCommitTransactionOnePhase(TransportConnection.java:529)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.command.TransactionInfo.visit(TransactionInfo.java:100)
~[activemq-client-5.15.2.jar:5.15.2]
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:330)
~[activemq-broker-5.15.2.jar:5.15.2]
at
[jira] [Updated] (CAMEL-12971) SJMS Component javax.jms.JMSException: Unmatched acknowledge: MessageAck when transactionBatchTimeout expired
[
https://issues.apache.org/jira/browse/CAMEL-12971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kachalov updated CAMEL-12971:
Description:
We use Apache ActiveMQ 5.15.2 and Camel 2.20.2.
When we switched to use camel-sjms instead of camel-jms we sometimes get this
error:
{code:java}
2018-11-30 20:39:33,264 +0300 INFO 19 [TransactionContext] commit failed for
transaction TX:ID:a-kachalov-61507-1543599563462-1:1:2
javax.jms.JMSException: COMMIT FAILED: Transaction marked rollback only
xaErrorCode:100
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54)
~[activemq-client-5.15.2.jar:5.15.2]
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1399)
~[activemq-client-5.15.2.jar:?]
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1428)
~[activemq-client-5.15.2.jar:?]
at
org.apache.activemq.BatchSynchronizationReproduceTest$2.answer(BatchSynchronizationReproduceTest.java:66)
~[classes/:?]
at
org.apache.activemq.TransactionContext.commit(TransactionContext.java:330)
~[activemq-client-5.15.2.jar:?]
at org.apache.activemq.ActiveMQSession.commit(ActiveMQSession.java:582)
[activemq-client-5.15.2.jar:?]
at
org.apache.camel.component.sjms.tx.SessionBatchTransactionSynchronization$TimeoutTask.run(SessionBatchTransactionSynchronization.java:135)
[camel-sjms-2.20.2.jar:2.20.2]
at java.util.TimerThread.mainLoop(Timer.java:555) [?:1.8.0_73]
at java.util.TimerThread.run(Timer.java:505) [?:1.8.0_73]
Caused by: javax.transaction.xa.XAException: COMMIT FAILED: Transaction marked
rollback only xaErrorCode:100
at
org.apache.activemq.transaction.Transaction.newXAException(Transaction.java:213)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.transaction.Transaction.prePrepare(Transaction.java:115)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.transaction.LocalTransaction.commit(LocalTransaction.java:54)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.broker.TransactionBroker.commitTransaction(TransactionBroker.java:252)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.broker.BrokerFilter.commitTransaction(BrokerFilter.java:114)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.broker.TransportConnection.processCommitTransactionOnePhase(TransportConnection.java:529)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.command.TransactionInfo.visit(TransactionInfo.java:100)
~[activemq-client-5.15.2.jar:5.15.2]
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:330)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:194)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
~[activemq-client-5.15.2.jar:5.15.2]
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:125)
~[activemq-client-5.15.2.jar:5.15.2]
at
org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:301)
~[activemq-client-5.15.2.jar:5.15.2]
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
~[activemq-client-5.15.2.jar:5.15.2]
at
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:235)
~[activemq-client-5.15.2.jar:5.15.2]
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:216)
~[activemq-client-5.15.2.jar:5.15.2]
at java.lang.Thread.run(Thread.java:745) ~[?:1.8.0_73]
Caused by: javax.jms.TransactionRolledBackException: COMMIT FAILED: Transaction
marked rollback only xaErrorCode:100
at
org.apache.activemq.transaction.Transaction.prePrepare(Transaction.java:116)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.transaction.LocalTransaction.commit(LocalTransaction.java:54)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.broker.TransactionBroker.commitTransaction(TransactionBroker.java:252)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.broker.BrokerFilter.commitTransaction(BrokerFilter.java:114)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.broker.TransportConnection.processCommitTransactionOnePhase(TransportConnection.java:529)
~[activemq-broker-5.15.2.jar:5.15.2]
at
org.apache.activemq.command.TransactionInfo.visit(TransactionInfo.java:100)
~[activemq-client-5.15.2.jar:5.15.2]
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:330)
~[activemq-broker-5.15.2.jar:5.15.2]
at
[jira] [Closed] (CAMEL-12972) Components missing jaxb dependencies on Java 11
[
https://issues.apache.org/jira/browse/CAMEL-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Palaga closed CAMEL-12972.
Resolution: Invalid
I learnt in between that this problem is being solved in [~zregvart] 's
`java-10-test` branch.
> Components missing jaxb dependencies on Java 11
> ---
>
> Key: CAMEL-12972
> URL: https://issues.apache.org/jira/browse/CAMEL-12972
> Project: Camel
> Issue Type: Bug
>Reporter: Peter Palaga
>Priority: Major
>
> The {{com.sun.xml.bind:jaxb-\*}} deps are added only for Java 8 in
> camel-parent [1]. Looking at the history, it looks as a leftover of porting
> to Java 8. I came across this when porting WildFly Camel (WFC) to Java 11.
> There in WFC the problem goes away when I make this profile active for
> [1.8,). This is probably not the cleanest solution, because the
> {{com.sun.xml.bind:jaxb-\*}} dependencies are not necessary in all Maven
> modules inheriting from camel-parent. I'd be very thankful for any
> suggestions how to proceed.
> [1]
> https://github.com/apache/camel/blob/camel-2.23.0/parent/pom.xml#L5676-L5691
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
