Ok, that was kind of what I was expecting looking at the stacktrace. This means that the bug is either in the ActiveMQ version or the HSQLDB version. It is not going to be fixable from an OpenEJB perspective other than playing with the distributed versions.
It would still be good if you could post a JIRA here https://issues.apache.org/jira/browse/OPENEJB and also here https://issues.apache.org/jira/browse/AMQ I know it is sometimes a hassle to register just to post an issue, so if you like I can create them for you - Just let me know here. Just for your info, I have a feeling for what the issue may be. Have a look at the source here http://www.docjar.org/html/api/org/activemq/store/jdbc/adapter/BytesJDBCAdapter.java.html and you can see that it is calling rs.getBytes(index) - This is failing, but accessing the data via getBlob seems to work. -- View this message in context: http://openejb.979440.n4.nabble.com/Default-JMS-Persistence-fails-on-restart-if-messages-are-left-in-a-queue-tp4655619p4655659.html Sent from the OpenEJB User mailing list archive at Nabble.com.
