THANKS! NOTE: I don't see that in the summary of changes for 1.3, and I truly question the default being true!
Please, developers need more detail in the summary of changes from release to release. If when I create stubs I see a 60x slowdown, (10 seconds to 600 seconds), that's a rather significant change, wouldn't everyone agree? On 9/28/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote: > > to stop pretty print you can use axis2.jalopy system variable. (set it to > false i.e -Daxis2.jalopy=false) > > Now it is change to pritty print only if it is given as - > Daxis2.jalopy=true. > > Amila. > > On 9/26/07, John G. Norman <[EMAIL PROTECTED]> wrote: > > > > I also am seeing extraordinary time generating stubs: From 15 minutes to > > 10+. > > > > My machine has 3 GB RAM, and the memory allocation to javac is ample. > > > > This use of jalopy without telling users is pretty horrible. It looks to > > me like it might have pretty-printed my whole project, so now everything's > > out of sync with my subversion repository. > > > > WHY would anyone do that!? > > > > On 9/24/07, Jake Goulding <[EMAIL PROTECTED]> wrote: > > > > > > Martin: > > > > > > I'm not quite sure what Tomcat has to do with generating the Java > > > stubs > > > from the WSDL. However, I did assign more memory to the java process > > > with -Xmx1500m (in the script wrapper that wsdl2java.sh calls). This > > > did > > > not improve performance at all. > > > > > > At this point, I'm quite sure it was the automatic code formatting > > > done > > > by jalopy, as Dims suggested. Removing the jalopy jar from the axis2 > > > libs folder caused my previous build of 6 files to take minutes, > > > compared to a few hours with it. > > > > > > -Jake > > > > > > Martin Gainty wrote: > > > > Hi Jake- > > > > > > > > I used to have the same performance issues until I bumped Physical > > > RAM from > > > > 2MB to 4MB > > > > > > > > and I also set these JAVA_OPTS to use 256MB (min) and 512MB (max) > > > for TOMCAT > > > > -Xms256m -Xmx512m -XX:MaxPermSize=512m -XX:+PrintGCDetails > > > -XX:+UseConcMarkS > > > > weepGC -XX:+CMSPermGenSweepingEnabled -XX:+CMSClassUnloadingEnabled > > > > > > > > start tomcat with JAV_OPTS > > > > $CATALINA_HOME/bin/java %JAVA_OPTS% -jar bootstrap.jar > > > > > > > > HTH/ > > > > Martin-- > > > > ----- Original Message ----- > > > > From: "Jake Goulding" < [EMAIL PROTECTED]> > > > > To: < [email protected]> > > > > Sent: Monday, September 24, 2007 2:50 PM > > > > Subject: Re: [axis2-1.3] wsdl2java takes forever - unbearably long > > > > > > > > > > > >> Martin: > > > >> > > > >> I have 2GB on my desktop. I also ran the process on another Linux > > > >> machine that has 4GB and a Windows machine with 6GB. All 3 machines > > > were > > > >> slow. > > > >> > > > >> -Jake > > > >> > > > >> Martin Gainty wrote: > > > >>> Jake-- > > > >>> > > > >>> Have much RAM do you have? > > > >>> > > > >>> M-- > > > >>> ----- Original Message ----- > > > >>> From: "Davanum Srinivas" < [EMAIL PROTECTED] > > > > >>> To: <[email protected]> > > > >>> Sent: Friday, September 21, 2007 8:50 PM > > > >>> Subject: Re: [axis2-1.3] wsdl2java takes forever - unbearably long > > > > > > >>> > > > >>> > > > >>>> please delete the jalopy.jar and try again. > > > >>>> > > > >>>> thanks, > > > >>>> dims > > > >>>> > > > >>>> On 9/21/07, Jake Goulding < [EMAIL PROTECTED]> wrote: > > > >>>>> I am upgrading from Axis2 1.1.1 to 1.3, and rebuilding my Java > > > stubs > > > > is > > > >>>>> taking forever. > > > >>>>> > > > >>>>> This is the command I am running: > > > >>>>> > > > >>>>> ../bin/wsdl2java.sh -s -p com.vivisimo.connector.sharepoint2007-uri > > > >>>>> sharepoint2007/SiteData.wsdl > > > >>>>> > > > >>>>> the WSDL file is attached. Can someone please explain what is > > > taking > > > > so > > > >>>>> long for these files? > > > >>>>> > > > >>>>> With 1.1.1, there was nowhere near this amount of time taken, > > > maybe > > > > 5-15 > > > >>>>> seconds. With 1.3, my processor has been spinning for over 15 > > > minutes > > > > at > > > >>>>> 100% CPU, and 450+ MB of resident memory. > > > >>>>> > > > >>>>> Things do not appear to be deadlocked, as if I let it sit, java > > > files > > > >>>>> eventually get produced. > > > >>>>> > > > >>>>> -Jake > > > >>>>> > > > >>>>> > > > >>>>> > > > --------------------------------------------------------------------- > > > >>>>> To unsubscribe, e-mail: [EMAIL PROTECTED] > > > >>>>> For additional commands, e-mail: [EMAIL PROTECTED] > > > >>>>> > > > >>>>> > > > >>>> -- > > > >>>> Davanum Srinivas :: http://davanum.wordpress.com > > > >>>> > > > >>>> > > > --------------------------------------------------------------------- > > > >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] > > > >>>> For additional commands, e-mail: [EMAIL PROTECTED] > > > >>>> > > > >>>> > > > >>> > > > >>> > > > --------------------------------------------------------------------- > > > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > > > >>> For additional commands, e-mail: [EMAIL PROTECTED] > > > >>> > > > >>> > > > >> > > > --------------------------------------------------------------------- > > > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > > > >> For additional commands, e-mail: [EMAIL PROTECTED] > > > >> > > > >> > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > -- > Amila Suriarachchi, > WSO2 Inc.
