[jira] [Comment Edited] (CAMEL-13916) website - Add migration guide page
[ https://issues.apache.org/jira/browse/CAMEL-13916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925965#comment-16925965 ] Alexandre Kieling edited comment on CAMEL-13916 at 9/9/19 5:56 PM: --- [~zregvart] does [MIGRATION.md|https://github.com/apache/camel/blob/master/MIGRATION.md] need to be moved to [https://github.com/apache/camel/tree/master/docs/user-manual/modules/ROOT/pages] and converted to asciidoc? was (Author: alexkieling): [~zregvart] does [[MIGRATION.md|https://github.com/apache/camel/blob/master/MIGRATION.md]|[https://github.com/apache/camel/blob/master/MIGRATION.md]] need to be moved to [https://github.com/apache/camel/tree/master/docs/user-manual/modules/ROOT/pages] and converted to asciidoc? > website - Add migration guide page > -- > > Key: CAMEL-13916 > URL: https://issues.apache.org/jira/browse/CAMEL-13916 > Project: Camel > Issue Type: Task > Components: website >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.0.0 > > > We need to have the migration guide on the website -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (CAMEL-13916) website - Add migration guide page
[ https://issues.apache.org/jira/browse/CAMEL-13916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925965#comment-16925965 ] Alexandre Kieling edited comment on CAMEL-13916 at 9/9/19 5:56 PM: --- [~zregvart] does [[MIGRATION.md|https://github.com/apache/camel/blob/master/MIGRATION.md]|[https://github.com/apache/camel/blob/master/MIGRATION.md]] need to be moved to [https://github.com/apache/camel/tree/master/docs/user-manual/modules/ROOT/pages] and converted to asciidoc? was (Author: alexkieling): [~zregvart] does [https://github.com/apache/camel/blob/master/MIGRATION.md|MIGRATION.md] need to be moved to [https://github.com/apache/camel/tree/master/docs/user-manual/modules/ROOT/pages] and converted to asciidoc? > website - Add migration guide page > -- > > Key: CAMEL-13916 > URL: https://issues.apache.org/jira/browse/CAMEL-13916 > Project: Camel > Issue Type: Task > Components: website >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.0.0 > > > We need to have the migration guide on the website -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (CAMEL-13916) website - Add migration guide page
[ https://issues.apache.org/jira/browse/CAMEL-13916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925965#comment-16925965 ] Alexandre Kieling edited comment on CAMEL-13916 at 9/9/19 5:55 PM: --- [~zregvart] does [https://github.com/apache/camel/blob/master/MIGRATION.md|MIGRATION.md] need to be moved to [https://github.com/apache/camel/tree/master/docs/user-manual/modules/ROOT/pages] and converted to asciidoc? was (Author: alexkieling): [~zregvart] does [[https://github.com/apache/camel/blob/master/MIGRATION.md||https://github.com/apache/camel/blob/master/MIGRATION.md] [MIGRATION.md|https://github.com/apache/camel/blob/master/MIGRATION.md] []|https://github.com/apache/camel/blob/master/MIGRATION.md] need to be moved to [https://github.com/apache/camel/tree/master/docs/user-manual/modules/ROOT/pages] and converted to asciidoc? > website - Add migration guide page > -- > > Key: CAMEL-13916 > URL: https://issues.apache.org/jira/browse/CAMEL-13916 > Project: Camel > Issue Type: Task > Components: website >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.0.0 > > > We need to have the migration guide on the website -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13916) website - Add migration guide page
[ https://issues.apache.org/jira/browse/CAMEL-13916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925965#comment-16925965 ] Alexandre Kieling commented on CAMEL-13916: --- [~zregvart] does [[https://github.com/apache/camel/blob/master/MIGRATION.md||https://github.com/apache/camel/blob/master/MIGRATION.md] [MIGRATION.md|https://github.com/apache/camel/blob/master/MIGRATION.md] []|https://github.com/apache/camel/blob/master/MIGRATION.md] need to be moved to [https://github.com/apache/camel/tree/master/docs/user-manual/modules/ROOT/pages] and converted to asciidoc? > website - Add migration guide page > -- > > Key: CAMEL-13916 > URL: https://issues.apache.org/jira/browse/CAMEL-13916 > Project: Camel > Issue Type: Task > Components: website >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.0.0 > > > We need to have the migration guide on the website -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925903#comment-16925903
]
Marco Tenti commented on CAMEL-13953:
-
Sorry freeman lost something during the copy and paste .
I have committed the absent beans.
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
> REPRODUCER PROJECT : https://github.com/p4535992/bug-load-namespace-blueprint
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925839#comment-16925839
]
Freeman Fang commented on CAMEL-13953:
--
Hi [~4535992],
I may miss something but the
src/main/resources/OSGI-INF/blueprint/blueprint.xml
in your test case seems messy for me.
1. There's several places use ref component-id="" but can't find where you
define the bean in ref
{code}
{code}
2. You have lots of Import-Package such as commons package with different
versions but I don't see where those packages comes from your test code(they
may be necessary for your real project but normally in Karaf the best practice
is to use a feature.xml to define all bundles you need, I don't see this
features.xml in your reproducer, nor in your README)
3. Plus I think most namespace in your blueprint.xml are not necessary.
Since we are talking about a Red Hat FUSE kit, I don't think community JIRA is
the appropriate place to discuss it. So please use your FUSE support channel to
get in touch with us.
Thanks!
Freeman
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
> REPRODUCER PROJECT : https://github.com/p4535992/bug-load-namespace-blueprint
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925751#comment-16925751
]
Marco Tenti commented on CAMEL-13953:
-
It's not a perfect solution, because i want to understand "why" something stop
working, but i resolved by updating the RedHat Fuse 7.3.1 to 7.4.0 and avoid
the installing of these features:
feature:install cxf-http-netty-client
feature:install cxf-http-netty-server
feature:install jms
feature:install activemq-client
feature:install pax-jms-pool-pooledjms
feature:install pax-jms-artemis
feature:install pax-jms-config
feature:install pax-jms-pool
feature:install artemis
feature:install artemis-core
feature:install artemis-core-client
feature:install artemis-jms-client
i will try to go more deep on this , but it's seem some collision lirbary order
between feature
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
> REPRODUCER PROJECT : https://github.com/p4535992/bug-load-namespace-blueprint
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925744#comment-16925744
]
Freeman Fang commented on CAMEL-13953:
--
Thanks [~4535992] for the reproducer, I will take a close look.
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
> REPRODUCER PROJECT : https://github.com/p4535992/bug-load-namespace-blueprint
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek resolved CAMEL-13951.
--
Resolution: Fixed
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.RC2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (CAMEL-13958) XPathBuilder threadSafe mode should also be enabled when the NodeList contains only 1 item
[
https://issues.apache.org/jira/browse/CAMEL-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Praet updated CAMEL-13958:
Description:
In CAMEL-10225 the "threadSafety" property was added. But looking at the code,
it is only enabled when the NodeList contains 2 or more items:
XPathBuilder:
[https://github.com/apache/camel/blob/master/components/camel-xpath/src/main/java/org/apache/camel/language/xpath/XPathBuilder.java#L1064]
{code:java}
if (threadSafety && answer != null && answer instanceof NodeList) {
try {
NodeList list = (NodeList)answer;// when the
result is NodeList and it has 2+ elements then its
// not thread-safe to use concurrently
// and we need to clone each node and build a thread-safe list
// to be used instead
boolean threadSafetyNeeded = list.getLength() >= 2;
if (threadSafetyNeeded) {
answer = new ThreadSafeNodeList(list);
if (LOG.isDebugEnabled()) {
LOG.debug("Created thread-safe result from: {} as: {}",
list.getClass().getName(), answer.getClass().getName());
}
}
} catch (Exception e) {
throw ObjectHelper.wrapRuntimeCamelException(e);
}
}
{code}
But I get the same type of error as mentioned in CAMEL-10225 when my NodeList
only contains 1 item:
{code:java}
org.apache.camel.TypeConversionException: Error during type conversion from
type: java.lang.String to the required type: java.io.InputStream with value
84073120992 due java.lang.NullPointerException
at
org.apache.camel.impl.converter.BaseTypeConverterRegistry.createTypeConversionException(BaseTypeConverterRegistry.java:666)
at
org.apache.camel.impl.converter.BaseTypeConverterRegistry.convertTo(BaseTypeConverterRegistry.java:157)
at org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:87)
at org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:61)
at org.apache.camel.builder.xml.XsltBuilder.process(XsltBuilder.java:124)
at
org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:103)
at
org.apache.camel.component.xslt.XsltEndpoint.onExchange(XsltEndpoint.java:139)
at
org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:71)
at
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
at
org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:76)
at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
at
org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:76)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:109)
at
org.apache.camel.processor.MulticastProcessor.doProcessParallel(MulticastProcessor.java:859)
at
org.apache.camel.processor.MulticastProcessor.access$200(MulticastProcessor.java:86)
at
org.apache.camel.processor.MulticastProcessor$1.call(MulticastProcessor.java:330)
at
org.apache.camel.processor.MulticastProcessor$1.call(MulticastProcessor.java:316)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
be.fgov.kszbcss.tracer.concurrent.TracerRunnable.run(TracerRunnable.java:27)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.camel.RuntimeCamelException:
java.lang.NullPointerException
at
[jira] [Created] (CAMEL-13958) XPathBuilder threadSafe mode should also be enabled when the NodeList contains only 1 item
Jimmy Praet created CAMEL-13958:
---
Summary: XPathBuilder threadSafe mode should also be enabled when
the NodeList contains only 1 item
Key: CAMEL-13958
URL: https://issues.apache.org/jira/browse/CAMEL-13958
Project: Camel
Issue Type: Bug
Components: camel-saxon
Affects Versions: 2.24.1
Reporter: Jimmy Praet
In CAMEL-10225 a the threadSafe property was added, but looking at the code, it
is only enabled when the NodeList contains 2 or more items:
XPathBuilder:
[https://github.com/apache/camel/blob/master/components/camel-xpath/src/main/java/org/apache/camel/language/xpath/XPathBuilder.java#L1064]
{code:java}
if (threadSafety && answer != null && answer instanceof NodeList) {
try {
NodeList list = (NodeList)answer;// when the
result is NodeList and it has 2+ elements then its
// not thread-safe to use concurrently
// and we need to clone each node and build a thread-safe list
// to be used instead
boolean threadSafetyNeeded = list.getLength() >= 2;
if (threadSafetyNeeded) {
answer = new ThreadSafeNodeList(list);
if (LOG.isDebugEnabled()) {
LOG.debug("Created thread-safe result from: {} as: {}",
list.getClass().getName(), answer.getClass().getName());
}
}
} catch (Exception e) {
throw ObjectHelper.wrapRuntimeCamelException(e);
}
}
{code}
But I get the same type of error as mentioned in CAMEL-10225 when my NodeList
only contains 1 item:
{code:java}
org.apache.camel.TypeConversionException: Error during type conversion from
type: java.lang.String to the required type: java.io.InputStream with value
84073120992 due java.lang.NullPointerException
at
org.apache.camel.impl.converter.BaseTypeConverterRegistry.createTypeConversionException(BaseTypeConverterRegistry.java:666)
at
org.apache.camel.impl.converter.BaseTypeConverterRegistry.convertTo(BaseTypeConverterRegistry.java:157)
at org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:87)
at org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:61)
at org.apache.camel.builder.xml.XsltBuilder.process(XsltBuilder.java:124)
at
org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:103)
at
org.apache.camel.component.xslt.XsltEndpoint.onExchange(XsltEndpoint.java:139)
at
org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:71)
at
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
at
org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:76)
at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
at
org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:76)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:109)
at
org.apache.camel.processor.MulticastProcessor.doProcessParallel(MulticastProcessor.java:859)
at
org.apache.camel.processor.MulticastProcessor.access$200(MulticastProcessor.java:86)
at
org.apache.camel.processor.MulticastProcessor$1.call(MulticastProcessor.java:330)
at
org.apache.camel.processor.MulticastProcessor$1.call(MulticastProcessor.java:316)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
be.fgov.kszbcss.tracer.concurrent.TracerRunnable.run(TracerRunnable.java:27)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
[jira] [Work logged] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?focusedWorklogId=308874=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-308874
]
ASF GitHub Bot logged work on CAMEL-13951:
--
Author: ASF GitHub Bot
Created on: 09/Sep/19 13:55
Start Date: 09/Sep/19 13:55
Worklog Time Spent: 10m
Work Description: grgrzybek commented on pull request #3156:
[CAMEL-13951] Implement PostgresAggregationRepository to handle speci…
URL: https://github.com/apache/camel/pull/3156
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
Issue Time Tracking
---
Worklog Id: (was: 308874)
Time Spent: 40m (was: 0.5h)
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.RC2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Work logged] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?focusedWorklogId=308808=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-308808
]
ASF GitHub Bot logged work on CAMEL-13951:
--
Author: ASF GitHub Bot
Created on: 09/Sep/19 13:19
Start Date: 09/Sep/19 13:19
Worklog Time Spent: 10m
Work Description: grgrzybek commented on pull request #3156:
[CAMEL-13951] Implement PostgresAggregationRepository to handle speci…
URL: https://github.com/apache/camel/pull/3156
…al PostgreSQL behavior
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
Issue Time Tracking
---
Worklog Id: (was: 308808)
Time Spent: 0.5h (was: 20m)
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.RC2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925678#comment-16925678
]
Grzegorz Grzybek commented on CAMEL-13951:
--
PR: https://github.com/apache/camel/pull/3156
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.RC2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925646#comment-16925646
]
Grzegorz Grzybek commented on CAMEL-13951:
--
I had to reopen. NESTED works, but not within JTA transaction. When
{{}} and {{JdbcAggregationRepository}} use different TMs, NESTED
doesn't make sense, so the only sane solution here is to actually add
{{org.apache.camel.processor.aggregate.jdbc.PostgresAggregationRepository}}
which overrides *one thing*:
* _problem_ [described
here|https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com]
which simply prevents the optimistic locking approach taken by original
{{JdbcAggregationRepository}}.
Give me a moment to send PR.
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.RC2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Reopened] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek reopened CAMEL-13951:
--
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.RC2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (CAMEL-13946) Upgrade to Maven 3.6.2
[ https://issues.apache.org/jira/browse/CAMEL-13946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-13946. --- Resolution: Implemented > Upgrade to Maven 3.6.2 > -- > > Key: CAMEL-13946 > URL: https://issues.apache.org/jira/browse/CAMEL-13946 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > Fix For: 3.0.0, 3.0.0.RC2 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (CAMEL-13946) Upgrade to Maven 3.6.2
[ https://issues.apache.org/jira/browse/CAMEL-13946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart reassigned CAMEL-13946: - Assignee: Zoran Regvart > Upgrade to Maven 3.6.2 > -- > > Key: CAMEL-13946 > URL: https://issues.apache.org/jira/browse/CAMEL-13946 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > Fix For: 3.0.0, 3.0.0.RC2 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925465#comment-16925465
]
Marco Tenti edited comment on CAMEL-13953 at 9/9/19 10:52 AM:
--
Ty all .
Freeman seem to tell the right thing the url
http://camel.apache.org/schema/cxf/camel-cxf-blueprint seem wrong and is not a
url i used previosuly.
For clarification i make a reproducer project with the old configuration on the
READ.me file it's worked just fine or at least not stuck on grace period two
week ago .
Here the reproducer project:
https://github.com/p4535992/bug-load-namespace-blueprint
i'm desperated to solve this issue any help is more than welcome.
it's very simlar to this issue open recently from another developer:
https://stackoverflow.com/questions/56887309/waiting-for-namespace-handlers
So maybe is some feature i have installed conflict with another feature, in the
README.md file of the reproducer project i put a list of all my insatlled
feature in order of installation.
was (Author: 4535992):
Ty all .
Freeman seem to tell the right thing the url
http://camel.apache.org/schema/cxf/camel-cxf-blueprint seem wrong and is not a
url i used previosuly.
For clarification i make a reproducer project with the old configuration on the
READ.me file it's worked just fine or at least not stuck on grace period two
week ago .
Here the reproducer project:
https://github.com/p4535992/bug-load-namespace-blueprint
i'm desperated to solve this issue any help is more than welcome.
it's very simlar to this issue open recently from another developer:
https://stackoverflow.com/questions/56887309/waiting-for-namespace-handlers
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
> REPRODUCER PROJECT : https://github.com/p4535992/bug-load-namespace-blueprint
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (CAMEL-13905) camel-any23 - ascii doc warning
[ https://issues.apache.org/jira/browse/CAMEL-13905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-13905. --- Resolution: Fixed I don't see any lines in the [build output|https://builds.apache.org/job/Camel.website/job/master/165/consoleText]. > camel-any23 - ascii doc warning > --- > > Key: CAMEL-13905 > URL: https://issues.apache.org/jira/browse/CAMEL-13905 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.0.0, 3.0.0.RC2 > > > [INFO] Found 389 ascii document files > asciidoctor: WARNING: any23-dataformat.adoc: line 13: section title out of > sequence: expected level 1, got level 2 > asciidoctor: WARNING: dropping line containing reference to missing > attribute: examplesdir > asciidoctor: WARNING: dropping line containing reference to missing > attribute: examplesdir > asciidoctor: WARNING: dropping line containing reference to missing > attribute: examplesdir > asciidoctor: WARNING: dropping line containing reference to missing > attribute: examplesdir > asciidoctor: WARNING: dropping line containing reference to missing > attribute: examplesdir > asciidoctor: WARNING: dropping line containing reference to missing > attribute: examplesdir > asciidoctor: WARNING: dropping line containing reference to missing > attribute: examplesdir > asciidoctor: WARNING: dropping line containing reference to missing > attribute: examplesdir > asciidoctor: WARNING: dropping line containing reference to missing > attribute: examplesdir -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13957) Dead link from Writing components documentation page
[ https://issues.apache.org/jira/browse/CAMEL-13957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925584#comment-16925584 ] Zoran Regvart commented on CAMEL-13957: --- Near the top right there's a "Edit this Page" link that takes directly to the GitHub editor to edit that document. Contributions welcome. > Dead link from Writing components documentation page > > > Key: CAMEL-13957 > URL: https://issues.apache.org/jira/browse/CAMEL-13957 > Project: Camel > Issue Type: Bug > Components: documentation, website >Reporter: Aurélien Pupier >Priority: Major > Labels: help-wanted > > from [https://camel.apache.org/manual/latest/writing-components.html there > are several dead > links:|https://camel.apache.org/manual/latest/writing-components.html] > * Component > [http://activemq.apache.org/camel/maven/current/camel-core/apidocs/org/apache/camel/Component.html] > * DefaultComponent > [http://activemq.apache.org/camel/maven/current/camel-core/apidocs/org/apache/camel/impl/DefaultComponent.html] > * CamelContext > [http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/CamelContext.html] > * createProducer() > [http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html#createProducer()] > * and not checked after that -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925465#comment-16925465
]
Marco Tenti edited comment on CAMEL-13953 at 9/9/19 10:45 AM:
--
Ty all .
Freeman seem to tell the right thing the url
http://camel.apache.org/schema/cxf/camel-cxf-blueprint seem wrong and is not a
url i used previosuly.
For clarification i make a reproducer project with the old configuration on the
READ.me file it's worked just fine or at least not stuck on grace period two
week ago .
Here the reproducer project:
https://github.com/p4535992/bug-load-namespace-blueprint
i'm desperated to solve this issue any help is more than welcome.
it's very simlar to this issue open recnetly but another developer:
https://stackoverflow.com/questions/56887309/waiting-for-namespace-handlers
was (Author: 4535992):
Ty all .
Freeman seem to tell the right thing the url
http://camel.apache.org/schema/cxf/camel-cxf-blueprint seem wrong and is not a
url i used previosuly.
For clarification i make a reproducer project with the old configuration on the
READ.me file it's worked just fine or at least not stuck on grace period two
week ago .
Here the reproducer project:
https://github.com/p4535992/bug-load-namespace-blueprint
i'm desperated to solve this issue any help is more than welcome.
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
> REPRODUCER PROJECT : https://github.com/p4535992/bug-load-namespace-blueprint
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925465#comment-16925465
]
Marco Tenti edited comment on CAMEL-13953 at 9/9/19 10:45 AM:
--
Ty all .
Freeman seem to tell the right thing the url
http://camel.apache.org/schema/cxf/camel-cxf-blueprint seem wrong and is not a
url i used previosuly.
For clarification i make a reproducer project with the old configuration on the
READ.me file it's worked just fine or at least not stuck on grace period two
week ago .
Here the reproducer project:
https://github.com/p4535992/bug-load-namespace-blueprint
i'm desperated to solve this issue any help is more than welcome.
it's very simlar to this issue open recently from another developer:
https://stackoverflow.com/questions/56887309/waiting-for-namespace-handlers
was (Author: 4535992):
Ty all .
Freeman seem to tell the right thing the url
http://camel.apache.org/schema/cxf/camel-cxf-blueprint seem wrong and is not a
url i used previosuly.
For clarification i make a reproducer project with the old configuration on the
READ.me file it's worked just fine or at least not stuck on grace period two
week ago .
Here the reproducer project:
https://github.com/p4535992/bug-load-namespace-blueprint
i'm desperated to solve this issue any help is more than welcome.
it's very simlar to this issue open recnetly but another developer:
https://stackoverflow.com/questions/56887309/waiting-for-namespace-handlers
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
> REPRODUCER PROJECT : https://github.com/p4535992/bug-load-namespace-blueprint
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (CAMEL-13957) Dead link from Writing components documentation page
[ https://issues.apache.org/jira/browse/CAMEL-13957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-13957: -- Component/s: documentation > Dead link from Writing components documentation page > > > Key: CAMEL-13957 > URL: https://issues.apache.org/jira/browse/CAMEL-13957 > Project: Camel > Issue Type: Bug > Components: documentation, website >Reporter: Aurélien Pupier >Priority: Major > Labels: help-wanted > > from [https://camel.apache.org/manual/latest/writing-components.html there > are several dead > links:|https://camel.apache.org/manual/latest/writing-components.html] > * Component > [http://activemq.apache.org/camel/maven/current/camel-core/apidocs/org/apache/camel/Component.html] > * DefaultComponent > [http://activemq.apache.org/camel/maven/current/camel-core/apidocs/org/apache/camel/impl/DefaultComponent.html] > * CamelContext > [http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/CamelContext.html] > * createProducer() > [http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html#createProducer()] > * and not checked after that -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13957) Dead link from Writing components documentation page
[ https://issues.apache.org/jira/browse/CAMEL-13957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-13957: -- Labels: help-wanted (was: ) > Dead link from Writing components documentation page > > > Key: CAMEL-13957 > URL: https://issues.apache.org/jira/browse/CAMEL-13957 > Project: Camel > Issue Type: Bug > Components: website >Reporter: Aurélien Pupier >Priority: Major > Labels: help-wanted > > from [https://camel.apache.org/manual/latest/writing-components.html there > are several dead > links:|https://camel.apache.org/manual/latest/writing-components.html] > * Component > [http://activemq.apache.org/camel/maven/current/camel-core/apidocs/org/apache/camel/Component.html] > * DefaultComponent > [http://activemq.apache.org/camel/maven/current/camel-core/apidocs/org/apache/camel/impl/DefaultComponent.html] > * CamelContext > [http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/CamelContext.html] > * createProducer() > [http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html#createProducer()] > * and not checked after that -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Tenti updated CAMEL-13953:
Description:
My bundle OSGI remains in "grace period" because of this error
{code}
is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
http://cxf.apache.org/transports/http/configuration,
http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
http://cxf.apache.org/configuration/security,
http://camel.apache.org/schema/blueprint,
http://cxf.apache.org/transports/http-undertow/configuration,
[http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
{code}
it' seem some url is down in the specific the url
http://camel.apache.org/schema/blueprint/cxf
is a couple of days is not reachable and give me error code 404 "Page not
found".
Is down for a error or the XSD is migrate to another url?
REPRODUCER PROJECT : https://github.com/p4535992/bug-load-namespace-blueprint
was:
My bundle OSGI remains in "grace period" because of this error
{code}
is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
http://cxf.apache.org/transports/http/configuration,
http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
http://cxf.apache.org/configuration/security,
http://camel.apache.org/schema/blueprint,
http://cxf.apache.org/transports/http-undertow/configuration,
[http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
{code}
it' seem some url is down in the specific the url
http://camel.apache.org/schema/blueprint/cxf
is a couple of days is not reachable and give me error code 404 "Page not
found".
Is down for a error or the XSD is migrate to another url?
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
> REPRODUCER PROJECT : https://github.com/p4535992/bug-load-namespace-blueprint
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925465#comment-16925465
]
Marco Tenti commented on CAMEL-13953:
-
Ty all .
Freeman seem to tell the right thing the url
http://camel.apache.org/schema/cxf/camel-cxf-blueprint seem wrong and is not a
url i used previosuly.
For clarification i make a reproducer project with the old configuration on the
READ.me file it's worked just fine or at least not stuck on grace period two
week ago .
Here the reproducer project:
https://github.com/p4535992/bug-load-namespace-blueprint
i'm desperated to solve this issue any help is more than welcome.
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek resolved CAMEL-13951.
--
Resolution: Fixed
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.RC2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek updated CAMEL-13951:
-
Fix Version/s: 2.23.4
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.RC2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13654) optaplanner-7.23 not usable in WildFly
[
https://issues.apache.org/jira/browse/CAMEL-13654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925445#comment-16925445
]
Andrea Cosentino commented on CAMEL-13654:
--
The problem has been fixed in Optaplanner 7.26.0.Final. Updated
> optaplanner-7.23 not usable in WildFly
> --
>
> Key: CAMEL-13654
> URL: https://issues.apache.org/jira/browse/CAMEL-13654
> Project: Camel
> Issue Type: Bug
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 3.0.0, 3.0.0.M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> drools-7.23 uses this code in `org.drools.core.common.ProjectClassLoader` ...
> {code}
> public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
> if (getParent() != droolsClassLoader &&
> isOsgiClassLoader(droolsClassLoader)) {
> this.droolsClassLoader = droolsClassLoader;
> if (CACHE_NON_EXISTING_CLASSES) {
> nonExistingClasses.clear();
> }
> }
> }
> {code}
> drools-7.14 uses
> {code}
> public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
> if (getParent() != droolsClassLoader) {
> this.droolsClassLoader = droolsClassLoader;
> if (CACHE_NON_EXISTING_CLASSES) {
> nonExistingClasses.clear();
> }
> }
> }
> {code}
> In a non flat classpath environment, the later version of drools does not
> allow the CL to get set to anything that is not an OSGi CL.
> CrossRefs: https://github.com/wildfly-extras/wildfly-camel/issues/2831,
> https://github.com/kiegroup/drools/commit/85c5308031a84a0ac4086c1df363bb1b4b3c6af9
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Work logged] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?focusedWorklogId=308670=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-308670
]
ASF GitHub Bot logged work on CAMEL-13951:
--
Author: ASF GitHub Bot
Created on: 09/Sep/19 08:02
Start Date: 09/Sep/19 08:02
Worklog Time Spent: 10m
Work Description: grgrzybek commented on pull request #3155: CAMEL-13951:
Expose setter for transaction propagation using name. Fi…
URL: https://github.com/apache/camel/pull/3155
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
Issue Time Tracking
---
Worklog Id: (was: 308670)
Time Spent: 20m (was: 10m)
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.0.0, 2.24.2, 2.25.0, 3.0.0.RC2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (CAMEL-13957) Dead link from Writing components documentation page
Aurélien Pupier created CAMEL-13957: --- Summary: Dead link from Writing components documentation page Key: CAMEL-13957 URL: https://issues.apache.org/jira/browse/CAMEL-13957 Project: Camel Issue Type: Bug Components: website Reporter: Aurélien Pupier from [https://camel.apache.org/manual/latest/writing-components.html there are several dead links:|https://camel.apache.org/manual/latest/writing-components.html] * Component [http://activemq.apache.org/camel/maven/current/camel-core/apidocs/org/apache/camel/Component.html] * DefaultComponent [http://activemq.apache.org/camel/maven/current/camel-core/apidocs/org/apache/camel/impl/DefaultComponent.html] * CamelContext [http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/CamelContext.html] * createProducer() [http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html#createProducer()] * and not checked after that -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?focusedWorklogId=308661=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-308661
]
ASF GitHub Bot logged work on CAMEL-13951:
--
Author: ASF GitHub Bot
Created on: 09/Sep/19 07:39
Start Date: 09/Sep/19 07:39
Worklog Time Spent: 10m
Work Description: grgrzybek commented on pull request #3155: CAMEL-13951:
Expose setter for transaction propagation using name. Fi…
URL: https://github.com/apache/camel/pull/3155
…x tests
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
Issue Time Tracking
---
Worklog Id: (was: 308661)
Remaining Estimate: 0h
Time Spent: 10m
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.0.0, 2.24.2, 2.25.0, 3.0.0.RC2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925432#comment-16925432
]
Grzegorz Grzybek commented on CAMEL-13951:
--
For a moment I was thinking about {{PostgresAggregationRepository}} that
extends {{JdbcAggregationRepository}} and configures the propagation behavior
to {{NESTED}}. But my initial scenario is not about _all_ PostgreSQL_ usages -
it's only when the JDBC aggregation is used within a route that:
* already has {{}}
* both {{}} and {{JdbcAggregationRepository}} use the same
transaction manager.
So it's better to just expose setter for the propagation behavior.
I have PR that:
* adds setter for propagation behavior by name
* fixes tests
* moves creation of transaction templates to {{doStart()}} because it relies on
data from two setters
PR: https://github.com/apache/camel/pull/3155
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.0.0, 2.24.2, 2.25.0, 3.0.0.RC2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (CAMEL-13933) website - Add menu item for EIP patterns
[ https://issues.apache.org/jira/browse/CAMEL-13933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-13933. --- Resolution: Implemented Thanks to [~alexkieling] for the [pull request|https://github.com/apache/camel-website/pull/85]. > website - Add menu item for EIP patterns > > > Key: CAMEL-13933 > URL: https://issues.apache.org/jira/browse/CAMEL-13933 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > We have user guide, component reference etc in the documentation menu. But we > should have a menu item for the EIP patterns as they are otherwise a bit > harder to find. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (CAMEL-13933) website - Add menu item for EIP patterns
[ https://issues.apache.org/jira/browse/CAMEL-13933?focusedWorklogId=308649=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-308649 ] ASF GitHub Bot logged work on CAMEL-13933: -- Author: ASF GitHub Bot Created on: 09/Sep/19 06:42 Start Date: 09/Sep/19 06:42 Worklog Time Spent: 10m Work Description: oscerd commented on pull request #85: CAMEL-13933: Add menu item for EIP patterns URL: https://github.com/apache/camel-website/pull/85 This is an automated message from the Apache Git Service. To respond to the message, please log on to 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 Issue Time Tracking --- Worklog Id: (was: 308649) Time Spent: 20m (was: 10m) > website - Add menu item for EIP patterns > > > Key: CAMEL-13933 > URL: https://issues.apache.org/jira/browse/CAMEL-13933 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > We have user guide, component reference etc in the documentation menu. But we > should have a menu item for the EIP patterns as they are otherwise a bit > harder to find. -- This message was sent by Atlassian Jira (v8.3.2#803003)
