IvyDE
  1. IvyDE
  2. IVYDE-283

Helios and ivyDe resolve/startup issue

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.2.0.beta1
    • Fix Version/s: None
    • Component/s: workspace resolver
    • Labels:
    • Environment:

      apache-ivyde-2.2.0.201104250538-hudson-186
      ivy 2.2.0RC
      Helios sr2
      2 computer

      Description

      I'm having problem with ivyDE and Eclipse Helios Sr2. The problem is that the cpu is used 100% and the process is stuck, when resolved is runned. However I also get the problem when starting up eclipse
      It seems to happen when I have the same project checkout twice. I have looked inside the log file in .metadata, but I couldn´t find any error messages.I have all of the ivy-files inside the project. The setup is like the one in defect ivyde-256
      I have also tried it on 2 different machines, where one of them was a single core.

      1. jstack23.txt
        28 kB
        Kim
      2. jstack22.txt
        27 kB
        Kim
      3. jstack21.txt
        29 kB
        Kim
      4. jstack12.txt
        26 kB
        Kim
      5. jstack11.txt
        28 kB
        Kim
      6. job1.txt
        25 kB
        Kim
      7. job.txt
        26 kB
        Kim
      8. ivyresolveerror.JPG
        203 kB
        Kim
      9. ivy.xml
        9 kB
        Kim

        Activity

        Hide
        Nicolas Lalevée added a comment -

        You may have a similar issue to IVYDE-273. Some circular dependency not well handled.
        What does the ivy.xml of the project checkout twice look like ?

        Show
        Nicolas Lalevée added a comment - You may have a similar issue to IVYDE-273 . Some circular dependency not well handled. What does the ivy.xml of the project checkout twice look like ?
        Hide
        Kim added a comment - - edited

        Hi

        I don't understand the question

        What does the ivy.xml of the project checkout twice look like ?

        I have added my ivy.xml and that is the one I have checked out twice in 2 different eclipse projects. I don't belive that there is any recursive dependencies. Is there anyway to check this?
        Also this ivy.xml file works fine with latest ivyde release and eclipse galileo

        Show
        Kim added a comment - - edited Hi I don't understand the question What does the ivy.xml of the project checkout twice look like ? I have added my ivy.xml and that is the one I have checked out twice in 2 different eclipse projects. I don't belive that there is any recursive dependencies. Is there anyway to check this? Also this ivy.xml file works fine with latest ivyde release and eclipse galileo
        Hide
        Nicolas Lalevée added a comment -

        You're probably right, no circular dependency seems to be involved.

        What do you see in the Ivy console while the resolve is apparently stuck ?

        The stack of Eclipse would help knowing what is going on too. To do that, get the process id of Eclipse and run 'jstack PROCESSID' while you see the resolve taking 100% of the cpu. It would be great if you could attach here the output of that command.

        Show
        Nicolas Lalevée added a comment - You're probably right, no circular dependency seems to be involved. What do you see in the Ivy console while the resolve is apparently stuck ? The stack of Eclipse would help knowing what is going on too. To do that, get the process id of Eclipse and run 'jstack PROCESSID' while you see the resolve taking 100% of the cpu. It would be great if you could attach here the output of that command.
        Hide
        Kim added a comment -

        show eclipse resolving and cpu levels

        Show
        Kim added a comment - show eclipse resolving and cpu levels
        Hide
        Kim added a comment -

        stacktraces

        Show
        Kim added a comment - stacktraces
        Hide
        Kim added a comment -

        I have added a picture showing the progressbar inside eclipse, when it was stuck. I wasn't able to goto ivy console. The eclipse ui was completly stuck, which was similiar to the other experinces.

        I have attached 2 runs of capturing stackstraces. jstack11 and jstack12 is from the same crash, but taken at different times. This crash wasn't when ivy was resolving.

        jstack21, jstack22 and jstack23 is the same crash and it is this crash the screenshot is from.

        Show
        Kim added a comment - I have added a picture showing the progressbar inside eclipse, when it was stuck. I wasn't able to goto ivy console. The eclipse ui was completly stuck, which was similiar to the other experinces. I have attached 2 runs of capturing stackstraces. jstack11 and jstack12 is from the same crash, but taken at different times. This crash wasn't when ivy was resolving. jstack21, jstack22 and jstack23 is the same crash and it is this crash the screenshot is from.
        Hide
        Nicolas Lalevée added a comment -

        Thank you for the stacks. With a first quick look at it, I see that Eclipse is compiling... no much to worry about. I'll look deeper into it later.

        But by crashing, what do you mean ? Does Eclipse stop itself ? Do you have to manually force it to quit ? How long do you wait before killing it ?

        Show
        Nicolas Lalevée added a comment - Thank you for the stacks. With a first quick look at it, I see that Eclipse is compiling... no much to worry about. I'll look deeper into it later. But by crashing, what do you mean ? Does Eclipse stop itself ? Do you have to manually force it to quit ? How long do you wait before killing it ?
        Hide
        Kim added a comment - - edited

        By crashing I mean that the cpu is running at 100%, that the gui is unresponsive and windows says "no response" in window bar.
        The only way to recover is by killing eclipse from the task manager. I have been waiting a couple of minutes before killing it.

        It odd that you saying it is compiling, becuase in both cases the "build workspace" text wasn't showing, neither was the compiling progress bar.

        Do you think this is a eclipse problem. I have been using helios before but not on these 2 machines.

        Show
        Kim added a comment - - edited By crashing I mean that the cpu is running at 100%, that the gui is unresponsive and windows says "no response" in window bar. The only way to recover is by killing eclipse from the task manager. I have been waiting a couple of minutes before killing it. It odd that you saying it is compiling, becuase in both cases the "build workspace" text wasn't showing, neither was the compiling progress bar. Do you think this is a eclipse problem. I have been using helios before but not on these 2 machines.
        Hide
        Nicolas Lalevée added a comment - - edited

        Yes, it is compiling. Due to the UI freeze, Eclipse may not be able to update the progress bar accordingly.
        This still may be a bug in IvyDE stealing the UI thread while resolving. Maybe if you wait enough, it could be able to finish compiling and let the UI unfreeze.

        But I'll need more time to investigate deeper.

        Show
        Nicolas Lalevée added a comment - - edited Yes, it is compiling. Due to the UI freeze, Eclipse may not be able to update the progress bar accordingly. This still may be a bug in IvyDE stealing the UI thread while resolving. Maybe if you wait enough, it could be able to finish compiling and let the UI unfreeze. But I'll need more time to investigate deeper.
        Hide
        Kim added a comment - - edited

        Hi

        I have added another thread dumps job and job1. I'm no longer sure that it is ivyDE, it happends more frequently with ivyDE. It seems to be when alot of jobs need to be run such as initiliazing the different tools, ivyde resolve.

        I have tried running it for 15 minutes before killing it, but no progress was made.

        Show
        Kim added a comment - - edited Hi I have added another thread dumps job and job1. I'm no longer sure that it is ivyDE, it happends more frequently with ivyDE. It seems to be when alot of jobs need to be run such as initiliazing the different tools, ivyde resolve. I have tried running it for 15 minutes before killing it, but no progress was made.
        Hide
        Kim added a comment -

        I have made some progress. The problem is only for one of my projects the others are fine. The others are plain java project and the one which fails is a dynamic web project. I don't know if this is the reason or not, but I will try to investigate.

        Show
        Kim added a comment - I have made some progress. The problem is only for one of my projects the others are fine. The others are plain java project and the one which fails is a dynamic web project. I don't know if this is the reason or not, but I will try to investigate.
        Hide
        Kim added a comment -

        I believe I have found my problem. It works when I disable "Jax-ws DOM Runtime" in startup and shutdown in preferences. I don't know why, perhasp come kind of weird setup in the poject, because I have another project were it works fine.
        I have tried removing the ivyde container in the project and enabling "Jax-ws DOM Runtime" and the it works fine.

        To recap I have one project, Jax-ws DOM Runtime and ivyde all of these components together results in the problem.

        Show
        Kim added a comment - I believe I have found my problem. It works when I disable "Jax-ws DOM Runtime" in startup and shutdown in preferences. I don't know why, perhasp come kind of weird setup in the poject, because I have another project were it works fine. I have tried removing the ivyde container in the project and enabling "Jax-ws DOM Runtime" and the it works fine. To recap I have one project, Jax-ws DOM Runtime and ivyde all of these components together results in the problem.
        Hide
        Nicolas Lalevée added a comment -

        Thank you for your report. I'll try to setup a such project to reproduce the freeze and understand what is really going on.

        Show
        Nicolas Lalevée added a comment - Thank you for your report. I'll try to setup a such project to reproduce the freeze and understand what is really going on.
        Hide
        Kim added a comment -

        I have just tried indigo and the same result. When all 3 component is present it freezes, but turning "Jax-ws DOM Runtime" off and it works.

        My teory is that I have some xml documents inside the project which are causing this reaction, but I need to investigate further.

        Show
        Kim added a comment - I have just tried indigo and the same result. When all 3 component is present it freezes, but turning "Jax-ws DOM Runtime" off and it works. My teory is that I have some xml documents inside the project which are causing this reaction, but I need to investigate further.

          People

          • Assignee:
            Unassigned
            Reporter:
            Kim
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development