[jboss-user] [EJB 3.0] - DLQhandler appears to have a bug fixed in other file version

I get an exception: 17:53:14,937 WARN [DLQHandler] Message resent too many times; sending it to DLQ; message id=ID:3-11612186025461 17:53:14,937 ERROR [StdServerSession] session failed to run; setting rollback only java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:396) at org.jboss.ejb3.mdb.DLQHandler.makeWritable(DLQHandler.java:357) at org.jboss.ejb3.mdb.DLQHandler.sendMessage(DLQHandler.java:269) at org.jboss.ejb3.mdb.DLQHandler.handleRedeliveredMessage(DLQHandler.java:228) at org.jboss.ejb3.mdb.MDB$MessageListenerImpl.onMessage(MDB.java:1066) at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:266) at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:902) at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:170) at org.jboss.mq.SpySession.run(SpySession.java:323) at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:194) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748) at java.lang.Thread.run(Thread.java:595) This bug is caused by using Hashtable instead of a HashMap for temp variable in makeWritable in DQLHandler.java. It was fixed already but not in MDB code see: http://lists.jboss.org/pipermail/jboss-jira/2006-July/001285.html View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979232#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...