Christian already gave you a few solutions.
RecoveryPolicy is probably close to what you want,
if you are prepared to write a little bit of code you
can solve the problem quite nicely with temp queues and
a subscription system.
Durable subscribers are just a headache.
Apollo and stomp won't do mo
Apollo targets JMS 1.1 also.
In ActiveMQ, take a look at virtual topics:
http://activemq.apache.org/virtual-destinations.html
Might also consider MQTT which is purely pub sub and doesn't adhere to JMS
restrictions.
Could also cobble up a solution w/ queues + topics using Camel...
On Fri, Sep 6
This question is a result of me realizing that there are somewhat conflicting
requirements that I need to implement using ActiveMQ 5.8.0 and I am not sure
if it's at all possible to get these requirements satisfied.
SCENARIO:
A backend server needs to send a message to a user accessing a web
appli
Not directly within the composite filter.
Camel would be perfect for this :)
On Fri, Sep 6, 2013 at 7:30 AM, gmicky wrote:
> Hi,
> I have following configuration using amq 5.8 :
>
>
>
>
>
>
>
>
> Filtering of the messages w
Hi,
I have following configuration using amq 5.8 :
Filtering of the messages works great, but is it possible to redirect
messages that do not match filters to either DLQ queue or some custom queue?
I do not want to lose messa
hi,
I'm beginning to use activemq-cpp-library-3.7.1,
Using simple_producer to produce 2,000,000 messages, the memory usage of the
producer process is constant.
But when starting simple_async_consumer, the memory usage of this process
gets bigger and bigger.
Enviroment:
ActiveMQ 5.8.0, java 1.7
On Thu, Sep 5, 2013 at 9:59 PM, gsk wrote:
> thanks for taking time to reply.
>
> 1. How can i set up camel as a consumer? Do you have any documents that
> will
> explain how to do this?
>
Yes. Tons.
http://camel.apache.org/jms.html
http://camel.apache.org/getting-started.html
http://camel.apache
"If you need queuing semantics check out virtual destinations or durable
subscribers. You could also take a look at subscription recovery policy on
the broker side."
On Fri, Sep 6, 2013 at 12:06 AM, AlexP wrote:
> Thanks for your reply.
>
> We need to deliver messages to web clients doing long p
johnbing==Anuj? same person posting all these under diff alias? funny
shit
so like i said, post your stack trace.. and also your config (broker + JVM
args + client settings, etc), and we can help out more. NIO doesn't "reduce
threads" magically in the overall broker... it reduces the number ne
Yes I have also tested it with 20 producers consumers. But still not seeing
any reduction in the number of threads. I have tested NIO with STOMP as well
as JMS producers.
USING(Language) No. of threads before running producer No. of
threads after running producers(~20)
STOMP (PYTHON pro
Thanks for your reply.
We need to deliver messages to web clients doing long poll. A web client
may not be there when message is generated, but we need the message to stay
in topic until at least one client sees it. We are using topics as a user
may open multiple browsers and we want notificatio
11 matches
Mail list logo
