I imagine that that is already enough memory for that. However, I don't know anything specific to the Mac server that would make that hungrier than any other system. Perhaps you could check that the sun implementation of java is installed on the mac. Sun's (Oracle's) jdk fares better than the open jdk.
Check out this thread, I found some potentially useful things to try. http://www.mail-archive.com/[email protected]/msg50655.html I would imagine the file to look into would be [dspace-source]/dspace/pom.xml at around line 529. Adding the argument to specify the memory to maven during the packaging. <build> <plugins> <!-- overall project assembly --> <plugin> <artifactId>maven-assembly-plugin</artifactId> <version>2.2-beta-1</version> <configuration> <argLine>-Xmx1024m</argLine> <descriptors> <descriptor>src/assemble/assembly.xml</descriptor> </descriptors> </configuration> Lastly, see if it works if you specify the memory limit to be as much as your system max. I do agree that it is unusual to need so much memory just for compilation though. Peter Dietz Systems Developer/Engineer Ohio State University Libraries On Tue, Apr 20, 2010 at 6:40 PM, Avarca, Anthony <[email protected]> wrote: > java.lang.OutOfMemoryError: Java heap space
------------------------------------------------------------------------------
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
