This content has been marked as final.
Show 3 replies
-
1. Re: Tests over LargeMessageExample
timfox Nov 10, 2009 9:48 AM (in response to clebert.suconic)I cannot replicate the issue any more, the error no longer appears (it did so every time). I can only asssume it has been fixed in the latest refactorings.
I have also disabled the memory manager by default. The memory manager is kind of bogus since it's memory calculations include non referenced objects which might be ready for GC. It's not practical to force GC every time before printing the memory manager statistics. -
2. Re: Tests over LargeMessageExample
clebert.suconic Nov 10, 2009 10:48 AM (in response to clebert.suconic)As for producing being faster than consuming, I have created this JIRA, so we can investigate possible optimizations later.
https://jira.jboss.org/jira/browse/HORNETQ-212 -
3. Re: Tests over LargeMessageExample
clebert.suconic Nov 10, 2009 3:36 PM (in response to clebert.suconic)"timfox" wrote:
I have also disabled the memory manager by default. The memory manager is kind of bogus since it's memory calculations include non referenced objects which might be ready for GC. It's not practical to force GC every time before printing the memory manager statistics.
Just a thought...
maybe we should add -verbose:gc in our run.bat and run.sh.
I haven't been on the production side for a while, but what I remember from previous jobs is that people will usually add that.
That would maybe help educate users?