JBOSS MDB MessageID coming as Null

[vijay sachin]

Hi,

Please help me with this ERROR message

 12:44:29,639 ERROR [AbstractDLQHandler] Message id is null? delegator->JBossMessage[21282220761317377]:PERSISTENT, deliveryId=1
12:44:29,842 INFO  [STDOUT] TrainMDB: Got request from Queue - delegator->JBossMessage[21282220761317377]:PERSISTENT, deliveryId=1
12:44:29,842 INFO  [STDOUT] MessageID--------null
12:44:30,405 INFO  [STDOUT] TrainMDB: MESSAGE Text- Hello World---------------------------------
12:44:30,405 ERROR [AbstractDLQHandler] Message id is null? delegator->JBossMessage[21282220761317377]:PERSISTENT, deliveryId=1

I am using EJB3 and Application Server JBOSS 5.1.0.GA
onMessage() Method in MDB, while receiving message from queue the MessageID is coming as null.

Please help me with this Error Mesage.

[Peter Johnson]

Some code would help...

[vijay sachin]

SENDER CODE

public class CallJMS
{

    public static void main(String a[]) throws Exception {
        
        Context jndiContext = null;
        try {
        	Properties props = new Properties();
    		props.setProperty("java.naming.factory.initial","org.jnp.interfaces.NamingContextFactory");
    		props.setProperty("java.naming.factory.url.pkgs", "org.jboss.naming");
    		props.setProperty("java.naming.provider.url", "127.0.0.1:1099");
    		jndiContext = new InitialContext(props);
        } catch (NamingException e) {
          System.out.println("Could not create JNDI API " +
            "context: " + e.toString());
          System.exit(1);
        }
		
        ConnectionFactory connectionFactory = (ConnectionFactory) jndiContext.lookup("ConnectionFactory");
        Destination dest = (Destination) jndiContext.lookup("MyQueue");
        
        Connection connection = null;
        MessageProducer producer = null;


        connection = connectionFactory.createConnection();
        
        Session session =connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
        producer = session.createProducer(dest);
        System.out.println("Sending Message to the Queue---------");
        TextMessage message = session.createTextMessage();
        try {
        message.setText("################################################################");
      	producer.send(message);
         producer.close();
         Thread.sleep(1000);
        } catch (Exception e) {
            System.out.println("Could not Send Message context: " + e.toString());
               }
        System.out.println(" Message Send with MessageID---------"+message.getJMSMessageID());        
    }
}

RECEIVER CODE MDB

@MessageDriven(mappedName="MyQueue", activationConfig = {
	    @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),
	    @ActivationConfigProperty(propertyName="destination", propertyValue="MyQueue"),
	})
public class TestMDB implements MessageListener {

   public TestMDB() {
        // TODO Auto-generated constructor stub    	
    }
	

    public void onMessage(Message message) {    	
        System.out.println("TrainMDB: Got request from Queue - " + message);        
        try {
                System.out.println("MessageID--------"+message.getJMSMessageID());
                TextMessage txtMsg = (TextMessage) message;
        
        	System.out.println("MessageID:   "+txtMsg.getJMSMessageID());        	
               System.out.println("TrainMDB: MESSAGE Text- " + txtMsg.getText());
        	}
        	}
        } catch (Exception aEx) {
            aEx.printStackTrace();
        }
        
    }

}

Receiver side MessageID is coming as NULL. But Text is receving correctly
Please help me in this issue

[Peter Johnson]

I tried this with one of my MDBs and I got a valid messageID. But that was with using HSQLDB. I tried to rerun with MySQL but ran into hard drive issues. I'll try MySQL later and see if I still get a messageID.

[vijay sachin]

I did not understand why DB came into picture in MDB.

As per my knowledge I am thing MDB is used to listen to queue which we configured in xml file.
and when sender sends message to JbossMQ then MDB onMessage() will listen to that and performs some logic.
This is want I understand Is it correct?

[Peter Johnson]

The messaging system uses a database. In some cases the messages are actually stored in the database. For example is there is no listener running then the messages might be persisted to a database. By default, JBoss Messaging uses the embedded HSQLDB. HSQLDB runs entirely in memory, so I wanted to see if there was a difference between using messaging for that and messaging with a real database. I am thinking that perhaps the messageId is assigned only when the it is stored in the database. I know this is grasping at straws but it is the only thing I can think of.

But then your reply tells me that you might not have configured messaging to use a different database, in which case I don't know why I am getting messageIds but you are not.