> At a guess (although I cannot be sure without seeing the source), > SwiftMQ is > obtaining 4,000 file descriptors for each of the persistent messages at > start-up, but it is failing to release the descriptors in enough time. That's not true. SwiftMQ doesn't open any file. It only reads the directory content and reconstructs the queues by just the filenames. This directory scanning has been improved for 2.1.1. Now only those queues are scanning the backstore which have persistent messages. Prior to 2.1.1 every queue has scanned the backstore on startup. When the problem is something like 'hammering the disk when a client connects' then this client has probably a message selector. In that case each message must be opened (and closed) to check the message props against the selector. -- Andreas Mueller, IIT GmbH, Bremen/Germany, http://www.iit.de SwiftMQ - JMS Enterprise Messaging System, http://www.swiftmq.com ------------------------------------------------------ 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/
