Bug 1156233
| Summary: | Updating Blocking Bounded Queue Thread Pools fails when queue-length is 0 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Armine Hovsepyan <ahovsepy> | ||||||
| Component: | Plugin -- JBoss EAP 6 | Assignee: | Thomas Segismont <tsegismo> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Mike Foley <mfoley> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | JON 3.3.0 | CC: | fbrychta, hrupp, jshaughn, loleary, mfoley, myarboro, rhatlapa | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | One-off release | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-01-15 20:57:54 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: |
|
||||||||
Created attachment 950124 [details]
eap.log
Created attachment 950125 [details]
eap_cli.log
This is more likely an EAP bug than a JON bug. Typical, positive, queue-lengths don't have a problem and I think it's unlikely that a real-world definition would hit this problem, as a zero-length queue is not useful. To avoid this on the JON side would require plugin-level validation code, it's not possible to specify this sort of validation in the descriptor. I recommend post-ga (or even wont-fix is fine imo). +1 on what Jay said As per comment 3, this issue is being closed and will not be fixed. It appears 0 is an invalid value and although the resource configuration should probably perform data validation and enforce this, that capability does not currently exist in JBoss ON. In any case, if a queue length of 0 is an invalid value, the EAP error is valid and the user should ensure the value is greater then 0. |
Description of problem: Updating Blocking Bounded Queue Thread Pools fails when queue-length is 0 Version-Release number of selected component (if applicable): JON 3.3 ER05 + EAP 6.2.0 How reproducible: always Steps to Reproduce: 1. create a Updating Blocking Bounded Queue Thread Pools with 'queue length=0' 2. edit any attribute (queue length or any other) 3. Actual results: update fails with: {JBAS014653: Composite operation failed and was rolled back. Steps that failed:={Operation step-7=JBAS014792: Unknown attribute handoff-executor}}, rolled-back=true Fragment from EAP log attached (eap.log) Expected results: thread pool resource is editable Additional info: update of the same resouce from eap cli is possible without issues. Lot attached (eap_cli.log)