JMS Topic usage based on HornetQ JMS API

[yairogen]

I am trying to work with JMS API without initial context lookups - should this work?

I am creating an array of TransportConfiguration.

creating the connection like this:

HornetQConnectionFactory connectionFactoryWithHA = HornetQJMSClient.createConnectionFactoryWithHA(JMSFactoryType.TOPIC_CF, transportConfigurationsArray);
Connection jmsConnection = connectionFactoryWithHA.createConnection();
Session session = jmsConnection.createSession(false, Session.AUTO_ACKNOWLEDGE);

I create the queue using the management API so I have a destination as viewed in JConsole and a registered consumer (also verified in JConsole).

My topic name is: jms.topic.myFirstTopic.

I create producer like this:

session..createProducer(new HornetQTopic("jms.topic.myFirstTopic"))

now - although judging from JConsole all queue exists and all is well, we fail on:

Caused by: javax.jms.InvalidDestinationException: Destination jms.topic.myFirstTopic does not exist
  at org.hornetq.jms.client.HornetQSession.createProducer(HornetQSession.java:332)

[gaohoward]

HornetQ automatically prefixes "jms.topic" to Topic names. I think you can try:

session..createProducer(new HornetQTopic("myFirstTopic"));

and see if it workds

[yairogen]

Thanks. The producer works but looks like the consumer is not. In Jconsole I see the messages but they are not consumed.

This is the consumer code:

TopicSubscriber durableSubscriber = HornetQJMSMessagingFactory.getSession().createDurableSubscriber(HornetQTopic.createTopic("myFirstTopic"), "consumer1");

durableSubscriber.setMessageListener(myListener);

Looks like my consumer is broken. It prints only the first I sent. messageCounter keeps going up as if the messages are not acknowladged and I can't read any more messages. If I send more I see messages added and messages count go up and the running consumer doesn't get anything.

Any ideas?

[gaohoward]

Not sure what's happened. Can you post a simple test?

[yairogen]

My bad. I mistakenly mixed non JMS hornetq session with JMS session.

works fine now.