I have now managed to discover that this is behaviour is cased by a bug in JBoss 4.2.3 (https://jira.jboss.org/jira/browse/JBAS-5801) and that a workaround is available. More details can be found in http://community.jboss.org/thread/49345.pdf
Reply to this message by going to Community
Start a new discussion in JBoss Messaging at Community