> If I understood right, then each requesting service A (A1...An) should
> maintain its own unique correlation id (permanent during the connection's
> life).
My initial suggestion was actually to have a unique correlation-id for each
request. This provides greater granularity than the above pro
You can use two normal (non-temporary) queues, one for requests and one for
responses. Each request will have a correlation-id header. Let's call the
requesting service A and the responding service B. Service A will send to
/queue/requests. Service B will receive (consume) the request, and
Mats,
Since Rob has noted that this as the correct way, would you consider adding
your plugin to the wiki when it is complete? I think others would find it
useful/interesting, including myself.
JLuna
- Original Message
> From: Rob Davies
> To: users@activemq.apache.org
> Sent: Mo
> Actually, using composite queues
> (http://activemq.apache.org/composite-destinations.html) you can send one
> message and have it automatically forwarded to all 500 destinations.
That wasn't the link I intended to send, refer to this one:
http://activemq.apache.org/virtual-destinations.ht
> thanks for your reply,the message that i want to send to clients is
> different,that is to say
> i want to tell one client a message.if i have only one topic ,every
> client must jude the message weather is sent to himself. do you have
> good idea?
If each client is getting it's own messages
> We have a pool of generic clients that each is listening to it's own
> temporary queue and all write to a common queue. These connections are
> open at creation time. They remain open until they get evicted by the
> pool manager.
>
> We have different applications that use this pool, and the si
We have no problems using activemq with binary data. I don't know the details
of your use case, but HTTP may be a better choice since it provides decent
caching semantics that are already well understood.
JLuna
- Original Message
> From: Carlo Camerino
> To: users@activemq.apach
- Original Message
> From: Bruce Snyder
> To: users@activemq.apache.org
> Sent: Thursday, July 16, 2009 10:54:24 AM
> Subject: Re: Changing the ManagmentContext to point to non-localhost
>
> On Thu, Jul 16, 2009 at 8:21 AM, mkondawrote:
> >
> > Hello All
> >
> > I have changed the m
> I must confess I am a newbie to STOMP Php library and find it really poor in
> terms of documentation. Feels like someone developer on some planet has done
> us all a favor by dumping some code on the google code list and given us a
> free hand on how to scratch our heads and try to get it al
Are you sure you're not setting the same client-id header for both clients? If
you are, I don't believe the second client will be allowed to connect -- you'll
receive an exception from the broker.
On that note, do you know if you're connecting to the broker at all with the
second client? If
I'm not sure I understand correctly, but I think you need Camel. Check out
the aggregator pattern:
http://camel.apache.org/aggregator.html
For more info about using Camel with Activemq:
http://activemq.apache.org/how-should-i-package-applications-using-camel-and-activemq.html
- Original
Nice work. I wasn't aware that ActiveMQBrowser was an option for
monitoring/administrationg activemq. Could someone with wiki access add this
to the list at: http://activemq.apache.org/how-can-i-monitor-activemq.html
JLuna
- Original Message
> From: NAOKI TAKEMURA
> To: users@act
Yes, I've definitely had this scenario working in the past. If I recall
correctly, something that tripped me up is that the messages must be persistent
with a stomp durable subscription. So try using the 'persistent: true' header
when sending the message.
I don't believe this is documented
> using only one queue can block consumers , besides i think that a queue can't
> support 30 million of messages
Again, it's not clear to me what you want to do with these messages after
they're persisted. I don't think you'll be able to get any useful help without
providing more details.
> This is the problem , because i need 30 millions queue and i can't use topics
> instead
>
> Thanks a lot Mr James for you help
>
It's not clear to me what you want to do with them after you persist them, but
you can send them all to a single queue then have a service that consumes from
> Any chance we can get a hold of your test code.
We use stomp, so our tests are very short python scripts using stomp.py:
http://www.briggs.net.nz/log/projects/stomppy/
They are simple scripts that create thousands of queues from a single
connection, send messages to those queues, and also send
> At this point it is clear that it is an operating system issue.
Frederik is correct on this, I tested with CentOS 5. Here is an example of
setting the hard and soft limit:
*softnofile 8192
*hardnofile 65535
After that:
ulimit -n 8192
Hello,
We have the requirement of creating a very large number of queues (tens of
thousands) in a single broker. My searches turned up several others trying to
do something similar, but with no results. We were recently able to accomplish
this, so I decided to write a little howto. All of thi
- Original Message
> From: fehm
> To: users@activemq.apache.org
> Sent: Friday, May 15, 2009 7:25:57 AM
> Subject: Installing DLQ Broker plugin (interceptor) for 5.3.0
>
>
> Hi,
>
> I have some difficulties installing the DLQ broker plugin as stated on the
> plugin installation ho
- Original Message
> From: zmiq2
> To: users@activemq.apache.org
> Sent: Wednesday, May 13, 2009 12:20:11 PM
> Subject: Need help with activemq - php architecture
>
>
> I'm a newbie in activemq, and haven't found much info about setting the
> correct architecture for a high performance
- Original Message
> From: jamesst
> To: users@activemq.apache.org
> Sent: Monday, May 11, 2009 8:34:27 AM
> Subject: Structured Data Accross Languages
>
>
> Does ActiveMQ support sending structured data (Data Objects) across languages
> or is additional 3rd party/ self developed soft
- Original Message
> From: Jose Luna
> To: users@activemq.apache.org
> Sent: Thursday, April 30, 2009 3:04:33 PM
> Subject: Durable subscription with subscription recovery policy
>
>
> Hello,
>
> I haven't received a response after a few days, so I
> Jose Luna-2 wrote:
> >
> > I don't have any recommendation regarding activemq and HTTP but you may
> > consider tunneling openwire through SSL
> > (http://activemq.apache.org/ssl-transport-reference.html).If you set
> > your broker up to use port 443
> I developed simplest application where
> client sends array of Integers as ObjectMessage to Server.
> Server application calculates sum of this values and return the result as
> ObjectMessage back to Client.
> Other words, it is simplest example ever.
>
> When I use tcp protocol (tcp://loc
> ht
Hello,
I haven't received a response after a few days, so I'd like to try again. I'll
try to be brief this time:
Our consumers disconnect/reconnect frequently. We need durable subscriptions
to work with the subscription recovery policy. Currently (Activemq 5.2),
durable subscriptions with t
Hello,
We have a large number (thousands) of durable subscribers that subscribe to a
set of topics. These consumers will be connecting/disconnecting frequently,
and we must ensure that they receive messages sent while they are disconnected
(hence durable subscriptions). These durable subscri
26 matches
Mail list logo
