Thanks, Roger! In Maven's dump of properties used during the build, there were two which set PermGen size: untitled text:43: env.CATALINA_OPTS=-Xmx768m -XX:MaxPermSize=512m, untitled text:83: env.ANT_OPTS=-Xmx768m -XX:MaxPermSize=512m -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled, However, I didn't see any MVN_OPTS setting that value - or for that matter, any mention of MVN_OPTS in this log file. Worth looking at, perhaps? Best, Aron On Mon, Apr 1, 2013 at 12:18 PM, Roger Howard <rogerhoward@gmail.com> wrote: > Here you go - thanks! > > > On Mon, Apr 1, 2013 at 12:06 PM, Aron Roberts <aron@socrates.berkeley.edu> > wrote: >> >> Hi Roger, >> >> (Responding off-list ...) >> >> I didn't see that build log on your last response? Could you >> possibly send it to me again? Privately is fine - thanks! >> >> Aron >> >> On Mon, Apr 1, 2013 at 11:24 AM, Roger Howard <rogerhoward@gmail.com> >> wrote: >> > Hi Aron, >> > >> > Happy to share the -X build log - I sent it to Jesse directly... >> > attached it >> > here (as its not all that big) >> > >> > I started with the memory defaults as shown in the docs and tried >> > several >> > variations (to a max of Xmx2048/MaxPermSize=1024 and down to 512/128). >> > >> > Verified the settings are sticking by running env to see - running the >> > install as root, so setup the environmental variables in >> > /etc/profile.d/collectionspace.sh instead of a .bashrc, which was >> > probably >> > my only real deviation from the install guide, but "env" shows the >> > settings >> > so it should be good. >> > >> > -R >> > >> > >> > On Mon, Apr 1, 2013 at 11:03 AM, Aron Roberts >> > <aron@socrates.berkeley.edu> >> > wrote: >> >> >> >> Sorry, Roger, I missed seeing this part of your note, as well as >> >> Jesse's responses: >> >> >> >> > I tried a range of memory settings for -Xmx and -XX:MaxPermSize for >> >> > both >> >> > ANT_OPTS and MAVEN_OPTS to no avail. >> >> >> >> What were the highest settings you tried? You might start with the >> >> recommended settings in that Troubleshooting guide: >> >> >> >> export ANT_OPTS="-Xmx768m -XX:MaxPermSize=512m" >> >> export MAVEN_OPTS="-Xmx768m -XX:MaxPermSize=512m" >> >> >> >> Also, you might verify that those settings are present, in the >> >> environment of the user running the build. The '-X' debug log, as >> >> Jesse points out, would be very helpful as well. >> >> >> >> Aron >> >> >> >> On Mon, Apr 1, 2013 at 11:00 AM, Aron Roberts <aronroberts@gmail.com> >> >> wrote: >> >> > Hi Roger, >> >> > >> >> >> The gist is a Maven compilation error with >> >> >> services.authorization.jaxb >> >> >> ... >> >> >> java.lang.OutOfMemoryError: PermGen space >> >> > >> >> > This might also help: >> >> > >> >> > >> >> > >> >> > http://wiki.collectionspace.org/display/DOC/Troubleshooting+Installation+Problems#TroubleshootingInstallationProblems-MemoryerrorswhenrunningAnt%28ant%29orMaven%28mvn%29 >> >> > >> >> > Aron >> >> > >> >> > On Mon, Apr 1, 2013 at 9:36 AM, Roger Howard <rogerhoward@gmail.com> >> >> > wrote: >> >> >> Hi, >> >> >> >> >> >> I'm trying to complete a 3.2 installation on a CentOS VM and after >> >> >> resolving >> >> >> a number of minor hurdles (mostly involving network security and our >> >> >> proxy >> >> >> servers) I'm now stuck and wondering if anyone can offer a hand by >> >> >> peaking >> >> >> at a console log. I'm a longtime Linux user, competent developer, >> >> >> but >> >> >> Java >> >> >> (and Maven) aren't my thing. >> >> >> >> >> >> The gist is a Maven compilation error with >> >> >> services.authorization.jaxb; >> >> >> a >> >> >> partial log showing the beginning of the failure report (I used -X >> >> >> in >> >> >> the >> >> >> Maven command to provide a debug log I can send to anyone who can >> >> >> help): >> >> >> >> >> >> -- >> >> >> >> >> >> [INFO] Compiling 4 source files to >> >> >> /tmp/collectionspace-services/services/authority/jaxb/target/classes >> >> >> [INFO] ------------------------------------------------------------- >> >> >> [ERROR] COMPILATION ERROR : >> >> >> [INFO] ------------------------------------------------------------- >> >> >> [ERROR] 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: PermGen space >> >> >> >> >> >> -- >> >> >> >> >> >> I tried a range of memory settings for -Xmx and -XX:MaxPermSize for >> >> >> both >> >> >> ANT_OPTS and MAVEN_OPTS to no avail. >> >> >> >> >> >> Thanks for any help pushing me in the right direction, >> >> >> >> >> >> Roger Howard >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> Talk mailing list >> >> >> Talk@lists.collectionspace.org >> >> >> >> >> >> >> >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >> >> >> > >> > > >

On Mon, Apr 1, 2013 at 12:27 PM, I wrote: > In Maven's dump of properties used during the build, there were two > which set PermGen size:... > However, I didn't see any MVN_OPTS setting that value - or for that > matter, any mention of MVN_OPTS in this log file. Correction: there was a MAVEN_OPTS (not MVN_OPTS - my confusion) environment variable reported within these dumped properties, but this seemed to have only proxy-related settings, not memory settings; e.g. env.MAVEN_OPTS= -Dhttps.proxyHost=... -Dhttp.proxyHost=... -Dhttps.proxyPort=... -Dhttp.proxyPort=.., > > Best, > Aron > > > On Mon, Apr 1, 2013 at 12:18 PM, Roger Howard <rogerhoward@gmail.com> wrote: >> Here you go - thanks! >> >> >> On Mon, Apr 1, 2013 at 12:06 PM, Aron Roberts <aron@socrates.berkeley.edu> >> wrote: >>> >>> Hi Roger, >>> >>> (Responding off-list ...) >>> >>> I didn't see that build log on your last response? Could you >>> possibly send it to me again? Privately is fine - thanks! >>> >>> Aron >>> >>> On Mon, Apr 1, 2013 at 11:24 AM, Roger Howard <rogerhoward@gmail.com> >>> wrote: >>> > Hi Aron, >>> > >>> > Happy to share the -X build log - I sent it to Jesse directly... >>> > attached it >>> > here (as its not all that big) >>> > >>> > I started with the memory defaults as shown in the docs and tried >>> > several >>> > variations (to a max of Xmx2048/MaxPermSize=1024 and down to 512/128). >>> > >>> > Verified the settings are sticking by running env to see - running the >>> > install as root, so setup the environmental variables in >>> > /etc/profile.d/collectionspace.sh instead of a .bashrc, which was >>> > probably >>> > my only real deviation from the install guide, but "env" shows the >>> > settings >>> > so it should be good. >>> > >>> > -R >>> > >>> > >>> > On Mon, Apr 1, 2013 at 11:03 AM, Aron Roberts >>> > <aron@socrates.berkeley.edu> >>> > wrote: >>> >> >>> >> Sorry, Roger, I missed seeing this part of your note, as well as >>> >> Jesse's responses: >>> >> >>> >> > I tried a range of memory settings for -Xmx and -XX:MaxPermSize for >>> >> > both >>> >> > ANT_OPTS and MAVEN_OPTS to no avail. >>> >> >>> >> What were the highest settings you tried? You might start with the >>> >> recommended settings in that Troubleshooting guide: >>> >> >>> >> export ANT_OPTS="-Xmx768m -XX:MaxPermSize=512m" >>> >> export MAVEN_OPTS="-Xmx768m -XX:MaxPermSize=512m" >>> >> >>> >> Also, you might verify that those settings are present, in the >>> >> environment of the user running the build. The '-X' debug log, as >>> >> Jesse points out, would be very helpful as well. >>> >> >>> >> Aron >>> >> >>> >> On Mon, Apr 1, 2013 at 11:00 AM, Aron Roberts <aronroberts@gmail.com> >>> >> wrote: >>> >> > Hi Roger, >>> >> > >>> >> >> The gist is a Maven compilation error with >>> >> >> services.authorization.jaxb >>> >> >> ... >>> >> >> java.lang.OutOfMemoryError: PermGen space >>> >> > >>> >> > This might also help: >>> >> > >>> >> > >>> >> > >>> >> > http://wiki.collectionspace.org/display/DOC/Troubleshooting+Installation+Problems#TroubleshootingInstallationProblems-MemoryerrorswhenrunningAnt%28ant%29orMaven%28mvn%29 >>> >> > >>> >> > Aron >>> >> > >>> >> > On Mon, Apr 1, 2013 at 9:36 AM, Roger Howard <rogerhoward@gmail.com> >>> >> > wrote: >>> >> >> Hi, >>> >> >> >>> >> >> I'm trying to complete a 3.2 installation on a CentOS VM and after >>> >> >> resolving >>> >> >> a number of minor hurdles (mostly involving network security and our >>> >> >> proxy >>> >> >> servers) I'm now stuck and wondering if anyone can offer a hand by >>> >> >> peaking >>> >> >> at a console log. I'm a longtime Linux user, competent developer, >>> >> >> but >>> >> >> Java >>> >> >> (and Maven) aren't my thing. >>> >> >> >>> >> >> The gist is a Maven compilation error with >>> >> >> services.authorization.jaxb; >>> >> >> a >>> >> >> partial log showing the beginning of the failure report (I used -X >>> >> >> in >>> >> >> the >>> >> >> Maven command to provide a debug log I can send to anyone who can >>> >> >> help): >>> >> >> >>> >> >> -- >>> >> >> >>> >> >> [INFO] Compiling 4 source files to >>> >> >> /tmp/collectionspace-services/services/authority/jaxb/target/classes >>> >> >> [INFO] ------------------------------------------------------------- >>> >> >> [ERROR] COMPILATION ERROR : >>> >> >> [INFO] ------------------------------------------------------------- >>> >> >> [ERROR] 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: PermGen space >>> >> >> >>> >> >> -- >>> >> >> >>> >> >> I tried a range of memory settings for -Xmx and -XX:MaxPermSize for >>> >> >> both >>> >> >> ANT_OPTS and MAVEN_OPTS to no avail. >>> >> >> >>> >> >> Thanks for any help pushing me in the right direction, >>> >> >> >>> >> >> Roger Howard >>> >> >> >>> >> >> >>> >> >> _______________________________________________ >>> >> >> Talk mailing list >>> >> >> Talk@lists.collectionspace.org >>> >> >> >>> >> >> >>> >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>> >> >> >>> > >>> > >> >>

An update on this issue: Roger reported privately, earlier this afternoon, that he has resolved the java.lang.OutOfMemoryError: PermGen space issue he encountered when installing CollectionSpace 3.2.1: > The build is progressing - it's gone much further now than before.. looks > like I'm hitting another network/proxy issue now, but the Java compile > problems are gone. In sum, he identified that a separate shell script, to address proxy issues, had inadvertently displaced the memory-related settings in the MAVEN_OPTS environment variable. FYI, Aron