Well, so far we are having problem with lower java heap size for largeCodeGen test only.  For largeCodeGen, heap size needs to be increased as follows:
 
- For framework embedded, simply need to change largeCodeGen_app.properties. So there is no problem with this scenario.
- For framework DerbyNetClient, jvm heap size needs to be changed while starting Network Server as well. Now we can not change the property file or code for Network Server as the change will get applicable to Network Server while running it for all other tests. Therefore, there has to be a way to pass -Djvmflags property while calling RunSuite and/or RunTest with java command. This passing jvmflags works ok while running RunTest, but it does not work while running RunSuite. Basically it looks like RunSuite needs to be modified so it properly parses -Djvmflags property.
 
Thanks, Raman
 
On 5/10/06, Myrna van Lunteren <[EMAIL PROTECTED]> wrote:
On 5/10/06, Ramandeep Kaur <[EMAIL PROTECTED] > wrote:
Hi All,
 
[snip]
 
1. jvm heap size need to be increased while running test case lang/largeCodeGen.java  which is easy to do in case of framework "embedded" as the change can be made to largeCodeGen_app.properties file.
In case of DerbyNetClient, java heap size need to be increased while starting Network Server as well which can be done by giving -Djvmflags="-mx512M -ms512M" while running lang/largeCodeGen.java test case individually with RunTest class. However while running lang/largeCodeGen.java as part of suite largeData with RunSuite class, -Djvmflags="-mx512M -ms512M" can not be given as command line as RunSuite does not parse this flag properly and does not pass it to RunTest properly. Now, if we change NetworkServer.java class to increase jvm heap size, it will be increased for all the test cases. I already have a JIRA bug open ( http://issues.apache.org/jira/browse/DERBY-1091 ) to fix jvmflags parsing problem.
 
 
I may be misunderstanding the problem, so this is to confirm - do you want to run all tests in the suite largeDataTests with these jvmflags?
 
As a workaround, does it work to have these jvmflags in every tests' _app.properties file?
 
Myrna
 
 



--
Ramandeep Kaur
[EMAIL PROTECTED]

Reply via email to