Good. Do they also know about the problem parsing '\u0000' ? Or that when a parse problem occurs it hangs the build... which sucks, as the compiler can *sometimes* do a better job of informing where the problem was.
--jason On Saturday 25 May 2002 10:01 pm, Andreas Schaefer wrote: > Hi Jason > > On the XDoclet dev mailing list they are already talking > about this problem. Didn't follow this discussion but > I think they are aware of that problem. > > Andy > > ----- Original Message ----- > From: "Jason Dillon" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]>; "Matthew Tippett" > <[EMAIL PROTECTED]> > Sent: Saturday, May 25, 2002 9:57 PM > Subject: Re: [JBoss-dev] Build not working on Linux? > > > What is XDoclet doing with so many threads? > > > > --jason > > > > On Saturday 25 May 2002 09:30 pm, Matthew Tippett wrote: > > > Technically speaking the docset is not 'too big', it is simply causes > > > too many native threads to be created for most 'default' Linux > > > distributions. > > > > > > Run the sample program and you should with a Linux 2.4 system get > > > around 220ish threads. The options without the change are as follows. > > > > > > o Use build.compiler=classic (which kicks the JVM into green > > > threads which doesn't have a 'real' thread limit. > > > o Set ulimit -u to greater around 1024 > > > o Modify /etc/security/limits.conf and nprocs to something > > > around 1024 > > > > > > So the 'fix' is a workaround. (Probably is the best solution for the > > > moment, but it isn't a bug in the code, more so a configuration problem > > > in the standard configuration of Linux distributions. > > > > > > Just thought people might be interested (I spent about 2 hours > > > attempting to get my first CVS build running when I came across this > > > problem :). > > > > > > Regards, > > > > > > Matthew 'The new developer on the block' Tippett > > > > > > Francisco Reverbel wrote: > > > > Found the cause: a recent change on server/build.xml made xdoclet > > > > to be called on a fileset too big (name="**/*.java"). > > > > > > > > I will revert the change. But it is strange that nobody else saw > > > > this... I have tried two Linux machines (a laptop with 128M and a > > > > box with 384M) with the same result: xdoclet barfed on the big > > > > fileset. Maybe there is something in my Linux environment that made > > > > me run out of memory before anybody else. > > > > > > > >>leset> > > > >>Running xdoclet.XDocletMain loaded by > > > >>sun.misc.Launcher$AppClassLoader. Forked:\ > > > >>true > > > >> [xdoclet] Running <mbeanInterface/> > > > >> [xdoclet] java.lang.OutOfMemoryError: unable to create new native > > > >> thread > > > > _______________________________________________________________ > > > > Don't miss the 2002 Sprint PCS Application Developer's Conference > > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > > > _______________________________________________ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
