java.lang.IllegalAccessError: This is a read-only buffer, setOperations are not supported

[veitg]

Hi.

We're using HornetQ 2.1.2 with JBoss 5.1.0.

In a redelivery usecase we receive a message in a MDB, change its properties and send it to another queue. To make this

work, we call the clearProperties() method on the message and re-set the values. As mentioned in  the javax.jms.Message javadoc this is allowed:

"If   clearProperties is called, the properties can now be both  read from and written to"

That indeed works with small messages. But when we use messages >100kb we get the following from the HornetQ server:

Caused by: java.lang.IllegalAccessError: This is a read-only buffer, setOperations are not supported
    at org.hornetq.core.client.impl.LargeMessageBufferImpl.writeInt(LargeMessageBufferImpl.java:949)
    at org.hornetq.jms.client.HornetQObjectMessage.doBeforeSend(HornetQObjectMessage.java:93)
    at org.hornetq.jms.client.HornetQMessageProducer.doSend(HornetQMessageProducer.java:426)
    at org.hornetq.jms.client.HornetQMessageProducer.send(HornetQMessageProducer.java:199)
    at org.hornetq.ra.HornetQRAMessageProducer.send(HornetQRAMessageProducer.java:221)

Is this a bug?

BTW: this also happens with trunk.

[clebert.suconic]

The JMS Specification doesn't say how you're supposed to send large messages.

Large Messages are read only after received.

[veitg]

I simply create an ObjectMessage via session.createObjectMessage(myObject). myObject is >100kb. Since ObjectMessage implements javax.jms.Message IMHO it must fulfill the contract to allow clearProperties() and write _properties_. It's independent of the fact that I'll send a message of a specific size. Internally it may be that large messages are read-only - but wouldn't that break the contract of javax.xml.Message (clearProperties)?

Sure that body and headers are read-only after receive, but properties can be written after calling clearProperties() - per contract.

[timfox]

Clebert Suconic wrote:

The JMS Specification doesn't say how you're supposed to send large messages.

Large Messages are read only after received.

I think the current behaviour of large messages is wrong.

If a user sends a message that's over the large message size, then, fair enough, on the server, the server can store it as a large message.

However, when consuming, unless the user specifies to stream it say to disk, then the message should be re-assembled as a normal message on the client side.

Sure this may run out of memory if the message is very large, but in that case the user can set a flag on the consumer (or factory) to specify it as a large message.

In short it should be possible to transfer messages over large message size transparently to and from the server and they should be dealt with as normal messages.

[timfox]

Clebert - no comment?

[clebert.suconic]

I will change it on 2.2. I have a bunch of tasks around large message and I will do it as part of that.

https://jira.jboss.org/browse/HORNETQ-538