Petals Web-Console

Web console unusable in multi-node Petals deployments

Details

  • Type: Bug Bug
  • Status: New New
  • Resolution: Unresolved
  • Affects Version/s: 2.0.5
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    This problem is multiple:

    • Console becomes too slow when multiple nodes are involved
    • In dynamic mode, new slaves are not visible
    • Monitoring does not seem to work for multi-node exchanges
      In fact, the Web console seems to fit only standalone deployments.
    Show
    This problem is multiple:
    • Console becomes too slow when multiple nodes are involved
    • In dynamic mode, new slaves are not visible
    • Monitoring does not seem to work for multi-node exchanges In fact, the Web console seems to fit only standalone deployments.
  • Environment:
    Petals 3.1.1, Linux/Tomcat

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Adrien Ruffie added a comment - Tue, 21 Dec 2010 - 10:57:33 +0100

What do you mean by dynamic mode ?!?!?
Do you have perform a refresh in the left menu ?
It not possible because you have release this maintenance version by testing with a big architecture like 4 nodes and 1200 endpoints ...

Show
Adrien Ruffie added a comment - Tue, 21 Dec 2010 - 10:57:33 +0100 What do you mean by dynamic mode ?!?!? Do you have perform a refresh in the left menu ? It not possible because you have release this maintenance version by testing with a big architecture like 4 nodes and 1200 endpoints ...
Hide
Permalink
Pierre-Yves Gibello added a comment - Tue, 21 Dec 2010 - 11:40:47 +0100

There is a "mode=dynamic" in the topology.xml .
Don't know if the same problem appears in "mode=static", the problem was detected on a customer site.

Show
Pierre-Yves Gibello added a comment - Tue, 21 Dec 2010 - 11:40:47 +0100 There is a "mode=dynamic" in the topology.xml . Don't know if the same problem appears in "mode=static", the problem was detected on a customer site.
Hide
Permalink
Adrien Ruffie added a comment - Tue, 21 Dec 2010 - 11:44:37 +0100

I don't understand the problem ... in dynamic mode what's appears ? If you start a new slave, it doesn't appears in Webconsole ? Also after a refresh ?

Show
Adrien Ruffie added a comment - Tue, 21 Dec 2010 - 11:44:37 +0100 I don't understand the problem ... in dynamic mode what's appears ? If you start a new slave, it doesn't appears in Webconsole ? Also after a refresh ?
Hide
Permalink
Pierre-Yves Gibello added a comment - Tue, 21 Dec 2010 - 13:30:33 +0100

Just tested here. The slave is detected by the master at slave startup (the topology.xml is overwritten by Petals, and the slave is added there...)
When I refresh the web console, I see a "server 1@localhost", which points to "javascript:void(0)" (does nothing when I click it).
The "server 0" (master, localhost) still works fine.
The master + web console are installed on the same host, the slave is on another machine.
Not sure my customer experienced exactly the same behaviour... but it did not work, and here, it does not work either.

Show
Pierre-Yves Gibello added a comment - Tue, 21 Dec 2010 - 13:30:33 +0100 Just tested here. The slave is detected by the master at slave startup (the topology.xml is overwritten by Petals, and the slave is added there...) When I refresh the web console, I see a "server 1@localhost", which points to "javascript:void(0)" (does nothing when I click it). The "server 0" (master, localhost) still works fine. The master + web console are installed on the same host, the slave is on another machine. Not sure my customer experienced exactly the same behaviour... but it did not work, and here, it does not work either.
Hide
Permalink
Adrien Ruffie added a comment - Wed, 5 Jan 2011 - 10:04:42 +0100

The javascript:void(0) ? Do the server1@localhost have a grey icon ? Is unabled ?
I don't understand the "topology.xml is overwritten by Petals" at the slave startup,
do you mean that the master node edit its topology.xml file in order to add xml
node which represent the new slave started ?

Could you show me, the next time to come in Toulouse please ?

Thank PY

Show
Adrien Ruffie added a comment - Wed, 5 Jan 2011 - 10:04:42 +0100 The javascript:void(0) ? Do the server1@localhost have a grey icon ? Is unabled ? I don't understand the "topology.xml is overwritten by Petals" at the slave startup, do you mean that the master node edit its topology.xml file in order to add xml node which represent the new slave started ? Could you show me, the next time to come in Toulouse please ? Thank PY

People

Dates

  • Created:
    Tue, 21 Dec 2010 - 10:46:42 +0100
    Updated:
    Wed, 5 Jan 2011 - 10:04:42 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.