Looks like Ian was working on this back in '06 using STOMP.
http://markmail.org/message/eahnrljkyemqvuag
Joe
http://www.ttmsolutions.com
ActiveMQ reference guide at
http://bit.ly/AMQRefGuide
newphoenix wrote:
>
> Hi
> Is there any J2ME library to connect and start using ActiveMQ as Client
The Camel wire tap route may do the trick for ya.
http://camel.apache.org/wire-tap.html
Joe
http://www.ttmsolutions.com
ActiveMQ reference guide at
http://bit.ly/AMQRefGuide
BenXS wrote:
>
> When I read on page
>
> http://activemq.apache.org/mirrored-queues.html
>
> I got the impression t
What about skipping the browser and simply issuing a selective
receiveNoWait() with the messageID that you're interested in removing from
the queue?
Joe
http://www.ttmsolutions.com
ActiveMQ reference guide at
http://bit.ly/AMQRefGuide
odysseyfx wrote:
>
> What's the best way to delete speci
There are a couple of dispatch policies in
org.apache.activemq.broker.region.policy that can perhaps serve as reference
implementations for ya.
Joe
http://www.ttmsolutions.com
ActiveMQ reference guide at
http://bit.ly/AMQRefGuide
mindstream wrote:
>
> I'd like to explore using a custom di
IMHO, things should remain as is. If the broker is not being granted access
to the lock, it will never be able to go to the next step of trying to
acquire the lock.
Joe
http://www.ttmsolutions.com
ActiveMQ reference guide at
http://bit.ly/AMQRefGuide
emilyj wrote:
>
> There is an issue with
This seems to work fine for me with 5.3.2. What version of AMQ are you using?
Care to share your AMQ cfg file?
Joe
http://www.ttmsolutions.com
ActiveMQ reference guide at
http://bit.ly/AMQRefGuide
Christian Hoffmann-5 wrote:
>
> Hi,
>
> I have a network of two brokers that have auto discove
See this post from Rob and corresponding thread.
http://old.nabble.com/StoreUsage%2C-TempUsage-and-MemoryUsage-to15206526.html#a15211788
Joe
http://www.ttmsolutions.com
ActiveMQ Ref Guide - http://bit.ly/AMQRefGuide
radha_mit wrote:
>
>
> Hi,
> we are planning to shift our jms provider
LaRockstar wrote:
>
>
> Hi Joe,
>
> Thanks for you answer ...
>
>
> Joe Fernandez wrote:
>>
>> If you use the discovery agent across all your brokers, the result will
>> be a full mesh, and not tree, topology. In other words, all the brokers
>
If you use the discovery agent across all your brokers, the result will be a
full mesh, and not tree, topology. In other words, all the brokers will be
interconnected.
You do not have to explicitly create the queues at the brokers. They will be
dynamically created on-demand.
Joe
http://www.ttm
There is the recipient pattern and mirrored queues.
http://camel.apache.org/recipient-list.html
http://activemq.apache.org/mirrored-queues.html
Joe
http://www.ttmsolutions.com
ActiveMQ Ref Guide - http://bit.ly/AMQRefGuide
BenXS wrote:
>
> I defined the following for camel in an ActiveMQ
If you want the brokers to be independent of one another (i.e., they're not
interconnected), then don't include networkConnectors (forwarding bridges)
in their configurations.
On the clients side, I think the discovery agent/connector should give you
what you want.
http://activemq.apache.org/d
I've attached a PDF that illustrates how to bind and lookup AMQ objects to
and from an LDAP server using JNDI.
http://old.nabble.com/file/p28891251/AmqLdapJndi.pdf AmqLdapJndi.pdf
Joe
ActiveMQ Ref Guide - http://bit.ly/AMQRefGuide
boevink wrote:
>
> We are using an LDAP server for registe
Well, I just gave it a try myself and it didn't quite do the trick. With the
failover, the slave does wait for the master, and when the master does
start, the two appear to connect okay. However, if you bring down the
master, the slave fails to open up it transports.
Joe
Joe Fernandez
Try using a failover connector like this.
Joe
http://www.ttmsolutions.com
Andreas.Weber wrote:
>
> Hi,
>
> in a cluster szenario we run a distributed application containing
> ActiveMQ. We configure a pure master/slave, with one cluster host as
> ActiveMQ master (waitForSlave="true") and
ons.
>
> -ste
>
> -Original Message-
> From: Joe Fernandez [mailto:joe.fernan...@ttmsolutions.com]
> Sent: Wednesday, June 09, 2010 3:39 PM
> To: users@activemq.apache.org
> Subject: Re: example.A queue keeps coming back.
>
>
>
> See the following.
What does the transport connector for your 'distant' broker look like? Reason
I ask is that the wildcard (0.0.0.0) vs localhost IP address issue has been
biting lots of folks.
https://issues.apache.org/activemq/browse/AMQ-2094
Can you telnet to your 'distant' broker?
Joe
http://www.ttmsolution
See the following.
http://activemq.apache.org/how-do-i-delete-a-destination.html
How are you deleting it?
Joe
http://www.ttmsolutions.com
shaun.t.erickson wrote:
>
> This queue gets created on ActiveMQ start up. I delete it and it comes
> back on the next start up. Lately, it has started
AMQ's producer flow control mechanism kicks in if one of the following
conditions occurs:
- The corresponding destination’s (queue) maximum memory usage limit has
been reached
- The message store’s maximum capacity has been reached.
If you don’t want your producer to block or hang when flow co
The file being referenced in that page is the broker's xml cfg file. The AMQ
5.3.x distribution includes a number of sample broker cfg files in
ACTIVEMQ_HOME/conf.
Here's a page that has links to some user submitted cfgs.
http://activemq.apache.org/user-submitted-configurations.html
Joe
in
I think you'll need a JMS-to-JMS bridge that connects the AMQ and WLS message
brokers.
http://activemq.apache.org/jms-to-jms-bridge.html
You can also use Camel to implement such a messaging bridge.
http://www.enterpriseintegrationpatterns.com/MessagingBridge.html
Joe
ActiveMQ Ref Guide - htt
http://activemq.apache.org/virtual-destinations.html
Joe
ActiveMQ Ref Guide - http://bit.ly/AMQRefGuide
ingorfano wrote:
>
> hi guys need documentation on how creating virtual topic in ActiveMQ. and
> also consumer of that virtual topic.Any clue?
>
> vo
>
--
View this message in context:
The InactivityMonitor should have detected the failed connection. What value
did you assign to maxInactivityDuration? By default it is set to 3ms.
Joe
ActiveMQ Ref Guide - http://bit.ly/AMQRefGuide
daniel.stucky-2 wrote:
>
> Hi ActiveMQ Team,
>
>
>
> in the eclipse open source projec
Is the AMQ message broker running on the server machine and listening on port
61616?
If so, try telnet'ing to xxx.yyy.zzz.xyz 61616 and see if the broker
responds.
Joe
ActiveMQ Ref Guide - http://bit.ly/AMQRefGuide
test4john wrote:
>
> 1. brand new installation of tomcat 6;
>
> 2. activemq
How about using Camel to create a content-based router?
http://camel.apache.org/content-based-router.html
Joe
ActiveMQ Ref Guide - http://bit.ly/AMQRefGuide
ingorfano wrote:
>
> Hi
>
> unfortunately Siebel sysytem doesn't support Message Selector, so i
> connect to a Topic using JNDI prope
Try using consumer prioritization.
http://activemq.apache.org/consumer-priority.html
>From the web page -
"The way it works is that the broker will simply order any queue consumers
according to their priorities and send messages to the highest priority
consumers first. Once a particular consu
Try 'deleteAllMessagesOnStartup'.
http://activemq.apache.org/broker-uri.html
Joe
ActiveMQ Ref Guide - http://bit.ly/AMQRefGuide
gng wrote:
>
> I'd like to delete all queues and topics (and all messages in them) when I
> restart ActiveMQ. In other words, I'd like to have an empty state.
>
>
timeBeforeDispatchStarts
http://activemq.apache.org/per-destination-policies.html
Joe
mar_kl wrote:
>
> Hi Joe,
>
> it occurs when the consumers are started after the messages have been
> enqueued.
> and all settings are at the defaults.
>
> Markus
>
>
> Joe Fernandez wrote
It looks like you have the discoveryUri set for your transportConnector. If
so and you're not relying on multicast, then try removing discoveryUri.
For example, change this
to this
See if that helps.
Also, I highly recommend moving up to 5.3.1 if you can.
Joe
ActiveMQ Ref Guide - http:/
When this occurs, do you fire up the consumers before or after the messages
have been queued up?
Are you using the default prefetch?
Joe
ActiveMQ Ref Guide - http://bit.ly/AMQRefGuide
mar_kl wrote:
>
> Hi,
>
> I'm using an ActiveMQ 5.3 broker embedded in geronimo 2.2.
>
> I got 4-10 consume
I think this is the normal behaviour for 5.2.
For 5.3, the message broker automatically sweeps destinations of expired
messages every 30 seconds. You can change this default value via the
'expireMessagesPeriod' policyEntry attribute.
Joe
ActiveMQ Ref Guide - http://bit.ly/AMQRefGuide
magell
What about recording all message events via the logging interceptor?
http://activemq.apache.org/logging-interceptor.html
Joe
CoreyTheiss wrote:
>
> Hi there,
>
> I'm trying to debug a problem whereby messages are being delivered to a
> black hole. However, once a message has been successful
How about using a bridge?
http://activemq.apache.org/jms-to-jms-bridge.html
Or look into Camel's JMS and AMQ connectors to implement your own bridge.
Joe
ActiveMQ Reference Guide: http://bit.ly/AMQRefGuide
pronity wrote:
>
> Hello,
>
> I have a running websphere MQ which subscribes to ano
One possible workaround is to use a combination of permanent queue and header
property (e.g., correlationId). See the following
http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html
Joe
ActiveMQ Reference Guide: http://bit.ly/AMQRefGuide
easyl wrote:
>
> I am usin
Amok,
To bridge two AMQ message brokers you should use a networkConnector. The
bridgeConnector is used to connect an AMQ broker to some other JMS provider.
The networkConnector is used to create a AMQ network of brokers.
http://activemq.apache.org/networks-of-brokers.html
With 5.3, 0.0.0.0 sh
Can you have two instances of the same POJO? If so, create two separate
threads with their own sessions to the appropriate destination and give each
thread an instance of the POJO.
What about spawning multiple threads, each having their own Session,
instance of the message listener POJO, and poi
If your topic consumer subscribes to the topic after the messages have been
published, then it will not receive those messages. It will only receive
messages that are published while it has an active subscription.
If you want your topic consumer to receive messages that are published while
it d
There is the LoggingBrokerPlugin, which Gary mentioned, and there is also the
wire tap pattern that you can implement using Camel.
http://camel.apache.org/wire-tap.html
Joe
http://www.ttmsolutions.com
BenXS wrote:
>
> How can I log all incoming and outgoing JMS msgs into a separate log fil
> ...I'm still missing something and getting OOMs.
> TIA,
> F.
>
>
> On Fri, Jan 22,
>
> any chance you can build from trunk and try it ?
>
> cheers,
>
> Rob
>
> On 22 Jan 2010, at 20:07, Joe Fernandez wrote:
>
Its Miller-time here in Florida, so I'll give it a go on Monday d:)
Joe
rajdavies wrote:
>
> Hi Joe,
>
> any chance you can build from trunk and try it ?
>
> cheers,
>
> Rob
>
> On 22 Jan 2010, at 20:07, Joe Fernandez wrote:
>
>
to fail for the
> producer if the broker ever does anything funny.
>
> Thanks for the feedback on the config, very helpful.
>
> -Original Message-
> From: Joe Fernandez [mailto:joe.fernan...@ttmsolutions.com]
> Sent: Thursday, January 21, 2010 1:01 PM
> To: users@activemq
Just for grins, I threw your cfg file into our 5.3 testbed and sure enough,
we got the OOMs; I pumped 200k messages with each being 2k in size. FWIW,
taking this out of the cfg file made things run a lot better.
With the above taken out of the cfg file, I was able to pump 400k me
To get rid of the INFO messages, set
org.apache.activemq.store.kahadb.LOG_SLOW_ACCESS_TIME to something like 8000
What message size are you using in your tests?
Joe
http://www.ttmsolutions.com
Daniel Kluesing-2 wrote:
>
> I tried the suggestion of going with the default cursor, but I still ge
I would strongly recommend moving up to 5.3. A LOT of issues have been
addressed since 5.1.
AFAIK, you cannot control the size of in-memory queues based on the number
of messages. If that is indeed the case, you could submit a JIRA requesting
this feature.
If these are transient messages and y
You can use the dataDirectory attribute of the broker element as follows
http://activemq.apache.org/schema/core";
brokerName="localhost" dataDirectory="/tmp/foo">
You can also specify the location of the file-based message store via the
persistenceAdapter element. For example
Joe
http
persistent messages with asyncSend?
Joe
jongraf wrote:
>
> Much appreciated Joe. Let me get this straight: higher throughput with
> persistent messaging + asyncSend vs. non-persistent messaging? It
> wouldn't be the same throughput?
>
>
> Joe Fernandez wrote:
>>
Non-persistent messages are, by default, sent asynchronously (a.k.a., fire
and forget).
Yes, if you send persistent messages with asyncSend, you will realize a nice
boost in throughput.
Joe
http://www.ttmsolutions.com
jongraf wrote:
>
> Two questions:
> 1) Is asyncSend set to true by defaul
By default, ActiveMQ sends or streams messages to a consumer's local buffer
in batches. The batching of the messages can be controlled via the prefetch
limit. So AMQ pushes messages to the consumer as opposed to having the
consumer pull each message on demand.
http://activemq.apache.org/what-is-
Wrt AMQ 5.3. By default, persistent messages that expire are automatically
moved from their destination to the DLQ. However, non-persistent messages
that expire are automatically removed/deleted from their destination.
By default, the message broker sweeps destinations of expired messages every
If you're using a message listener and depending on your prefetch limit size,
then mixing AUTO_ACKNOWLEDGE with optimizeAcknowledge can result in
unacknowledged messages. Switch to DUPS_OK_ACKNOWLEDGE or drop the use of
optimizeAcknowledge.
Joe
http://www.ttmsolutions.com
Gary Tully wrote:
>
>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
Cool
BTW - The framework also comes with a SNMP v2 Agent and MIB for AMQ through
which you can query the broker. It essentially exposes the MBeans via SNMP.
Anyway, thought I'd mention that just in case it makes it easier for cacti.
Joe
ripienaar wrote:
>
>
> Joe Fernandez wro
Hi,
Can you post your broker's cfg file?
Also, what is the average size of the non-persistent messages that you're
pushing through the broker?
Joe
http://www.ttmsolutions.com
Adrian A wrote:
>
> Hello All
>
> On 5.3.0.4 and 5.3.0.5
>
> Seeing some odd behaviour with a messageproducer.send
You may find this free AMQ monitoring framework interesting or applicable to
your env.
http://www.ttmsolutions.com/Transactional_Software_Solutions/Active_Monitor_AMon.php
It allows you to develop and embed Camel-based monitoring agents within the
Broker. The agents use a monitoring expression
You can find org.apache.activemq.pool.PooledConnectionFactory in
ACTIVEMQ_HOME/lib/optional/activemq-pool-5.3.0.jar. If I'm not mistaken,
that jar file was initially created with the 5.2 release.
Joe
http://www.ttmsolutions.com
migbri wrote:
>
> What is the current (AMQ 5.3) recommended impl
It sounds to me like an embedded broker is what you're look for?
http://activemq.apache.org/how-do-i-embed-a-broker-inside-a-connection.html
With this feature the broker and client both execute within the same JVM.
Joe
http://www.ttmsolutions.com
#include_fto wrote:
>
> I need my Broker
You might also want to look into the DiscardingDLQBroker plugin.
See bottom of this page
http://activemq.apache.org/message-redelivery-and-dlq-handling.html
Joe
http://www.ttmsolutions.com
Eric-AWL wrote:
>
> Hi Joe.
>
> Thank you very much for your answer.
>
> Eri
With AMQ 5.3, non-persistent messages that expire are automatically
removed/deleted from their destination. Persistent messages are moved to the
DLQ.
By default, the destination sweeps occur every 30 seconds. You can change
this default via the 'expireMessagesPeriod' property.
Joe
http://www.t
Looks like enableJournalDiskSyncs is comparable to the AMQ message store's
syncOnWrite (sync every write to disk) property, which by default it set to
'false'.
http://activemq.apache.org/amq-message-store.html
Joe
Duro wrote:
>
> It seems enableJournalDiskSyncs="false" do the trick, but what
You should get some improvement on the producer side if you set useAsyncSend
to true.
If you have a relatively small number of destinations and high throughput is
important, the AMQ message store is the way to go.
Joe
http://www.ttmsolutions.com
Duro wrote:
>
> Hi,
>
> i've tested kahadb a
It is possible for one broker to handle many producers and consumers. And
given adequate resources and proper tuning, I think you'll be surprised as
to the number of consumers and producers one broker can handle.
Joe
http://www.ttmsolutions.com
niko_dim wrote:
>
> Hi,
>
>I have an ap
You can use JMX to tap the broker's MBeans for the information.
Or you can use this free monitoring product (AMon) and create a monitoring
agent (Monlet) that can inform your application whenever a queue's threshold
(high water or low water mark) has been breached. It basically allows you to
imp
tworks-of-brokers is used for connecting activemq brokers.
> In my case, I need to connect 2 jboss messaging services on 2 jboss
> servers with activemq.
> Is that possible?
>
>
>
> Joe Fernandez wrote:
>>
>> Yes, you use what's referred to as a 'forwardi
gt; Is there any other workaround or won't I just be able to know when a
> consumer or producer disconnects or subscribes to a Stomp queue or topic?
>
> Thanks,
> Tiago
>
>
>
> Joe Fernandez wrote:
>>
>> You may want to look at using advisory messages
>
Yes, you use what's referred to as a 'forwarding bridge' or 'network
connector' between the two brokers.
http://activemq.apache.org/networks-of-brokers.html
Joe
http://www.ttmsolutions.com
jeff yung wrote:
>
> Is it possible to make use of activemq bridge to forward the messages from
> a rem
You may want to look at using advisory messages
http://activemq.apache.org/advisory-message.html
Or for more finer-grained control check out this free AMQ monitoring
framework.
http://www.ttmsolutions.com/Transactional_Software_Solutions/Active_Monitor_AMon.php
Joe
Boarder wrote:
>
> I can
wrote:
>
>
> Joe Fernandez wrote:
>>
>> Sounds like you're wanting to implement a message-level audit trail? With
>> Camel, you could very quickly implement a wiretap message pattern
>> (http://camel.apache.org/wire-tap.html) and have the wiretap route the
>> ta
JMS is an API not a transport protocol. Each JMS provider has its own
transport or wire-level protocol. For example, one of AMQ's transport
protocols is called OpenWire
(http://activemq.apache.org/openwire-version-2-specification.html) which can
be tunneled over or through HTTP/S
(http://activemq.
Sounds like you're wanting to implement a message-level audit trail? With
Camel, you could very quickly implement a wiretap message pattern
(http://camel.apache.org/wire-tap.html) and have the wiretap route the
tapped messages to a log4j appender. The appender's logfile could rollover
based on si
See the following nabble thread
http://old.nabble.com/Memory-Leak-to16120738.html#a16120738
Joe
http://www.ttmsolutions.com
Websphere and ActiveMQ wrote:
>
> Hi, I started to use ActiveMQ to replace IBM MQ. My working environmeng is
> Websphere, JVM1.5_11 and ActiveMQ, use pure java applica
A connection is associated with only one broker. So you'd have to spawn two
threads and have each thread establish a connection to a different broker.
Thread 1's connection = failover://(tcp://host1:61616)
Thread 2's connection = failover://(tcp://host2:61616)
Using Camel, you'd simply create t
Here's a good starting point.
http://camel.apache.org/writing-components.html
But you might want to first bone-up on Camel in general.
Joe
http://www.ttmsolutions.com
AL_DK wrote:
>
>
> James.Strachan wrote:
>>
>>
>> It would be pretty easy to create an RV component for Camel
>> http:/
e time to get the message
Thread.sleep(1000);
// close everything down
topicSender.close();
topicSession.close();
queueSession.close();
conn.close();
Shyam Santhanam wrote:
>
>
> Joe Fernandez wrote:
>>
>
I forgot to mention that once the consumer queues have been created, the
messages will be forwarded on to the queues, even if the corresponding
consumers are not active. One option is to have the broker create the queues
on start up.
Joe
http://www.ttmsolutions.com
Joe Fernandez wrote
If you activate your consumer after the messages have been published to the
topic, then the messages will not be forwarded on to the consumer's queue.
As an alternative, you might want to check out Camel to implement a similar
messaging pattern.
http://camel.apache.org/recipient-list.html
J
Hi Geoff,
A Network of Brokers (NoB) is set up so that you can forward messages from
one broker to another in the NoB. A connection between two brokers in the
NoB is also referred to as a forwarding bridge. See the following
http://activemq.apache.org/networks-of-brokers.html
AMQ 5.3 comes wi
AFAIK, AMQ does not persist statistics out to secondary storage.
You could write your own plugin that taps the MBeans for the info and writes
it out to a db. Or write a Monlet using this
http://www.ttmsolutions.com/Transactional_Software_Solutions/Active_Monitor_AMon.php
monitoring tool .
The
tes). Do I
still use Camel in this case, or ActiveMQ?
Camel has a handful of DB-related components. Again, you'll still use
ActiveMQ as your JMS provider.
Cheers,
Linuca.
Joe Fernandez wrote:
>
> You may want to consider using Camel to implement the request/reply
> messaging pat
FWIW, I have gotten throughput rates of ~3000 msg/s under the following
conditions.
Used persistent messages, default msg store, message size = 1k, queues, and
producer had jms.useAsyncSend=true
Broker ran on an openSUSE 11.0 laptop (2GB memory, Intel Core 2 Duo T5550,
1.83 GHz, JDK 1.6) and
You may want to consider using Camel to implement the request/reply messaging
pattern in combination with a content based router to route messages to
their respective systems.
http://camel.apache.org/request-reply.html
http://camel.apache.org/content-based-router.html
Camel makes it a lot easie
Here are some snippets taken from the
http://www.ttmsolutions.com/Apache_Software/ActiveMQ_Reference_Guide.php
ActiveMQ Reference Guide . You'd use a 'ssl' connector instead of 'tcp'.
Hope this helps
To configure a broker and client to discover each other using the rendezvous
connector, specif
I think that by design a message will not be forwarded to a broker that it
has already visited.
Joe
http://www.ttmsolutions.com
Eric Van wrote:
>
> ActiveMQ 5.3.0_SNAPSHOT (Sep 8th according to the snapshots listing)
>
> I'm running into an issue with the store and forward feature of
> acti
Are you setting the delivery mode on the publisher to be non-persistent?
Joe
http://www.ttmsolutions.com
nkleinsch wrote:
>
> Adding some of the things I've tried in case they'd be of help to other
> people in the future.
>
> - Disabled producer flow control
> (http://activemq.apache.org/pr
I don't have a date, but from what I understand it is getting very close to
being released.
Joe
http://www.ttmsolutions.com
farshad wrote:
>
> Hi Joe,
>
> Thanks again for your reply. Do you know when 5.3 is going to be
> released?
>
> -Farshad
>
>
Not sure about ActiveMQ and RSS, but for your logging alternative perhaps
using Camel to set up a wire tap may do the trick for you.
http://camel.apache.org/wire-tap.html
There is also this ActiveMQ monitoring product.
http://www.ttmsolutions.com/Transactional_Software_Solutions/Active_Monitor
ot;static://(tcp://host1:61616,tcp://host2:61616,tcp://host3:61616,tcp://host4:61616)">
> networkTTL=4
> dynamicOnly=true
>
>
>
>discoveryUri="multicast://default"/>
>
>
> Thank you,
> FarshadK
>
>
>
You should use the static and not failover connector to configure your
network of brokers. Also make sure that you have the appropriate values
assigned to the networkTTL and dynamicOnly parameters.
http://activemq.apache.org/networks-of-brokers.html
Joe
http://www.ttmsolutions.com
farshad w
I believe this is working as designed. In the process of connecting to the
two different brokers, your consumer has pollinated the two brokers with the
same 'durable subscription'.
You may want to consider using Virtual Topics.
http://activemq.apache.org/virtual-destinations.html
Joe
http://ww
Prior to sending a message, your scheduler can use a QueueBrowser w/selector
to peek at the queue and make sure a message with the same entity id as the
one about to be sent doesn't already exist.
Or your consumer can use a selector to fetch any other messages on the queue
that have an entity id
You can try setting up a Camel route that reads messages from an ActiveMQ
topic and then forwards/routes the messages to a mail component.
http://camel.apache.org/activemq.html ---> http://camel.apache.org/mail.html
Joe
http://www.ttmsolutions.com
shaldar wrote:
>
> Hello all -
>
> I am
You can use composite destinations.
http://activemq.apache.org/composite-destinations.html
You can also use Camel to implement this messaging pattern and at the same
time, keep yourself JMS provider neutral.
Joe
http://www.ttmsolutions.com - FREE AMQ foundation guide.
Locuester wrote:
>
>
Bear in mind that an expired message remains in its destination until some
activity occurs on its destination.
Joe
http://www.ttmsolutions.com
pshar...@sapient.com wrote:
>
> Thanks for replying. I tried with this line of code. but still messages
> are not getting expired.
>
> TimeSpan tim
There is a reference guide available at this site
http://www.ttmsolutions.com/Apache_Software/ActiveMQ_Reference_Guide.php
Joe
gowri_nm wrote:
>
> Hi,
> Is there any ActiveMQ configuration guide?, If so, can I come to know the
> URL link?
>
> Thanks
>
--
View this message in context:
ht
I think you need to have something similar to the following
Joe
http://www.ttmsolutions.com
yesnid wrote:
>
> Hello All,
>
> Do I need to configure the "discoveryAgent" property of the activemq
> configuration file, if I am using rendezvous, as my discovery medium?
>
> Thank
What about using virtual topics instead of topics? This way, all your
consumers consume from queues.
Joe
http://www.ttmsolutions.com
MatsH wrote:
>
> Hey,
>
> We use both topics and queues alongside selectors, ActiveMQ 5.2, and we
> were intending to go live using a network of brokers and the
If you want to create queues & topics (JMS administered objects) in code and
then later be able to have your clients locate them via jndi lookups, then
one thing you may want to consider is to use a LDAP directory server (e.g.,
Apache DS) as your centralized JNDI server. The two things that greatl
AFAIK, not possible. My guess is that you'd have to develop a http transport
connector for ActiveMQ that also understands the MQ wire or channel
protocol.
Joe
http://www.ttmsolutions.com
jshailes wrote:
>
> I have set up MQ internet pass-thru for one way communication to receive
> messages fr
sign, Mentoring & Agile Consulting
> p. (866) BLiNC-411: (254-6241-1)
> f. (415) 685-4233
>
> Website: http://baselogic.com
> Linked IN: http://linkedin.com/in/mickknutson
> Vacation Rental: http://tahoe.baselogic.com
> ---
>
>
>
> On Tue, Aug 4, 2009 at 3:52 PM
I believe that by default, the corresponding queue names must follow this
syntax
Consumer..VirtualTopic.
You can override the default naming convention via the
element.
You might also want to look into using Camel to implement a similar
messaging pattern (i.e., recipient list).
http://www
So is that one consumer connected to serverA or serverB?
Joe
Bas Verhoeven wrote:
>
> Hello Joe,
>
> Thanks for the reply.
>
>
> Joe Fernandez wrote:
>>
>> Try setting dynamicOnly to 'true'. Doing so should preclude the brokers
>> from
1 - 100 of 233 matches
Mail list logo