You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Doug Whitfield <dw...@perforce.com.INVALID> on 2023/03/21 14:15:49 UTC
Re: Truncated messages in 5.16.1 when using Postman
Hi folks,
This is still an issue. I believe the setting to fix this is in https://github.com/apache/activemq/blob/d48cf3758312a25122508854946c399a2e6f6f69/activemq-web/src/main/java/org/apache/activemq/web/MessageServletSupport.java but I am not a java developer and a little confused about how we would actually change this. Would we have to recompile or is there a config file?
This is the same issue list at https://issues.apache.org/jira/browse/AMQ-8611
This seems to be caused by https://issues.apache.org/jira/browse/AMQ-8029
From: Doug Whitfield <dw...@perforce.com>
Date: Wednesday, June 16, 2021 at 4:28 PM
To: dev@activemq.apache.org <de...@activemq.apache.org>
Subject: Re: Truncated messages in 5.16.1 when using Postman
Hi JB,
Thanks for taking a look at this.
Here are the steps to reproduce:
1. Download ActiveMQ 5.15.14 or later OR 5.16.1 or later.
2. Untar the package
3. Start ActiveMQ
4*. Send payload (as size-described in the initial email) to http://localhost:8161/api/message/orders.input?type=queue (I assume this is the REST API given the URL. Also, doesn’t need to be localhost)*
5. Look at the message in the ActiveMQ UI.
6. Note that the message is truncated
To clarify, there is no need to involve a consumer to see the issue. We haven’t tested using a producer, just the API.
Since you are asking about the consumer, I assume you are concerned about the ultimate use case. In the customer use case, once MDB processes, it puts that to dlq since the queue doesn’t has complete(required) XML messages.
*We’ve played around with part 4 a bit. We can get curl to truncate if we set a different Content-Type. We can get postman to work in some cases. One thing we noticed is that the payload from postman is much larger than that of curl. Whatever curl does with x-www-form-urlencoded works but we can’t get postman to replicate that exactly. Currently, we are thinking it might be related to https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FAMQ-8029&data=04%7C01%7Cdwhitfield%40perforce.com%7C6c1b5348b196484b460108d9310d8df9%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C637594757017880030%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=vcTw9Qe2f748qrQVYGJQvZvXHklL2AoHqyyZtkTm%2BJY%3D&reserved=0 -- with the urlencoding, it could be larger, and in some cases things could get compressed. It seems like it should be throwing an error, but those fix versions line up with where the issue exists and when it doesn’t. We haven’t tested the 5.17.0 builds yet. That’s probably on the horizon though if we can’t get this resolved in the next couple of days. Maybe it’s a bystander bug that’s gotten fixed.
The fact that the payload piece of the XML is random might play into this if there is compression. Also, the fact that this is XML, might play into the exact numbers.
Another piece I want to be clear about is that this is not a postman issue. The customer is seeing this with their production workloads. Postman was just an easy way to replicate and at the beginning we didn’t understand that Content-Type played some role here. We still don’t know what role exactly it plays, but we do know it plays some role.
Best Regards,
Doug Whitfield
From: Jean-Baptiste Onofre <jb...@nanthrax.net>
Date: Wednesday, June 16, 2021 at 10:55 AM
To: dev@activemq.apache.org <de...@activemq.apache.org>
Subject: Re: Truncated messages in 5.16.1 when using Postman
Hi Doug,
Sorry, but I don’t fully understand what you are doing ;)
My understanding (correct me if I’m wrong) is:
1. You have a http related transport connector in activemq.xml (<transportConnector name="http" uri="https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2F0.0.0.0%3A8888%2F&data=04%7C01%7Cdwhitfield%40perforce.com%7C6c1b5348b196484b460108d9310d8df9%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C637594757017880030%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=9ctFB%2FmJ%2FTAYgCmxb7A3sJMce19g11XTrAXrv9AhD%2Fc%3D&reserved=0 <https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2F0.0.0.0%3A8888%2F&data=04%7C01%7Cdwhitfield%40perforce.com%7C6c1b5348b196484b460108d9310d8df9%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C637594757017880030%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=9ctFB%2FmJ%2FTAYgCmxb7A3sJMce19g11XTrAXrv9AhD%2Fc%3D&reserved=0>"/<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2F0.0.0.0%3A8888%2F&data=04%7C01%7Cdwhitfield%40perforce.com%7C6c1b5348b196484b460108d9310d8df9%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C637594757017880030%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=9ctFB%2FmJ%2FTAYgCmxb7A3sJMce19g11XTrAXrv9AhD%2Fc%3D&reserved=0<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2F0.0.0.0%3A8888%2F&data=04%7C01%7Cdwhitfield%40perforce.com%7C6c1b5348b196484b460108d9310d8df9%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C637594757017880030%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=9ctFB%2FmJ%2FTAYgCmxb7A3sJMce19g11XTrAXrv9AhD%2Fc%3D&reserved=0%3e%22/%3chttps://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2F0.0.0.0%3A8888%2F&data=04%7C01%7Cdwhitfield%40perforce.com%7C6c1b5348b196484b460108d9310d8df9%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C637594757017880030%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=9ctFB%2FmJ%2FTAYgCmxb7A3sJMce19g11XTrAXrv9AhD%2Fc%3D&reserved=0>>>)
2. You push a message via a connection factory ? Or you go through the REST API ?
3. The message you consume is incomplete (don’t consider the log message, but the consumed message)
Is that correct ?
Regards
JB
> Le 16 juin 2021 à 17:31, Doug Whitfield <dw...@perforce.com> a écrit :
>
> Hi JB,
>
> We took the jetty jar from 5.16.0 (which does not have the issue) and replaced the jetty jar in 5.16.1. Tcpdump confirms that we were testing jetty 9.4.28. This does not resolve the issue. That said, we didn’t change any of the other related jetty files, so there could still be something in jetty.
>
> We believe this has something to do with the Content-Type flag (but still unclear why the difference in ActiveMQ versions). By default, these are different in Postman and curl. The ultimate customer issue is in WebLogic, but I don’t have access to that for testing.
>
> Best Regards,
> Doug Whitfield
>
> From: Jean-Baptiste Onofre <jb@nanthrax.net <ma...@nanthrax.net>>
> Date: Tuesday, June 15, 2021 at 10:38 PM
> To: dev@activemq.apache.org <ma...@activemq.apache.org> <dev@activemq.apache.org <ma...@activemq.apache.org>>
> Subject: Re: Truncated messages in 5.16.1 when using Postman
> Hi,
>
> I will try to reproduce, so, I will start from ActiveMQ "vanilla" distribution (I’m suspecting something related to Jetty update).
>
> I will use curl to submit message. Just to be sure, what transport connector are you using: http, https, ws, … to post the message (the full URL would be helpful) ?
>
> Thanks,
> Regards
> JB
>
>> Le 15 juin 2021 à 22:33, Doug Whitfield <dw...@perforce.com> a écrit :
>>
>> Hi JB,
>>
>> The test instance AP is using is completely stock (downloaded from the ActiveMQ website). We will confirm with the customer their jetty.xml situation (I’m skeptical, since they see the exact same jump in version that we do), but there’s something strange going on in the default build.
>>
>> You mention that we would get a message in the log regarding maxFrameSize. We see no such message. Would we need a non-standard debugging level to see such a message?
>>
>> Is there anything that would be useful for us to send, like a tcpdump?
>>
>> Best Regards,
>>
>> Doug Whitfield
>>
>>
>>
>> From: Jean-Baptiste Onofre <jb@nanthrax.net <ma...@nanthrax.net> <mailto:jb@nanthrax.net <ma...@nanthrax.net>>>
>> Date: Tuesday, June 15, 2021 at 9:19 AM
>> To: dev@activemq.apache.org <ma...@activemq.apache.org> <mailto:dev@activemq.apache.org <ma...@activemq.apache.org>> <dev@activemq.apache.org <ma...@activemq.apache.org> <mailto:dev@activemq.apache.org <ma...@activemq.apache.org>>>
>> Subject: Re: Truncated messages in 5.16.1 when using Postman
>> But you go throw the HTTP connector right ?
>> Not tcp.
>>
>> So, do you have maxFrameSize on the http connector ? And also, do you use a jetty.xml dedicated for the http connector (it’s not the same as conf/jetty.xml used by the admin web console).
>>
>> Regards
>> JB
>>
>>> Le 15 juin 2021 à 14:58, Andrew Pomponio <APomponio@perforce.com <ma...@perforce.com>> a écrit :
>>>
>>> Yes, the message size that seems to start the issue is 65,536 b or 65k in size. Smaller than that and the issue does not occur, we tried with a 32k message and did not have issues.
>>>
>>> On 6/15/21, 6:37 AM, "Jean-Baptiste Onofre" <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
>>>
>>> OK, and the message you sent is smaller than 104857600 b ?
>>>
>>> Anyway, if the message is greater than the maxFrameSize, you have a message in the activemq log and an exception on the client side (JMSException).
>>>
>>> Regards
>>> JB
>>>
>>>> Le 15 juin 2021 à 13:53, Andrew Pomponio <APomponio@perforce.com <ma...@perforce.com>> a écrit :
>>>>
>>>> Hello Jean-Baptiste, thank you so much for your reply,
>>>>
>>>> For testing, we've been using stock defaults, for example, in our test for 5.15.14 we used maxFrameSize=104857600.
>>>>
>>>> On 6/15/21, 5:48 AM, "Jean-Baptiste Onofre" <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> Sorry I missed the message.
>>>>
>>>> Maybe you have reach the maxFrameSize on the transport connector. Did you try to increase it ?
>>>>
>>>> What’s your transport connector configuration in activemq.xml ?
>>>>
>>>> Regards
>>>> JB
>>>>
>>>>> Le 15 juin 2021 à 13:35, Andrew Pomponio <APomponio@perforce.com <ma...@perforce.com>> a écrit :
>>>>>
>>>>> Dear ActiveMQ Community,
>>>>>
>>>>> An update on the issue, we've done continued testing and found that this issue starts as far back as 5.15.14 and is also present in 5.16.2.
>>>>>
>>>>> On 6/10/21, 8:57 AM, "Andrew Pomponio" <APomponio@perforce.com <ma...@perforce.com>> wrote:
>>>>>
>>>>> Dear ActiveMQ Community,
>>>>>
>>>>> I am reaching out on behalf of a customer of ours experiencing what appears to be a bug (or new default limitation) in an upgraded version of AMQ from the version they are currently using. We have tested this behavior in our lab environment and are able to replicate what they are seeing using the following environmental components;
>>>>>
>>>>> ActiveMQ 5.15.11 (works) and 5.16.1 (does not work)
>>>>> Postman 8.6.1
>>>>> 72k sized payload (the exact limitations appears to be 65536 bytes)
>>>>>
>>>>> The following test is to be run once on 5.15 and then on 5.16.
>>>>>
>>>>> First, create a payload of random gibberish by executing the following;
>>>>>
>>>>> dd bs=1024 count=71 </dev/random >payload-test72k.txt
>>>>>
>>>>> cat the file and copy the contents (gibberish) into the <ns2:Data> tags like so;
>>>>>
>>>>> <ns2:NormalizedMessage xmlns:ns2="http://private <http://private/> <http://private/ <http://private/>>" xmlns:ns4="http://differentprivate <http://differentprivate/> <http://differentprivate/ <http://differentprivate/>>"><ns2:BaseDescriptor><ns2:MsgID>AVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgT>>> <http://differentprivate"><ns2:basedescriptor><ns2:msgid>avsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID>>>>> <http://differentprivate <http://differentprivate/>"><ns2:basedescriptor><ns2:msgid>avsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID>>> <http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID>>>>>over 9000</ns2:SourceApplicationID><ns2:SourceUserID>over 9000</ns2:SourceUserID><ns2:SequenceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SequenceTimeStamp> </ns2:BaseDescriptor><ns2:RoutingDescriptor><ns4:RoutingInfo><ns4:ApplicationName>over 9000</ns4:ApplicationName><ns4:ApplicationCode>over 9000</ns4:ApplicationCode><ns4:ApplicationVersion>1.0</ns4:ApplicationVersion><ns4:PublishTimeStamp>2021-04-28T15:28:57.294Z</ns4:PublishTimeStamp><ns4:Status>true</ns4:Status><ns4:StatusDescription>DocumentUploadRequest</ns4:StatusDescription> </ns4:RoutingInfo> </ns2:RoutingDescriptor><ns2:lolDescriptor><ns2:lolReferenceID>MEDDOCINT042803</ns2:lolReferenceID><ns2:AliaslolReferenceIDs><ns2:lolReferenceID>MEDDOCINT042803</ns2:lolReferenceID> </ns2:AliaslolReferenceIDs><ns2:lolFolderID>0</ns2:lolFolderID><ns2:ClientFileID></ns2:ClientFileID><ns2:nopeCompany><ns2:VantiveCode>QO</ns2:VantiveCode><ns2:nahbroCustID>0</ns2:nahbroCustID> </ns2:nopeCompany> </ns2:lolDescriptor><ns2:Payload><ns2:Data>[…] �M��pt=��/�s
>>>>> .7u�a��F�{�S���Zt��R�^&�(/k�*!y���\��}I�i
>>>>> ��
>>>>> �؍I�����ՙ�y1
>>>>> ��2��˧v�i�
>>>>> ���-F�ʅ�"��5�ԍ;C�+V[…]</ns2:Data> </ns2:Payload> </ns2:NormalizedMessage>
>>>>>
>>>>> Copy the above XML into the raw body of Postman. The XML and payload you copy and pasted from payload-test72k.txt is going to http://localhost:8161/api/message/orders.input/. With ActiveMQ running in debug mode, using Postman, with basic authorization login, click POST. You should receive an output of message sent, though the message will not show up in the UI of AMQ. We do not need it to for the purposes of this experiment.
>>>>>
>>>>> Back in a terminal from the bin directory in AMQ;
>>>>>
>>>>> tail -200 ../data/activemq.log
>>>>>
>>>>> You then can see in the log entries two different examples of the message, one that shows the full body of text being sent to ActiveMQ, and another that shows a condensed summary of the message being sent.
>>>>>
>>>>> 2021-06-10 07:50:44,510 | DEBUG | Sent! to destination: topic://orders.input. message: ActiveMQTextMessage {commandId = 0, responseRequired = false, messageId = ID:apomponio-56497-1623331633553-4:1:1:1:6, originalDestination = null, originalTransactionId = null, producerId = null, destination = topic://orders.input., transactionId = null, expiration = 0, timestamp = 1623333044509, arrival = 0, brokerInTime = 0, brokerOutTime = 0, correlationId = null, replyTo = null, persistent = true, type = null, priority = 5, groupID = null, groupSequence = 0, targetConsumerId = null, compressed = false, userID = null, content = null, marshalledProperties = null, dataStructure = null, redeliveryCounter = 0, size = 0, properties = null, readOnlyProperties = false, readOnlyBody = false, droppable = false, jmsXGroupFirstForConsumer = false, text = <ns2:NormalizedMessage xmlns:ns2="http://priv...�T�T�Z5� �]
>>>>> } | org.apache.activemq.web.WebClient | qtp632475595-35
>>>>>
>>>>> In the example above from the 5.16 server, we see in the text = field the start of our message, and right after http://priv we see … followed by the portion of gibberish where the message ends in the log. In our 5.15 logs we see http://priv...zedMessage><http://priv...zedMessage%3e> showing us the partial ending XML tag of </ns2:NormalizedMessage> which is the expected behavior.
>>>>>
>>>>> In 5.15.11, the full length of the body message shows up in the activemq.log file, but in 5.16.1 that same message sent exactly the same way is truncated around the 64k size.
>>>>>
>>>>> Is this a known default limitation introduced in 5.16? If so, how do we increase it?
>>>>>
>>>>> If this is anticipated to be a bug, what additional information, if any, do you need from us? Also, in the future, would something like this be more appropriate for the users mailing list instead?
>>>>>
>>>>>
>>>>>
>>>>> This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.
>>>>>
>>>>
>>>>
>>>>
>>>> CAUTION: This email originated from outside of the organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe.
>>>>
>>>>
>>>> This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.
>>>>
>>>
>>>
>>>
>>> CAUTION: This email originated from outside of the organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe.
>>>
>>>
>>> This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.
>>>
>>
>>
>>
>> CAUTION: This email originated from outside of the organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe.
>>
>>
>> This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.
>
>
>
> CAUTION: This email originated from outside of the organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe.
>
>
> This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.
CAUTION: This email originated from outside of the organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe.
This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.
This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.
Re: Truncated messages in 5.16.1 when using Postman
Posted by Doug Whitfield <dw...@perforce.com.INVALID>.
So, I think this should look something like this:
<web-app>
<servlet>
<servlet-name>HandleMessage</servlet-name>
<servlet-class>SubClassOfMessageServletSupport</servlet-class>
<init-param>
<param-name>maxMessageSize</param-name>
<param-value>1000000</param-value>
</init-param>
</servlet>
However, I am not sure what the servlet-class here is.
From: Doug Whitfield <dw...@perforce.com.INVALID>
Date: Tuesday, March 21, 2023 at 9:16 AM
To: dev@activemq.apache.org <de...@activemq.apache.org>
Subject: Re: Truncated messages in 5.16.1 when using Postman
Hi folks,
This is still an issue. I believe the setting to fix this is in https://github.com/apache/activemq/blob/d48cf3758312a25122508854946c399a2e6f6f69/activemq-web/src/main/java/org/apache/activemq/web/MessageServletSupport.java but I am not a java developer and a little confused about how we would actually change this. Would we have to recompile or is there a config file?
This is the same issue list at https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FAMQ-8611&data=05%7C01%7Cdwhitfield%40perforce.com%7C0fee2cb39a6a41192d9b08db2a16e77f%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638150050103359107%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=T%2FFWXkKhwIHbBO3QYEFhSRo9ZSbPnGhxeN%2FnX0rvEC0%3D&reserved=0
This seems to be caused by https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FAMQ-8029&data=05%7C01%7Cdwhitfield%40perforce.com%7C0fee2cb39a6a41192d9b08db2a16e77f%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638150050103359107%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=aYHqcJYoR7o%2BIsop%2Bn7ePJ9o%2FbiKK5pga1vXrqM7wKo%3D&reserved=0
From: Doug Whitfield <dw...@perforce.com>
Date: Wednesday, June 16, 2021 at 4:28 PM
To: dev@activemq.apache.org <de...@activemq.apache.org>
Subject: Re: Truncated messages in 5.16.1 when using Postman
Hi JB,
Thanks for taking a look at this.
Here are the steps to reproduce:
1. Download ActiveMQ 5.15.14 or later OR 5.16.1 or later.
2. Untar the package
3. Start ActiveMQ
4*. Send payload (as size-described in the initial email) to http://localhost:8161/api/message/orders.input?type=queue (I assume this is the REST API given the URL. Also, doesn’t need to be localhost)*
5. Look at the message in the ActiveMQ UI.
6. Note that the message is truncated
To clarify, there is no need to involve a consumer to see the issue. We haven’t tested using a producer, just the API.
Since you are asking about the consumer, I assume you are concerned about the ultimate use case. In the customer use case, once MDB processes, it puts that to dlq since the queue doesn’t has complete(required) XML messages.
*We’ve played around with part 4 a bit. We can get curl to truncate if we set a different Content-Type. We can get postman to work in some cases. One thing we noticed is that the payload from postman is much larger than that of curl. Whatever curl does with x-www-form-urlencoded works but we can’t get postman to replicate that exactly. Currently, we are thinking it might be related to https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FAMQ-8029&data=05%7C01%7Cdwhitfield%40perforce.com%7C0fee2cb39a6a41192d9b08db2a16e77f%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638150050103359107%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=aYHqcJYoR7o%2BIsop%2Bn7ePJ9o%2FbiKK5pga1vXrqM7wKo%3D&reserved=0 -- with the urlencoding, it could be larger, and in some cases things could get compressed. It seems like it should be throwing an error, but those fix versions line up with where the issue exists and when it doesn’t. We haven’t tested the 5.17.0 builds yet. That’s probably on the horizon though if we can’t get this resolved in the next couple of days. Maybe it’s a bystander bug that’s gotten fixed.
The fact that the payload piece of the XML is random might play into this if there is compression. Also, the fact that this is XML, might play into the exact numbers.
Another piece I want to be clear about is that this is not a postman issue. The customer is seeing this with their production workloads. Postman was just an easy way to replicate and at the beginning we didn’t understand that Content-Type played some role here. We still don’t know what role exactly it plays, but we do know it plays some role.
Best Regards,
Doug Whitfield
From: Jean-Baptiste Onofre <jb...@nanthrax.net>
Date: Wednesday, June 16, 2021 at 10:55 AM
To: dev@activemq.apache.org <de...@activemq.apache.org>
Subject: Re: Truncated messages in 5.16.1 when using Postman
Hi Doug,
Sorry, but I don’t fully understand what you are doing ;)
My understanding (correct me if I’m wrong) is:
1. You have a http related transport connector in activemq.xml (<transportConnector name="http" uri="https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2F0.0.0.0%3A8888%2F&data=05%7C01%7Cdwhitfield%40perforce.com%7C0fee2cb39a6a41192d9b08db2a16e77f%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638150050103359107%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pzPDGh2SsUEF8Iw8fkfygU0KFQnKHgdaL8aSIxErHx8%3D&reserved=0 <https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2F0.0.0.0%3A8888%2F&data=05%7C01%7Cdwhitfield%40perforce.com%7C0fee2cb39a6a41192d9b08db2a16e77f%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638150050103359107%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pzPDGh2SsUEF8Iw8fkfygU0KFQnKHgdaL8aSIxErHx8%3D&reserved=0>"/<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2F0.0.0.0%3A8888%2F&data=05%7C01%7Cdwhitfield%40perforce.com%7C0fee2cb39a6a41192d9b08db2a16e77f%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638150050103359107%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pzPDGh2SsUEF8Iw8fkfygU0KFQnKHgdaL8aSIxErHx8%3D&reserved=0<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2F0.0.0.0%3A8888%2F&data=05%7C01%7Cdwhitfield%40perforce.com%7C0fee2cb39a6a41192d9b08db2a16e77f%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638150050103359107%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pzPDGh2SsUEF8Iw8fkfygU0KFQnKHgdaL8aSIxErHx8%3D&reserved=0<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2F0.0.0.0%3A8888%2F&data=05%7C01%7Cdwhitfield%40perforce.com%7C0fee2cb39a6a41192d9b08db2a16e77f%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638150050103359107%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pzPDGh2SsUEF8Iw8fkfygU0KFQnKHgdaL8aSIxErHx8%3D&reserved=0%3e%22/%3chttps://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2F0.0.0.0%3A8888%2F&data=05%7C01%7Cdwhitfield%40perforce.com%7C0fee2cb39a6a41192d9b08db2a16e77f%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638150050103359107%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pzPDGh2SsUEF8Iw8fkfygU0KFQnKHgdaL8aSIxErHx8%3D&reserved=0%3chttps://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2F0.0.0.0%3A8888%2F&data=05%7C01%7Cdwhitfield%40perforce.com%7C0fee2cb39a6a41192d9b08db2a16e77f%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638150050103359107%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pzPDGh2SsUEF8Iw8fkfygU0KFQnKHgdaL8aSIxErHx8%3D&reserved=0>>>>)
2. You push a message via a connection factory ? Or you go through the REST API ?
3. The message you consume is incomplete (don’t consider the log message, but the consumed message)
Is that correct ?
Regards
JB
> Le 16 juin 2021 à 17:31, Doug Whitfield <dw...@perforce.com> a écrit :
>
> Hi JB,
>
> We took the jetty jar from 5.16.0 (which does not have the issue) and replaced the jetty jar in 5.16.1. Tcpdump confirms that we were testing jetty 9.4.28. This does not resolve the issue. That said, we didn’t change any of the other related jetty files, so there could still be something in jetty.
>
> We believe this has something to do with the Content-Type flag (but still unclear why the difference in ActiveMQ versions). By default, these are different in Postman and curl. The ultimate customer issue is in WebLogic, but I don’t have access to that for testing.
>
> Best Regards,
> Doug Whitfield
>
> From: Jean-Baptiste Onofre <jb@nanthrax.net <ma...@nanthrax.net>>
> Date: Tuesday, June 15, 2021 at 10:38 PM
> To: dev@activemq.apache.org <ma...@activemq.apache.org> <dev@activemq.apache.org <ma...@activemq.apache.org>>
> Subject: Re: Truncated messages in 5.16.1 when using Postman
> Hi,
>
> I will try to reproduce, so, I will start from ActiveMQ "vanilla" distribution (I’m suspecting something related to Jetty update).
>
> I will use curl to submit message. Just to be sure, what transport connector are you using: http, https, ws, … to post the message (the full URL would be helpful) ?
>
> Thanks,
> Regards
> JB
>
>> Le 15 juin 2021 à 22:33, Doug Whitfield <dw...@perforce.com> a écrit :
>>
>> Hi JB,
>>
>> The test instance AP is using is completely stock (downloaded from the ActiveMQ website). We will confirm with the customer their jetty.xml situation (I’m skeptical, since they see the exact same jump in version that we do), but there’s something strange going on in the default build.
>>
>> You mention that we would get a message in the log regarding maxFrameSize. We see no such message. Would we need a non-standard debugging level to see such a message?
>>
>> Is there anything that would be useful for us to send, like a tcpdump?
>>
>> Best Regards,
>>
>> Doug Whitfield
>>
>>
>>
>> From: Jean-Baptiste Onofre <jb@nanthrax.net <ma...@nanthrax.net> <mailto:jb@nanthrax.net <ma...@nanthrax.net>>>
>> Date: Tuesday, June 15, 2021 at 9:19 AM
>> To: dev@activemq.apache.org <ma...@activemq.apache.org> <mailto:dev@activemq.apache.org <ma...@activemq.apache.org>> <dev@activemq.apache.org <ma...@activemq.apache.org> <mailto:dev@activemq.apache.org <ma...@activemq.apache.org>>>
>> Subject: Re: Truncated messages in 5.16.1 when using Postman
>> But you go throw the HTTP connector right ?
>> Not tcp.
>>
>> So, do you have maxFrameSize on the http connector ? And also, do you use a jetty.xml dedicated for the http connector (it’s not the same as conf/jetty.xml used by the admin web console).
>>
>> Regards
>> JB
>>
>>> Le 15 juin 2021 à 14:58, Andrew Pomponio <APomponio@perforce.com <ma...@perforce.com>> a écrit :
>>>
>>> Yes, the message size that seems to start the issue is 65,536 b or 65k in size. Smaller than that and the issue does not occur, we tried with a 32k message and did not have issues.
>>>
>>> On 6/15/21, 6:37 AM, "Jean-Baptiste Onofre" <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
>>>
>>> OK, and the message you sent is smaller than 104857600 b ?
>>>
>>> Anyway, if the message is greater than the maxFrameSize, you have a message in the activemq log and an exception on the client side (JMSException).
>>>
>>> Regards
>>> JB
>>>
>>>> Le 15 juin 2021 à 13:53, Andrew Pomponio <APomponio@perforce.com <ma...@perforce.com>> a écrit :
>>>>
>>>> Hello Jean-Baptiste, thank you so much for your reply,
>>>>
>>>> For testing, we've been using stock defaults, for example, in our test for 5.15.14 we used maxFrameSize=104857600.
>>>>
>>>> On 6/15/21, 5:48 AM, "Jean-Baptiste Onofre" <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> Sorry I missed the message.
>>>>
>>>> Maybe you have reach the maxFrameSize on the transport connector. Did you try to increase it ?
>>>>
>>>> What’s your transport connector configuration in activemq.xml ?
>>>>
>>>> Regards
>>>> JB
>>>>
>>>>> Le 15 juin 2021 à 13:35, Andrew Pomponio <APomponio@perforce.com <ma...@perforce.com>> a écrit :
>>>>>
>>>>> Dear ActiveMQ Community,
>>>>>
>>>>> An update on the issue, we've done continued testing and found that this issue starts as far back as 5.15.14 and is also present in 5.16.2.
>>>>>
>>>>> On 6/10/21, 8:57 AM, "Andrew Pomponio" <APomponio@perforce.com <ma...@perforce.com>> wrote:
>>>>>
>>>>> Dear ActiveMQ Community,
>>>>>
>>>>> I am reaching out on behalf of a customer of ours experiencing what appears to be a bug (or new default limitation) in an upgraded version of AMQ from the version they are currently using. We have tested this behavior in our lab environment and are able to replicate what they are seeing using the following environmental components;
>>>>>
>>>>> ActiveMQ 5.15.11 (works) and 5.16.1 (does not work)
>>>>> Postman 8.6.1
>>>>> 72k sized payload (the exact limitations appears to be 65536 bytes)
>>>>>
>>>>> The following test is to be run once on 5.15 and then on 5.16.
>>>>>
>>>>> First, create a payload of random gibberish by executing the following;
>>>>>
>>>>> dd bs=1024 count=71 </dev/random >payload-test72k.txt
>>>>>
>>>>> cat the file and copy the contents (gibberish) into the <ns2:Data> tags like so;
>>>>>
>>>>> <ns2:NormalizedMessage xmlns:ns2="http://private <http://private/> <http://private/ <http://private/>>" xmlns:ns4="http://differentprivate <http://differentprivate/> <http://differentprivate/ <http://differentprivate/>>"><ns2:BaseDescriptor><ns2:MsgID>AVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp<http://differentprivate/%3e%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgT>><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgT>>> <http://differentprivate"><ns2:basedescriptor><ns2:msgid>avsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:BaseDescriptor%3e%3cns2:MsgID%3eAVSN#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType>>>>>> <http://differentprivate <http://differentprivate/>"><ns2:basedescriptor><ns2:msgid>avsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate/%3e%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID<http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType>>>> <http://differentprivate%22%3e%3cns2:basedescriptor%3e%3cns2:msgid%3eavsn#I64534#ajz123403252016#2016-03-25T13:15:55</ns2:MsgID><ns2:MsgType>INTF</ns2:MsgType><ns2:MsgMode>INBOUND</ns2:MsgMode><ns2:SourceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SourceTimeStamp><ns2:SourceApplicationID>>>>>over 9000</ns2:SourceApplicationID><ns2:SourceUserID>over 9000</ns2:SourceUserID><ns2:SequenceTimeStamp>2021-04-28T15:28:57.294Z</ns2:SequenceTimeStamp> </ns2:BaseDescriptor><ns2:RoutingDescriptor><ns4:RoutingInfo><ns4:ApplicationName>over 9000</ns4:ApplicationName><ns4:ApplicationCode>over 9000</ns4:ApplicationCode><ns4:ApplicationVersion>1.0</ns4:ApplicationVersion><ns4:PublishTimeStamp>2021-04-28T15:28:57.294Z</ns4:PublishTimeStamp><ns4:Status>true</ns4:Status><ns4:StatusDescription>DocumentUploadRequest</ns4:StatusDescription> </ns4:RoutingInfo> </ns2:RoutingDescriptor><ns2:lolDescriptor><ns2:lolReferenceID>MEDDOCINT042803</ns2:lolReferenceID><ns2:AliaslolReferenceIDs><ns2:lolReferenceID>MEDDOCINT042803</ns2:lolReferenceID> </ns2:AliaslolReferenceIDs><ns2:lolFolderID>0</ns2:lolFolderID><ns2:ClientFileID></ns2:ClientFileID><ns2:nopeCompany><ns2:VantiveCode>QO</ns2:VantiveCode><ns2:nahbroCustID>0</ns2:nahbroCustID> </ns2:nopeCompany> </ns2:lolDescriptor><ns2:Payload><ns2:Data>[…] �M��pt=��/�s
>>>>> .7u�a��F�{�S���Zt��R�^&�(/k�*!y���\��}I�i
>>>>> ��
>>>>> �؍I�����ՙ�y1
>>>>> ��2��˧v�i�
>>>>> ���-F�ʅ�"��5�ԍ;C�+V[…]</ns2:Data> </ns2:Payload> </ns2:NormalizedMessage>
>>>>>
>>>>> Copy the above XML into the raw body of Postman. The XML and payload you copy and pasted from payload-test72k.txt is going to http://localhost:8161/api/message/orders.input/. With ActiveMQ running in debug mode, using Postman, with basic authorization login, click POST. You should receive an output of message sent, though the message will not show up in the UI of AMQ. We do not need it to for the purposes of this experiment.
>>>>>
>>>>> Back in a terminal from the bin directory in AMQ;
>>>>>
>>>>> tail -200 ../data/activemq.log
>>>>>
>>>>> You then can see in the log entries two different examples of the message, one that shows the full body of text being sent to ActiveMQ, and another that shows a condensed summary of the message being sent.
>>>>>
>>>>> 2021-06-10 07:50:44,510 | DEBUG | Sent! to destination: topic://orders.input. message: ActiveMQTextMessage {commandId = 0, responseRequired = false, messageId = ID:apomponio-56497-1623331633553-4:1:1:1:6, originalDestination = null, originalTransactionId = null, producerId = null, destination = topic://orders.input., transactionId = null, expiration = 0, timestamp = 1623333044509, arrival = 0, brokerInTime = 0, brokerOutTime = 0, correlationId = null, replyTo = null, persistent = true, type = null, priority = 5, groupID = null, groupSequence = 0, targetConsumerId = null, compressed = false, userID = null, content = null, marshalledProperties = null, dataStructure = null, redeliveryCounter = 0, size = 0, properties = null, readOnlyProperties = false, readOnlyBody = false, droppable = false, jmsXGroupFirstForConsumer = false, text = <ns2:NormalizedMessage xmlns:ns2="http://priv...�T�T�Z5� �]
>>>>> } | org.apache.activemq.web.WebClient | qtp632475595-35
>>>>>
>>>>> In the example above from the 5.16 server, we see in the text = field the start of our message, and right after http://priv we see … followed by the portion of gibberish where the message ends in the log. In our 5.15 logs we see http://priv...zedMessage><http://priv...zedMessage%3e><http://priv...zedMessage%3e%3chttp:/priv...zedMessage%3e%3e> showing us the partial ending XML tag of </ns2:NormalizedMessage> which is the expected behavior.
>>>>>
>>>>> In 5.15.11, the full length of the body message shows up in the activemq.log file, but in 5.16.1 that same message sent exactly the same way is truncated around the 64k size.
>>>>>
>>>>> Is this a known default limitation introduced in 5.16? If so, how do we increase it?
>>>>>
>>>>> If this is anticipated to be a bug, what additional information, if any, do you need from us? Also, in the future, would something like this be more appropriate for the users mailing list instead?
>>>>>
>>>>>
>>>>>
>>>>> This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.
>>>>>
>>>>
>>>>
>>>>
>>>> CAUTION: This email originated from outside of the organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe.
>>>>
>>>>
>>>> This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.
>>>>
>>>
>>>
>>>
>>> CAUTION: This email originated from outside of the organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe.
>>>
>>>
>>> This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.
>>>
>>
>>
>>
>> CAUTION: This email originated from outside of the organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe.
>>
>>
>> This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.
>
>
>
> CAUTION: This email originated from outside of the organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe.
>
>
> This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.
CAUTION: This email originated from outside of the organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe.
This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.
This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.
This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.