Hello all,
Coming back on this problem it seems that if I remove the broker from my
webapp and run an external broker, I have no more OutOfMemoryError.
Now if I run an embedded broker without any memory limit parameters, I run
out of java heap space.
If I put some destinationPolicy and
Hello to all,
My last chance, I've spend last hours to make it work, modifying a lot of
parameters but without any success ...
We have a web application using Spring 2.5.4 and ActiveMQ which is working
very well, with ajax access etc ... and we would like to upgrade to 5.1.0.
The configuration
