Bug 912805
| Summary: | Unable to change async-handler queue length | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Thomas Segismont <tsegismo> |
| Component: | Logging | Assignee: | James Perkins <jperkins> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1.0 | CC: | atangrin, brian.stansberry, jdoyle, pkremens, rhatlapa, rsvoboda, smcgowan |
| Target Milestone: | ER4 | ||
| Target Release: | EAP 6.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 911319 | ||
Why was the version changed to EAP 6.0.0.DR4 when the issue occurs in EAP 6.1.0.DR4. Not sure, history https://bugzilla.redhat.com/show_activity.cgi?id=912805 says it was done by John Doyle. I think it's accidental change, fixing version. Need an upstream bug for this. This BZ is filled against product, so this is the right place to solve the issue. If you need additional place to track your work, please create JIRA or what you prefer and link it with this BZ using 'External Trackers' section. The fix is made for ER4 which is not yet available for QA setting to MODIFIED (In ER3 it is not fixed) Verified on EAP 6.1.0 ER4 |
Description of problem: Changing an async-handler queue length does not work. Version-Release number of selected component (if applicable): EAP 6.1.DR4 How reproducible: Always Steps to Reproduce: 1. With EAP admin console create an aync-handler under the logging subsystem 2. Then edit the properties to change the queue length 3. Save Actual results: Queue length unchanged without error message. Expected results: Queue length should have been updated Additional info: It also doesn't work through the CLI: [standalone@localhost:10631 async-handler=ASYNC] :write-attribute(name=queue-length,value=511) { "outcome" => "failed", "failure-description" => "JBAS014746: queue-length may not be null", "rolled-back" => true }