From 7a242f24ac75ad73e40f0e26da20302234518e1f Mon Sep 17 00:00:00 2001 From: riniangreani Date: Mon, 20 Feb 2012 06:56:23 +0000 Subject: [PATCH] Added section for memory requirements for app-schema online tests. git-svn-id: https://svn.codehaus.org/geoserver/trunk@16774 ef1d6e69-97e5-0310-af46-8a06194da32a --- .../developer/source/programming-guide/app-schema/index.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/en/developer/source/programming-guide/app-schema/index.rst b/doc/en/developer/source/programming-guide/app-schema/index.rst index b596a6f52d8..f30747588e8 100644 --- a/doc/en/developer/source/programming-guide/app-schema/index.rst +++ b/doc/en/developer/source/programming-guide/app-schema/index.rst @@ -48,6 +48,12 @@ To run online tests, enable the profile:: This profile enables the data reference set tests and offline tests to run online. Data reference set tests are online tests based on data and use cases from GeoScience Victoria. Each is explicit for a database type (Oracle and Postgis) and has a copy to run with joining enabled. The offline tests are configured to run online with joining through separate modules for each database: app-schema-oracle-test and app-schema-postgis-test. These modules are placeholders for pom.xml files containing database specific parameters. This makes it easy to identify when a test fails with a particular database when running from Maven/buildbot. + +Memory requirements +``````````````````` + +The online tests require more memory than usual, so specifying the usual -Dtest.maxHeapSize=256m is not enough. Specify --Dtest.maxHeapSize=1024m instead. + When the build is successful, you would see this in the "Reactor Summary":: [INFO] Application Schema Integration Online Test with Oracle Database SUCCESS [5:52.980s]