When our router is started with > 4K existing persistent messages it appears to 'hang' when the first client attempts a receive. When this happens the router appears busy thrashing the hard-disk and continues to do until we kill it If we halt the router, delete messages to reduce the message count below 4K and restart then everything works normally again. (even when the message count grows above 4K). The only time we seem to get this problem is when we start the router with an existing store > 4K messages. We've been able to replicate this problem with v2.0.0 and v2.1.1 in two different environments (both NT). We've tried; - Ensuring that flow control is disabled for the queue and to be extra paranoid we've increased the flow control start size to 100K messages. - Setting the min consumer threads to 10 and the max consumer threads to -1 - Making sure the router has more than enough disk space and that memory isn't an issue. - Setting the default (and queue specific) cleanup interval to 1 hour - Checking the router logs but found no indication of a problem. Anything else we should have tried ? Any help appreciated. Carlos. ------------------------------------------------------ SwiftMQ developers mailing list * http://www.swiftmq.com To unsubscribe from this list, send an eMail to [EMAIL PROTECTED] and write in the body of your message: UNSUBSCRIBE developers <your-email-address> Archive: http://www.mail-archive.com/developers@mail.iit.de/
