I haven't used it personally, but on your last point around setting
expiration on DLQ messages...a quick google turned up this page
suggesting it can do that since 5.12.0:
https://activemq.apache.org/components/classic/documentation/message-redelivery-and-dlq-handling
Look for the section headed "
Hello
We're using ActiveMQ "classic" 5.18.3
Regards.
Le mar. 11 mars 2025 à 15:01, Justin Bertram a écrit :
> Are you using ActiveMQ Classic or ActiveMQ Artemis? Also which version are
> you using?
>
>
> Justin
>
> On Tue, Mar 11, 2025 at 8:08 AM Ephemeris Lappis <
> ephemeris.lap...@gmail.com
ction handlers
in Camel contexts or Spring Boot applications to alter messages on rollback.
Thanks anyway.
Regards.
Le mar. 11 mars 2025 à 14:42, Mattern, Alex
a écrit :
> If you are just looking to trash old messages then use the timeToLive
> setting when producing messages on the D
Are you using ActiveMQ Classic or ActiveMQ Artemis? Also which version are
you using?
Justin
On Tue, Mar 11, 2025 at 8:08 AM Ephemeris Lappis
wrote:
> 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 co
of messages, where X is specified on startup.
--
Alex
-Original Message-
From: Ephemeris Lappis
Sent: Tuesday, March 11, 2025 9:07 AM
To: us...@camel.apache.org; users@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
> I have a Camel Route that drains all of the queues and topics (excluding
Advisory Topics) from the old broker to the new broker.
Conceptually speaking, there is no real way to "drain a topic" since topics
don't hold messages like a queue does. When dealing with topics, mess
to the new broker setup
with database persistence.
I have a Camel Route that drains all of the queues and topics (excluding
Advisory Topics) from the old broker to the new broker. I am using XPath on
the to get all the queues and topics using these 2 URLs on the old ActiveMQ
broker:
http://xxx
To be clear, Camel 4.x requires Java 17 [1], but ActiveMQ Artemis is still
built with Java 11. The example probably could be updated to explicitly use
Java 17, but it's probably best to just leave it as is for now until we
move to Java 17 (or later) in a future version.
Justin
[1]
The Camel example in the activemq-artemis-examples GIT repo still depends on
Camel 3.16.
However, Camel 3.x will become obsolete at the end of this year.
The supported Camel version is now 4.8.
Can someone update the example? Many thanks!
Erik
MQUnblockedException,
ActiveMQRemoteDisconnectedException, and ActiveMQNotConnectedException
without more details.
Justin
On Thu, Nov 30, 2023 at 8:47 AM Zoltan Lutor (Nokia)
wrote:
> Hi,
>
> I've experienced some strange behavior during trying to experiment with
> Apache Camel 4.0
Hi,
I've experienced some strange behavior during trying to experiment with Apache
Camel 4.0 SJMS2 and Wildfly 29.0.1-1 and Apache ActiveMQ Artemis:
1. AMQ212051: Invalid concurrent session usage. Sessions are not
supposed to be used by more than one thread concurrently.
java.lang.Exce
Hi
Yes activemq-camel component has been removed.
You should now use camel-activemq or camel-jms provided by Camel.
Regards
JB
Le lun. 11 juil. 2022 à 14:50,
a écrit :
> Hello,
>
> I was just updating my activemq server to the latest version (5.17.1) when
> I realized that my c
Hello,
I was just updating my activemq server to the latest version (5.17.1) when I
realized that my camel context was not working anymore.
Apparently the library activemq-camel was removed in version 5.17.* It was
needed for the ActiveMQ Component
Hello,
I was just updating my activemq server to the latest version (5.17.1) when I
realized that my camel context was not working anymore.
Apparently the library activemq-camel was removed in version 5.17.*
It was needed for the ActiveMQ Component
We have activated the DEBUG logging on AMQ and the slave broker does not log
anything else then trying to lock the KahaDB, even though the
Camel client got connected to it:
From amq log on slave broker:
2021-08-01 05:43:52,899 | DEBUG | Database
\\usgwdfsfs01\GWD_DFS_FS\GWD_DFS_PRO\AMQ
FWIW, this was also asked on Stack Overflow [1].
Justin
[1]
https://stackoverflow.com/questions/68525964/activemq-slave-broker-accepts-incoming-connection-from-apache-camel
On Mon, Jul 26, 2021 at 2:09 AM Stefan Schotte
wrote:
> Hi,
>
> I have the following configuration:
>
&
; * Two actively running Tomcat instances running Apache Camel 2.20.2 that
> use the competing consumer concept to read message of the same queue
> * AMQ 5.15.0 in an Master Slave configuration using a shared kahaDB.
>
>
> It happens that one of the Camel instances connec
Hi,
I have the following configuration:
* Two actively running Tomcat instances running Apache Camel 2.20.2 that
use the competing consumer concept to read message of the same queue
* AMQ 5.15.0 in an Master Slave configuration using a shared kahaDB.
It happens that one of the Camel
Hello everyone. I try to send messages from the Camel rout JMS component,
on some messages the error below occurs. Out of 50,000 messages, 4937
reached an average speed of 497 mes/sec. At the same time, with the same
settings, the classic ActiveMQ gives about 10,000 mes/sec
Artemis version 2.11.0
Hi,
You can take a look on a blog I wrote about that:
http://blog.nanthrax.net/?p=820 <http://blog.nanthrax.net/?p=820>
Generally speaking, I’m using Camel for short redelivery (temporary error).
When I want « long » redelivery, I’m using ActiveMQ redelivery with scheduler,
and in tha
Hi
Apologies but I'm a little confused after reading up on Camel docs and books
as well as AMQ docs. My confusion might be due to almost zero experience but
thought I'd ask hopefully some simple questions before I dive in to
development with routes that consume messages from
> your current setup does without the need for any Camel configuration.
>
> Tim
>
> On Mon, Sep 23, 2019 at 10:21 PM William Culler
> wrote:
>
> > Hello Tim.
> >
> > Thanks for taking the time for a response.
> >
> > You are correct. The setup is
of virtual
destinations across a NoB, but I think that as long as you forward the
queues between the brokers and don't forward the topic, it should work as
your current setup does without the need for any Camel configuration.
Tim
On Mon, Sep 23, 2019 at 10:21 PM William Culler
wrote:
> Hello T
messages to ActiveMQ. I assume they used a topic and then used the camel
routes to intercept those messages and write them to the local and local
remote queues as we have the same number of threads consuming messages from
the local queue and then 25 consumers set on the camel routes that route
th
William,
If I understand you correctly, you're using Camel to clone the message so
you get one per data center, and then using Camel to move the message from
the data center at which it was produced to the other one. And you're doing
this so that you can have all messages reach consume
We have the following configuration.
3 brokers in Datacenter A in a master/slave configuration using a shared
file system. 3 brokers in Datacenter B in a master/slave configuration
using a shared file system.
There are producers sending messages to topics at Datacenter A. There are
Camel routes
2019, 3:14 PM bterhune One last update.. The more I learn about what is going on, I realize the
> information I left out of my original post.
>
> The Camel configuration is connecting to the broker in question using the
> vm: protocol AND connecting to a remote broker. The VM connect
One last update.. The more I learn about what is going on, I realize the
information I left out of my original post.
The Camel configuration is connecting to the broker in question using the
vm: protocol AND connecting to a remote broker. The VM connection was the
one causing reconnect to spin
As a workaround I found setting "initialRecconectDelay=1500" on the failover
connection string caused enough delay to avoid the KahaDB from being
creating in the default location.
http://activemq.apache.org/failover-transport-reference.html
--
Sent from: http://activemq.2283324.n4.nabble.com/Ac
r)
runTask:133, PooledTaskRunner (org.apache.activemq.thread)
run:48, PooledTaskRunner$1 (org.apache.activemq.thread)
runWorker:1149, ThreadPoolExecutor (java.util.concurrent)
run:624, ThreadPoolExecutor$Worker (java.util.concurrent)
run:748, Thread (java.lang)
If I had to guess, p
Hi, We have installed activemq and camel for Dataservices 4.2, setup
real-time jobs within dataservices (JMS config), when we send 10 of the same
messages the 1st 5 are processing and then the rest fail. We get the
following error com.acta.adapter.sdk.RecoverableOperationAdapterException:
JMS GET
hat's
relevant to this thread specifically.
Tim
On Sun, Apr 1, 2018 at 9:19 PM, Tim Bain wrote:
-- Forwarded message --
> From:
> Date: Thu, Mar 29, 2018 at 5:44 PM
> Subject: Re: Camel generating message with correlationid=null and
> tmp-queue null
>
> 3
t now,
and then I'll add my responses in a separate message.
Tim
-- Forwarded message --
From:
Date: Thu, Mar 29, 2018 at 5:44 PM
Subject: Re: Camel generating message with correlationid=null and tmp-queue
null
To: tb...@alumni.duke.edu
I dont know, because of some reasons I a
I'm still struggling to understand what exactly you're describing. To the
best of my knowledge, Camel doesn't use KahaDB, so that's making me unsure
of how to interpret what you've written. (Or if it does, please provide a
reference to documentation indicating how i
Rajesh,
First, I want to let you know that although it's possible to edit/delete
mailing list posts on the Nabble site after you've posted them, the edits
are not sent out to the mailing list via email, so anyone (like me) who
works primarily from email will not see the changes you make. So the be
Thank you Tim
for this IOException, we have not observed any reasonable exceptions on
broker [ producer ] side.
attached thread dump jstack.out. Can you please look into and help.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
it seems blockingQueue is not actually ACTiveMQDestination, just it is java,
so any other suggestions ?
at that state we are not able to connect to cloud broker , on client side we
are getting :
Caused by: java.io.EOFException
at java.io.DataInputStream.readInt(Unknown Source)[:1.8.0_60]
thank you Tim,
>>Caused by: java.io.IOException: Failed to perform GET on: https://URL
>>Reason: null
>>at
org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:33)[120:org.apache.activemq.activemq-osgi:5.12.3]
>>at
org.apache.activemq.transport.http.HttpClientTrans
Thanks for looking at my message..
We have two activeMQ brokers that send messages back and forth. We are now
using camel and spring configuration to define those routes
For example:
Support Bundle Response
We are using persistence on topics but not durable
x27;s nothing in the broker's logs that indicates a problem, this would
be the next place to dig into.
Otherwise, I'd attach a debugger to the client and put a breakpoint in
org.apache.activemq.jms.pool.PooledSession.close() and try to figure out
who's calling it and why.
> we
rl authenticating. this
scenario is working properly in <5.8.0
of activemq however not working with 5.12.3 version. I mean, for some
hours it is working after that it is giving errors like attached :
error.txt <http://activemq.2283324.n4.nabble.com/file/t378915/error.txt>
we are using
:org.
> springframework.jms.listener.DefaultMessageListenerContainer:909)
> ERROR - Could not refresh JMS Connection for destination 'queue' -
> retrying
> in 2 ms. Cause: The JMS connection has failed: Channel was inactive (no
> connection attempt made) for too (>
Can you please provide a reference for what "Camel Routing" is in the
context of ActiveMQ, and how it's a replacement for a network of brokers,
or how Camel would cause the creation of KahaDB content? I've never heard
of either such thing and Google didn't shed any a
We recently switched our activemq (5.15.2) broker to broker routing from
using "Network of Brokers" to "Camel Routing" (2.13.0) using Spring XML
configuration.
In our activemq.xml configuration we specify the location of kahaDB
persistence.
We notice after our product restar
25:16,292 369222850 [Camel (camel-4) thread #378 -
TemporaryQueueReplyManager[ ]]
(org.apache.servicemix.bundles.spring-jms:org.springframework.jms.listener.DefaultMessageListenerContainer:909)
ERROR - Could not refresh JMS Connection for destination 'temporary' -
retrying in 5000 ms.
gt;
>> Issue: I am routing a message from active mq topic to Ibm mq queue, using
>> Apache camel as the medium between these two. Apache camel is used for
>> intermediate routing and for transformations. I am setting JMSDestination
>> in message header as some topic name(eg: FM
On 03/12/2018 12:20 PM, Gupta Bharat wrote:
Hello,
Issue: I am routing a message from active mq topic to Ibm mq queue, using
Apache camel as the medium between these two. Apache camel is used for
intermediate routing and for transformations. I am setting JMSDestination in
message header as
Hello,
Issue: I am routing a message from active mq topic to Ibm mq queue, using
Apache camel as the medium between these two. Apache camel is used for
intermediate routing and for transformations. I am setting JMSDestination in
message header as some topic name(eg: FMP/1.0/a/bguxmb). But when
y starting
assumption is that the two are unrelated.
Tim
On Thu, Mar 8, 2018 at 9:58 PM, Rajesh Malla wrote:
> following error messages we are seeing on client side :
> 2018-03-08 18:38:24,248 41319597 [Camel (jcsCoreCamelContext) thread #12 -
> JmsConsumer[uniquequename]]
> (org.ap
following error messages we are seeing on client side :
2018-03-08 18:38:24,248 41319597 [Camel (jcsCoreCamelContext) thread #12 -
JmsConsumer[uniquequename]]
(org.apache.activemq.activemq-osgi:org.apache.activemq.jms.pool.PooledSession:126)
WARN - Caught exception trying close() when putting
I'll start with the bad news. From what you've written, it could be either
product (Camel or ActiveMQ) that's causing the problem, and the people that
support the two products are both likely to initially assume it's the other
product's doing. So one of the best things yo
we are using activemq : 5.12.3
apache camel : 2.16.2
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi
we are using mesh n/w connectors A,B,C. and we have two consumers. upto some
hours system is working fine, after that when we are checking messages those
are generated by camel with correlationId as null
ActiveMQObjectMessage {commandId = 4, responseRequired = true, messageId =
ID:asdf-55403
I'm running Karaf 4.1.0 and Artemis 2.0 on AWS EC2.
It's running fine but when I setup a camel route that connects to Artemis I
get the following errors.
org.apache.activemq -- Cannot be resolved
org.apache.activemq.camel.component -- Cannot be resolved
Question 1 - When running Ar
4.n4.nabble.com/Conduit-subscriptions-when-using-Network-of-brokers-and-Camel-topic-subscriptions-tp4715559p4715560.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
tk connector
** The ttl is set so that messages and subscriptions can go through all the
brokers
* Create 3 camel contexts with some routes that allow to:
** Post a message to the topic1 from any client connected to any broker
** Subscribes to topic1 from any client connected to any broker
The unit te
ed. I commented out the "to" as they
are not required for what I need but once again does work if
uncommenting.
Cheers
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Help-with-Camel-Config-routing-using-a-custom-ActiveMQ-Message-Property-tp4713278p4713418
No - Camel don’t have a “/dev/null” endpoint. However, if you don’t want the
message to go anywhere, just don’t send it (i.e. bypass the to). If you really
need the to, you can always send it to a log uri - something like
message is
automatically acknowledged when it is first delivered to you (before you
have processed it), and that's the mode it sounds like your Camel route is
using. So the message is acknowledged when it exits your from tag, and if
you want to drop it, you just need to not route it onward t
Currently the configuration is just pulling from a remote queue to a local
queue and that is it.
The Camel XML config file just has a FROM and TO XML tag.
Some changes are being made upstream that will send messages to my system
that I may not want.
That is the reason for wanting this filtering
or have your processor return null), which
> in the default Camel configuration happens automatically when your Camel
> route receives the message. If your route is somehow set up for individual
> acks, you'd have to do the ack manually, but the code you've inherited
> would h
To trash a message, do not send it to a DLQ! DLQ != /dev/null.
Instead, just ack the message after you consume it (without doing anything
in response, just end the route or have your processor return null), which
in the default Camel configuration happens automatically when your Camel
route
Hello,
You can route messages following messages properties with filtered
destinations http://activemq.apache.org/virtual-destinations.html
or camel http://activemq.apache.org/sample-camel-routes.html
http://camel.apache.org/message-filter.html
to trash a message i think you can route it to
I've taken over a project in which everyone that knows anything is gone.
I'm new to ActiveMQ and have never used Camel before.
I'm trying to do content message routing and have a sample of what I'm
attempting to do but have a couple of questions.
* How to access a cus
I have an application with two camel routes:
Route 1 (Consumer Route)
Reads a text file having no. of records (line separated), split them based
on each line and sends each split record to another queue ('intermediate'
queue)
Route 2 (Producer Route)
Reads each r
On Thu, Apr 28, 2016 at 2:49 PM, Quinn Stevenson <
qu...@pronoia-solutions.com> wrote:
>
>
>
> MyHeaderValue
>
>
> broker://${header[JMSDestination]}
>
>
>
I have a nearly identical route r
>
> BTW - I did it working with the Camel Broker Component by switching from
> to . I’m not sure why that made a difference,
> but it did.
>
> > On Apr 28, 2016, at 10:53 PM, Tim Bain wrote:
> >
> > I think you want to be using interceptors (
> > http://ac
Thank You Tim -
Is there an example of an interceptor somewhere in the code base I can use as a
reference to get started on this?
BTW - I did it working with the Camel Broker Component by switching from
to . I’m not sure why that made a difference, but
it did.
> On Apr 28, 2016, at 10
I think you want to be using interceptors (
http://activemq.apache.org/interceptors.html), not consuming from a queue
and then publishing back to the same queue. I've always believed that
embedded Camel routes couldn't be inserted into the middle of accepting a
message (which is what
I’m trying to use the ActiveMQ Broker Camel Component to add some JMS user
properties to messages as they arrive at the broker. I’m using a wildcard on
the from so I can apply the same logic to a set of topics or queues, but I
can’t seem to send the message back to the original queue.
Without
Hello forum, any inputs would be greatly appreciated..
--
View this message in context:
http://activemq.2283324.n4.nabble.com/AMQ-fails-if-remote-broker-is-not-started-via-Camel-using-STOMP-and-MQTT-tp4710709p4710871.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
afterwards.
Is this expected or is there any additional configuration we require?
We are using the following:
AMQ - 5.10.0
camel - 2.17
RabbitMQ - 3.5.0
This runs on:
Linux 6.4
In terms of CAMEL route configuration we have the following:
>:<>&login=&am
Note, by the way, that asyncSend=false only affects the send from the
producer to the broker - not from the broker to the consumer.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Reject-an-incoming-message-from-Camel-broker-component-tp4706168p4706422.html
Sent from the
message in context:
http://activemq.2283324.n4.nabble.com/Reject-an-incoming-message-from-Camel-broker-component-tp4706168p4706421.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I wonder if you need to use asyncSend=false (to force sync) on the
client, and then with the camel broker component you can route and
possible reject the incoming message. Which maybe can affect that the
client get a NACK ?
http://activemq.apache.org/broker-camel-component.html
http
Thanks. I'd prefer the clients to not have to do anything special.
Is there any way to intercept an inbound message and affect the
acknowledgement back to the producer so they know the send failed
immediately?
This doesn't necessarily have to be camel if there is another way to achiev
, 2016 10:36 AM, "slew77" wrote:
> Hi,
>
> I've configured a camel route intercepting an inbound message.
>
> If something goes wrong when processing the camel route, I'd like to be
> able
> to reject the incoming message in a way that the client knows
Hi,
I've configured a camel route intercepting an inbound message.
If something goes wrong when processing the camel route, I'd like to be able
to reject the incoming message in a way that the client knows that the
message hasn't been accepted.
If my route doesn't forward
Hi,
>From the docs:
The broker camel...intercepts messages as they move through the broker
itself, allowing them to be modified and manipulated before they are
persisted to the message store or *delivered to end consumers*.
I can see how to intercept messages before they are persisted to
camel.xml and the activemq.xml files? I’d like to see what
the differences are.
Quinn Stevenson
qu...@pronoia-solutions.com
(801) 244-7758
> On Dec 29, 2015, at 10:14 PM, Tim Bain wrote:
>
> Nope, never; I've only read about it here and on the wiki. (I've used
> Camel, b
Nope, never; I've only read about it here and on the wiki. (I've used
Camel, but never embedded in a broker.) Sorry. But others on this list
have, so hopefully they can share first-hand knowledge.
On Dec 29, 2015 10:22 AM, "Quinn Stevenson"
wrote:
> Have you tried
Have you tried using the Broker Camel Component (
http://activemq.apache.org/broker-camel-component.html
<http://activemq.apache.org/broker-camel-component.html> )? I thought that it
wouldn’t start the route unless the broker was running.
Quinn Stevenson
qu...@pronoia-solutions.com
(80
ould like to happen but the question is how?
>
> Thanks
>
> Mike
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/suppress-error-from-Camel-Route-on-slave-tp4705457p4705478.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
That's what I would like to happen but the question is how?
Thanks
Mike
--
View this message in context:
http://activemq.2283324.n4.nabble.com/suppress-error-from-Camel-Route-on-slave-tp4705457p4705478.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Maybe the broker should automatically suspend all embedded Camel routes
when it becomes a slave, and resume them when it becomes a master?
On Dec 28, 2015 4:18 PM, "mtod" wrote:
> I'm running ActiveMQ 5.13 on a leveldb cluster.
> My ActiveMQ.xml config contains a Camel rou
I'm running ActiveMQ 5.13 on a leveldb cluster.
My ActiveMQ.xml config contains a Camel route in an include file.
I route xml from one queue to a topic but when slave is in standby mode I
keep getting this error :
INFO | jvm 1| 2015/12/28 18:10:26 | ERROR | Could not refres
I'm running ActiveMQ 5.12.0 in a leveldb cluster and I'm using the Camel
functionality built in to ActiveMQ.
I keep getting this error on the stand by servers.
ERROR | Could not refresh JMS Connection for destination 'esb.*' - retrying
in 5000 ms. Cause: Could not crea
Without using Apache Karaf, is there a way to set up hot deployable camel
routes in ActiveMQ? I would like to drop in either a single new route or
all of the routes and have ActiveMQ pick up the changes on the fly. If this
feature is version dependent then please let me know what version to use
Yes, I tried \" and " plus I tried using %3D instead of =. None of them
have worked for me.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Broker-camel-component-message-selectors-tp4696923p4696925.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Did you try wrapping the selector expression in escaped quotes? () I've never used embedded
Camel routes, but that's how I'd expect it to work so give it a shot.
On May 26, 2015 3:17 PM, "davidthomas426" wrote:
> I'd like to do something like thi
I'd like to do something like this with the broker camel component:
I'm getting org.apache.camel.ResolveEndpointFailedException about the
"selector" parameter of the endpoint. How can I set up this route? Do I need
to use MessageBrokerView, maybe? Or is the
Just getting back to this.
So it's sounds like there's no resolution to this namespace issue.
Short of removing name spaces from the messages or not using this feature.
Thanks
Mike
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-5-11-Dynamic-C
at 75.
I believe that the combination of ms.prefetchPolicy.all=1 and having
* causes this
issue and I am not sure why!
Thanks
Matt
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-using-in-Camel-In-OUT-endpoint-creates-additional-consumers-on-response-queue-which
but if
what you're doing is creating a new producer without stopping the previous
one, then that's broken too if you aren't changing the replyTo parameter.
You need to make sure that you're shutting down the existing consumers
before you start the new route. Maybe Camel is sup
http://activemq.2283324.n4.nabble.com/Apache-camel-monitor-activemq-tp4693789p4693838.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Tim
On Wed, Mar 25, 2015 at 9:44 AM, Claus Ibsen wrote:
> Hi
>
> There is also mirrored queues
> http://activemq.apache.org/mirrored-queues.html
>
> On Wed, Mar 25, 2015 at 4:38 PM, Tim Bain wrote:
> > It's not something I've done personally, but the docume
Hi
There is also mirrored queues
http://activemq.apache.org/mirrored-queues.html
On Wed, Mar 25, 2015 at 4:38 PM, Tim Bain wrote:
> It's not something I've done personally, but the documentation at
> http://activemq.apache.org/broker-camel-component.html should get you
> star
It's not something I've done personally, but the documentation at
http://activemq.apache.org/broker-camel-component.html should get you
started.
Tim
On Wed, Mar 25, 2015 at 9:14 AM, Jonasty wrote:
> Mr Tim
> Thanks for the advice, I need a message ID so I don't know if o
Mr Tim
Thanks for the advice, I need a message ID so I don't know if option 3 is
going to work.
I can't turn my queue in a topic so I go for option 2.
Can you explain how you can make a camel route to the broker itself?
Thanks in advance
Jonasty
--
View this message in cont
1 - 100 of 441 matches
Mail list logo
