There is a broker attribute, org.apache.activemq.broker.BrokerService#cacheTempDestinations that should help in the failover: case. Set that to true in xml configuration, and a temp destination will not be removed immediately when a client disconnects. A fast failover: reconnect will be able to producer and/or consume from the temp queue again. There is a timer task based … Read more
As noted in the question, the JBoss 4.2.1 server has been upgraded to 7.1.1 Final. Upgrading has resolved the issue and the client now works as expected, but unfortunately this solution does not explain the problem.
Apache ActiveMQ is a great workhorse full of features and nice stuff. It’s not the fastest MQ software around but fast enough for most use cases. Among features are flexible clustring, fail-over, integrations with different application servers, security etc. Apache Apollo is an attempt to write a new core for ActiveMQ to cope with a … Read more
JMS and messaging is really about 2 totally different things. publish and subscribe (sending a message to as many consumers as are interested – a bit like sending an email to a mailing list, the sender does not need to know who is subscribed high performance reliable load balancing (message queues) See more info on … Read more
JMS and Scala actors share a theoretical similarity but don’t think of them as necessarily solving the same problems architecturally. Actors are meant to be a lightweight alternative to shared-memory concurrency where races and deadlocks are generally harder to accidentally create. JMS is a sophisticated API that’s meant to span direct messaging, publish/subscribe, transactions, EJB … Read more
First off the “older” message systems (MQ) are older in implementation but they are a newer in engineering idea of: transactional persistent queues. Scala Actors and Akka maybe a newer implementation but are built on an older concurrency model of Actors. The two models however end up being very similar in practice because they both … Read more
Your question is a bit messy but Let’s see its bits one by one. General concept: The Java Message Service (JMS) API is a Java Message Oriented Middleware (MOM) API for sending messages between two or more clients. JMS is a part of the Java Platform, Enterprise Edition, and is defined by a specification developed … Read more
We choose Camel over Spring-Integration because the fluent API is really nice. We actually use it in Spring projects and use Spring to configure part of it. The programming API’s are clear and there is a large set of sensible components. We did a small scale shootout and basically at that time for our requirement … Read more
JMS (ActiveMQ is a JMS broker implementation) can be used as a mechanism to allow asynchronous request processing. You may wish to do this because the request take a long time to complete or because several parties may be interested in the actual request. Another reason for using it is to allow multiple clients (potentially … Read more
That means a topic is appropriate. A queue means a message goes to one and only one possible subscriber. A topic goes to each and every subscriber.