Yes, the consumer is separated from the broker and the producer.
Now, I installed the YourKit on the consumer PC and run it to try capture
somthing.
I put follow codes in my source code, then find the used memory was released
in every 10minuts.
...
final Thread thread = new Thread(
new Runnable(){
public void run() {
try {
final Controller controller = new Controller();
for (;;) {
Thread.sleep(10 /* minutes */ * 60 /*seconds in minute*/ * 1000 /*
millis in second */);
controller.captureMemorySnapshot();
}
}
catch (Exception e) {
e.printStackTrace();
}
}
}
);
thread.setDaemon(true); // let the application normally terminate
thread.start();
....
Is just the consumer running in the JVM and the broker & producer are
seperate? If you think you've found some kind of memory leak, please
run a profiler to help us figure out whats going on.
On 9/28/06, HU <[EMAIL PROTECTED]> wrote:
>
> Hi, James.
>
> Our system have to continue to keep the running one month or more long
> term without any memory leaks.
>
> Yesterday's test was interrupted due to the memory leak(OutOfMemory) on
> the
> consumer thread side after I changed the java heap to -Xmx512K.
>
> Now I began a new test following the prefetch limit.
> I changed the code:
> destinetionQueue = session.createQueue("RequestQueue");
> to
> destinetionQueue = New
> ActiveMQQueue("RequestQueue?consumer.prefetchSize=1");
> .
> The test is running now, but the GC tell me the heap is used slowing up...
>
>
>
--
View this message in context:
http://www.nabble.com/Broker-used-up-the-memory-tf2316972.html#a6544834
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
