semog wrote: > > Like you, we can get messages to go for a while, and then the consumer > just stops getting new messages. The producer can still send messages, > though. It's very odd and frustrating. A couple of guys on my team are > working on tracking it down. >
It is 100% my fault and I take full responsibility, but as a warning for others I will openly admit I made the mistake of integrating AMQ/NMS into our production application and pushing it out the door based on 1) my limited AMQ/NMS proof-of-concept code and 2) my high opinion of Apache projects. Of course, the simple cases of reading and writing messages worked flawlessly, and the performance was superb. Both PostgreSQL and MySQL worked without a hitch, along with all the other various broker configurations I tried. However, the "stuck message" problem has been a thorn in my side for months and as a result of my poor decision to rush integration testing I am now paying the price of babysitting AMQ and our service, restarting as necessary to push things along. All is not lost, as this has been a valuable lesson for me. I am hopeful that the delivery problems will get ironed out eventually and in the meantime I will continue working around issues as necessary. For everyone else out there-- here's a reminder from the pages of "Software Development 101": Before you choose *any* third party solution (open source or otherwise) to integrate with your own code, do yourself a favor and don't skimp on the due diligence phase. Make sure it works on production hardware, with production volumes of data, for a sufficient time period. -- View this message in context: http://www.nabble.com/Nms-Reconnect-tp20582834p20605466.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
