I'll be re-running my stress test and Monday and report my findings back to
this thread. Thanks! Your questions are thought provoking.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Stress-testing-OOME-tp4677959p4678010.html
Sent from the ActiveMQ - User mailing
age in context:
http://activemq.2283324.n4.nabble.com/Stress-testing-OOME-tp4677959p4678009.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
r: GC overhead limit exceeded.
> See log file for details.
> Uncaught Exception java.lang.OutOfMemoryError: GC overhead limit exceeded.
> See log file for details.
> Uncaught Exception java.lang.OutOfMemoryError: GC overhead limit exceeded.
> See log file for details.
>
>
>
.
Still, I would expect the broker to run OOM in that scenario - not the
consumer JVM.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Stress-testing-OOME-tp4677959p4677968.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
mely small.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Stress-testing-OOME-tp4677959p4677967.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
nabble.com/Stress-testing-OOME-tp4677959p4677966.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
tivemq.2283324.n4.nabble.com/Stress-testing-OOME-tp4677959.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
The topic prefetch limit by default is quite large, you could set this
to a lower value to control how many messages pile in there.
--
Tim Bish
Sr Software Enginee
file for details.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Stress-testing-OOME-tp4677959.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
