Yes, I did tried those configurations. But still same slow down. My test
case works fine for 11g Oracle drivers.
jdbc.pool.maxTotal
jdbc.pool.minIdle
jdbc.pool.testOnBorrow
InitialSize too.
On Thu, May 23, 2019 at 2:20 PM FabryProg wrote:
> Hi guy
>
> Perhaps the error is another: do you tr
Hi guy
Perhaps the error is another: do you tried to change initial and max pool
size ? Or connectionharvest settings?
King regards
Il Gio 23 Mag 2019, 23:12 Saiteja Parna ha
scritto:
> This issue is resolved. My post might help others.
> Batch Update/Insert/Delete has issues with Oracle_Jd
This issue is resolved. My post might help others.
Batch Update/Insert/Delete has issues with Oracle_Jdbc drivers 12c and
above.
If any one using Camel-sql or any other Camel database components with
Oracle_jdbc drivers (12c and latest) will see very slow performance issue
with batch insert/update/
I am using below in applicaiton.yml
camel:
cloud:
consul:
service-discovery:
url: http://localhost:8500
then call another service which is registered in consul service discovery
like below
but always receiving this error
java.util.concurrent.RejectedExecutionExcep
> Can you try with a newer version?
Unfortunately, I have no time to do that.
Can you try with a newer version? Camel 2.15 is not released anymore.
Il giorno gio 23 mag 2019 alle ore 12:11 Hildegard Meier
ha scritto:
> Apache Camel 2.15.6
>
> Hi, the following Camel XML route honours renameUsingCopy=true, which is
> set once:
>
> uri="file:/edidaten/edi-smtpdak/ezv?delay
Apache Camel 2.15.6
Hi, the following Camel XML route honours renameUsingCopy=true, which is set
once:
File processing speed is fast.
But setting renameUsingCopy=true a second time afterwards, it seems that it
sets renameUsingCopy=false, at least it makes the processing very slow (1-2
secon
Camel exchange needs to work with multiple components, so it doesn't make
any sense to have specific methods used only for JMS message. That's why
there is a this "translation" to headers.
Il giorno gio 23 mag 2019 alle ore 09:17 Marx, Peter <
peter.m...@knorr-bremse.com> ha scritto:
> indeed, th
indeed, that works!
I don't understand the background why the camel.Exchange class has less methods
than the javax.jms.Message class, but as there is a clever "workaround" I am
fine.
Thanks
Peter
-Original Message-
From: Steve Huston
Sent: Tuesday, May 21, 2019 3:26 PM
To: users@ca