To make this a little more clear, the few items I am struggling to still understand are these. Really appreciate any comments or ideas anyone has.
>From the byte stream that’s incoming to the broker, the size provided in bytes 21 to 24 before the Datatype parameter and the ActiveMQ magic, this is the value that’s pulled for use to make sure its not beyond the configured maxFrameSize. Are we missing a required configuration that’s allowing this size to be a negative value or is that expected? byte|[21] |0 byte|[22] |0 byte|[23] |0 byte|[24] |-16 byte|[25] |1 byte|[26] |65 ->A byte|[27] |99 ->c byte|[28] |116 ->t byte|[29] |105 ->i byte|[30] |118 ->v byte|[31] |101 ->e byte|[32] |77 ->M byte|[33] |81 ->Q Later on in the stream, if it was parsed correctly, after the ActiveMQ magic and the Version (10 in our example), the size used for the Byte array would be parsed as 16mb. Far better than the 64mb its currently trying to allocate for us, but still that size seems large for the data passed in. Again is this a setting we are missing when the connection is created? ActiveMQ magic: byte|[26] |65 ->A byte|[27] |99 ->c byte|[28] |116 ->t byte|[29] |105 ->i byte|[30] |118 ->v byte|[31] |101 ->e byte|[32] |77 ->M byte|[33] |81 ->Q Version (10) byte|[34] |0 byte|[35] |0 byte|[36] |0 byte|[37] |10 Byte array size (16777216) byte|[38] |1 byte|[39] |0 byte|[40] |0 byte|[41] |0 We plan to test both with tightEncodingEnabled set to false, and also with the 5.14 version, but I wanted to clear up my questions around this. We use the ActiveMQSslConnectionFactory and these are the parameters we currently pass into this when the factory is created: initialReconnectDelay=10 maxReconnectDelay=30000 maxReconnectAttempts=10 startupMaxReconnectAttempts=1 timeout=60000 randomize=false useExponentialBackOff=true priorityBackup=true jms.useAsyncSend=true nested.soTimeout=60000 nested.soWriteTimeout=60000 nested.wireFormat.maxFrameSize=262144 -- View this message in context: http://activemq.2283324.n4.nabble.com/MaxFrameSize-not-honored-and-allowing-64MB-messages-to-go-through-tp4715094p4715595.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
