can not send a 300Kb text message in 3.0.0.GA

[d.gouraud]

Hi,

We were using till recently HornetQ 3.0.0.CR3 where we are able to send a 300Kb text message between the endpoints. We have moved to the 3.0.0.GA version but we have the following errors :

Error in the client application :
javax.jms.JMSException
    at org.hornetq.core.remoting.impl.ChannelImpl.sendBlocking(ChannelImpl.java:280)
    at org.hornetq.core.client.impl.ClientProducerImpl.doSend(ClientProducerImpl.java:269)
    at org.hornetq.core.client.impl.ClientProducerImpl.send(ClientProducerImpl.java:139)
    at org.hornetq.jms.client.HornetQMessageProducer.doSend(HornetQMessageProducer.java:455)
    at org.hornetq.jms.client.HornetQMessageProducer.send(HornetQMessageProducer.java:208)
    at com.rifan.glpi.diff.exporter.technical.QueueTransferFileSender.sendGlpiDiffTransferFile(QueueTransferFileSender.java:129)
    at com.rifan.glpi.diff.exporter.manager.ExporterManager.export(ExporterManager.java:183)
    at com.rifan.glpi.diff.exporter.GlpiDiffExport.main(GlpiDiffExport.java:79)
Caused by: HornetQException[errorCode=0 message=null]

Error in the Jboss server :

java.lang.IllegalStateException: Can't write records bigger than the bufferSize(501760) on the journal
    at org.hornetq.core.journal.impl.TimedBuffer.checkSize(TimedBuffer.java:208)
    at org.hornetq.core.journal.impl.AbstractSequentialFile.fits(AbstractSequentialFile.java:162)
    at org.hornetq.core.journal.impl.JournalImpl.appendRecord(JournalImpl.java:2812)
    at org.hornetq.core.journal.impl.JournalImpl.appendAddRecord(JournalImpl.java:755)
    at org.hornetq.core.persistence.impl.journal.JournalStorageManager.storeMessage(JournalStorageManager.java:489)
    at org.hornetq.core.postoffice.impl.PostOfficeImpl.processRoute(PostOfficeImpl.java:904)
    at org.hornetq.core.postoffice.impl.PostOfficeImpl.route(PostOfficeImpl.java:665)
    at org.hornetq.core.server.impl.ServerSessionImpl.send(ServerSessionImpl.java:1995)
    at org.hornetq.core.server.impl.ServerSessionImpl.handleSend(ServerSessionImpl.java:1426)
    at org.hornetq.core.server.impl.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:275)
    at org.hornetq.core.remoting.impl.ChannelImpl.handlePacket(ChannelImpl.java:466)
    at org.hornetq.core.remoting.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:423)
    at org.hornetq.core.remoting.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:389)
    at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:432)
    at org.hornetq.integration.transports.netty.HornetQChannelHandler.messageReceived(HornetQChannelHandler.java:67)
    at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:98)
    at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560)
    at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:796)
    at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:358)
    at org.hornetq.integration.transports.netty.HornetQFrameDecoder2.messageReceived(HornetQFrameDecoder2.java:124)
    at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80)
    at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560)
    at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:555)
    at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:345)
    at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:332)
    at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:323)
    at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:275)
    at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:196)
    at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
    at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
    at org.jboss.netty.util.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:179)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:619)

Any thoughts ??

TIA

[timfox]

Have you read the chapter in the user manual on large messages?

Or looked at the large message example in the distro?

[d.gouraud]

In fact, no. We just use HornetQ in one way, find it it very disturbing thta it can not follow the same dynamic in an upgrade.
Anyway, We will look at the docs.

[timfox]

I find it very disturbing that you cannot be bothered to read the user manual before posting

Try reading this too:

http://community.jboss.org/wiki/Howtoreportabugissue

[d.gouraud]

Thanks to the doc http://hornetq.sourceforge.net/docs/hornetq-2.0.0.GA/user-manual/en/html/configuration-index.html, we found that the following setup <journal-type>NIO</journal-type> was missing in the file hornetq-configuration.xml for our buffer size surcharge.

[clebert.suconic]

You are probably not setting up minLargeMessage size on the ConnectionFactory:

http://hornetq.sourceforge.net/docs/hornetq-2.0.0.GA/user-manual/en/html/large-messages.html

[mcleanl]

I would just like to thank you for making this post about the journal-type. I ran into the same issue as I am working with emails. bufferSize needed to be increased but had no effect until NIO was specified.  Thank you Damien!

EDIT: Although this is a workaround for the buffer size issue not being set the root cause is actually that the minLargeMessageSize is having no effect and all messages (including those set as large messages) are being treated as normal messages http://community.jboss.org/message/526320#526320 and hence hitting the journal and freaking out the buffer.

Message was edited by: Luke McLean