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 bit.
On Thu, May 31, 2018 at 3:55 PM, Christopher Shannon < [email protected]> wrote: > Found the culprit: Seems to be related to https://issues.apache.org/ > jira/browse/AMQ-5857 > > Specifically, this commit: https://git-wip-us.apache.org/repos/asf?p= > activemq.git;a=blobdiff;f=activemq-client/src/main/java/ > org/apache/activemq/command/ActiveMQTextMessage.java;h= > cca09be21bfb877213a4a506415929f1f81a1902;hp=347db78da559bf57b049574c96cd3a > 8e08681dae;hb=84ec047;hpb=de86f473f776fe3a8ca32d7f929ecec7993c458b > > 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 <[email protected]> > wrote: > >> 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 >> *feels* >> really wasteful to be marshaling the message and using TCP when we're in >> the >> 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. >> html >> > >
