Hi there,



We have a message routing application currently in production whose goal is to get messages, process them and route them to their final destination. Each message received is finally stored in the Archive queue if it has been fully processed and delivered or in the Trash queue otherwise.



This application is currently running on a single server with one instance of SwiftMQ router. An upgrade will be done soon so that the application runs on two faster servers with SwiftMQ HA to provide High Availability.



The only problem we are facing now is about browsing the Archive queue (which may contains thousands of messages) with a selector to find and select message to be "replayed"(resent into the process queue). On our current server (using File Store), browsing into 6000 messages takes around 30 seconds which is not acceptable since there is a user waiting behind the GUI.



I see 3 solutions to solve the problem :

1) take the Archive messages out of SwiftMQ and store them into a dedicated database (MySQL); search would then be executed in this database but we need to develop some code to recreate message into SwiftMQ from the database.

2) same as 1 but with placing only a copy of each message into the database so that we do not need the code that recreate the message inside SwiftMQ.

3) using another instance of SwiftMQ + JDBC Store swiftlet to host the Archive Queue.



Solution 3 seems the most straight-forward if and only if browsing a queue using JDBC Store is really faster than doing it using the File Store.



My question (as you already got it) is : have you some numbers about peformance of the JDBC Store vs File Store as far as browsing is concerned ? Have you another solution to adress my pb ? (any idea is welcome).



Thanks