On 1 June 2010 15:49, Rajith Attapattu <[email protected]> wrote: > Robbie, > > Have you had a chance to look at the log output? > I also think it's better to exclude this from the in-vm broker profile > as in this case everything runs on the same JVM. > > Rajith > > On Wed, May 19, 2010 at 9:58 AM, Robbie Gemmell > <[email protected]> wrote: >> I had modified the test log4j configuration previously to stop it >> outputing that specific logging, it seems to be back though - some >> class name changes altering the Logger name used perhaps ? >> >> On 19 May 2010 13:32, Martin Ritchie <[email protected]> wrote: >>> Hi Rajith, >>> >>> I think this is actually down to the erroneous adjustment of the >>> ExpiredMessageTask frequency in the NullApplicationRegistry. >>> >>> I recent change I made was to cause HouseKeepingTasks to log when they >>> execute. The NAR though sets the run frequency to every 200ms. This >>> was done for one test. Which test I don't recall right now but will >>> track it down and ensure that it sets the configuration it needs >>> without breaking the other tests. >>> >>> The OOM will be due to the test framework holding on to all the broker >>> log messages. >>> >>> I actually haven't seen a OOM locally on any of my full suite test >>> runs (default,java,java.0.10) but hopefully the change to the >>> housekeeping frequency will address this in your test env. >>> >>> In the mean time I beleive uping the memory avalable to ant will address >>> this. >>> >>> Cheers >>> Martin >>> On 19 May 2010 00:09, Rajith Attapattu <[email protected]> wrote: >>>> Hi Martin, >>>> >>>> The slow consumer test seems to run out of memory. >>>> Could you perhaps adjust the test or the memory requirements to ensure >>>> it doesn't go OOM ? >>>> >>>> test: >>>> [echo] Using profile:default >>>> [junit] Running org.apache.qpid.systest.SlowConsumerTest >>>> test:ExpiredMessagesTask 2010-05-18 17:38:48,908 DEBUG >>>> [qpid.server.virtualhost.VirtualHostImpl$1ExpiredMessagesTask] >>>> Checking message status for queue: ping >>>> development:ExpiredMessagesTask 2010-05-18 17:38:48,909 DEBUG >>>> [qpid.server.virtualhost.VirtualHostImpl$1ExpiredMessagesTask] >>>> Checking message status for queue: ping >>>> java.lang.OutOfMemoryError: PermGen space >>>> PermGen space >>>> Thread-1259 2010-05-18 17:38:50,812 INFO >>>> [qpid.server.registry.ApplicationRegistry] Shutting down >>>> ApplicationRegistry(1):org.apache.qpid.server.registry.configurationfileapplicationregis...@2268898 >>>> Thread-1259 2010-05-18 17:38:50,812 INFO >>>> [qpid.server.registry.ApplicationRegistry] Shutting down >>>> ApplicationRegistry:org.apache.qpid.server.registry.configurationfileapplicationregis...@2268898 >>>> Exception in thread "Thread-93" java.lang.OutOfMemoryError: PermGen space >>>> Stopping Plugin manager >>>> Exception in thread "AnonymousIoService-1" java.lang.OutOfMemoryError: >>>> PermGen space >>>> Stopped Plugin manager >>>> Thread-1259 2010-05-18 17:39:08,086 INFO [qpid.message] MESSAGE >>>> [Broker(1)] BRK-1005 : Stopped >>>> Exception in thread "Thread-1259" java.lang.OutOfMemoryError: PermGen space
Hi. This is now happening in the simple-xml plugin tests, although it's intermittent... I have attached a file to a new JIRA, QPID-2635, which ups the PermGen limit to 256Mb. This seems to fix it for me, but I can't test it fully, so maybe a different value would be better? And, I'd prefer a better solution, too. Andrew. -- -- andrew d kennedy ? edinburgh : +44 7941 197 134 --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
