There is one thing I suggest you do after delaying. Create a test class that sends messages every 2 hours and make sure you are not getting this error message:
org.jboss.mq.SpyJMSException: Exiting on IOE; - nested throwable: (java.io.EOFException) | at org.jboss.mq.Connection.asynchFailure(Connection.java:436) | at org.jboss.mq.il.uil2.UILClientILService.asynchFailure(UILClientILService.java:145) | at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleStop(SocketManager.java:406) | at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:338) | at java.lang.Thread.run(Thread.java:534) | Caused by: java.io.EOFException | at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2603) | at java.io.ObjectInputStream.readByte(ObjectInputStream.java:845) | at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:285) | ... 1 more Jboss has awkward reactions to delayed messages. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3905694#3905694 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3905694 ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user