12:15 a.m.
[
https://issues.jboss.org/browse/AS7-4276?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-4276:
----------------------------------
Fix Version/s: 7.1.2.Final
Scheduling for 7.1.2 so it's on our radar screen, although it may not get done. This
needs to be part of a broader look at what sorts of boot problems result in complete
termination of the server VM, versus the existing lenient behavior.
This is actually an example of an invalid model reference problem.
Dividing things somewhat arbitrarily, boot can see these types of problems:
1) Primordial issues, before parsing even begins.
2) Parsing issues
3) Problems applying the operations generated by the model to the in-memory configuration
model (i.e. OperationStepHandler problems in Stage.MODEL)
4) Invalid model reference problems. Resource A has an attribute that refers to invalid
config item B. These we need to do a better job of detecting before Stage.RUNTIME. We
basically don't detect this now in most cases.
5) Problems applying the operations generated by the model to the runtime services (i.e.
OperationStepHandler problems in Stage.MODEL)
6) Service start issues (detected by the verification steps in Stage.VERIFY)
Basically, 1-4 should result in server process termination, since boot doesn't get to
the point where any runtime service that would allow the user to fix an issue is started.
This particular JIRA exists because 4 isn't there, so the problem only shows up as a
6)
For 5 and 6, I'm considering making it configurable, so the user can elect to fail the
entire boot if an error occurs during the runtime phases.
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
Fix For: 7.1.2.Final
[standalone@localhost:9999 socket-binding-group=standard-sockets]
/:read-children-names(type=interface)
'type' is not found among the supported properties: [child-type]
[standalone@localhost:9999 socket-binding-group=standard-sockets]
/:read-children-names(child-type=interface)
{
"outcome" => "success",
"result" => [
"management",
"public",
"unsecure"
]
}
[standalone@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@localhost:9999 socket-binding-group=standard-sockets] /:reload
{
"outcome" => "success",
"response-headers" => {"process-state" =>
"reload-required"}
}
[standalone@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