JBossDeveloper

I am using the same code to start the HornetQ. I create Queue only at the first run and after that I comment it out.

Code to intialiasize HorrnetQ.

          Configuration configuration = new ConfigurationImpl();
          configuration.setPersistenceEnabled(true);
          configuration.setSecurityEnabled(false);
          //configuration.set
          configuration.getAcceptorConfigurations().add(new TransportConfiguration(InVMAcceptorFactory.class.getName()));

          // Step 2. Create and start the server
          HornetQServer server = HornetQServers.newHornetQServer(configuration);
          server.start();

To add on

the Queue is created as a Durable Queue.

          // Step 3. As we are not using a JNDI environment we instantiate the objects directly
          ClientSessionFactory sf = HornetQClient.createClientSessionFactory(new                                                  TransportConfiguration(InVMConnectorFactory.class.getName()));

          // Step 4. Create a core queue
          ClientSession coreSession = sf.createSession(false, false, false);

          coreSession.createQueue(QUEUE_NAME, QUEUE_NAME, true);
          coreSession.close();

As I am testing in a standalone app (with Main method), I have even setup the binding and journal directory.

    configuration.setBindingsDirectory("D:/hq/bindings");
    configuration.setJournalDirectory("D:/hq/journal");

I tried viewing the JMX parameters(MessageCount) for the Queue using JConsole.   I have disabled all my receivers. The scenario I am looking out  is

if I pump some messages (say 100) with my receivers disabled (or no receivers), and crash the server (by doing Ctrl-c) ,  I should be able to see the 100 messages (MessageCount) when I restart the server. This is not happening. Am I missing something ?

I have the testcase files in Zip along with this message.

The participant classes are

MessageSendAndReceive

The entry class which start the HornetQ emebedded server and starts the message pushing (MessagePusher) or Message receiving (MessageReciver) or do both.

MessagePusher

This class starts a executor framework to send messages parallely.

OrigSender.java implements Runnable

This does original job of sending the message by creating the producer.

MessageReceiver.java

This classes created multiple consumers and assings and MessageHandler for each and every consumer

MsgHandler implements MessageHandler

MessageHandler with onMessage method.

Please let me know if you need anything else.

Thanks for all your support

That did the Trick. Thanks !!!!!.  I always assumed durability can be only expressed at the Queue level. I didnt realise this can be expressed at message level also.  I will take care of your adivice on reusing the Session.

You guys are reallty cool !!! and supportive.

Once again, Thanks a lot for ur Support

Hi Andy,

Do we need to call the clientSession.commit() to explicity dequeue or remove the message from the queue? From the same testcase, I am seeing that the queue are only removed only after a commit even though the session is non-transactional session and I am also doing a explicit acknowledge.

Also I want to understand what are the best practises I need to follow if I want to reuse a session.

Tim/Andy

Any Ideas ?

Thats works. But I need a clarification on the acknowledge. Support for some business conditition I want to retain a message in the queue

for ex: if a Message processing leads to a exception I want this message to be retried after some time. I am assuming that if I dont acknowledge a

message it will remain in the queue and we can set a retry time so that the message can be retried by any of the available consumer.

Is my assumption correct ???

I tried implementing this by doing a conditional acknowledge, but the message is dequeued anyway.

BTW, I have implemeted a SessionPool (ClientSession) based on apache commons pool. From the documentation I found that it is better to reuse session even though if it is InVM calls, but I didnt find anything like a SessionPool as ActiveMQ provides.

Without Pooling, how we can acheive Session reuse. I have already went through the section 46.6., it talks about the Anti-Patterns, but doesnt talk about how to do Session reuse  for Core API.

Another quick questions ? I am currently trying transactional sesstions and for this I am trying to set the Max-Delivery-Attempts and DeadQuery using

AddressSettings.

            HornetQServer server = HornetQServers.newHornetQServer(configuration);
          AddressSettings settings = new AddressSettings();
          settings.setDeadLetterAddress(new SimpleString("queue.DLQ"));
          //settings.setExpiryAddress(new SimpleString("jms.queue.DLQ"));
          //settings.setRedeliveryDelay(5000);
          settings.setMaxDeliveryAttempts(3);
          server.getAddressSettingsRepository().setDefault(settings);
          //server.getAddressSettingsRepository().addMatch("queue.TestQueue11",settings);
          server.start();

I am explicity rolling back one transaction and I want to check if the message is pusher to DLQ after three attempts. Seems this is not happening.

PS: I have explicity created the DLQ using the below code.

coreSession.createQueue("queue.DLQ","queue.DLQ",true);

Any thoughts on this ?

I have already peeked the example. My questions was, if I do the AddressSettings through code rather than FileConfiguration will the max retry or DLQ, the functionality is not working as expected. I am seeing the same message with infinite retries. The worst case, no further message is processed as the rollbacked message is in the head of the queue

Feb 11, 2010 6:09:05 PM org.hornetq.core.logging.impl.JULLogDelegate warn
WARNING: Timed out waiting for handler to complete processing

Seems it is getting stuck somewhere is ClientConsumerImpl

Any clues or workarounds ?