Re: TextMessage.getText returning null
Yeah, TCP should be fine. Even if this gets fixed it will take time before
a new release is done anyways so you'll need to use the TCP or NIO for a
On Thu, May 31, 2018 at 3:55 PM, Christopher Shannon <
> Found the culprit: Seems to be related to https://issues.apache.org/
> Specifically, this commit: https://git-wip-us.apache.org/repos/asf?p=
> Changing the storeContentAndClear() call back to storeContent() fixes it,
> however it was changed for a reason to prevent memory waste so need to see
> if/what a permanent fix is
> On Thu, May 31, 2018 at 3:54 PM, codingismy11to7 <steven@xxxxxxxxxxxxxx>
>> Ok, thank you...my thought also was that performance impact of using tcp
>> wouldn't be enough to hurt us in any substantial way, even though it
>> really wasteful to be marshaling the message and using TCP when we're in
>> same JVM.
>> In response to your first message, I changed the transport from nio:// to
>> tcp:// on all the non-vm threads and the behavior still reproduces. Using
>> Java and raw AMQ libs is a much tougher problem...which I can do...but I
>> probably won't be able to get to that for a few days.
>> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.