[
https://issues.apache.org/jira/browse/DISPATCH-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek updated DISPATCH-791:
--------------------------------
Description:
Both hawtio and stand-alone versions are affected. Issue was observed in Chrome
and Firefox. In Firefox, if I move to another panel and back, the console node
sometimes appears. In Chrome, it usually appears the first time and then
disappears.
Video: https://youtu.be/q3_8HT4iVzc
The following exception is displayed in browser console (from hawtio version)
{noformat}
app.js?c8641b2e13788127:16 [Window] Uncaught TypeError: Cannot read property
'results' of undefined (<a
href="http://127.0.0.1:8080/hawtio/dispatch_hawtio_console/topology:5";>http://127.0.0.1:8080/hawtio/dispatch_hawtio_console/topology:5:8603</a>)
consoleLogger @ app.js?c8641b2e13788127:16
c @ app.js?c8641b2e13788127:16
(anonymous) @ app.js?c8641b2e13788127:16
invoke @ app.js?c8641b2e13788127:4
error @ app.js?c8641b2e13788127:4
window.onerror @ app.js?c8641b2e13788127:16
{noformat}
in stand-alone version, it is
{noformat}
Uncaught TypeError: Cannot read property 'results' of undefined
at initializeLinks (qdrTopology.js:723)
at qdrTopology.js:1009
at qdrService.js:440
at i._call (d3-queue.min.js:2)
at s (d3-queue.min.js:2)
at d3-queue.min.js:2
at qdrService.js:668
at Object.resolver (qdrService.js:813)
at Object.resolve (qdrService.js:172)
at Receiver.<anonymous> (qdrService.js:1073)
angular.js:14362 QDR: GET-MGMT-NODES returned an empty list. Using [...]
{noformat}
was:
Both hawtio and stand-alone versions are affected. Issue was observed in Chrome
and Firefox. In Firefox, if I move to another panel and back, the console node
sometimes appears. In Chrome, it usually appears the first time and then
disappears.
The following exception is displayed in browser console (from hawtio version)
{noformat}
app.js?c8641b2e13788127:16 [Window] Uncaught TypeError: Cannot read property
'results' of undefined (<a
href="http://127.0.0.1:8080/hawtio/dispatch_hawtio_console/topology:5";>http://127.0.0.1:8080/hawtio/dispatch_hawtio_console/topology:5:8603</a>)
consoleLogger @ app.js?c8641b2e13788127:16
c @ app.js?c8641b2e13788127:16
(anonymous) @ app.js?c8641b2e13788127:16
invoke @ app.js?c8641b2e13788127:4
error @ app.js?c8641b2e13788127:4
window.onerror @ app.js?c8641b2e13788127:16
{noformat}
in stand-alone version, it is
{noformat}
Uncaught TypeError: Cannot read property 'results' of undefined
at initializeLinks (qdrTopology.js:723)
at qdrTopology.js:1009
at qdrService.js:440
at i._call (d3-queue.min.js:2)
at s (d3-queue.min.js:2)
at d3-queue.min.js:2
at qdrService.js:668
at Object.resolver (qdrService.js:813)
at Object.resolve (qdrService.js:172)
at Receiver.<anonymous> (qdrService.js:1073)
angular.js:14362 QDR: GET-MGMT-NODES returned an empty list. Using [...]
{noformat}
> The node representing Console in Topology tab is not displayed
> --------------------------------------------------------------
>
> Key: DISPATCH-791
> URL: https://issues.apache.org/jira/browse/DISPATCH-791
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Console
> Affects Versions: 1.0.0
> Environment: Dispatch and Dispatch plugin at commit e22091b3
> Built without libwebsocket, used the old websockify way to connect console
> Firefox 51.0.1, Chrome 56.0.2924.87 (64-bit) on Linux
> Reporter: Jiri Danek
>
> Both hawtio and stand-alone versions are affected. Issue was observed in
> Chrome and Firefox. In Firefox, if I move to another panel and back, the
> console node sometimes appears. In Chrome, it usually appears the first time
> and then disappears.
> Video: https://youtu.be/q3_8HT4iVzc
> The following exception is displayed in browser console (from hawtio version)
> {noformat}
> app.js?c8641b2e13788127:16 [Window] Uncaught TypeError: Cannot read property
> 'results' of undefined (<a
> href="http://127.0.0.1:8080/hawtio/dispatch_hawtio_console/topology:5";>http://127.0.0.1:8080/hawtio/dispatch_hawtio_console/topology:5:8603</a>)
> consoleLogger @ app.js?c8641b2e13788127:16
> c @ app.js?c8641b2e13788127:16
> (anonymous) @ app.js?c8641b2e13788127:16
> invoke @ app.js?c8641b2e13788127:4
> error @ app.js?c8641b2e13788127:4
> window.onerror @ app.js?c8641b2e13788127:16
> {noformat}
> in stand-alone version, it is
> {noformat}
> Uncaught TypeError: Cannot read property 'results' of undefined
> at initializeLinks (qdrTopology.js:723)
> at qdrTopology.js:1009
> at qdrService.js:440
> at i._call (d3-queue.min.js:2)
> at s (d3-queue.min.js:2)
> at d3-queue.min.js:2
> at qdrService.js:668
> at Object.resolver (qdrService.js:813)
> at Object.resolve (qdrService.js:172)
> at Receiver.<anonymous> (qdrService.js:1073)
> angular.js:14362 QDR: GET-MGMT-NODES returned an empty list. Using [...]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
