Re: [JBoss-dev] Build not working on Linux?
I think build.sh should try to setup the desired limits, perhaps run.sh should too. --jason Quoting Matthew Tippett <[EMAIL PROTECTED]>: > 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 > >> [xdoclet] java.lang.OutOfMemoryError: unable to create new native > thread > > > > -- > Matthew Tippett - [EMAIL PROTECTED] > Toronto, Canada - (416) 435-4118 > - This mail sent through IMP: http://horde.org/imp/ ___ 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
Re: [JBoss-dev] Build not working on Linux?
On Sun, 26 May 2002, 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. Not a real option, as some VMs (the newer ones) don't support green threads. > o Set ulimit -u to greater around 1024 Yes, this worked fine for me. Thanks! > o Modify /etc/security/limits.conf and nprocs to something > around 1024 In my system (Debian Woody) /etc/security/limits.conf is essentially empty (only has commented out example entries), so I guess this is the reason `ulimit -u 1024' worked for me without any change to limits.conf. > 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 :). This sounds like an argument for the fix/workaround/whatever. It shouldn't be this hard to build and run the CVS code! (Yesterday I had just a couple of hours for some JBoss hacking and also spent them on the xdoclet error...) Cheers, Francisco ___ 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
Re: [JBoss-dev] Build not working on Linux?
Thanks for your reply, Jason. > Eventually we will have everything listed... in fact we have a similar include > for the javac task, so perhaps XDoclet needs to be fixed to not cache so much > data at one (or whatever). Yes. > Have you tried increasing the heap for the vm used to build? I would prefer > that local fix to this global one. > > JAVA_OPTS="-X128m" build/build.sh I have, but still got OutOfMemoryError. (Had to say "-Xms128m -Xmx128m", though. The 1.3 VM doesn't recognize "-X128m as an option. And with just "-Xms128m" it complains about incompatible initial and max heap sizes.) Best, Francisco ___ 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
Re: [JBoss-dev] Build not working on Linux?
Good. Do they also know about the problem parsing '\u' ? 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 > > > >> [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
Re: [JBoss-dev] Build not working on Linux?
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 > > >> [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
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 > >> [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
Re: [JBoss-dev] Build not working on Linux?
Maybe this is the reason that the build has been barfing on MacOS X as
well.
I've been getting the same problem that Scott Stark mentioned yesterday,
but it is not very deterministic.
ie. yesterday's CVS checkout stops in a different place to today's CVS
checkout.
It's not difficult to imagine low memory somehow mapping to a
FileNotFound exception (which is what is causing the
IllegalStateException on MacOS X) somewhere in the JVM implementation.
On Sunday, May 26, 2002, at 02: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 mademe run out of memory
>> before anybody else.
> >
> >
>>> leset>
>>> Running xdoclet.XDocletMain loaded by
>>> sun.misc.Launcher$AppClassLoader. Forked:\
>>> true
>>> [xdoclet] Running
>>> [xdoclet] java.lang.OutOfMemoryError: unable to create new native
>>> thread
>
>
>
> -- Matthew Tippett - [EMAIL PROTECTED]
> Toronto, Canada - (416) 435-4118
>
> public class TestThread extends Thread {
>
> public static void main(String argv[]) {
>
> int i=0;
> while(true) {
> TestThread thread = new TestThread();
> try {
> thread.start();
> } catch (Throwable e) {
> System.out.println("Maximum number of threads is
> "+Thread.activeCount());
> System.exit(-1);
> }
> }
> }
>
> public void run() {
> while (true) {
> try {
> sleep(1);
> } catch (Exception e) {
> }
> }
> }
> }
___
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
Re: [JBoss-dev] Build not working on Linux?
- Original Message - From: "Matthew Tippett" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, May 25, 2002 9:30 PM Subject: Re: [JBoss-dev] Build not working on Linux? > 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. > Well, this change also fixed the IllegalStateException I was seeing on OSX so I'm not sure there is not an issue passing this many files to xdoclet. Scott Stark Chief Technology Officer JBoss Group, LLC ___ 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
Re: [JBoss-dev] Build not working on Linux?
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
>> [xdoclet] java.lang.OutOfMemoryError: unable to create new native thread
--
Matthew Tippett - [EMAIL PROTECTED]
Toronto, Canada - (416) 435-4118
public class TestThread extends Thread {
public static void main(String argv[]) {
int i=0;
while(true) {
TestThread thread = new TestThread();
try {
thread.start();
} catch (Throwable e) {
System.out.println("Maximum number of threads is "+Thread.activeCount());
System.exit(-1);
}
}
}
public void run() {
while (true) {
try {
sleep(1);
} catch (Exception e) {
}
}
}
}
Re: [JBoss-dev] Build not working on Linux?
I have had no problems building on Linux with 1.3.1 and 1.4, though my laptop has 512, but that should not matter really. Eventually we will have everything listed... in fact we have a similar include for the javac task, so perhaps XDoclet needs to be fixed to not cache so much data at one (or whatever). I changed this because I was in the process of moving more stuff to use XDoclet generated MBeans and did not want to keep maintaining the list of files to included. Have you tried increasing the heap for the vm used to build? I would prefer that local fix to this global one. JAVA_OPTS="-X128m" build/build.sh Or whatever you want for -X, and to make sure it really works: ANT_DEBUG=true JAVA_OPTS="-X128m" build/build.sh Should show the java command line which is used. --jason On Saturday 25 May 2002 08:54 pm, 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. > > Cheers, > > Francisco > > On Sat, 25 May 2002, Francisco Reverbel wrote: > > Help! > > > > I am running build/build.sh on HEAD and Branch_3_0 trees just > > checked out from CVS. On both trees build fails within xdoclet: > > > > java.lang.OutOfMemoryError: unable to create new native thread > > > > (Branch 3.0 error included below.) > > > > Both Sun and IBM JDKs are giving me the same error. My config is: > > > > Linux pong 2.4.10 #1 Sun Oct 14 23:31:01 BRST 2001 i686 unknown > > > > Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03) > > Java HotSpot(TM) Client VM (build 1.3.1_03-b03, mixed mode) > > > > Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) > > Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20010626 (JIT > > enabled: jitc)) > > > > Is anybody else seeing this? > > > > Thanks, > > > > Francisco > > > > > > > >== > > == Executing 'most' in module 'server'... > > == > > > > _buildmagic:init: > > > > configure: > > > > init: > > > > generate-parsers: > > Target is already built - skipping > > (/home/reverbel/Branch_3_0/jboss-all/server/\ > > src/main/org/jboss/ejb/plugins/cmp/ejbql/JBossQLParser.jjt) > > Target is already built - skipping > > (/home/reverbel/Branch_3_0/jboss-all/server/\ > > src/main/org/jboss/ejb/plugins/cmp/ejbql/EJBQLParser.jjt) > > > > compile-bean-sources: > > sourcepath is deprecated. the preferred way to design sources is via > > nested > leset> > > Running xdoclet.XDocletMain loaded by > > sun.misc.Launcher$AppClassLoader. Forked:\ > > true > > [xdoclet] Running > > [xdoclet] Running > > [xdoclet] Running > > [xdoclet] Running > > [xdoclet] Running > > > > compile-mbean-sources: > > sourcepath is deprecated. the preferred way to design sources is via > > nested > leset> > > Running xdoclet.XDocletMain loaded by > > sun.misc.Launcher$AppClassLoader. Forked:\ > > true > > [xdoclet] Running > > [xdoclet] java.lang.OutOfMemoryError: unable to create new native > > thread [xdoclet] at java.lang.Thread.start(Native Method) > > [xdoclet] at xjavadoc.XJavaDoc.scanAndPut(XJavaDoc.java:562) > > [xdoclet] at xjavadoc.XJavaDoc.getXClass(XJavaDoc.java:393) > > [xdoclet] at xjavadoc.ProxyClass.resolve(ProxyClass.java:584) > > [xdoclet] at xjavadoc.ProxyClass.doc(ProxyClass.java:483) > > [xdoclet] at > > xdoclet.DocletSupport.isDocletGenerated(DocletSupport.java:2\ > > 69) > > [xdoclet] at > > xdoclet.TemplateSubTask.matchesGenerationRules(TemplateSubTa\ > > sk.java:633) > > [xdoclet] at > > xdoclet.TemplateSubTask.startProcess(TemplateSubTask.java:57\ > > 6) > > [xdoclet] at > > xdoclet.TemplateSubTask.execute(TemplateSubTask.java:488) [xdoclet] > > at xdoclet.XDocletMain.start(XDocletMain.java:54) [xdoclet] at > > xjavadoc.ant.XJavaDocMain.main(XJavaDocMain.java:94) > > > > Is anybody else seeing this? I am on Linux > > > > > > > > > > ___ > > > > 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 > > __
Re: [JBoss-dev] Build not working on Linux?
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. Cheers, Francisco On Sat, 25 May 2002, Francisco Reverbel wrote: > Help! > > I am running build/build.sh on HEAD and Branch_3_0 trees just > checked out from CVS. On both trees build fails within xdoclet: > > java.lang.OutOfMemoryError: unable to create new native thread > > (Branch 3.0 error included below.) > > Both Sun and IBM JDKs are giving me the same error. My config is: > > Linux pong 2.4.10 #1 Sun Oct 14 23:31:01 BRST 2001 i686 unknown > > Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03) > Java HotSpot(TM) Client VM (build 1.3.1_03-b03, mixed mode) > > Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) > Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20010626 (JIT > enabled: jitc)) > > Is anybody else seeing this? > > Thanks, > > Francisco > > > >== > == Executing 'most' in module 'server'... > == > > _buildmagic:init: > > configure: > > init: > > generate-parsers: > Target is already built - skipping > (/home/reverbel/Branch_3_0/jboss-all/server/\ > src/main/org/jboss/ejb/plugins/cmp/ejbql/JBossQLParser.jjt) > Target is already built - skipping > (/home/reverbel/Branch_3_0/jboss-all/server/\ > src/main/org/jboss/ejb/plugins/cmp/ejbql/EJBQLParser.jjt) > > compile-bean-sources: > sourcepath is deprecated. the preferred way to design sources is via nested > leset> > Running xdoclet.XDocletMain loaded by > sun.misc.Launcher$AppClassLoader. Forked:\ > true > [xdoclet] Running > [xdoclet] Running > [xdoclet] Running > [xdoclet] Running > [xdoclet] Running > > compile-mbean-sources: > sourcepath is deprecated. the preferred way to design sources is via nested > leset> > Running xdoclet.XDocletMain loaded by > sun.misc.Launcher$AppClassLoader. Forked:\ > true > [xdoclet] Running > [xdoclet] java.lang.OutOfMemoryError: unable to create new native thread > [xdoclet] at java.lang.Thread.start(Native Method) > [xdoclet] at xjavadoc.XJavaDoc.scanAndPut(XJavaDoc.java:562) > [xdoclet] at xjavadoc.XJavaDoc.getXClass(XJavaDoc.java:393) > [xdoclet] at xjavadoc.ProxyClass.resolve(ProxyClass.java:584) > [xdoclet] at xjavadoc.ProxyClass.doc(ProxyClass.java:483) > [xdoclet] at > xdoclet.DocletSupport.isDocletGenerated(DocletSupport.java:2\ > 69) > [xdoclet] at > xdoclet.TemplateSubTask.matchesGenerationRules(TemplateSubTa\ > sk.java:633) > [xdoclet] at > xdoclet.TemplateSubTask.startProcess(TemplateSubTask.java:57\ > 6) > [xdoclet] at xdoclet.TemplateSubTask.execute(TemplateSubTask.java:488) > [xdoclet] at xdoclet.XDocletMain.start(XDocletMain.java:54) > [xdoclet] at xjavadoc.ant.XJavaDocMain.main(XJavaDocMain.java:94) > > Is anybody else seeing this? I am on Linux > > > > > ___ > > 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
[JBoss-dev] Build not working on Linux?
Help! I am running build/build.sh on HEAD and Branch_3_0 trees just checked out from CVS. On both trees build fails within xdoclet: java.lang.OutOfMemoryError: unable to create new native thread (Branch 3.0 error included below.) Both Sun and IBM JDKs are giving me the same error. My config is: Linux pong 2.4.10 #1 Sun Oct 14 23:31:01 BRST 2001 i686 unknown Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03) Java HotSpot(TM) Client VM (build 1.3.1_03-b03, mixed mode) Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)) Is anybody else seeing this? Thanks, Francisco == == Executing 'most' in module 'server'... == _buildmagic:init: configure: init: generate-parsers: Target is already built - skipping (/home/reverbel/Branch_3_0/jboss-all/server/\ src/main/org/jboss/ejb/plugins/cmp/ejbql/JBossQLParser.jjt) Target is already built - skipping (/home/reverbel/Branch_3_0/jboss-all/server/\ src/main/org/jboss/ejb/plugins/cmp/ejbql/EJBQLParser.jjt) compile-bean-sources: sourcepath is deprecated. the preferred way to design sources is via nested Running xdoclet.XDocletMain loaded by sun.misc.Launcher$AppClassLoader. Forked:\ true [xdoclet] Running [xdoclet] Running [xdoclet] Running [xdoclet] Running [xdoclet] Running compile-mbean-sources: sourcepath is deprecated. the preferred way to design sources is via nested Running xdoclet.XDocletMain loaded by sun.misc.Launcher$AppClassLoader. Forked:\ true [xdoclet] Running [xdoclet] java.lang.OutOfMemoryError: unable to create new native thread [xdoclet] at java.lang.Thread.start(Native Method) [xdoclet] at xjavadoc.XJavaDoc.scanAndPut(XJavaDoc.java:562) [xdoclet] at xjavadoc.XJavaDoc.getXClass(XJavaDoc.java:393) [xdoclet] at xjavadoc.ProxyClass.resolve(ProxyClass.java:584) [xdoclet] at xjavadoc.ProxyClass.doc(ProxyClass.java:483) [xdoclet] at xdoclet.DocletSupport.isDocletGenerated(DocletSupport.java:2\ 69) [xdoclet] at xdoclet.TemplateSubTask.matchesGenerationRules(TemplateSubTa\ sk.java:633) [xdoclet] at xdoclet.TemplateSubTask.startProcess(TemplateSubTask.java:57\ 6) [xdoclet] at xdoclet.TemplateSubTask.execute(TemplateSubTask.java:488) [xdoclet] at xdoclet.XDocletMain.start(XDocletMain.java:54) [xdoclet] at xjavadoc.ant.XJavaDocMain.main(XJavaDocMain.java:94) Is anybody else seeing this? I am on Linux ___ 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
