I would like to have one transaction, one commit and one database connection
for an Apache Camel route that only uses Oracle. In my current setup it appears
that the Oracle AQ JMS transaction and the Oracle INSERT transaction are
separate.
Why do I want it
With separate transactions there
I would like Apache Camel to perform a graceful shutdown within the default 45
seconds. After 45 seconds I would like the the shutdown to be forced.
I normally expect the default 45 second timeout to work, but unfortunately it
does not seem to work when using a JMS component with a long receiveT
timeout should be a reasonable value that allows camel-jms (eg spring jms)
to react on shutdown or stopping, or reducing concurrent consumers if there are
no more pending messages.
On Thu, Oct 7, 2021 at 3:05 PM Mattern, Alex
wrote:
>
> I would like Apache Camel to perform a graceful sh
Square, Boston, MA 02110
T 617-772-0096 | M 857-283-3724 | alex.matt...@bbh.com
www.bbh.com
-Original Message-
From: Mattern, Alex
Sent: Tuesday, September 28, 2021 9:08 AM
To: users@camel.apache.org
Subject: [EXTERNAL SENDER:] Apache Camel single transaction with oracle aq and
row inserts
I
-
From: Mattern, Alex
Sent: Thursday, October 7, 2021 3:00 PM
To: users@camel.apache.org
Subject: [EXTERNAL SENDER:] RE: camel-jms long receiveTimeout preventing
shutdown with Oracle AQ
Claus Isben,
The reason for wanting a long receive timeout is to prevent the queue server
from having
Cc: users@camel.apache.org
Subject: [EXTERNAL SENDER:] Re: Apache Camel single transaction with oracle aq
and row inserts
It looks like you need an external JTA TransactionManager to coordinate these
two resources ( oneis database and the other is Oracle AQ).
On Fri, Oct 15, 2021 at 10:20 PM Mattern, Alex
wro
Mikael Andersson Wigander,
While it is not a Camel solution, large documents can be parsed using a
streaming Xpath parser. This can be implemented using SAX. This would work in
your use case since the Xpath in question are not performing lookback. This way
the entire document is never read int
Doug Snaith,
Message History is disabled by default in Camel 3. Override the default on your
camelcontext or route.
https://camel.apache.org/components/3.14.x/eips/message-history.html
Alex Mattern | AVP | Infomediary Architect | Investor Services
[cid:image001.gif@01D8A665.13516A00]BROWN BROT
This helped me understand that Camel Timer is defaulting to fixed-delay.
From the Camel code:
https://github.com/Talend/apache-camel/blob/master/camel-core/src/main/java/org/apache/camel/component/timer/TimerConsumer.java
if (endpoint.isFixedRate()) { timer.scheduleAtFixedRate(task,
endpoint.get
Mi Jane,
You could consider writing your own custom:
MiJaneEmailEndpoint extends DefaultEndpoint
MiJaneEmailComponent extends DefaultComponent
MiJaneEmailPollConsumer extends ScheduledPollConsumer
This is as we have done and we can receive attachments from Microsoft Exchange.
Camel version 3.7.2
On converting from Camel 3.x to 4.x:
1. You should get the canonicalHostName
public static String getHostName() {
try {
return
InetAddress.getLocalHost().getCanonicalHostName();
}
}
2. You should update your keystore to acc
test my app without the hassle of creating their
own keystore, right?
/fedd
On 21.09.2023 17:13, Mattern, Alex wrote:
> On converting from Camel 3.x to 4.x:
>
> 1. You should get the canonicalHostName
>
> public static String getHostName() {
>
Srikant Mantha,
Here is an example of filtering on a jms topic:
https://camel.apache.org/components/4.0.x/jms-component.html#_receiving_from_jms
-Original Message-
From: Ivan Kulaga
Sent: Sunday, January 14, 2024 10:29 PM
To: users@camel.apache.org
Subject: [EXTERNAL SENDER:] Re: How w
If you are just looking to trash old messages then use the timeToLive setting
when producing messages on the DLQ.
https://camel.apache.org/components/4.10.x/eips/message-expiration.html
If you want a manually triggered process, then you can create a consumer
application that consumes X number of
14 matches
Mail list logo
