sailfin
  1. sailfin
  2. SAILFIN-1529

ANT setup command hangs forever.....

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Incomplete
    • Affects Version/s: 1.0
    • Fix Version/s: milestone 1
    • Component/s: build_system
    • Labels:
      None
    • Environment:

      Operating System: Linux
      Platform: All

    • Issuezilla Id:
      1,529
    • Tags:

      Description

      Hi,

      we are experiencing a new frequent error.
      The command

      ant -f setup-cluster.xml $(ARGS)

      hangs 25% of the times (for at least one service instance) when is used.
      This does not occur in all our clusters service instances, the majority is
      operating well.
      We are facing this problem on our 20 blade clusters running:

      SGCS v1 b60b

      BR

      Babbis

      1. console.txt
        103 kB
        e_karin
      2. killprocess.txt
        18 kB
        e_karin

        Activity

        Hide
        e_karin added a comment -

        Created an attachment (id=921)
        Console output of RPM installation

        Show
        e_karin added a comment - Created an attachment (id=921) Console output of RPM installation
        Hide
        e_karin added a comment -

        Created an attachment (id=922)
        Log of commands used

        Show
        e_karin added a comment - Created an attachment (id=922) Log of commands used
        Hide
        e_karin added a comment -

        Sorry, switched the file names and descriptions.

        Show
        e_karin added a comment - Sorry, switched the file names and descriptions.
        Hide
        e_karin added a comment -

        After a proposal from Naman in a mail, which said:

        I checked updated bug details in issue tracker and looks like it's failing due
        to memory problem. Have you tried by setting value for ANT_OPTS variable? Using
        this variable we can set heap size for ant.

        Please set ANT_OPTS value and try again(set ANT_OPTS=-Xmx1024m). Let me know on
        this. If it doesn't work then we need to look more into this.

        Regards,
        Naman

        Since we did'nt really think that the memory was the reason for the failure, we
        tested with the oposite, and set a lower value in ANT_OPTS.
        When set lower than 13 MB then we got a clear error:
        ...
        ..
        .
        jarpack-tasks:

        jar-unpack:
        [unpack200] Unpacking with Unpack200
        [unpack200] Source File :/opt/sailfin-v1-b60b/lib/toplink-essentials.jar.pack.gz
        [unpack200] Dest. File :/opt/sailfin-v1-b60b/lib/toplink-essentials.jar
        [delete] Deleting: /opt/sailfin-v1-b60b/lib/toplink-essentials.jar.pack.gz

        jarpack-tasks:

        jar-unpack:
        [unpack200] Unpacking with Unpack200
        [unpack200] Source File :/opt/sailfin-v1-b60b/lib/appserv-rt.jar.pack.gz
        [unpack200] Dest. File :/opt/sailfin-v1-b60b/lib/appserv-rt.jar

        BUILD FAILED
        /opt/sailfin-v1-b60b/setup-cluster.xml:171: The following error occurred while
        executing this line:
        /opt/sailfin-v1-b60b/setup-cluster.xml:221: The following error occurred while
        executing this line:
        /opt/sailfin-v1-b60b/setup-cluster.xml:849: The following error occurred while
        executing this line:
        /opt/sailfin-v1-b60b/setup-cluster.xml:1055: The following error occurred while
        executing this line:
        /opt/sailfin-v1-b60b/setup-cluster.xml:1067: The following error occurred while
        executing this line:
        java.lang.OutOfMemoryError: Java heap space

        Total time: 7 seconds

        So the default 64MB for the JVM seems to be high above the limit for running
        the command. The problem we have is that ant hangs the process, but from the
        above we see that a low memory problem exits ok with clear info.

        Show
        e_karin added a comment - After a proposal from Naman in a mail, which said: I checked updated bug details in issue tracker and looks like it's failing due to memory problem. Have you tried by setting value for ANT_OPTS variable? Using this variable we can set heap size for ant. Please set ANT_OPTS value and try again(set ANT_OPTS=-Xmx1024m). Let me know on this. If it doesn't work then we need to look more into this. Regards, Naman Since we did'nt really think that the memory was the reason for the failure, we tested with the oposite, and set a lower value in ANT_OPTS. When set lower than 13 MB then we got a clear error: ... .. . jarpack-tasks: jar-unpack: [unpack200] Unpacking with Unpack200 [unpack200] Source File :/opt/sailfin-v1-b60b/lib/toplink-essentials.jar.pack.gz [unpack200] Dest. File :/opt/sailfin-v1-b60b/lib/toplink-essentials.jar [delete] Deleting: /opt/sailfin-v1-b60b/lib/toplink-essentials.jar.pack.gz jarpack-tasks: jar-unpack: [unpack200] Unpacking with Unpack200 [unpack200] Source File :/opt/sailfin-v1-b60b/lib/appserv-rt.jar.pack.gz [unpack200] Dest. File :/opt/sailfin-v1-b60b/lib/appserv-rt.jar BUILD FAILED /opt/sailfin-v1-b60b/setup-cluster.xml:171: The following error occurred while executing this line: /opt/sailfin-v1-b60b/setup-cluster.xml:221: The following error occurred while executing this line: /opt/sailfin-v1-b60b/setup-cluster.xml:849: The following error occurred while executing this line: /opt/sailfin-v1-b60b/setup-cluster.xml:1055: The following error occurred while executing this line: /opt/sailfin-v1-b60b/setup-cluster.xml:1067: The following error occurred while executing this line: java.lang.OutOfMemoryError: Java heap space Total time: 7 seconds So the default 64MB for the JVM seems to be high above the limit for running the command. The problem we have is that ant hangs the process, but from the above we see that a low memory problem exits ok with clear info.
        Hide
        naman_mehta added a comment -

        As per the last email this issue is due to Hardware Problem/Setup. Nothing to do
        with build script. So marking as invalid and closing the same.

        Show
        naman_mehta added a comment - As per the last email this issue is due to Hardware Problem/Setup. Nothing to do with build script. So marking as invalid and closing the same.

          People

          • Assignee:
            naman_mehta
            Reporter:
            babbisx
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: