Hi Stefan,
Thanks for the config, I will run some tests on my machine with yoru
settings (maybe I will get lucky). Let us know how you get on with your
tests on the other machine. Would be interested to know if a third party
product could be interfering with the message store files - I have not hea
Hi Dave,
Unfortunately I haven't been able to reproduce this with a unit test. You
were likely correct when you said that it's a race condition causing the
problem. I'm currently in the process of setting up the broker on another
machine that has less running on it. There is a chance that it's
Hi Stefan,
Is it possible to reproduce with a Junit. It would be great to get a
testcase & jira logged for this one. Can you post a summary of your broker
config (activemq.xml) and the amount of load your putting on the broker?
Cheer's,
/Dave
On Fri, Apr 17, 2009 at 1:04 PM, stefan.moser wrote:
Bad news. After running fine as a standalone broker for two days, it died
again today with the same error. I've tried the syncOnWrite=true setting,
but it slows down the broker too much for what is acceptable in my system.
I think I'm pretty much out of options.
Stefan
Dave Stanley wrote:
>
Hi Stefan,
Thanks for the update, and I'm glad to hear things are running well so far
in standalone mode.
I don't have any good answers on why the win32 java service wrapper exhibits
different behaviour.
Some things that might be different are:
1) The java service wrapper will by default run und
Hi Dave,
I've been running the broker standalone, without the service wrapper, and so
far it's working great. Can I ask why you suggested this? Why would it
have an effect on the internals of how ActiveMQ runs? It makes it quite
impractical if I can't use the service wrapper once I deploy my a
Thanks for your reply Dave.
I'll try your first two suggestions and see how it goes. I've been getting
the error about once a day, so I should see results soon.
Right now I'm just running ActiveMQ on my dev machine. Quad core 2.40GHz,
4GB RAM running XP SP3, standard disk, plenty of space, not
It seems as though your message store has been corrupted. You will probably
need to wipe the /data directory to start from a clean
In order to try and narrow down why this might be occurring:
1) Try test without the java service wrapper (standalone broker) and see if
it makes any difference
2) Tr
