| Summary: | [EAP6] Managed server creating / starting problem | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Jan Stefl <jstefl> |
| Component: | Plugin -- JBoss EAP 6 | Assignee: | RHQ Project Maintainer <rhq-maint> |
| Status: | CLOSED NOTABUG | QA Contact: | Mike Foley <mfoley> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | JON 3.2 | CC: | hrupp, jstefl, loleary, lzoubek, myarboro, rhatlapa, tsegismo |
| Target Milestone: | --- | ||
| Target Release: | JON 3.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-11-04 13:31:27 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
After stopping mentioned server via JON UI, I was unable to create another mananged server. - the server is actually started but with failed services. - it is caused due missing definition of socket bindings for certain services. The server group is set to use full profile which uses messaging and when adding server the socket binding was redefined to use one without defined socket bindings for this service. The use case is that customer can easily define wrong socket binding (one which doesn't cover all services being started based on the profile being used) without JON notifying the customer that it caused EAP server start up with errors. We recommend this to be fixed in current release. There should be some notification that server wasn't started successfully (but only partially) Jan, I don't think there is a good way for JON to detect server state, if you take look at DC admin console, such server is reported as running, so even domain controller does not know. Same way .. you can set 'standart-sockets' binding for server that belongs to 'main-server-group' using DC admin console. In JON, user still has a way how to get information from server log. You can enable 'Log Event Source' in managed server's Connection settings and then check 'Events'. At least there should be done some validation on JON side when adding the managed server and warn him that using different socket-binding than the one defined in server-group can cause server to start only with limited services (some services may fail to start due undefined socket binding). moving to JON 3.3 per BZ Triage 11/11/2013 heute, loleary, foley, santos, yarboro Closing as NOTABUG, as there's nothing we can do. |
Scenario: - EAP started as domain. - JON UI: agent -> JBossAS7 Host Controllers -> EAP Domain controller -> Create child (Managed server) - insert relevant infomation and in step 2 set socket binding as "standard sockets" - finish - Start just create server (you can do it via JON UI) Result - JON reports no problem and everything seems that server was started, but the server was not started and log contains: 09:25:04,242 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.binding.jacorb (missing) dependents: [service jboss.jacorb.orb-service] service jboss.binding.jacorb-ssl (missing) dependents: [service jboss.jacorb.orb-service] service jboss.binding.messaging (missing) dependents: [service jboss.messaging.default] service jboss.binding.messaging-throughput (missing) dependents: [service jboss.messaging.default] - OK, it is clear that at least full-sockets is expected, but 1. JON mustn't allow us to set such bindings 2. JON must identify that server was not started