Thanks a lots for those pointers Clebert. I will take a look on those and come back

Tim, Thanks for your reply. I am looking for a PTP model where I want only one message consumer. I want pool of MDB/Listeners/MessageHandlers to listen on the queue and process message parallely. AFAIK multiple consumers denote a publish-subscribe model which I dont want.

My usecase is simple, I want to do some tasks in async way, where the message is produced and consumed in the same vm (Jboss 4.2.3/JDK 6) and I want to leverage Embeded HQ mode with core(InVM) rather than JMS. I am stuck with the parallel processing of message in the queue. AFAIK the EJB container calls the onMessage on reception of message in case of MDB and also provides pooling. I am trying to see if Core has similar option, but going through the API and examples, I am not able to locate anything concrete.

Thanks again for your reply and sorry for my ignorance in JMS

Tim,

Do you have any pointers or examples that captures multiple consumers with core. I tried one in a simple standalone application by trying multiple consumers in the loop. Its working as expected. But I am wondering, How do close the session as I want idefinetly wait for the new messages. If I am not closing the session I am getting warning for not closing the session

    for (int i = 0; i < numConsumers; i++)
        {
        ClientSession session = sf.createSession();
        ClientConsumer messageConsumer = session.createConsumer(queueName);
        messageConsumer.setMessageHandler(new MsgHandler());
        session.start();
        }

Closing the session would terminate the session and this means the consumer will not available for sconsuming new messages. What I want to is to intialiase the consumer and wait for the new messages indefinetly.  But when I keep the session open I am getting the warning and that the consumer is garbage collected

Below is my code snippet

        //Start the receiver. This will intialise 6 consumers with it own message handler.

        MessageReceiver receiver = new MessageReceiver();
        receiver.receiveMessage();

       //Start pushing 130 messages parallely

        MessagePusher pusher = new MessagePusher();
        pusher.sendMessage(0);

        //A time delay

        Thread.sleep(1000);

       //Pump another 130 messages

        pusher.sendMessage(130);

what is happenings is all the consumers are garbage collected as the session is closed and garbage collected with the below message.

WARNING: I'm closing a core ClientSession you left open. Please make sure you close all ClientSessions explicitly before letting them go out of scope! 2830910
Feb 9, 2010 2:05:49 AM org.hornetq.core.logging.impl.JULLogDelegate warn
WARNING: The ClientSession you didn't close was created here:
java.lang.Exception
    at org.hornetq.core.client.impl.DelegatingSession.<init>(DelegatingSession.java:92)

What I want is to have this consumers available indefinetly for the new messages.

Sorry If I am not clear with my question.

I am using core's MessageHandler. I am not clear with "adding a reference to the session from your MessageListener".

Sorry for my ignorance.

Thanks !!!. That worked. One final question. Does persistence works out of the box? I am setting the persistence to true

         Configuration configuration = new ConfigurationImpl();
          configuration.setPersistenceEnabled(true);
          configuration.setSecurityEnabled(false);

I am trying to first push the messages to queues (I have commented the receiver part). After this I terminate my JVM and restart with commenting the message pusher part and enabling the message receiver.  What I am expecting is, all the message that went in the first try should be processed by the receiver. But this is not happening in the currently. Do I need to tweak some configuration ?

Thanks for all your wonderful support.