Question

in JSP when i reach “QueueingConsumer.Delivery delivery = consumer.nextDelivery()” the page gets stuck loading. the message is consumed but the jsp won’t load nor does it give errors. please help

String QUEUE_NAME = "hello";

ConnectionFactory factory = new ConnectionFactory();
factory.setHost("localhost");
Connection connection = factory.newConnection();
Channel channel = connection.createChannel();

channel.queueDeclare(QUEUE_NAME, false, false, false, null);
out.println(" [*] Waiting for messages. To exit press CTRL+C");

QueueingConsumer consumer = new QueueingConsumer(channel);
channel.basicConsume(QUEUE_NAME, true, consumer);

while (true) {
  QueueingConsumer.Delivery delivery = consumer.nextDelivery();
  String message = new String(delivery.getBody());
  out.println(" [x] Received '" + message + "'");
}

Answer 1

I am guessing that you are trying to implement the RabbitMQ “Hello World” tutorial in a JSP page.
You can’t do this as:

• QueueingConsumer.nextDelivery will block until a message is available on the queue
• To show all messages as they arrive at the head of the queue you need an infinite loop (as shown in the tutorial) which won’t work in a JSP page.

Your JSP page is part of the request lifecycle, which needs to end as soon as possible and return the requested resource (in this case the HTML etc in your JSP page) to the user’s browser. Although most browsers will start displaying results as they receive them they won’t deal with a long hiatus or a never-ending response. Even if they could you don’t want this as there will be a limit to the number of concurrent requests your server can handle.

If you are playing around with RabbitMQ to see how it works then I would recommend you develop a Java application (as per the tutorial), i.e. don’t try to do it in a webapp. (Also, as pointed out by fvu, note that QueueingConsumer is now deprecated).

If you need to do it in a webapp then you’ll need to think of a way to store messages (e.g. in a database or a singleton data structure if you have a single instance of e.g. Tomcat) as they are taken off the message queue (probably by a background thread, i.e. not one that services requests). Your JSP page can then read the messages from your data structure to display to the user.