Here is a collection of most of the interview questions in JMS.
How is a java object message delivered to a non-java Client?
It is according to the specification that the message sent should be received in the same format. A non-java client cannot receive a message in the form of java
object. The provider in between handles the conversion of the data type and the message is transferred to the other end.
MDB is Message driven bean, which very much resembles the Stateless session bean. The incoming and out going messages can be handled by the Message driven bean. The
ability to communicate asynchronously is the special feature about the Message driven bean.
There are two kinds of Messaging.
Synchronous Messaging: Synchronous messaging involves a client that waits for the server to respond to a message.
Asynchronous Messaging: Asynchronous messaging involves a client that does not wait for a message from the server. An event is used to trigger a message from a server.
Each JMS-enabled client must establish the following:
A connection object provided by the JMS server (the message broker)
Within a connection, one or more sessions, which provide a context for message sending and receiving
Within a session, either a queue or topic object representing the destination (the message staging area) within the message broker
Within a session, the appropriate sender or publisher or receiver or subscriber object (depending on whether the client is a message producer or consumer and uses a
point-to-point or publish/subscribe strategy, respectively)
Within a session, a message object (to send or to receive)