[jboss-jira] [JBoss JIRA] (WFLY-1682) ugly style allowing to start multiple servers refer to the same server-config file

杰 吴 (JIRA) jira-events at lists.jboss.org
Fri Jul 12 03:30:21 EDT 2013


杰 吴 created WFLY-1682:
-------------------------

             Summary: ugly style allowing to start multiple servers refer to the same server-config file
                 Key: WFLY-1682
                 URL: https://issues.jboss.org/browse/WFLY-1682
             Project: WildFly
          Issue Type: Bug
          Components: ConfigAdmin
    Affects Versions: 8.0.0.Alpha2
            Reporter: 杰 吴
            Assignee: Thomas Diesler


{color:red} 
WildFly allows to start multiple servers refer to the same server-config as following
{color}
{noformat}  
standalone.bat -server-config=standalone.xml -Djboss.node.name=node1
{noformat} 
{noformat} 
standalone.bat -server-config=standalone.xml -Djboss.socket.binding.port-offset=100 -Djboss.node.name=node2
{noformat}
{noformat} 
standalone.bat -server-config=standalone.xml -Djboss.socket.binding.port-offset=200 -Djboss.node.name=node3
{noformat}

{color:red} 
the three nodes do not share the modification, but the later will overwrite  the former in the standalone.xml.
{color} 
{quote}
for example
(1) create datasource "ds4node1" to node1 which created above.
    and ds4node1 is written into standalone.xml.
↓
(2) careate datasource "ds4node2" to node2
    and ds4node1 which was created in step(1) is deleted from standalone.xml,
    ds4node2 is written into  standalone.xml.    
↓
(3) careate datasource "ds4node3" to node3
    and ds4node2 which was created in step(2) is deleted from standalone.xml,
    ds4node3 is written into  standalone.xml.
{quote}

{color:red}
after restarting the three nodes, the three nodes refers to standalone.xml, and share the last created datasource "ds4node3"。
{color} 

{color:red}
the above style may confuse users.
if it is a style flaw, is there any plan to improve it.
{color} 


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the jboss-jira mailing list