I am trying to answer few questions based on my experience on JMS. Answer 1:- JMS is Java Message Service API; it provides uniform interface for Java clients to access messaging framework. Beneath JMS API is a JMS compliant messaging provider, for example WebSphere MQ provider. JMS supports transport of a payload over any messaging … Read more
From here: The difference between the PooledConnectionFactory and the CachingConnectionFactory is a difference in implementation. Below are some of the characteristics that differ between them: Although both the PooledConnectionFactory and the CachingConnectionFactory state that they each pool connections, sessions and producers, the PooledConnectionFactory does not actually create a cache of multiple producers. It simply uses … Read more
There is not really an official definition for what a JMS broker is, but there is conceptual difference between a message queue and broker. Here is my take on it. A message queue only looks at the message headers to figure out where to send the message, the message queue does not examine the message … Read more
You already know about method calls. What if the object that you want to invoke the method on is on a different computer? You use RMI to send the call from one computer (client) to the other (server). The client will wait (or “block”) until the result comes back from the server. This is called … Read more
The password you are referring to is most probably different from the one provided by users while login. While the use case is not clear from the question, but it appears you are trying to use the username/password provided by external users to create a connection to JMS Connection Factory. This does not sound architecturally … Read more
Is it OK if some of the messages are duplicated or lost? When the JMS client connects to the JMS broker over the network there are three phases to any API call. The API call, including any message data, is transmitted over the wire to the broker. The API call is executed by the broker. … Read more
Before delving into JMS, consider AMQP as well – might be a new standard. JMS providers I worked with (in varying degrees): TIBCO EMS – very quick and robust, good API support, Java friendly, native C API exists. Best commercial choice I’ve used. Websphere MQ (and its JMS implementation) – so, so. Pub/sub not exactly … Read more
Mule is an ESB (Enterprise Service Bus). RabbitMQ is a message broker. An ESB provides added layers atop of a message broker such as routing, transformations and business process management. It is a mediator between applications, integrating Web Services, REST endpoints, database connections, email and ftp servers – you name it. It is a high-level … Read more
Always use REST. It is the most modern, advanced and scalable integration approach available today. Load balancing a REST based service is achieved simply with hardware or software HTTP load balancer and can be considered just as free as load balancing in JMS. MOM (Message Oriented Middleware) doesn’t scale easily (but may scale big enough … Read more
In ActiveMQ as well as some other projects like Qpid JMS we pull in the JMS spec classes from Apache Geronimo JARs, the 1.1 APIs are available in this dependency: <dependency> <groupId>org.apache.geronimo.specs</groupId> <artifactId>geronimo-jms_1.1_spec</artifactId> <version>1.1.1</version> </dependency> For JMS 2 APIs you’d need to use a different dependency, for instance <dependency> <groupId>org.apache.geronimo.specs</groupId> <artifactId>geronimo-jms_2.0_spec</artifactId> <version>1.0-alpha-2</version> </dependency> These are … Read more