| Summary: | modcluster subsystem XSDs do not describe worker-timeout attribute | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Jay SenSharma <jsenshar> |
| Component: | mod_cluster | Assignee: | Radoslav Husar <rhusar> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michal Karm Babacek <mbabacek> |
| Severity: | low | Docs Contact: | Russell Dickenson <rdickens> |
| Priority: | low | ||
| Version: | 6.1.0 | CC: | darran.lofthouse, kkhan, mbabacek, rhusar, sjadhav, smumford |
| Target Milestone: | DR6 | ||
| Target Release: | EAP 6.3.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
In previous versions of JBoss EAP 6, the mod_cluster XSD used for validations did not specify worker-timeout attribute.
This meant that using XSD to validate configuration might have failed validation even though the configuration was correct and correctly parsed by the server.
The XSD schema has been fixed and now using XSD schema for validation when using worker-timeout attribute will now pass validation.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-28 15:43:56 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: | |
|
Description
Jay SenSharma
2013-10-17 06:51:30 UTC
Upstream Wildfly also has issue reported: https://issues.jboss.org/browse/WFLY-2303 No Jay, mod_cluster as such has virtually nothing to do with Clustering component. Radoslav Husar <rhusar> made a comment on jira WFLY-2303 https://github.com/wildfly/wildfly/pull/5272 Started the process for 6.3. -- there is no 6.3, so 6.2.. The upstream is already fixed, see WFLY-2303. @Michal: the reporter just copied the component from upstream issue where we dont differetiate between modcluster and clustering. Nevertheless, its better to use the specific component in EAP issue tracker. EAP 6.3.0.DR6 O.K. Documentation: this is minor, but I have provided the text anyway. |