activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gwittel <gwit...@proofpoint.com>
Subject EOF Exception When Serializing Large Message
Date Mon, 07 Jan 2008 17:53:27 GMT

Hi

We're using a Perl/Stomp client to retrieve messages out of a standard
queue.  When a large message was encountered (~20MB of XML), the client
stopped processing data.  After more debugging, it looks like the server
throws an exception when a client hits this message or opens a queue with
this message at the front of the queue:

2008-01-03 09:23:05,769 [serverip:42663] DEBUG Transport                     
- Transport failed: java.io.EOFException
java.io.EOFException
        at java.io.DataInputStream.readByte(Unknown Source)
        at
org.apache.activemq.transport.stomp.StompWireFormat.readLine(StompWireFormat.java:186)
        at
org.apache.activemq.transport.stomp.StompWireFormat.unmarshal(StompWireFormat.java:94)
        at
org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:190)
        at
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:182)
        at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:170)
        at java.lang.Thread.run(Unknown Source)
2008-01-03 09:23:05,769 [serverip:42663] DEBUG TransportConnection           
- Stopping connection: /serverip:42663
2008-01-03 09:23:05,770 [serverip:42663] DEBUG TcpTransport                  
- Stopping transport tcp:///serverip:42663
2008-01-03 09:23:05,770 [serverip:42663] DEBUG TransportConnection           
- Stopped connection: /serverip:42663
2008-01-03 09:23:05,770 [serverip:42663] DEBUG TransportConnection           
- Cleaning up connection resources: /serverip:42663
2008-01-03 09:23:05,770 [serverip:42663] DEBUG TransportConnection           
- Connection Stopped: /serverip:42663

We're using AMQ 5.0-RC3 with the AMQ persistent store.  Since this error was
encountered on a production system I have not yet been able to upgrade the
host to the 5.0-Release.  Any thoughts on how we can debug the issue, if its
a server memory issue (JVM is allowed 1GB at this time), or some other
problem.  I was able to view the message via the HTTP admin GUI without an
exception being thrown.

Thanks,
-Greg
-- 
View this message in context: http://www.nabble.com/EOF-Exception-When-Serializing-Large-Message-tp14671931s2354p14671931.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message