]
Misty Stanley-Jones commented on MODCLUSTER-264:
------------------------------------------------
I spoke with Jean Frederic last night and apparently you are supposed to use
:write-attribute() with syntax like:
:write-attribute(name=proxy-list,value="127.0.0.1:123,127.0.0.2:234")
The :add-proxy is not the right thing. Maybe it should be removed from the list of
available commands, to ease confusion?
jboss-admin.sh accepts crazy values for :add-proxy()
----------------------------------------------------
Key: MODCLUSTER-264
URL:
https://issues.jboss.org/browse/MODCLUSTER-264
Project: mod_cluster
Issue Type: Bug
Environment: modcluster subsystem of AS 7.1 trunk
Reporter: Misty Stanley-Jones
Assignee: Jean-Frederic Clere
I am allowed to use all of these kinds of syntax with :add-proxy():
[domain@localhost:9999 subsystem=modcluster] :add-proxy(host=abc.com,port=123)
{
"outcome" => "success",
"result" => {
"domain-results" => {"step-1" => undefined},
"server-operations" => [{
"servers" => [],
"operation" => {
"address" => [("subsystem" =>
"modcluster")],
"operation" => "add-proxy",
"port" => 123,
"host" => "abc.com",
"operation-headers" => {"execute-for-coordinator"
=> true}
}
}]
}
}
[domain@localhost:9999 subsystem=modcluster] :add-proxy(host=def.com)
{
"outcome" => "success",
"result" => {
"domain-results" => {"step-1" => undefined},
"server-operations" => [{
"servers" => [],
"operation" => {
"address" => [("subsystem" =>
"modcluster")],
"operation" => "add-proxy",
"host" => "def.com",
"operation-headers" => {"execute-for-coordinator"
=> true}
}
}]
}
}
[domain@localhost:9999 subsystem=modcluster] :add-proxy(port=999)
{
"outcome" => "success",
"result" => {
"domain-results" => {"step-1" => undefined},
"server-operations" => [{
"servers" => [],
"operation" => {
"address" => [("subsystem" =>
"modcluster")],
"operation" => "add-proxy",
"port" => 999,
"operation-headers" => {"execute-for-coordinator"
=> true}
}
}]
}
}
I think only the first one should be valid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: