You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org> on 2007/01/18 11:49:29 UTC

[jira] Created: (QPID-302) Management console Eclipse plug-in grabbing 100% CPU

Management console Eclipse plug-in grabbing 100% CPU
----------------------------------------------------

                 Key: QPID-302
                 URL: https://issues.apache.org/jira/browse/QPID-302
             Project: Qpid
          Issue Type: Bug
          Components: Java Client
    Affects Versions: M1
            Reporter: Marnie McCormack
            Priority: Minor
             Fix For: M2


User reported:

Possible management console bug - if you stop the broker with the Eclipse manager open, the Eclipse process grabs 100% CPU and stays there.
Once you reconnect CPU drops back down.

Sounds like the mgt plug-in might be thrashing when the broker connection is down ?


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Resolved: (QPID-302) Management console Eclipse plug-in grabbing 100% CPU

Posted by "Bhupendra Bhardwaj (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bhupendra Bhardwaj resolved QPID-302.
-------------------------------------

    Resolution: Fixed
      Assignee: Bhupendra Bhardwaj

Console now sleeps for few seconds if there are no servers connected. 

> Management console Eclipse plug-in grabbing 100% CPU
> ----------------------------------------------------
>
>                 Key: QPID-302
>                 URL: https://issues.apache.org/jira/browse/QPID-302
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: M1
>            Reporter: Marnie McCormack
>         Assigned To: Bhupendra Bhardwaj
>            Priority: Minor
>             Fix For: M2
>
>
> User reported:
> Possible management console bug - if you stop the broker with the Eclipse manager open, the Eclipse process grabs 100% CPU and stays there.
> Once you reconnect CPU drops back down.
> Sounds like the mgt plug-in might be thrashing when the broker connection is down ?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.