I'm trying to receive a JMS message and send it to a MQ queue, keeping
headers on the message.
But headers are sent when using targetClient=1.
So when using the following, no headers are sent.
from("*wmq:queue:A0*").log("${headers}");
template.sendBodyAndHeader("*wmq:queue:A0*", "body", "h1", "hea
So a bit interesting, i tried to to a similar thing that the old project did
in Java Caps, batching.
from("wmq:queue:A1")
.log("Incoming")
.process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
I forgot to mention that I do use connection pool on the application server.
Removed a bit of the logging, but here's some start/end logging:
15:59:42.571 [Camel (camel-1) thread #0 - JmsConsumer[A1]] TRACE
o.a.c.c.j.EndpointMessageListener - onMessage START
15:59:42.599 [Camel (camel-1) thread #0
Interesting.
I'm not using a local transactions, but the one that the app server
provides. Which works as XA.
So then I should not use CACHE_CONSUMER, reading the docs, or is this only
related to local transactions?
"So you can say the default setting is conservative. Consider using
cacheLevelNam
We are reading from a websphere mq which reads about 36-40msg/s which is very
slow. We are using this in a liberty profile environment. The old version,
which is on Java Caps on websphere is 3x faster.
Not ok.
The code is basically this (one of out components):
from(wmq:queue:inqueue).to(direct:h
