4 Replies Latest reply on Jan 29, 2003 4:48 PM by Brett Finnell

    Build Fail/Hang JBoss_3_0_4 jboss-3.0

    Scott Clasen Newbie

      I am trying to build from CVS, and I am having various trouble.

      I do a checkout as suggested in an earlier form post.

      cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/jboss co -r JBoss_3_0_4 jboss-3.0

      This succeeds.

      Then

      ./build/build.sh init

      succeeds.

      Then if I do a build with default local.properties

      ./build/build.sh

      I get some wierd errors like this (full build output attached as sunjavac.txt, with init.verbose)

      [javac] Compiling 454 source files to /home/users/fd99tlc/jboss/workspace/jboss-3.0/jmx/output/classes
      [execmodules] error: compiler message file broken: key=compiler.err.sun.io.MalformedInputException arguments=null, null, n
      ull, null, null, null, null
      [execmodules] error: compiler message file broken: key=compiler.err.sun.io.MalformedInputException arguments=null, null, n
      ull, null, null, null, null
      [execmodules] /home/users/fd99tlc/jboss/workspace/jboss-3.0/jmx/src/main/org/jboss/mx/capability/DispatcherFactory.java:70
      : cannot resolve symbol
      [execmodules] symbol : method create (javax.management.MBeanInfo,java.lang.Object)


      If I do a ./build/build.sh clean
      and switch to jikes in local.properties
      then ./build/build.sh

      I get different behavior, where xdoclet just hangs(full output attached as jikes.txt) at the below output.


      compile-mbean-sources:
      [mkdir] Created dir: /home/users/fd99tlc/jboss/workspace/jboss-3.0/system/output/gen-src
      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] Generating output for 'org.jboss.deployment.cache.DeploymentCache' using template file 'jar:file:/home/users/fd99tlc/jboss/workspace/jboss-3.0/tools/lib/xdoclet.jar!/xdoclet/jmx/mbean.j'.
      .....Hang indefinitely......

      Any Ideas What is going on here??
      Thanks
      Scott Clasen

        • 1. Re: Build Fail/Hang JBoss_3_0_4 jboss-3.0
          Juha Lindfors Master

          Hmm, what version of sun compiler is that? Smells like a compiler bug...

          • 2. Re: Build Fail/Hang JBoss_3_0_4 jboss-3.0
            Scott Clasen Newbie

            I upgraded the sun compiler from 1.3.1_03 to 1.3.1_06 and that fixed the compiler error, but now I am getting the same behavior with both sun javac and jikes.

            When I run

            ./build/build.sh

            I get up to the 'compile-mbean-sources' task and then hang here

            init:

            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] Generating output for 'org.jboss.deployment.cache.DeploymentStore' using template file 'jar:file:/home/users/fd99tlc/jboss/workspace/jboss-3.0/tools/lib/xdoclet.jar!/xdoclet/jmx/mbean.j'.
            [xdoclet] Generating output for 'org.jboss.deployment.cache.FileDeploymentStore' using template file 'jar:file:/home/users/fd99tlc/jboss/workspace/jboss-3.0/tools/lib/xdoclet.jar!/xdoclet/jmx/mbean.j'.

            ...Hangs here indefinitely.....


            Any Ideas?

            Thanks!
            SC

            • 3. Re: Build Fail/Hang JBoss_3_0_4 jboss-3.0
              Juha Lindfors Master

              Don't know why it hangs.. sometimes running xdoclet can eat up alot of memory so you need to set your max heap bigger than the default but you usually see this as an OutOfMemoryError.

              • 4. Re: Build Fail/Hang JBoss_3_0_4 jboss-3.0
                Brett Finnell Newbie

                I had a similar problem with the "compiler message file broken" errors while building the sources using the Sun JDK version 1.3.1_06 on a RedHat 8.0 distribution.

                Apparently, Red Hat changed the default locale from en_US to en_US.UTF-8 in 8.0 which seemed to break my build. I set my LANG environment variable back to en_US and tried building and didn't get any of the errors again. It might be worth a try for you.

                Hope this helps
                - Brett