[jboss-jira] [JBoss JIRA] (JBMESSAGING-1802) Sending MapMessage with large String value is broken

[Jess Sightler (JIRA)]

    [ https://issues.jboss.org/browse/JBMESSAGING-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742188#comment-12742188 ] 

Jess Sightler commented on JBMESSAGING-1802:
--------------------------------------------

Hi Justin,

The comment itself essentially describes the bug, IMO. It's described as for "performance reasons", but I don't see how that could apply to only StreamMessage. Why would we support writeObject for an ObjectMessage (containing a String) of >65535, but not for a StreamMessage of the same? Performance concerns and considerations would be the same for both of those cases, IMO.

I've tried this with HornetQ, and large messages are accepted with StreamMessage. I believe that competing products do as well (this came up in a recent WebLogic migration).

Isn't the fix fairly straightforward anyway (pass the longStrings boolean all the way down)? Or is there more here that I'm not seeing?
                
> Sending MapMessage with large String value is broken
> ----------------------------------------------------
>
>                 Key: JBMESSAGING-1802
>                 URL: https://issues.jboss.org/browse/JBMESSAGING-1802
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.SP3.CP10, 1.4.6.GA
>            Reporter: Justin Bertram
>            Assignee: Yong Hao Gao
>             Fix For: 1.4.8.SP10
>
>
> Sending a javax.jms.MapMessage that has a String value >= 65536 characters fails.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira