qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lorenz Quack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-7172) HTTP Management threads are blocked by potentially long running operations
Date Thu, 31 Mar 2016 14:07:25 GMT

     [ https://issues.apache.org/jira/browse/QPID-7172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lorenz Quack updated QPID-7172:
-------------------------------
    Description: 
As an operator of the Broker using the Web Management Console, I can initiate operations such
as purge queue.  These operations may be long running.

When issuing a long running operation the user ought to get visual feedback that it is in
progress.  Later the user should be able to return and find out if the task is finished and
get the result.

Currently the operator may believe that the operation is 'stuck', and try the operation again,
or get a colleague to do the same.

Internally within the Java Broker, the web thread is blocked awaiting the operation on the
configuration thread.  If many such operations are in flight (or the operator retries an operation
in belief it is stuck), the web tier may become slow or unresponsive.


  was:
As an operator of the Broker using the Web Management Console, I can initiate operations such
as purge queue.  These operations may be long running.  Currently the browser hangs whilst
the operation is in progress.  If the operation takes a very long time the browser or an intermediate
proxy may timeout the connection.

The user ought to be able to initiate a long running operation than continue to work on other
tasks.  Later the user should be able to return and find out if the task is finished and get
the result.

Currently the operator may believe that the operation is 'stuck', and try the operation again,
or get a colleague to do the same.

Internally within the Java Broker, the web thread is blocked awaiting the operation on the
configuration thread.  If many such operations are in flight (or the operator retries an operation
in belief it is stuck), the web tier may become slow or unresponsive.



> HTTP Management threads are blocked by potentially long running operations
> --------------------------------------------------------------------------
>
>                 Key: QPID-7172
>                 URL: https://issues.apache.org/jira/browse/QPID-7172
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>            Reporter: Keith Wall
>
> As an operator of the Broker using the Web Management Console, I can initiate operations
such as purge queue.  These operations may be long running.
> When issuing a long running operation the user ought to get visual feedback that it is
in progress.  Later the user should be able to return and find out if the task is finished
and get the result.
> Currently the operator may believe that the operation is 'stuck', and try the operation
again, or get a colleague to do the same.
> Internally within the Java Broker, the web thread is blocked awaiting the operation on
the configuration thread.  If many such operations are in flight (or the operator retries
an operation in belief it is stuck), the web tier may become slow or unresponsive.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message