[
https://issues.jboss.org/browse/JBMESSAGING-1802?page=com.atlassian.jira....
]
Justin Bertram commented on JBMESSAGING-1802:
---------------------------------------------
[~jsight], my point was that this is not a bug, but an intentional decision. You can
certainly argue about the logic of the decision, but the fact remains that it's not a
bug. To my knowledge, this is not required to support JMS 1.1.
Also, it's unlikely this is going to change now that HornetQ is the JMS broker of
choice in the JBoss community and in JBoss EAP. EAP 4.3 (which only uses JBoss Messaging)
will reach EOL in January 2013 and anybody using EAP 5 can move to 5.1.2 and install
HornetQ. Of course, there is no option to use JBoss Messaging in EAP 6.
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