Latest posts for the topic "Replacing JMS queue"

Replacing JMS queue

hervbarr — GMT

Hi, I would replace a JMS queue by a Terracotta/Ehcache similar queue mechanism. I have seen a post about a way to replace topics (using ehcache + Quartz) : http://forums.terracotta.org/forums/posts/list/6551.page And another one which tells to use TIM-messaging : http://forums.terracotta.org/forums/posts/list/2359.page I need the following functionalities : Multiple Producers [same or different JVM]. Multiple Concurrent Consumers [same or different JVM]. No message Loss (even if a consumer crash), [in JMS, it relies on the principle of client acknowledgment]. The primary idea was to use the terracotta queues but there is no simple way to have multiple consumers and no message loss. What is the best way (and the terracotta tools) to achieve this mechanism ? Regards Hervé

Re:Replacing JMS queue

klalithr — GMT

Have you considered toolkit queues? http://terracotta.org/documentation/terracotta-toolkit/toolkit-usage#queues While the queue footprint itself will reside in Terracotta, you can have multiple consumers and producers. The queue itself is clustered and durable and backed by the TSA. For performance a queue is best performant when its point to point - one consumer and one producer. Lastly, newer versions of Terracotta will provide additional enhancements to the Toolkit. Stay tuned.

Re:Replacing JMS queue

hervbarr — GMT

Hi, I have used toolkit queues. I noticed that performance are effectively better in point to point. Thanks for information. Regards Hervé

Re:Replacing JMS queue

hervbarr — GMT

klalithr wrote:

Lastly, newer versions of Terracotta will provide additional enhancements to the Toolkit. Stay tuned.

Hi, I have seen a new (maintenance ?) release for terracotta (3.6.2) Is there some news about enhancements to the Toolkit ?