Hi Jacob,
the problem occurred due to some maintenance on our Nexus. Everything should
be back to normal now.
Regards
--
Dejan Bosanac
-
FuseSource - The experts in open source integration and messaging.
Email: dej...@fusesource.com
Web: http://fusesource.com
Twitter: http://twi
you are using a durable subscriber but with non persistent messages.
Because a non persistent message is not in the brokers messages store,
it needs to be locally persisted by the durable subscription cursor,
so it uses the filebased message cursor and replays the messages to
that.
I think what you
Yes, the schedule message should persist.
take a look at the respective test in
https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/broker/scheduler/JmsSchedulerTest.java?hb=true
and https://issues.apache.org/jira/browse/AMQ-2897
Try creating a s
Hi,
I'm facing issue with ActiveMQ 5.1.0 performance. I have a Topic (non
durable, non persistence) with 3 async listeners. Each listener has a
threadpool attached to it, so that messages can be processed by multiple
threads. Listener receives message in onMessage and delgate it to a thread.
My
seems that the xml content does not display correctly.
briefly,the setting is like this,
pendingSubscriberPolicy = vmCursor
memoryUsage limit=10 kb
--
View this message in context:
http://activemq.2283324.n4.nabble.com/what-s-the-relation-between-memoryUsage-and-PendingQueueSize-tp3342989p334300
I did an experiment below(one producer and one consumer):
producer:constantly send text message whose size is 1k
consumer:block it when it receive a message,so that the subsequent message
cannot deliver to it (debugging)
in no time,the activeMQ console log displayed the message below,as is
expecte
