-
> From: Ephemeris Lappis
> Sent: Tuesday, March 11, 2025 9:07 AM
> To: users@camel.apache.org; us...@activemq.apache.org
> Subject: [EXTERNAL SENDER:] Camel JMS consumer with dynamic selector to
> read ActiveMQ DLQueues
>
> Hello.
>
> I'm looking for a simple wa
of messages, where X is specified on startup.
--
Alex
-Original Message-
From: Ephemeris Lappis
Sent: Tuesday, March 11, 2025 9:07 AM
To: users@camel.apache.org; us...@activemq.apache.org
Subject: [EXTERNAL SENDER:] Camel JMS consumer with dynamic selector to read
ActiveMQ DLQueues
Hello
Hello.
I'm looking for a simple way to clean DLQ queues on our ActiveMQ brokers.
Messages are moved to DLQ queues when some unexpected conditions lead
consumers to fail. We've no automatic processing for DLQ messages that are
only needed for diagnosis. Nevertheless, when the queues contain too man
On Mon, Sep 16, 2024 at 5:30 PM Chirag wrote:
> Thanks Claus.
>
> Balint, fix is on a new branch and not on 4.0.x. Would you know how to
> cherrypick to 4.0.x branch to get it in version you need and validate?
>
>
Camel 4.0.x is EOL and not supported.
>
> On Mon, Sep 16, 2024 at 4:55 AM Bálint
Thanks Claus.
Balint, fix is on a new branch and not on 4.0.x. Would you know how to
cherrypick to 4.0.x branch to get it in version you need and validate?
On Mon, Sep 16, 2024 at 4:55 AM Bálint Baráth
wrote:
> Thanks for the quick response, and the fix!
>
> Claus Ibsen ezt írta (időpont: 202
Thanks for the quick response, and the fix!
Claus Ibsen ezt írta (időpont: 2024. szept. 14.,
Szo 11:31):
> Hi
>
> Yeah lets investigate this I created a ticket
> https://issues.apache.org/jira/browse/CAMEL-21219
>
> On Thu, Sep 12, 2024 at 8:36 AM Bálint Baráth
> wrote:
>
> > Hello!
> >
> > I'm
Hi
Yeah lets investigate this I created a ticket
https://issues.apache.org/jira/browse/CAMEL-21219
On Thu, Sep 12, 2024 at 8:36 AM Bálint Baráth
wrote:
> Hello!
>
> I'm using camel 4.0.6 with java 17 and springboot 3.2.6.
> When using camel with JMS and using a request-reply EIP, camel puts som
Yes, the property gets added as 'CamelJmsDeliveryMode' and has a value of 1
or 2.
But the usual JMSDeliveryMode with persistent/nonpersistent is also there,
added by the camels JmsConfiguration class.
I saw a comment in the code, that this property is temporary, and it
removes it, when setting the
Is Tibco seeing it as DeliveryMode or with Camel name on it? Do you also
see DeliveryMode?
regards,
On Thu, Sep 12, 2024 at 10:13 AM Bálint Baráth
wrote:
> Hello!
>
> FYI if somebody runs into the same problem:
> I managed to create a workaround, after finding where the header gets
> added. I
Hello!
FYI if somebody runs into the same problem:
I managed to create a workaround, after finding where the header gets
added. It's inside the tibco jms implementation, where all the properties
on the message get added as jms headers, so the CamelJmsDeliveryMode int
property was added.
I created
Hello!
I'm using camel 4.0.6 with java 17 and springboot 3.2.6.
When using camel with JMS and using a request-reply EIP, camel puts some
extra headers on the reply message. The CamelMessageTimestamp can be
removed using the removeHeaders("Camel*") feature, but there is a header
named "*CamelJmsDel
Hello Claus.
Indeed, this is a perfect way to get the dynamic queue name : {{sys:XXX}}.
Thanks a lot !
Regards.
Le mer. 17 avr. 2024 à 17:04, Claus Ibsen a écrit :
>
> Hi
>
> You can use {{ }} syntax that can refer to JVM sys properties also.
>
> The toD example you have is using simple langua
Hi
You can use {{ }} syntax that can refer to JVM sys properties also.
The toD example you have is using simple language and its not the same as
{{ }} but they can both use sys/env variables etc.
On Wed, Apr 17, 2024 at 4:36 PM Ephemeris Lappis
wrote:
> Hello.
>
> I'm looking for some way to
Hello.
I'm looking for some way to set a JMS consumer on a queue whose name
depends on the context (in my real case, a system property).
For a producer, the route (we use blueprint DSL) can be something like that :
But I don't see any way for the "from" uri...
Any idea ?
Thanks for your help
Hello.Claus !
Well ! after more tests, I can confirm that on the broker side all
works as expected. I've also found some way to set set the route such
a way that failing messages are moved to the DLQ the same way they are
when processed by applications.
Hello Claus.
I'm not sure that I should change anything on the broker side : with
the same ActiveMQ, java applications with a similar connection factory
configuration (maximumRedeliveries=0) actually do a rollback on
failing messages processing, and the broker moves them to DLQ queues.
These appli
Hi
You need to set this on the broker side, it's the one that does the
redelivery.
Every broker has their own settings for DLQ and redelivery.
On Mon, Mar 11, 2024 at 2:20 PM Ephemeris Lappis
wrote:
> Hello.
>
> It seems that the JMS consumer ignores the redelivery conditions that
> I set on my
Hello.
It seems that the JMS consumer ignores the redelivery conditions that
I set on my route :
java.lang.Exception
${body
Hello.
For almost all our JMS consumer routes, we didn't need to move
messages to a DLQ queue : for now only redelivery is handled to avoid
repeated errors with something like that on the routes :
java.lang.Exception
done : https://issues.apache.org/jira/browse/CAMEL-20338
Le mer. 17 janv. 2024 à 08:03, Claus Ibsen a écrit :
>
> Hi
>
> No this is not possible out of the box with dynamic queue names.
>
> It may be desirable to enrich the message with
> a CamelJmsDestinationNameProduced header that includes the
Hi
No this is not possible out of the box with dynamic queue names.
It may be desirable to enrich the message with
a CamelJmsDestinationNameProduced header that includes the name.
You are welcome to create a JIRA.
On Mon, Jan 8, 2024 at 10:05 AM Ephemeris Lappis
wrote:
> Hello.
>
> If it's
Hello.
If it's confirmed, it means that I can't retrieve the actual resulting
queue the message is sent to ?
I'd need to retrieve it in some event notifiers, out of the Camel
routes code, that spies all the exchanges, the same way I do for
generated files retrieving the header "CamelFileNameProduc
I think Camel only sets those headers when a JMS message is received.
https://camel.apache.org/components/4.0.x/jms-component.html#_message_format_when_receiving
On Thu, Jan 4, 2024 at 5:56 AM Ephemeris Lappis
wrote:
> Hello.
>
> I've observed that some JMS headers are not updated after a messa
Hello.
I've observed that some JMS headers are not updated after a message is sent.
For example, using this statement :
Hello again !
The code I've given before, setting the header "JMSExpiration" with a
computed date ("now+30m", it seems that Camel takes the timestamp's
long value, and not the date string, to set the sent message header)
works if and only if I add "preserveMessageQos=true" to the endpoint's
URI.
T
I think setting "JMSExpiration" from a header isn't supported. Only these
four:
CamelJMSDestinationName (producer)
CamelJmsRequestTimeout (producer)
JMSCorrelationID (producer)
JMSReplyTo (producer)
Don't know why, but other ones have no effect. The component does some
message mapping though
No, I can't : we work on a Red-Hat Fuse cluster, and the brokers and
the related configured components are provided by the cluster (in
groups including Karaf instances), and are shared for all our business
bundles and their queues. We'd want to set time to live (expiration)
only for some queues, no
Can you set the parameter globally like this:
ActiveMQComponent activeMQComponent = new ActiveMQComponent();
activeMQComponent.setPreserveMessageQos(true);
context.addComponent("activemq2",activeMQComponent);
On Mon, Apr 3, 2023 at 12:27 PM Ephemeris Lappis
wrote:
> Hello.
>
> In fact I think
Hello.
In fact I think I'd only need to set one header for expiration time.
Something like that :
${date:now+30m}
But it seems that for overriding the default JMSExpiration another
change must be done on the endpoint (otherwise the JMSExpira
I should be possible as Camel Headers are translated to JMS Headers when
sending to an ActiveMQ queue or topic. This can be tricky though as
sometimes JMS Headers are not set by the client but by the broker (for
example JMSTimestamp), so you can't use all headers.
You can check this page with the
Hello.
Thanks for your idea. I had a look at the JMs component unit tests,
but I've not found any that use only headers to set messages time to
live.
Could you please give us some example ?
Thanks again. Regards
Le ven. 31 mars 2023 à 18:34, Claus Ibsen a écrit :
>
> A good idea is to look at t
A good idea is to look at the unit tests in the camel components
On Fri, Mar 31, 2023 at 6:27 PM Ephemeris Lappis
wrote:
> Hello.
>
> I've not found any way to set messages time to live when sending to a
> JMS (activemq) queue.
>
> I'd like to set headers only, without changing the endpoint URI.
Hello.
I've not found any way to set messages time to live when sending to a
JMS (activemq) queue.
I'd like to set headers only, without changing the endpoint URI. Is it
possible ?
I've read (and tested it too) that if a message header is set for the
JMSExpiration, it's not taken into account if
s bad).
On Wed, Nov 24, 2021 at 7:23 AM Mi Jane 米静 wrote:
>
> Dear community,
>
> We have 2 camel services: camel-A and camel-B and both of them use camel-jms
> component.
>
> Camel-A is the JMS producer with: uri="jms:queue:queue.name?disableTimeToLive=true&tr
Dear community,
We have 2 camel services: camel-A and camel-B and both of them use camel-jms
component.
Camel-A is the JMS producer with:
Camel-B is the JMS consumer with:
After stress testing, we got camel-B OOM exception and found the memory leak
root cause is DefaultInflightRepository
. November 2021 15:58
An: users@camel.apache.org
Betreff: EXT:Re: Trouble installing Camel with Camel-Activemq + Camel-JMS +
Camel-AMQP in Karaf 4.2.10 and ActiveMQ 5.16.2 ...
By the way, you can use camel-JMS with ActiveMQ as camel-activemq is deprecated.
Regards
JB
> Le 10 nov. 2021 à 15:40,
By the way, you can use camel-JMS with ActiveMQ as camel-activemq is
deprecated.
Regards
JB
> Le 10 nov. 2021 à 15:40, JB Onofré a écrit :
>
> Camel jms force use of JMS 2 whereas activemq only supports jms 1. So we
> have a conflict. ActiveMQ however works with JMS
Camel jms force use of JMS 2 whereas activemq only supports jms 1. So we have a
conflict. ActiveMQ however works with JMS 2 so we can override/blacklist the
JMS 1 bundle.
I’m in the train now but I can provide a workaround.
Regards
JB
> Le 10 nov. 2021 à 15:34, Zinner, Frank Uwe Alf
Hello,
I'm having trouble to install Apache Camel 3.7.5 with camel-activemq (3.7.5),
camel-jms (3.7.5) and camel-amqp (3.7.5) in Apache Karaf 4.2.10.
I used a fresh Karaf 4.2.10 Binary distribution and added ActiveMQ 5.16.2 along
with Camel 3.7.5 and was able to install ActiveMQ with
-
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
Mattern
-Original Message-
From: Claus Ibsen
Sent: Thursday, October 7, 2021 10:24 AM
To: users@camel.apache.org
Subject: [EXTERNAL SENDER:] Re: camel-jms long receiveTimeout preventing
shutdown with Oracle AQ
Hi
Do NOT use such a long receive timeout, that is not its purpose.
The
Hi
Do NOT use such a long receive timeout, that is not its purpose.
The 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
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
quot;: 20,
> "XMSC_WMQ_RECEIVE_EXIT": null,
> "XMSC_RTT_DIRECT_AUTH": 0,
> "XMSC_WMQ_TEMP_TOPIC_PREFIX": "",
> "multicast": 0,
> "XMSC_WMQ_PROVIDER_VERSION": "unspecified
ot;XMSC_ADMIN_OBJECT_TYPE": 20,
"XMSC_WMQ_RECEIVE_EXIT": null,
"XMSC_RTT_DIRECT_AUTH": 0,
"XMSC_WMQ_TEMP_TOPIC_PREFIX": "",
"multicast": 0,
"XMSC_WMQ_PROVIDER_VERSION": "unspecified",
"XMSC_WMQ_SEND_EXIT"
Oh i see what you mean!
Indeed, I need to establish a jms connection. I decided to use camel-jms
component. Referred this official ibm git example here ->
https://github.com/ibm-messaging/mq-cloud-demo/blob/master/aws-backend-request/JMSLambdaFunction/src/main/java/com/example/lambda/ib
nFactory">
>
>
>
>
>
>
>
And you provide this connection factory to the camel-jms endpoint (using
?connectionFactory=#wmqConnectionFactory).
If you want to use directly MQ "native" channel, you can use camel-wmq
component (in camel-extra).
Regards
JB
> Le 14 ma
Hello community
Has anyone tried connecting to IBM Cloud MQ via camel jms component? I see
it needs an implementation of javax.jms.ConnectionFactory.
One of the implementations provided of above interface by IBM
is com.ibm.mq.jms.MQConnectionFactory. The MQ cloud provides following
information
emains null and startup
fails.
My work-around is to define connectionFactory parameter manually using
camel-jms-starter's camel.component.jms.connection-factory parameter. That
works fine.
Any thoughts about this, is it a bug? The issue might be related or introduced
by CAMEL-14190.
Regards,
Simo Kivimäki
essage.setObjectProperty(ActiveMQMessage.java:693)
> ~[artemis-jms-client-2.6.2.jar:2.6.2]
> at
> org.apache.camel.component.jms.JmsBinding.createByteArrayFromBytesMessage(JmsBinding.java:251)
> ~[camel-jms-2.22.1.jar:2.22.1]
> at
> org.apache.camel.component.jms.JmsBinding.extractBodyFromJms(JmsB
6.2.jar:2.6.2]
at
org.apache.camel.component.jms.JmsBinding.createByteArrayFromBytesMessage(JmsBinding.java:251)
~[camel-jms-2.22.1.jar:2.22.1]
at
org.apache.camel.component.jms.JmsBinding.extractBodyFromJms(JmsBinding.java:163)
~[camel-jms-2.22.1.jar:2.22.1]
... 21 more
The pr
ctual master. I think a
> backport to 2.x branch shouldn't be that hard.
>
> Regards
> Benjamin
>
> Gesendet: Dienstag, 13. August 2019 um 15:57 Uhr
> Von: "Claus Ibsen"
> An: users@camel.apache.org
> Betreff: Re: Re: Definition of subscriptionname in Came
: Definition of subscriptionname in Camel JMS-Endpoint does not
work as expected
On Tue, Aug 13, 2019 at 2:50 PM Benjamin Graf wrote:
>
> Hi,
>
> yes it seems non-durable shared subscription are not implemented correctly.
> Subscription name should be set for non-durable as well.
>
ix this
> Regards
> Benjamin
>
>
> Gesendet: Dienstag, 13. August 2019 um 11:57 Uhr
> Von: "Claus Ibsen"
> An: users@camel.apache.org
> Betreff: Re: Definition of subscriptionname in Camel JMS-Endpoint does not
> work as expected
> Hi
>
> Shared subsc
inition of subscriptionname in Camel JMS-Endpoint does not work
as expected
Hi
Shared subscription is something new in JMS 2.0.
So it may be a bug or not, I can't recall on top of my head. I suggest
you spend a bit time research and come back and tell us.
On Tue, Aug 13, 2019 at 11:46 AM wrote:
>
>
Hi
Shared subscription is something new in JMS 2.0.
So it may be a bug or not, I can't recall on top of my head. I suggest
you spend a bit time research and come back and tell us.
On Tue, Aug 13, 2019 at 11:46 AM wrote:
>
> Dear Camel guys and girls,
>
>
> I have a question regarding the propert
Dear Camel guys and girls,
I have a question regarding the property "subscriptionName" which can be
specified for a JMS-Consumer.
First, here is my project setup:
* Camel 2.24.1
* Spring-Boot: 2.1.0.RELEASE
I create a simple standalone JAR which just should consume from defined
JMS-Q
, this seems not
being supported by camel-jms. CiA lists some components, but not camel-jms
Spring Boot docs do not mention parameters related to activemq and TLS.
So what is the right way to set the TLS parameters, ideally externalized via
application.properties ?
Peter
Hi,
I am learning and observed the transaction are not getting committed in
oracle database. I am using Apace Camel 2.16.0 with Spring Boot
I have following code. It doesnt camit and doesnt throw any error. It shows in
logs it has executed end to end successfully. But when i see in databa
The official documentation now is in the Camel repo. As you may see from the
link posted by Claus
https://github.com/apache/camel/blob/master/components/camel-jms/src/main/docs/jms-component.adoc
We are in the process of migrating the whole documentation in .adoc and the
site is no longer
us.ib...@gmail.com]
Gesendet: Montag, 15. Jänner 2018 10:56
An: users@camel.apache.org
Betreff: Re: Camel JMS transferExchange=true Exception
Hi
Its an Apache ActiveMQ setting (not Camel specific) that do not allow java
serialized objects by default, and you need to configure it with the app
://github.com/apache/camel/blob/master/components/camel-jms/src/main/docs/jms-component.adoc
And how to contribute to Camel is here
http://camel.apache.org/contributing
On Mon, Jan 15, 2018 at 10:34 AM, Leber, Thomas
wrote:
> Hi,
>
> I'm sending in an onException clause the exchange to
Hi,
I'm sending in an onException clause the exchange to another camel route via
JMS.
In order to handle the error, the idea was to use transferExchange=true, since
the documentations states the exchange exception is transferred as well.
Unfortunately I get this error in the JMS listener:
-
Hi
I think you can configure a custom errorHandler on the JMS endpoint /
component and there you can log only what you want. See details at
https://github.com/apache/camel/blob/master/components/camel-jms/src/main/docs/jms-component.adoc
On Tue, Dec 19, 2017 at 6:54 PM, Кристина Солдатко wrote
Hi.
My service use MQ and receives some data from it. When connection to MQ is
broken - I can see in logs following situation: error report is logged as
multiple line text like:
December 19, 2017 5:32:47 PM UTC[Camel (camel-1) thread #0 -
JmsConsumer[ROUTER]]
com.ibm.msg.client.jms.internal.JmsPro
essage processor bean, it's removed from
> the queue.
>
> Please let me know what I need to change. I tried searching for client
> acknowledge mode sample code, but couldn't find much info. Any thoughts or
> sample code will be greatly appreciated!
>
>
>
> --
>
Camel Friends, any thoughts? Any help will be greatly appreciated!
--
View this message in context:
http://camel.465427.n5.nabble.com/Help-needed-how-to-use-Camel-JMS-Client-Acknowledge-mode-for-queue-consumption-tp5812049p5812112.html
Sent from the Camel - Users mailing list archive at
ext:
http://camel.465427.n5.nabble.com/Help-needed-how-to-use-Camel-JMS-Client-Acknowledge-mode-for-queue-consumption-tp5812049.html
Sent from the Camel - Users mailing list archive at Nabble.com.
nothing works for me.
Do you guys have any idea on suggestion to bypass this situation?
Thanks,
Fernando.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-JMS-producers-not-recovering-from-WMQ-restart-or-network-issue-tp5791385.html
Sent from the Camel - Users mailing
(ThreadPoolExecutor.java:617)[:1.8.0_25]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_25]
Appreciate any help to resolve this issue.
Thanks,
Pravin
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-JMS-XA-Client-tp5790967.html
Sent from the Camel - Users mailing
See this link
<http://camel.465427.n5.nabble.com/stand-alone-problem-tp5790885.html> for
how my problem was solved.
BAsically, use /main.run()/ instead of /main.start()/
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-jms-tp5790832p5790898.html
Sent from the
Funnily enough, when I swap the activeMQConnectionFactory with
websphereConnectionFactory, spring does the reconnect.
I might be missing something.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-jms-tp5790832p5790895.html
Sent from the Camel - Users mailing list
Id did the testing with Spring trying to reconnect to a Websphere and I did
configured the factory as follows:
Sadly it does not reconnect. What I am missing?
Thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-jms-tp5790832p5790875
setting this up.
So both camel-jms and camel-sjms can do reconnect if you configure it
correctly with your JMS client / connection pool.
On Wed, Nov 30, 2016 at 9:19 PM, Quinn Stevenson
wrote:
> You’re not missing anything - that’s the way the camel-jms and camel-sjms
> components work. They
I did not know that. I will test it.
Thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-jms-tp5790832p5790844.html
Sent from the Camel - Users mailing list archive at Nabble.com.
You’re not missing anything - that’s the way the camel-jms and camel-sjms
components work. They get a connection from the connection factory when they
startup, and the keep using it. You can configure the Camel route to handle
some JMS Exceptions and sometimes get the reconnect to work that
gone. Am I
missing something?
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-jms-tp5790832p5790836.html
Sent from the Camel - Users mailing list archive at Nabble.com.
If you’re using ActiveMQ, use a failover URL (
http://activemq.apache.org/how-do-i-configure-automatic-reconnection.html
<http://activemq.apache.org/how-do-i-configure-automatic-reconnection.html> )
and both camel-jms and camel-sjms will reconnect.
> On Nov 30, 2016, at 11:38 AM,
Camel noob needs some help.
It seems SJMS does not do reconnect. Now I am looking at camel-jms and it
seems camel-jms does not batch. Any other alternatives out there?
Regards
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-jms-tp5790832.html
Sent from the Camel
FYI: if your camel header is named "camel.is.great" then the JMS property
will be named "camel_DOT_is_DOT_great"
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-JMS-Properties-tp5787616p5787736.html
Sent from the Camel - Users mailing list archive at Nabble.com.
>
> On the JMS Server Side (onMessage):
>TextMessage txtMsg = (TextMessage)message;
> txtMsg.getStringProperty("PropertyName");
>
> The /inString/ is in the JMS Text Message body . but the
> /txtMsg.getStringProperty("PropertyName") == null/;
>
PropertyName");
The /inString/ is in the JMS Text Message body . but the
/txtMsg.getStringProperty("PropertyName") == null/;
Any Ideas?
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-JMS-Properties-tp5787616.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
We are struggling to put a JMS header for MessageID so that the downstream
application can access it as MQMD header.
The downstream application is expecting this.
Pls help
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-jms-setting-specific-MQ-headers
Hi,
camel JMS component client connects to Weblogic queue. Fuse restart
requires whenever Web logic bounced.
Jms pulls mgs from wbelogic server. Whenever weblogic bounced , JMS retry
every 5000 ms but it never connected automatically when weblogic is up. we
need to restart Fuse every-time
Yeah - it's also present on 2.17.3
I created https://issues.apache.org/jira/browse/CAMEL-10237
/Preben
--
View this message in context:
http://camel.465427.n5.nabble.com/possible-camel-jms-regression-in-2-17-2-tp5786290p5786306.html
Sent from the Camel - Users mailing list archi
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/possible-camel-jms-regression-in-2-17-2-tp5786290p5786294.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in
lol - localized error messages is an $$ enterprice feature. And Oracle is
kind of a sticky pease of junk.
--
View this message in context:
http://camel.465427.n5.nabble.com/possible-camel-jms-regression-in-2-17-2-tp5786290p5786294.html
Sent from the Camel - Users mailing list archive at
Hi
Yeah your American Oracle has been too long in Denmark and learned to
talk Danish. Its visa is overdue please return it back.
On Thu, Aug 11, 2016 at 8:41 AM, Preben.Asmussen wrote:
> Hi
>
> I just tried to upgrade camel-jms from 2.17.1 to 2.17.2 and got jms errors
> due
Hi
I just tried to upgrade camel-jms from 2.17.1 to 2.17.2 and got jms errors
due to Oracle AQ regards JMSX*** properties as read only. As I re call there
were som special handling regarding exchange header copying this in 2.xx.
due to this fact.
I think the change was introduced in
https
k-from-activemq-using-camel-jms-component-tp5784312.html
Sent from the Camel - Users mailing list archive at Nabble.com.
.
On May 19, 2016, at 4:07 AM, Adarsh_GU wrote:
Hi Guys,
Is there is any option to override *JMS message id * gernerated by
camel,while using camel jms component?
I have simple route pushes data to queue testQueue
/
/
and saw message id from active mq console as follows
ote:
>
> Hi Guys,
> Is there is any option to override *JMS message id * gernerated by
> camel,while using camel jms component?
>
> I have simple route pushes data to queue testQueue
>
> /
>
>
> /
>
> and saw message id from acti
working.
for each request it is picking up response from response queue (if response
with matching corelation id exists).
But didnt understand why request-reply didnt with above response polling
route :)
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-jms-In-Out-Pattern
Hi Guys,
Is there is any option to override *JMS message id * gernerated by
camel,while using camel jms component?
I have simple route pushes data to queue testQueue
/
/
and saw message id from active mq console as follows
/*Message ID*
ID:ICB1864-53042-1463651730680-1:1
It looks like the other system isn’t setting the JMSCorrelationID, so the route
is timing-out waiting for a response with that correlation ID.
Have you tried setting replyToType=Exclusive? You can see the details in the
camel-jms docs (http://camel.apache.org/jms.html
<http://camel.apache.
> I have 2 queues provided by third party provider 1.request queue, 2.reply
> queue
>
> using camel jms i will send request to request queue, so third party provider
> will push respective response to response queue.
Ok.
> I would to make these calls synchronous. so for eac
Hi Guys,
I have 2 queues provided by third party provider 1.request queue, 2.reply
queue
using camel jms i will send request to request queue, so third party
provider will push respective response to response queue.
I would to make these calls synchronous. so for each request send to
request
eue provided by third
party provider.
>
>
> uri="jms:queue:requestQuee?replyTo=queue:*responseQueue*&exchangePattern=InOut"
>
> />
>/
--
View this message in context:
http://camel.465427.
sponseQueue.
> Exchange[ID-ICB1864-58611-1463553066644-3-8][Message:
>
> *If i remove inout pattern.message is en queued to requestQuee and after
> dequeed by mockresponse route ,eventually MockResponseGenerator prepares
> mock response and enqueued to responseQueue.*
>
> Please updat
44-3-9 not received on destination:
queue://responseQueue. Exchange[ID-ICB1864-58611-1463553066644-3-8][Message:
http://camel.465427.n5.nabble.com/Camel-jms-In-Out-Pattern-tp5782730.html
Sent from the Camel - Users mailing list archive at Nabble.com.
1 - 100 of 334 matches
Mail list logo
