Over the last few weeks I've been struggling with intermittent
behavior in activemq trunk. Some of this is in the build running the
junit tests: I've been opening jiras as these occur:
AMQ-2031 Intermittent test failure - InactivityMonitorTest
AMQ-2050 Intermittent test failure -- ProxyConnectorTest
AMQ-2072 Intermittent test failure - TopicMasterSlaveTest
AMQ-2073 Intermittent test failure - QueueConsumerPriorityTest
AMQ-2074 Intermittent test failure - QuickJPAStoreRecoveryBrokerTest
AMQ-2075 Intermittent test failure - BrokerTest
AMQ-2076 Intermittent test failure - DataFileNotDeletedTest
AMQ-2077 Intemittent test failure - JmsDurableTopicSlowReceiveTest
AMQ-2078 Intermittent test failure -- like
JmsTransactionTestSupport.testReceiveRollback
Even more frustrating is intermittent problems running the tck. So
far my attempts to reproduce the problems seen in the tck in a form
that can be made public have failed completely. However the behavior
being tested is generally really simple stuff that should always
work. One problem, which occurs when removing a queue, can leave the
broker totally inoperable.
I've pretty much reached the limit of my time and patience for
investigating these problems directly myself. I think it would be
great if someone who understands more of AMQ internals could take a
look, especially at the tck related problems. I'd be happy to help
AMQ commtters get access to the tck, or to try out potiential fixes.
FWIW I'm working on mac osx 10.5.6
thanks
david jencks
