It seems an issue with your application?
Are you using clustering? Maybe you should update to a latest version from a checkout on Branch_2_2_AS7. There was one fix that would involve large messages and clustering.
Doesn't the stacktrace point to an issue with hornetq? The message was created with hornetq and sent with hornetq.
Other Jboss Community posts seem to point to an issue with min-large-message-size setting, but I am not sure it applies here.
Yes, we are clustering on the worker queue side of things, but not on the consumer side where the temporaryqueue message is received and "getObject" is called on the message. Are there any other options, we could look into?
it points an issue on plain serialization.. it will depend on your code.
if you see an issue with HOrnetq you would need to find us a way to replicate it.