This content has been marked as final. Show 3 replies
You mention both ActiveMQ and Open MQ, but don't say which provider your performance query relates to, or how the two compare.
Can you give some more information about why you need to use the queue browser and how are you using it?
Would you be able to achieve the behaviour you require by consuming the message with client acknowledgement or in a local transaction?
We tested with both providers "Activemq"/"OPENMQ", performace is more or less the same,
the reason for using queuebrowser is Message should not be delete until application receives an Acknowledgement from client ( Note : this is not same as JMS Acknowledge Mode).
We may atleast hit closer to our performace target, if we Consume the message, but the issue with Consumer is it does not garentee message delivary,
If you're relying on the queue browser in normal message processing, please note the caveats about the queue browser in the JMS spec.
You say that you don't want to "delete" a message until the application receives a notification from the client that it should do so. That is what client-acknowledgement or local transactions were provided for. Obviously I don't enough about your application to understand why you can't use them, but you would probably get better performance if you could.