[
https://issues.apache.org/jira/browse/QPID-7492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-7492:
-----------------------------
Description:
# Logging in occasionally fails with a 417 error response especially when
the browsers developer tools are open. This is probably due to a timeout in
SaslServlet (default 3000 ms).
# The memory log viewer grid in "Auto Refresh" mode has the "jumping page"
problem
# The BrokerLogbackSocket seems to have a default port (6000) but it needs
to be entered regardless.
# When using BrokerLogbackSocket and nothing is connected to it it waits
100ms for each log event to time out. When using DEBUG this brings the broker
to a crawl (e.g., broker startup ~ 4 minutes). I could imagine this also being
a problem when logging over a network. Could this also be a problem for other
loggers (e.g. Syslog?)
# Add Port dialogue does not have a scroll bar in case it does not
completely fit onto the screen. If the dialogue box resizes (e.g., by closing
the Developer Tools pane in IE) only the original part of the dialogue box has
a solid background. the newly exposed part is transparent.
# deletion of TrustStore displays the trust store name in the confirmation
dialogue as 'undefined'.
# add dialogue of AclFile type is wonky
# RuleBased ACL has no useful UI
# If the add Queue dialogue has a scrollbar the lower part (the one you have
to scroll to) is transparent. This applies to all addQueue dialogues.
# dialogue layout gets messed up when dialogue has to display a scrollbar
# dashboard browser has empty row where the query browser displays the query
type.
# the text elements in question/notification/warning-yellow.svg are not
centered correctly in IE. In chrome and FF only the warning-yellow.svg seems of
center.
was:
Logging in occasionally fails with a 417 error response especially when the
browsers developer tools are open. This is probably due to a timeout in
SaslServlet (default 3000 ms).
The memory log viewer grid in "Auto Refresh" mode has the "jumping page"
problem
The BrokerLogbackSocket seems to have a default port (6000) but it needs to
be entered regardless.
When using BrokerLogbackSocket and nothing is connected to it it waits
100ms for each log event to time out. When using DEBUG this brings the broker
to a crawl (e.g., broker startup ~ 4 minutes). I could imagine this also being
a problem when logging over a network. Could this also be a problem for other
loggers (e.g. Syslog?)
Add Port dialogue does not have a scroll bar in case it does not completely
fit onto the screen. If the dialogue box resizes (e.g., by closing the
Developer Tools pane in IE) only the original part of the dialogue box has a
solid background. the newly exposed part is transparent.
deletion of TrustStore displays the trust store name in the confirmation
dialogue as 'undefined'.
add dialogue of AclFile type is wonky
RuleBased ACL has no useful UI
If the add Queue dialogue has a scrollbar the lower part (the one you have
to scroll to) is transparent. This applies to all addQueue dialogues.
dialogue layout gets messed up when dialogue has to display a scrollbar
dashboard browser has empty row where the query browser displays the query
type.
the text elements in question/notification/warning-yellow.svg are not
centered correctly in IE. In chrome and FF only the warning-yellow.svg seems of
center.
> [Java Broker, WMC] Minor UI issues
> ----------------------------------
>
> Key: QPID-7492
> URL: https://issues.apache.org/jira/browse/QPID-7492
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-6.1
> Reporter: Alex Rudyy
>
> # Logging in occasionally fails with a 417 error response especially when
> the browsers developer tools are open. This is probably due to a timeout in
> SaslServlet (default 3000 ms).
> # The memory log viewer grid in "Auto Refresh" mode has the "jumping page"
> problem
> # The BrokerLogbackSocket seems to have a default port (6000) but it needs
> to be entered regardless.
> # When using BrokerLogbackSocket and nothing is connected to it it waits
> 100ms for each log event to time out. When using DEBUG this brings the broker
> to a crawl (e.g., broker startup ~ 4 minutes). I could imagine this also
> being a problem when logging over a network. Could this also be a problem for
> other loggers (e.g. Syslog?)
> # Add Port dialogue does not have a scroll bar in case it does not
> completely fit onto the screen. If the dialogue box resizes (e.g., by closing
> the Developer Tools pane in IE) only the original part of the dialogue box
> has a solid background. the newly exposed part is transparent.
> # deletion of TrustStore displays the trust store name in the confirmation
> dialogue as 'undefined'.
> # add dialogue of AclFile type is wonky
> # RuleBased ACL has no useful UI
> # If the add Queue dialogue has a scrollbar the lower part (the one you
> have to scroll to) is transparent. This applies to all addQueue dialogues.
> # dialogue layout gets messed up when dialogue has to display a scrollbar
> # dashboard browser has empty row where the query browser displays the
> query type.
> # the text elements in question/notification/warning-yellow.svg are not
> centered correctly in IE. In chrome and FF only the warning-yellow.svg seems
> of center.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
