While doing a build clean build deploy on a component (that has around 100 xsd and 5 wsdl), I am always getting Memory Out Of Space Error -XX:PermSize. Googling the error gave me a command to increase the maxPermSize and I have increased it to 2048. But the error persists.
Before accessing whether Maven would help, you need to understand more about the error. Maven wouldn't help directly as Ant isn't giving the error, something it is calling is. I say directly because using Maven might force you to restructure your project into smaller ones. Which could help. You could do that in Ant too.
What part of your build is throwing the out of memory error? Compiling? Running a web services tasks? Be specific.
Are you sure that you increased the correct perm size? It could be that Ant is still using the default value.
What have you done to verify that Ant picked up the correct perm size? For example, have you looked at garbage collection data to verify the perm size? Have to looked at the command line used to run the java process hosting Ant to ensure that the command line has the perm size set? Have you used a Java monitoring tool, such as VirtualVM, to see what Ant's perm size is set to?
Hi Peter - Searching on the web about this type of error gave me the command to set maxpermsize. I did give an echo in the build.bat file to see whether the permsize have been modified for that instance of build, and it did change. I have not been able to check all the things that you have kindly noted in your response, but I did try managing some of the Virtual memory of the Windows XP.
Hi Jeanne - It is the web services part which is throwing an error
Interesting part (at least for me) - I have managed to build the same component (without any modifications to any of the windows properties) successfully in a different desktop and a laptop. Configurations are different though!
The goal is accomplished, which was to build and get the required dependencies in place. I am keen to know/assist to know how a fix/resolution can be achieved.