Martin, I did get an OOM exception but it was during a test case. (See Below)
I also see the following test failures that pass for me under ant (0-8 java broker). It's worth investigating them for sure. Running org.apache.qpid.test.unit.basic.LargeMessageTest Tests run: 9, Failures: 2, Errors: 2, Skipped: 0, Time elapsed: 62.046 sec <<< FAILURE! Running org.apache.qpid.test.unit.client.connection.ConnectionTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.599 sec Running org.apache.qpid.client.AMQQueueDeferredOrderingTest Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 42.496 sec <<< FAILURE! [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] org.apache.qpid.test.unit.basic.MultipleConnectionTest; nested exception is java.lang.OutOfMemoryError: Java heap space; nested exception is org.apache.maven.surefire.testset.TestSetFailedException: org.apache.qpid.test.unit.basic.MultipleConnectionTest; nested exception is java.lang.OutOfMemoryError: Java heap space On Thu, Feb 28, 2008 at 11:11 AM, Martin Ritchie <[EMAIL PROTECTED]> wrote: > Rajith, try giving maven a run. There you may find like I do that this > occurs: > > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:compile] > Compiling 76 source files to C:\dev\ApacheProjects\Qpid-clean\ > [INFO] ------------------------------------------------------- > [ERROR] BUILD FAILURE > [INFO] ------------------------------------------------------- > [INFO] Compilation failure > > Failure executing javac, but could not parse the error: > > > The system is out of resources. > Consult the following stack trace for details. > java.lang.OutOfMemoryError: Java heap space > > > Also if you do a stack trace dump (kill -3) then you will see that the > probably cause is the ~200 Dispatcher Threads that are kicking about. > > I would recommend adding this profile to the top level pom: > <!--- Build profile to ignore test failures. --> > <profile> > <id>ignore</id> > <properties> > <maven.test.failure.ignore>true</maven.test.failure.ignore> > <maven.test.error.ignore>true</maven.test.error.ignore> > </properties> > </profile> > </profiles> > > so you can do > mvn -Pignore > > that way you can get past any failures. So far today I haven't manged > to get the run to complete without it OOME on me. > > On 28/02/2008, Rajith Attapattu <[EMAIL PROTECTED]> wrote: > > On Thu, Feb 28, 2008 at 4:52 AM, Aidan Skinner <[EMAIL PROTECTED]> wrote: > > > > > On Wed, Feb 27, 2008 at 8:15 PM, Rajith Attapattu <[EMAIL PROTECTED] > > > > > wrote: > > > > > > > The remaining test failures were there before the destination > > > changes. (I > > > > am working on getting them resolved as well) > > > > > > Can we *please*, *please* make sure that all the tests on trunk pass > > > before anybody checks in? I'm working on making the merged code base > > > pass all it's tests and random test failures make this exceptionally > > > difficult. > > > > > > > > > Aidan, now the trunk has zero test failures. Arnaud has made a fix for > the > > last remaining failure identified by QPID-817. > > > > > > Rajith > > > > > > > > > Thanks, > > > > > > - Aidan > > > -- > > > aim/y!:aidans42 g:[EMAIL PROTECTED] > > > http://aidan.skinner.me.uk/ > > > "We belong to nobody and nobody belongs to us. We don't even belong > to > > > each other." > > > > > > > > > > > > > -- > > > > Regards, > > > > Rajith Attapattu > > Red Hat > > blog: http://rajith.2rlabs.com/ > > > > > -- > Martin Ritchie > -- Regards, Rajith Attapattu Red Hat blog: http://rajith.2rlabs.com/
