Announcement Announcement Module
Collapse
No announcement yet.
STS hangs when creating spring-osgi-bundle-archetype project Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • STS hangs when creating spring-osgi-bundle-archetype project

    STS is stuck at 10%, No disk operations nothing . Anybody else faced this issue ?

    Regards
    Sathya

  • #2
    Hi Sathya!

    Is this reproduceable on your machine? If so, I would like to ask you to send us some stack traces from STS while hanging. Run jps to get a list of all java processes running on your system. And then jstack on the specific process to print the stack, while your STS hangs. That would be great!

    Thanks!
    -Martin

    Comment


    • #3
      Hi Martin,
      Attached is the output from jstack. (Had to split the file in to two, because forum won't allow files larger than 20K).

      Below is last few lines in maven console (if it helps)
      Regards
      Sathya

      Comment


      • #4
        Hey Sathya!

        Thanks for the traces, they look fine. I think. Can you post some detailed steps to reproduce for me?
        Thanks!

        -Martin

        Comment


        • #5
          Martin,
          I use STS 2.6.0.SR1.

          Below is steps I followed.

          1. File->New->Other.. And choose Maven project
          2. Uncheck "Create a simple project(skip archetype selecion)" (if enabled ).
          3. Choose archetype spring-osgi-bundle-archetype (version 1.0.2, groupId: org.springframework.osgi).
          4. Enter other required details and click finish.

          Note that am working behind a firewall. I've configured STS preferences to setup proxy for http and https traffic and settings seem fine.

          Hope this helps.

          Regards
          Sathya

          Comment


          • #6
            On a home network, the error is a NullPointerException in STS. And in maven console,

            5/9/11 9:12:26 PM IST: [WARN] Failure to transfer org.apache.maven.plugins:maven-install-plugin/maven-metadata.xml from http://repo1.maven.org/maven2/ was cached in the local repository, resolution will not be reattempted until the update interval of maven-repo has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.maven.plugins:maven-install-plugin/maven-metadata.xml from/to maven-repo (http://repo1.maven.org/maven2/): connection timed out
            5/9/11 9:12:26 PM IST: [WARN] Failure to transfer org.apache.maven.plugins:maven-resources-plugin/maven-metadata.xml from http://repo1.maven.org/maven2/ was cached in the local repository, resolution will not be reattempted until the update interval of maven-repo has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.maven.plugins:maven-resources-plugin/maven-metadata.xml from/to maven-repo (http://repo1.maven.org/maven2/): connection timed out
            5/9/11 9:12:26 PM IST: [WARN] Failure to transfer org.apache.maven.plugins:maven-surefire-plugin/maven-metadata.xml from http://repo1.maven.org/maven2/ was cached in the local repository, resolution will not be reattempted until the update interval of maven-repo has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.maven.plugins:maven-surefire-plugin/maven-metadata.xml from/to maven-repo (http://repo1.maven.org/maven2/): connection timed out
            5/9/11 9:12:26 PM IST: [WARN] Failure to transfer org.apache.maven.plugins:maven-compiler-plugin/maven-metadata.xml from http://repo1.maven.org/maven2/ was cached in the local repository, resolution will not be reattempted until the update interval of maven-repo has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.maven.plugins:maven-compiler-plugin/maven-metadata.xml from/to maven-repo (http://repo1.maven.org/maven2/): connection timed out
            5/9/11 9:12:26 PM IST: [WARN] Failure to transfer org.apache.maven.plugins:maven-compiler-plugin/maven-metadata.xml from http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.maven.plugins:maven-compiler-plugin/maven-metadata.xml from central (http://repo1.maven.org/maven2): ConnectException
            5/9/11 9:12:26 PM IST: [WARN] Failure to transfer org.apache.maven.plugins:maven-compiler-plugin/maven-metadata.xml from http://repo1.maven.org/maven2/ was cached in the local repository, resolution will not be reattempted until the update interval of maven-repo has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.maven.plugins:maven-compiler-plugin/maven-metadata.xml from/to maven-repo (http://repo1.maven.org/maven2/): connection timed out
            5/9/11 9:12:26 PM IST: [WARN] Failure to transfer org.apache.maven.plugins:maven-compiler-plugin/maven-metadata.xml from http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.maven.plugins:maven-compiler-plugin/maven-metadata.xml from central (http://repo1.maven.org/maven2): ConnectException
            .

            So for now, I think am better off starting a simple archetype and manually add all dependencies ,

            Comment


            • #7
              Ok, I think the archetype available in the STS catalogs is outdated. When I tried creating the archetype from command line using "mvn archetype:generate" and chose 1.2.1 version of archetype and then imported the generated project in to STS, its working fine. Phew...

              Comment


              • #8
                Thanks for the tips. Very useful.


                ________________
                Los Angeles wedding DJ

                Comment

                Working...
                X