activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From madsum <>
Subject What is the use case of BrokerService in ActiveMQ and how to use it correctly
Date Sun, 24 Sep 2017 15:35:52 GMT
I am new about ActiveMQ. I'm trying to study and check how it works by
checking the example code provided by Apache at this link:-

public class Server implements MessageListener {
        private static int ackMode;
        private static String messageQueueName;
        private static String messageBrokerUrl;

        private Session session;
        private boolean transacted = false;
        private MessageProducer replyProducer;
        private MessageProtocol messageProtocol;

        static {
            messageBrokerUrl = "tcp://localhost:61616";
            messageQueueName = "client.messages";
            ackMode = Session.AUTO_ACKNOWLEDGE;

        public Server() {
            try {
                //This message broker is embedded
                BrokerService broker = new BrokerService();
            } catch (Exception e) {
                System.out.println("Exception: "+e.getMessage());
                //Handle the exception appropriately

            //Delegating the handling of messages to another class,
instantiate it before setting up JMS so it
            //is ready to handle messages
            this.messageProtocol = new MessageProtocol();

        private void setupMessageQueueConsumer() {
            ActiveMQConnectionFactory connectionFactory = new
            Connection connection;
            try {
                connection = connectionFactory.createConnection();
                this.session = connection.createSession(this.transacted,
                Destination adminQueue =

                //Setup a message producer to respond to messages from
clients, we will get the destination
                //to send to from the JMSReplyTo header field from a Message
                this.replyProducer = this.session.createProducer(null);

                //Set up a consumer to consume messages off of the admin
                MessageConsumer consumer =
            } catch (JMSException e) {
                System.out.println("Exception: "+e.getMessage());

        public void onMessage(Message message) {
            try {
                TextMessage response = this.session.createTextMessage();
                if (message instanceof TextMessage) {
                    TextMessage txtMsg = (TextMessage) message;
                    String messageText = txtMsg.getText();

                //Set the correlation ID from the received message to be the
correlation id of the response message
                //this lets the client identify which message this is a
response to if it has more than
                //one outstanding message to the server

                //Send the response to the Destination specified by the
JMSReplyTo field of the received message,
                //this is presumably a temporary queue created by the client
                this.replyProducer.send(message.getJMSReplyTo(), response);
            } catch (JMSException e) {
                System.out.println("Exception: "+e.getMessage());

        public static void main(String[] args) {
            new Server();

My confusion about the messageBrokerUrl = "tcp://localhost:61616"; You know
ActiveMQ service is running on port 61616 by default. Why does this example
choose same port? If I try to run the code throws exception as: Exception:
Failed to bind to server socket: tcp://localhost:61616 due to: Address already in use: JVM_Bind

Perhaps if I stop the ActiveMQ service then I can execute the code. Then it

My assumptions are if I embed BrokerService in the code then I don't need
ActiveMQ service running anymore BrokerService represent ActiveMQ service in
the coed. I don't need ActiveMQ service running if I use BrokerService my
code.  Please correct me. 

Please let me know why it is like this in the example and how to work with
BrokerService correctly. Thanks in advnace! 


Sent from:

View raw message