[jira] [Created] (DISPATCH-564) Error when switching routers on Entities page
Ernest Allen created DISPATCH-564: - Summary: Error when switching routers on Entities page Key: DISPATCH-564 URL: https://issues.apache.org/jira/browse/DISPATCH-564 Project: Qpid Dispatch Issue Type: Bug Components: Console Reporter: Ernest Allen Assignee: Ernest Allen Choosing a different router from the dropdown on the list page doesn't work. The information in the table doesn't change and there is a javascript error displayed in the browser's console window. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-564) Error when switching routers on Entities page
[ https://issues.apache.org/jira/browse/DISPATCH-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-564. --- Resolution: Fixed Fix Version/s: 0.8.0 > Error when switching routers on Entities page > - > > Key: DISPATCH-564 > URL: https://issues.apache.org/jira/browse/DISPATCH-564 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Reporter: Ernest Allen >Assignee: Ernest Allen > Fix For: 0.8.0 > > > Choosing a different router from the dropdown on the list page doesn't work. > The information in the table doesn't change and there is a javascript error > displayed in the browser's console window. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-565) Error fetching log on Entities page
Ernest Allen created DISPATCH-565: - Summary: Error fetching log on Entities page Key: DISPATCH-565 URL: https://issues.apache.org/jira/browse/DISPATCH-565 Project: Qpid Dispatch Issue Type: Bug Components: Console Reporter: Ernest Allen Assignee: Ernest Allen On the Entities page, if you select a log module and then click on the Fetch button, an error is displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-565) Error fetching log on Entities page
[ https://issues.apache.org/jira/browse/DISPATCH-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-565. --- Resolution: Fixed Fix Version/s: 0.8.0 > Error fetching log on Entities page > --- > > Key: DISPATCH-565 > URL: https://issues.apache.org/jira/browse/DISPATCH-565 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Reporter: Ernest Allen >Assignee: Ernest Allen > Fix For: 0.8.0 > > > On the Entities page, if you select a log module and then click on the Fetch > button, an error is displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-565) Error fetching log on Entities page
[ https://issues.apache.org/jira/browse/DISPATCH-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667163#comment-15667163 ] Ernest Allen commented on DISPATCH-565: --- Fix was committed: commit 8b48b0eaa2225b42147f1abb7088abbe17aab0a9 Author: Ernest Allen Date: Mon Nov 14 16:59:09 2016 -0500 DISPATCH-565 Fix the order of the argements passed to sendMethod > Error fetching log on Entities page > --- > > Key: DISPATCH-565 > URL: https://issues.apache.org/jira/browse/DISPATCH-565 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Reporter: Ernest Allen >Assignee: Ernest Allen > Fix For: 0.8.0 > > > On the Entities page, if you select a log module and then click on the Fetch > button, an error is displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-561) Create python program that returns fake management data
[ https://issues.apache.org/jira/browse/DISPATCH-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-561. --- Resolution: Fixed Fix Version/s: 0.8.0 > Create python program that returns fake management data > --- > > Key: DISPATCH-561 > URL: https://issues.apache.org/jira/browse/DISPATCH-561 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Reporter: Ernest Allen >Assignee: Ernest Allen > Fix For: 0.8.0 > > > To stress the console with various large topologies, a python program that > responds to management queries and returns fake management info would be > useful. > The program should: > - accept connections from a console and respond to GET-MGMT-NODES, QUERY, > and METHOD requests and return fake management data. > - accept management commands to create fake management data > > Separately, a new version of the console is needed to create the new > topologies and send the python program commands. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-543) Initial load of topology page fetches too much information
[ https://issues.apache.org/jira/browse/DISPATCH-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-543. --- Resolution: Fixed Fix Version/s: 0.8.0 > Initial load of topology page fetches too much information > -- > > Key: DISPATCH-543 > URL: https://issues.apache.org/jira/browse/DISPATCH-543 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Reporter: Ernest Allen >Assignee: Ernest Allen > Fix For: 0.8.0 > > > As the topology graph is created, several entities for each router are > fetched: > - .connection > - .router.link > - .router > - .router.node > For large numbers of routers this takes a while. > Break up the creation of the topology graph. The routers and their > connections to other routers can be generated using only .connection > information. > .router-link is used: > - to draw the small client circles. After the initial graph is drawn, go back > and fetch the .router.link info for any router that has connections that are > not "inter-router". > - to display the popup when a client is clicked. This can quickly be fetched > for the individual router when one of it's clients is clicked. > - to display the cross-section popup. This can be fetched when needed. > .router.node is used to generate the highlight line between routers. This > entity can be fetched when needed. > .router is used when adding a new node. This can be fetched when needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-536) Circular buffer overflow errors occur when there are a large number of routers
[ https://issues.apache.org/jira/browse/DISPATCH-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-536. --- Resolution: Fixed Fix Version/s: 0.8.0 > Circular buffer overflow errors occur when there are a large number of routers > -- > > Key: DISPATCH-536 > URL: https://issues.apache.org/jira/browse/DISPATCH-536 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Reporter: Ernest Allen >Assignee: Ernest Allen > Fix For: 0.8.0 > > > As the number of routers increases, the number of management calls that are > sent each poll cycle increases. This can cause buffer errors in rhea. > - Don't allow a large number of management calls to be made without returning > control to the browser. > Another problem with a large number of routers is that the pages may render > before all the router information is ready. This can cause javascript errors. > - Don't render the page until all router info is available. However, dong so > may cause a noticeable delay where a blank page is shown. A loading > message/animation may be necessary. > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-548) Add ability to page through large tables
[ https://issues.apache.org/jira/browse/DISPATCH-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-548. --- Resolution: Fixed > Add ability to page through large tables > > > Key: DISPATCH-548 > URL: https://issues.apache.org/jira/browse/DISPATCH-548 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Reporter: Ernest Allen >Assignee: Ernest Allen > > On the overview page some of the tables can contain a large number of rows. > This slows down the page render and is not very user friendly. > Add the ability to page through the data. Paging must work with sorting and > filtering. > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-575) The console should only pass 'amqp' in the list of protocols when connecting
Ernest Allen created DISPATCH-575: - Summary: The console should only pass 'amqp' in the list of protocols when connecting Key: DISPATCH-575 URL: https://issues.apache.org/jira/browse/DISPATCH-575 Project: Qpid Dispatch Issue Type: Bug Components: Console Reporter: Ernest Allen Assignee: Ernest Allen The console currently passes ["binary", "base64", "AMQWSB10"] as the list of protocols that it supports when it connects to a proxy/router. Once the router can directly handle the websockets protocol, the console should pass 'amqp' as the protocol. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-575) The console should only pass 'amqp' in the list of protocols when connecting
[ https://issues.apache.org/jira/browse/DISPATCH-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702596#comment-15702596 ] Ernest Allen commented on DISPATCH-575: --- Depends on DISPATCH-103 > The console should only pass 'amqp' in the list of protocols when connecting > > > Key: DISPATCH-575 > URL: https://issues.apache.org/jira/browse/DISPATCH-575 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Reporter: Ernest Allen >Assignee: Ernest Allen > > The console currently passes ["binary", "base64", "AMQWSB10"] as the list of > protocols that it supports when it connects to a proxy/router. > Once the router can directly handle the websockets protocol, the console > should pass 'amqp' as the protocol. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-576) Use new log entity statistic counter in console
Ernest Allen created DISPATCH-576: - Summary: Use new log entity statistic counter in console Key: DISPATCH-576 URL: https://issues.apache.org/jira/browse/DISPATCH-576 Project: Qpid Dispatch Issue Type: Improvement Components: Console Reporter: Ernest Allen Assignee: Ernest Allen The router will now return the number of log entries and their severity for each module. The console should use these statistics instead of retrieving all log entries from each router and counting them on the client side. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-580) Log stats should be graphable
Ernest Allen created DISPATCH-580: - Summary: Log stats should be graphable Key: DISPATCH-580 URL: https://issues.apache.org/jira/browse/DISPATCH-580 Project: Qpid Dispatch Issue Type: Bug Components: Management Agent Affects Versions: 0.8.0 Reporter: Ernest Allen Priority: Minor The log statistics added with DISPATCH-553 are integers that could be graphed. However, in order to graph them the console needs a 'graph' property present in the schema for each graphable attribute in the logStats entity. Add a graph property to the counts in logStats. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-576) Use new log entity statistic counter in console
[ https://issues.apache.org/jira/browse/DISPATCH-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-576. --- Resolution: Fixed Fix Version/s: 0.8.0 > Use new log entity statistic counter in console > --- > > Key: DISPATCH-576 > URL: https://issues.apache.org/jira/browse/DISPATCH-576 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Reporter: Ernest Allen >Assignee: Ernest Allen > Fix For: 0.8.0 > > > The router will now return the number of log entries and their severity for > each module. > The console should use these statistics instead of retrieving all log entries > from each router and counting them on the client side. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-585) Firefox dropdown and buttons on list page have incorrect padding
Ernest Allen created DISPATCH-585: - Summary: Firefox dropdown and buttons on list page have incorrect padding Key: DISPATCH-585 URL: https://issues.apache.org/jira/browse/DISPATCH-585 Project: Qpid Dispatch Issue Type: Bug Components: Console Reporter: Ernest Allen Assignee: Ernest Allen Priority: Trivial The padding for the select dropdown and the buttons on the Entities page for firefox have some padding issues. A firefox specific css style needs to be updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-585) Firefox dropdown and buttons on list page have incorrect padding
[ https://issues.apache.org/jira/browse/DISPATCH-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-585. --- Resolution: Fixed Fix Version/s: 0.8.0 > Firefox dropdown and buttons on list page have incorrect padding > > > Key: DISPATCH-585 > URL: https://issues.apache.org/jira/browse/DISPATCH-585 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Trivial > Fix For: 0.8.0 > > > The padding for the select dropdown and the buttons on the Entities page for > firefox have some padding issues. > A firefox specific css style needs to be updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-587) Provide feedback when loading log entries
Ernest Allen created DISPATCH-587: - Summary: Provide feedback when loading log entries Key: DISPATCH-587 URL: https://issues.apache.org/jira/browse/DISPATCH-587 Project: Qpid Dispatch Issue Type: Bug Components: Console Reporter: Ernest Allen Assignee: Ernest Allen There can be a couple of seconds delay between requesting log entries for a particular router/module/level and when the logs are displayed. A visual indication that a log request has been sent and a response is awaited is needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-587) Provide feedback when loading log entries
[ https://issues.apache.org/jira/browse/DISPATCH-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-587. --- Resolution: Fixed Fix Version/s: 0.8.0 > Provide feedback when loading log entries > - > > Key: DISPATCH-587 > URL: https://issues.apache.org/jira/browse/DISPATCH-587 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Reporter: Ernest Allen >Assignee: Ernest Allen > Fix For: 0.8.0 > > > There can be a couple of seconds delay between requesting log entries for a > particular router/module/level and when the logs are displayed. > A visual indication that a log request has been sent and a response is > awaited is needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-588) Schema is not loaded if auto-login is enabled
Ernest Allen created DISPATCH-588: - Summary: Schema is not loaded if auto-login is enabled Key: DISPATCH-588 URL: https://issues.apache.org/jira/browse/DISPATCH-588 Project: Qpid Dispatch Issue Type: Bug Components: Console Reporter: Ernest Allen Assignee: Ernest Allen On the connect page, if you check the auto-login box and then refresh the page, the console will automatically login using the host:port specified. However, when doing that the schema is not loaded and various javascript errors are later generated. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-588) Schema is not loaded if auto-login is enabled
[ https://issues.apache.org/jira/browse/DISPATCH-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-588. --- Resolution: Fixed Fix Version/s: 0.8.0 > Schema is not loaded if auto-login is enabled > - > > Key: DISPATCH-588 > URL: https://issues.apache.org/jira/browse/DISPATCH-588 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Reporter: Ernest Allen >Assignee: Ernest Allen > Fix For: 0.8.0 > > > On the connect page, if you check the auto-login box and then refresh the > page, the console will automatically login using the host:port specified. > However, when doing that the schema is not loaded and various javascript > errors are later generated. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-433) Navigating to console from bookmark displays empty page with just toolbars
[ https://issues.apache.org/jira/browse/DISPATCH-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-433. --- Resolution: Fixed I believe the changes for DISPATCH-588 fixed the remaining issues with this. Note: When navigating directly to a hawtio page that is NOT under dispatch, like http://127.0.0.1:8080/hawtio/logs, Firefox will display the page with just the top navigation visible. There will be no page body. Chrome behaves as expected. I believe this is a problem with hawtio and not the dispatch plugin. > Navigating to console from bookmark displays empty page with just toolbars > -- > > Key: DISPATCH-433 > URL: https://issues.apache.org/jira/browse/DISPATCH-433 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.6.1 >Reporter: Jiri Danek >Assignee: Ernest Allen > Fix For: 0.8.0 > > Attachments: actual_chrome_4-90415a-test_open_connect_page__10.png, > expected_chrome_4-90415a_test_redirect_to_connect_page__10.png, overview.png > > > Judging by the description on DISPATCH-275, when navigating to > http://127.0.0.1:8080/hawtio/dispatch_plugin/overview from a bookmark or by > entering the URL directly, I should be redirected to the Connect page. > What actually happens is that I am shown an empty page with just toolbars. > The dialog for connecting to router is not displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-589) Missing links on topology page
Ernest Allen created DISPATCH-589: - Summary: Missing links on topology page Key: DISPATCH-589 URL: https://issues.apache.org/jira/browse/DISPATCH-589 Project: Qpid Dispatch Issue Type: Bug Components: Console Reporter: Ernest Allen Assignee: Ernest Allen Some links between nodes are missing on the topology graph. This appears to be intermittent. It looks like the connection names are not unique across the router network. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-589) Missing links on topology page
[ https://issues.apache.org/jira/browse/DISPATCH-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-589. --- Resolution: Fixed Fix Version/s: 0.8.0 > Missing links on topology page > -- > > Key: DISPATCH-589 > URL: https://issues.apache.org/jira/browse/DISPATCH-589 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Reporter: Ernest Allen >Assignee: Ernest Allen > Fix For: 0.8.0 > > > Some links between nodes are missing on the topology graph. This appears to > be intermittent. > It looks like the connection names are not unique across the router network. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-590) List of log modules on the overview page is occationally doubled
Ernest Allen created DISPATCH-590: - Summary: List of log modules on the overview page is occationally doubled Key: DISPATCH-590 URL: https://issues.apache.org/jira/browse/DISPATCH-590 Project: Qpid Dispatch Issue Type: Bug Components: Console Reporter: Ernest Allen Assignee: Ernest Allen The list of log modules on the overview page is sometimes duplicated. If you quickly jump between tree nodes on the left of the page, the list of log modules gets doubled. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-591) Add http listener to example/test router configs in the tests directory
Ernest Allen created DISPATCH-591: - Summary: Add http listener to example/test router configs in the tests directory Key: DISPATCH-591 URL: https://issues.apache.org/jira/browse/DISPATCH-591 Project: Qpid Dispatch Issue Type: Task Components: Tools Reporter: Ernest Allen Now that the routers have the ability to handle websockets directly, the sample config files in the qpid-dispatch/tests directory should contain a listener that is configured for http. Only one config file in each directory needs an http listener. Also, the listener should be on port 5673. Once the routers can handle secure websockets traffic, the sample config files that handle ssl should include an https listener on port 5674. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-592) Attempt to auto-login to the host:port that served the web page
Ernest Allen created DISPATCH-592: - Summary: Attempt to auto-login to the host:port that served the web page Key: DISPATCH-592 URL: https://issues.apache.org/jira/browse/DISPATCH-592 Project: Qpid Dispatch Issue Type: Improvement Components: Console Reporter: Ernest Allen Assignee: Ernest Allen Now that the router can service the web site directly we can bypass the connect page by attempting to connect to the same host:port that was used to deliver the html page. The connect page should still be available as the 1st tab but if the auto-connection is successful, the overview page should be displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-592) Attempt to auto-login to the host:port that served the web page
[ https://issues.apache.org/jira/browse/DISPATCH-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-592. --- Resolution: Fixed Fix Version/s: 0.8.0 > Attempt to auto-login to the host:port that served the web page > --- > > Key: DISPATCH-592 > URL: https://issues.apache.org/jira/browse/DISPATCH-592 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Reporter: Ernest Allen >Assignee: Ernest Allen > Fix For: 0.8.0 > > > Now that the router can service the web site directly we can bypass the > connect page by attempting to connect to the same host:port that was used to > deliver the html page. > The connect page should still be available as the 1st tab but if the > auto-connection is successful, the overview page should be displayed. > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-591) Add http listener to example/test router configs in the tests directory
[ https://issues.apache.org/jira/browse/DISPATCH-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-591. --- Resolution: Fixed Assignee: Ernest Allen Fix Version/s: 0.8.0 > Add http listener to example/test router configs in the tests directory > --- > > Key: DISPATCH-591 > URL: https://issues.apache.org/jira/browse/DISPATCH-591 > Project: Qpid Dispatch > Issue Type: Task > Components: Tools >Reporter: Ernest Allen >Assignee: Ernest Allen > Fix For: 0.8.0 > > > Now that the routers have the ability to handle websockets directly, the > sample config files in the qpid-dispatch/tests directory should contain a > listener that is configured for http. > Only one config file in each directory needs an http listener. Also, the > listener should be on port 5673. > Once the routers can handle secure websockets traffic, the sample config > files that handle ssl should include an https listener on port 5674. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-552) Allow only one tree node to be expanded if there is a large number of routers
[ https://issues.apache.org/jira/browse/DISPATCH-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen updated DISPATCH-552: -- Summary: Allow only one tree node to be expanded if there is a large number of routers (was: Allow only tree node to be expanded if there is a large number of routers ) > Allow only one tree node to be expanded if there is a large number of routers > -- > > Key: DISPATCH-552 > URL: https://issues.apache.org/jira/browse/DISPATCH-552 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Reporter: Ernest Allen >Assignee: Ernest Allen > > There is a navigation tree on the left of the Overview and Entities pages. > Management calls are periodically made to update the data for each node in > the tree that is expanded . > The amount of data requested becomes problematic when there is a large number > of router in the network: > - It takes a long time to retrieve > - It takes a lot of memory to store > - It uses bandwidth > For large networks, the expand all/collapse all arrows at the top of the tree > should be hidden and expanding a tree node should automatically collapse the > other nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-552) Allow only one tree node to be expanded if there is a large number of routers
[ https://issues.apache.org/jira/browse/DISPATCH-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-552. --- Resolution: Fixed Fix Version/s: 0.8.0 > Allow only one tree node to be expanded if there is a large number of routers > -- > > Key: DISPATCH-552 > URL: https://issues.apache.org/jira/browse/DISPATCH-552 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Reporter: Ernest Allen >Assignee: Ernest Allen > Fix For: 0.8.0 > > > There is a navigation tree on the left of the Overview and Entities pages. > Management calls are periodically made to update the data for each node in > the tree that is expanded . > The amount of data requested becomes problematic when there is a large number > of router in the network: > - It takes a long time to retrieve > - It takes a lot of memory to store > - It uses bandwidth > For large networks, the expand all/collapse all arrows at the top of the tree > should be hidden and expanding a tree node should automatically collapse the > other nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-314) If a router has a normal listener, show it in a different color on the topology page
[ https://issues.apache.org/jira/browse/DISPATCH-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-314. --- Resolution: Fixed Fix Version/s: 0.8.0 Instead of drawing the router circle differently, the row in the router's info popup that shows the router's normal listeners is drawn with a green background color > If a router has a normal listener, show it in a different color on the > topology page > > > Key: DISPATCH-314 > URL: https://issues.apache.org/jira/browse/DISPATCH-314 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.7.0 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Minor > Fix For: 0.8.0 > > > It would be nice see which routers can have clients attached to them at a > glance on the topology page. > Currently all routers are displayed with a gray background. Routers that have > a normal listener can be displayed with a different background color. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1914) Console Entities view looks to be misformatted
[ https://issues.apache.org/jira/browse/DISPATCH-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-1914. Resolution: Fixed Fix with commit d08f33a45ddae8bafb556ad0df2f28eddb2c0003 > Console Entities view looks to be misformatted > -- > > Key: DISPATCH-1914 > URL: https://issues.apache.org/jira/browse/DISPATCH-1914 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 1.14.0 > Environment: Firefox 82.0.2 on NixOS >Reporter: Jiri Daněk >Assignee: Ernest Allen >Priority: Major > Fix For: 1.17.0 > > Attachments: image-2021-01-16-12-47-09-270.png > > > Looking at the entities view in Dispatch 0.14.0, it feels to me like it is > rendered wrong. The expanding list is missing a distinct formatting for the > expanded lines. I am not sure what it was meant to look like, but this > probably isn't it. > I did not yet investigate what went wrong. I am now focusing on other things > (updating dependencies without causing any regressions). > !image-2021-01-16-12-47-09-270.png|width=100%! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2097) [console] GUI displays many connections to pseudo-host egress-dispatch
[ https://issues.apache.org/jira/browse/DISPATCH-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17361018#comment-17361018 ] Ernest Allen commented on DISPATCH-2097: [~chug] Can you attach your router config files that illustrate this problem to this Jira? > [console] GUI displays many connections to pseudo-host egress-dispatch > -- > > Key: DISPATCH-2097 > URL: https://issues.apache.org/jira/browse/DISPATCH-2097 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console, Protocol Adaptors >Reporter: Charles E. Rolke >Assignee: Ernest Allen >Priority: Major > Fix For: 1.17.0 > > Attachments: DISPATCH-2097_Screenshot.png > > > In a network of 12 routers each router has a TCP Listener and Connector > defined. There are no TCP adaptor connections in progress. > The GUI topology page shows a green receiver host named _egress-dispatch_. > Every router has a line drawn to this host. That's 12 lines going to the same > little circle and its seriously confuses the topology page. > The egress-dispatch host and connections to it are purely for housekeeping > purposes and are not involved in any activity that in important enough to be > shown on the main page as it is. > This host and connections to it should be hidden. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2097) [console] GUI displays many connections to pseudo-host egress-dispatch
[ https://issues.apache.org/jira/browse/DISPATCH-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-2097. Resolution: Fixed - Reproduced problem with attached zip files. - Applied [~chug]'s fix. - Modified console to ignore connections with 'qd.adaptor' defined - Built and restarted routers - The problem no longer happens. > [console] GUI displays many connections to pseudo-host egress-dispatch > -- > > Key: DISPATCH-2097 > URL: https://issues.apache.org/jira/browse/DISPATCH-2097 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console, Protocol Adaptors >Reporter: Charles E. Rolke >Assignee: Ernest Allen >Priority: Major > Fix For: 1.17.0 > > Attachments: D-2097.zip, DISPATCH-2097_Screenshot.png > > > In a network of 12 routers each router has a TCP Listener and Connector > defined. There are no TCP adaptor connections in progress. > The GUI topology page shows a green receiver host named _egress-dispatch_. > Every router has a line drawn to this host. That's 12 lines going to the same > little circle and its seriously confuses the topology page. > The egress-dispatch host and connections to it are purely for housekeeping > purposes and are not involved in any activity that in important enough to be > shown on the main page as it is. > This host and connections to it should be hidden. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2176) Update version of d3 in console
Ernest Allen created DISPATCH-2176: -- Summary: Update version of d3 in console Key: DISPATCH-2176 URL: https://issues.apache.org/jira/browse/DISPATCH-2176 Project: Qpid Dispatch Issue Type: Improvement Components: Console Affects Versions: 1.16.0 Reporter: Ernest Allen The console uses version 3 of the d3 library. The latest is version 7. For development support and bug fixes, we should update the code to use the latest version. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1623) Investigate why the console sometimes drops the connection to the router a few seconds after login
[ https://issues.apache.org/jira/browse/DISPATCH-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-1623. Fix Version/s: 1.17.0 Resolution: Fixed Turns out, the connection wasn't being dropped. The console was responding to an event generated by rhea a few minutes after an auto-login attempt failed. The fix was to only register the "disconnected" event handler after a successful connect, and the re-register the handler after a re-connect event. > Investigate why the console sometimes drops the connection to the router a > few seconds after login > -- > > Key: DISPATCH-1623 > URL: https://issues.apache.org/jira/browse/DISPATCH-1623 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 1.11.0 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Major > Fix For: 1.17.0 > > > After successfully connecting to the router, the console sometimes goes back > to the login page after a few seconds. > This may be because the connection is actually closing, in which case, this > is the correct behavior. > However, it may the something the console is doing incorrectly. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1944) Qpid dispatch console dashboard is showing incorrect number of in/out counts at the "most active addresses" section
Ernest Allen created DISPATCH-1944: -- Summary: Qpid dispatch console dashboard is showing incorrect number of in/out counts at the "most active addresses" section Key: DISPATCH-1944 URL: https://issues.apache.org/jira/browse/DISPATCH-1944 Project: Qpid Dispatch Issue Type: Bug Components: Console Affects Versions: 1.14.0 Reporter: Ernest Allen Assignee: Ernest Allen The values for deliveries in and out on the console's dashboard page in the "Most active addresses" table is incorrect. The values appear to be double what they should be and are inconsistent with the values shown on the Addresses overview page. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1944) Qpid dispatch console dashboard is showing incorrect number of in/out counts at the "most active addresses" section
[ https://issues.apache.org/jira/browse/DISPATCH-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-1944. Fix Version/s: 2.0.0 Resolution: Fixed I'm not sure about the "Fix Version". The fix is on master now. > Qpid dispatch console dashboard is showing incorrect number of in/out counts > at the "most active addresses" section > --- > > Key: DISPATCH-1944 > URL: https://issues.apache.org/jira/browse/DISPATCH-1944 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 1.14.0 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Major > Fix For: 2.0.0 > > > The values for deliveries in and out on the console's dashboard page in the > "Most active addresses" table is incorrect. > The values appear to be double what they should be and are inconsistent with > the values shown on the Addresses overview page. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1945) Cleanup some GUI glitches on console's visualization pages
Ernest Allen created DISPATCH-1945: -- Summary: Cleanup some GUI glitches on console's visualization pages Key: DISPATCH-1945 URL: https://issues.apache.org/jira/browse/DISPATCH-1945 Project: Qpid Dispatch Issue Type: Bug Components: Console Affects Versions: 1.14.0 Reporter: Ernest Allen Assignee: Ernest Allen There are a few graphic glitches on the console's topology page and the message flow page. There is a double line under the toolbar. There is extra padding at the bottom of the toolbar. There is a useless scrollbar at the right of the visualization. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1945) Cleanup some GUI glitches on console's visualization pages
[ https://issues.apache.org/jira/browse/DISPATCH-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-1945. Fix Version/s: 1.15.0 Resolution: Fixed Updated style sheet and removed some extraneous console.log statements. > Cleanup some GUI glitches on console's visualization pages > -- > > Key: DISPATCH-1945 > URL: https://issues.apache.org/jira/browse/DISPATCH-1945 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 1.14.0 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Minor > Fix For: 1.15.0 > > > There are a few graphic glitches on the console's topology page and the > message flow page. > There is a double line under the toolbar. > There is extra padding at the bottom of the toolbar. > There is a useless scrollbar at the right of the visualization. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
