• Icon: Bug Bug
    • Resolution: Can't Do
    • Icon: Major Major
    • 12.21.2.AM1
    • 8.1.0.GA
    • usage
    • None
    • NEW

      Seems like there's a lot of querying to check if Usage Reporting is enabled. Not sure why it's taking so long, or why it needs to ask so many times. I've disabled Usage Reporting, so I would assume it would come back fast when it's set to No.

      This is something I usually ignore, but is problem-some when the clients keep pointing out how slow JBDS is because of this.

        1. Capture4.PNG
          Capture4.PNG
          28 kB
        2. Capture3.PNG
          Capture3.PNG
          140 kB
        3. Capture2.PNG
          Capture2.PNG
          81 kB
        4. Capture.PNG
          Capture.PNG
          14 kB

            [JBDS-3882] Too much querying if Usage Reporting is enabled

            Yes, please do a thread dump.
            It's OK to have many queries when plugins are being started. But it looks likes something is blocking them. Anyway it should not slow eclipse down at all. All requests are made in separate jobs and they do very little job: just check preferences and system variables.

            Alexey Kazakov added a comment - Yes, please do a thread dump. It's OK to have many queries when plugins are being started. But it looks likes something is blocking them. Anyway it should not slow eclipse down at all. All requests are made in separate jobs and they do very little job: just check preferences and system variables.

            Fred Bricon added a comment -

            Can you please do a thread dump when all these threads are stuck? (jstack is your friend)

            Fred Bricon added a comment - Can you please do a thread dump when all these threads are stuck? (jstack is your friend)

              jmaury@redhat.com Jeff MAURY
              stran@redhat.com Steve Tran
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: