Bug 900227 (JBPAPP6-1348)
| Summary: | Confusing error when stopping a server in a domain | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Jan Martiska <jmartisk> | ||||||
| Component: | Web Console | Assignee: | Harald Pehl <hpehl> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 6.0.0 | CC: | atangrin, brian.stansberry, dosoudil, hpehl, ike.braun, jcechace, rsvoboda | ||||||
| Target Milestone: | CR3 | ||||||||
| Target Release: | EAP 6.2.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| URL: | http://jira.jboss.org/jira/browse/JBPAPP6-1348 | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-12-15 16:21:08 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: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Attachment: Added: server-one.png Link: Added: This issue relates to JBQA-6251 Labels: Added: eap6_need_triage Release Notes Text: Added: will be included in console 1.3.0 (7.1.2-redhat1) Reopening so a proper fix version can be set. Paul, can you? the fix goes into console 1.3.0 that will ship with 7.1.2-redhat1 Labels: Removed: eap6_need_triage This doesn't seem to be fixed in ER7. The issue might have changed a little. It seems the console still queries servers which are not active. Please try experimenting with it a little- stop a server on one host, then switch your view to another host and then switch back to the first host (and select a server in the selection), etc. Or navigate to a completely different page and then go back to Server Instances page. the error will appear. Sorry I don't know how to explain it more precisely, try to experiment with it :) Please open a new related jira for this, and describe the exact steps to reproduce. What is the point? The issue still persists, I don't know why a new jira should be created. Heiko, can you take a brief look at it? If you get into trouble with reproducing it, please ping me on IRC. yes. i can reproduce it. it's fixed and will ship with the console > 1.3.1 Release Notes Text: Removed: will be included in console 1.3.0 (7.1.2-redhat1) Still no good in EAP CR1, console 1.3.1.Final. Heiko, by "> 1.3.1" do you mean it should be fixed in 1.3.1.Final? I tried searching for the commit fixing this but wasn't able to find it. Now the error appears when you open the server selection popup and click a server that is currently offline, see the new screenshot. new screenshot (1.3.1.Final) Attachment: Added: Screenshot.png Labels: Added: eap601-qe-triage Not approved for EAP 6.0.1. If this should be reconsidered, please add the label: eap601-qe-triage Labels: Removed: eap601-qe-triage Docs QE Status: Removed: NEW Since the way a server is (re)started has changed fundamentally in EAP 6.2, this BZ should be obsolete. Verified 6.2.0.CR3 |
project_key: JBPAPP6 When stopping a server on a managed host controller, the stop will be performed successfully, but after that, the console seems to query that host controller for a server named 'X', even when there is no server with 'X' name. I noticed that 'X' is equal to the name of the first listed server of the host controller (call it hostA), which is listed first in the server selection combobox (in the top-left corner). The consequence is, if you stop a managed server for the host controller which is listed first in the combobox (that means hostA) , it will work fine, but if you stop a managed server of another host controller (hostB), the server on hostB will shutdown, but the console will query a server which is located on hostA. This confusing error occurs: {noformat} Internal Server Error { "outcome" => "failed", "result" => undefined, "failure-description" => "JBAS010850: No handler for operation read-attribute at address [ (\"host\" => \"jawa11.englab.brq.redhat.com\"), (\"server\" => \"server-one\"), (\"core-service\" => \"platform-mbean\"), (\"type\" => \"runtime\") ]", "rolled-back" => true } {noformat} Also attached screenshot.