[jboss-jira] [JBoss JIRA] (AS7-4276) setting default-interface to crap makes AS completely non-responsive
Heiko Rupp (JIRA)
jira-events at lists.jboss.org
Fri Mar 23 12:30:47 EDT 2012
Heiko Rupp created AS7-4276:
-------------------------------
Summary: setting default-interface to crap makes AS completely non-responsive
Key: AS7-4276
URL: https://issues.jboss.org/browse/AS7-4276
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.1.Final
Reporter: Heiko Rupp
Assignee: Brian Stansberry
[standalone at localhost:9999 socket-binding-group=standard-sockets] /:read-children-names(type=interface)
'type' is not found among the supported properties: [child-type]
[standalone at localhost:9999 socket-binding-group=standard-sockets] /:read-children-names(child-type=interface)
{
"outcome" => "success",
"result" => [
"management",
"public",
"unsecure"
]
}
[standalone at localhost:9999 socket-binding-group=standard-sockets] :write-attribute(name=default-interface,value=non-existing-crap)
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
[standalone at localhost:9999 socket-binding-group=standard-sockets] /:reload
{
"outcome" => "success",
"response-headers" => {"process-state" => "reload-required"}
}
[standalone at localhost:9999 socket-binding-group=standard-sockets] :read-attribute(name=default-interface)
Failed to perform read-operation-description to validate the request: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:9999. The connection timed out
console says:
17:27:25,358 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.network.non-existing-crap (missing) dependents: [service jboss.socket-binding-manager]
17:27:25,366 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.0.0.Beta1 (AS 7.1.0.Final-redhat-1) started (with errors) in 5676ms - Started 116 of 206 services (43 services failed or missing dependencies, 46 services are passive or on-demand)
No ports are open. User has to shut down the server, edit standalone.xml and try again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list