Hi, do you get it work?
You need comment out the vmcursor in the queue policy and the whole policy for
the queue
looks like this,
I have tested it and it does work but performance penalty becomes arrestive.
At 2013-01-07 22:07:11,"Gary Tully" wrote:
>your important message is in the store, but
It could be a number of things. But first, a couple questions:
1. how does your network look like - 2/3 level switches in the DC, flat or
something else? Where are the producers deployed relative to the broker
clusters? Do you have tcp keep-alive turned on, spl routing, firewalls, etc?
2. any
Hi,
I am facing a strange performance issue with an activemq broker (v. 5.4.0).
The setup is very simple:
- 1 broker instance
- no persistence provider
- about 200 consumers and producers using non-persistent messages. The
message size can be anything up to 1-2MB but is usually smaller.
- dedicat
I've only tried on this one test server but all the data I'm throwing in
ends up empty in the console but fully-formed in a stomp client.
Interestingly if I consume the "bad message" and forward it onward it
remains unreadable in the console. This is occurring across a number of
messages including
Thanks for your reply Dejan.
I just started to explore that solution.
So I appended to the connection URL
this: ?jms.prefetchPolicy.queuePrefetch=0
And now it's delivering the messages.
What I wonder is why this is happening in this environment and not in any
other we've tested. Any clue?
Than
What prefetch limit are you using?
http://activemq.apache.org/what-is-the-prefetch-limit-for.html
Maybe you should use 0 prefetch for your use case
http://activemq.apache.org/i-do-not-receive-messages-in-my-second-consumer.html
Regards
--
Dejan Bosanac
--
Red Hat, Inc.
FuseS
Hi James,
it doesn't sound familiar. Any chance you can reproduce it?
Regards
--
Dejan Bosanac
--
Red Hat, Inc.
FuseSource is now part of Red Hat
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/
On Wed, Jan 9,
Hi Travis,
I think the main change is that now slave broker exposes it's JMX and
shows that it's slave. In older version, the slave MBean server was
not running when broker was slave, so you were connected to the master
instead. I'm not sure there's a workaround for what are you trying to
achieve
As per further investigations, I have some logs to post.
It's odd because the logs says that the message has been delivered but the
consumer sisn't receive any. And in the next checkpoint activemq says that
there is a pagedInMessage, where there shouldn't be any, right?
What is the difference bet
Hi!
I've solved the problem.
My CLASSPATH variable was wrong and it was introducing something "recursive"
that was causing the problem I've reported.
i.e.: CLASSPATH=%CLASSPATH%;c:\Program Files\foo\bar
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Unable-to-expand-env
10 matches
Mail list logo