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 under the "system" account, and so maybe this is affecting things somehow. Perhaps the system account has different permissions/classpath? to the user account. Would be interesting to associate your user account with the AMQ service and see if that changes the behaviour (using the windows scm) 2) Wonder if the broker process is somehow running under a different priority when running as a service and you have uncovered some kind of rare race condition that only exhibits itself when running under the control of the windows scm. You could run some basic producer/consumer load tests and see if you get different msg/response rates when using the service version vs the standalone version. 3) I think its unlikely but the java service wrapper adds a few jars to the classpath. Wonder could one if its classes be some how conflicting with AMQ classes. Hope some of this helps, /Dave On Wed, Apr 15, 2009 at 5:08 PM, stefan.moser <stefan.mo...@wolverton.ca>wrote: > > 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 app. > > Cheers, > Stefan > > > Dave Stanley wrote: > > > > It seems as though your message store has been corrupted. You will > > probably > > need to wipe the <AMQ>/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) Try and enable syncOnWrite=true for the persistenceAdapter and see if > > that helps > > 3) Can you post some specs on the machine your using for your tests..is > it > > particularly fast? anything unusual about the disk setup? > > 4) How are you stopping your broker. Are you using the windows scm (or > > killing it using the windows task manager ..). > > > > Hope this helps, > > /Dave > > > > > > On Tue, Apr 14, 2009 at 4:19 PM, stefan.moser > > <stefan.mo...@wolverton.ca>wrote: > > > >> > >> In the http://activemq.apache.org/amq-message-store.html documentation > >> for > >> the AMQ Message Store, it mentions that it uses Kaha by default for the > >> reference store. I'm assuming then that there are other options for the > >> reference store, but I can't find any mention of them. I'm new to > >> ActiveMQ, > >> so maybe I'm just not recognizing the lingo. > >> > >> The reason why I would like to look at other reference stores is that > I'm > >> currently experiencing a halting problem with my current AMQ Message > >> Store > >> setup, > >> > >> > http://www.nabble.com/Could-not-locate-data-file-data-topic-data-X-tt22916586.html > >> detailed here . I've tried switching to JDBC persistence using Derby, > >> but > >> it's too slow for my needs. > >> > >> Can someone please help! > >> > >> Cheers, > >> Stefan > >> -- > >> View this message in context: > >> > http://www.nabble.com/Changing-the-reference-store-for-the-AMQ-Message-Store-tp23047210p23047210.html > >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >> > >> > > > > > > -- > View this message in context: > http://www.nabble.com/Changing-the-reference-store-for-the-AMQ-Message-Store-tp23047210p23067175.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
