I have been testing JBoss Messaging, and ran into an interesting exception on the server. Our testing of TextMessage worked great. We then went to test BytesMessage, and received the below exception. This exception occurs when a Consumer attempts to get a message from the queue. Placing messages into the queue did not generate an exception. These ByteMessages are 7MB in size.

15:39:03,467 ERROR [SocketManager] Failed to handle: org.jboss.mq.il.uil2.msgs.R
eceiveMsg26485067[msgType: m_receive, msgID: 7, error: null]
java.lang.NullPointerException
at org.jboss.mq.pm.jdbc3.PersistenceManager.loadFromStorage(PersistenceM
anager.java:850)
at org.jboss.mq.server.MessageCache.loadFromStorage(MessageCache.java:41
1)
at org.jboss.mq.server.MessageReference.makeHard(MessageReference.java:3
51)
at org.jboss.mq.server.MessageReference.getMessage(MessageReference.java
:156)
at org.jboss.mq.server.BasicQueue.setupMessageAcknowledgement(BasicQueue
.java:881)
at org.jboss.mq.server.BasicQueue.receive(BasicQueue.java:488)
at org.jboss.mq.server.JMSQueue.receive(JMSQueue.java:136)
at org.jboss.mq.server.ClientConsumer.receive(ClientConsumer.java:222)
at org.jboss.mq.server.JMSDestinationManager.receive(JMSDestinationManag
er.java:673)
at org.jboss.mq.server.JMSServerInterceptorSupport.receive(JMSServerInte
rceptorSupport.java:226)
at org.jboss.mq.security.ServerSecurityInterceptor.receive(ServerSecurit
yInterceptor.java:100)
at org.jboss.mq.server.TracingInterceptor.receive(TracingInterceptor.jav
a:570)
at org.jboss.mq.server.JMSServerInvoker.receive(JMSServerInvoker.java:22
6)
at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocke
tManagerHandler.java:149)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.j
ava:362)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:377)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExec
utor.java:748)
at java.lang.Thread.run(Thread.java:534)