Bug 1314388

Summary:

ejb3 -> Strict Max Bean Instance Pool: failed to change configuration parameters

Product:

[JBoss] JBoss Operations Network

Reporter:

Hayk Hovsepyan <hhovsepy>

Component:

Plugin -- JBoss EAP 7

Assignee:

Michael Burman <miburman>

Status:

CLOSED CURRENTRELEASE

QA Contact:

Hayk Hovsepyan <hhovsepy>

Severity:

medium

Docs Contact:

Priority:

medium

Version:

JON 3.3.5

CC:

fbrychta, jmartine, loleary, miburman, spinder

Target Milestone:

CR01

Keywords:

Triaged

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-06-06 18:58:19 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:

Bug Depends On:

Bug Blocks:

1314853

Attachments:

Description	Flags
server.log	none

Description Hayk Hovsepyan 2016-03-03 13:39:27 UTC

Description of problem:
It is not possible to change ejb3 subsystem's "Strict Max Bean Instance Pool" configuration property values.

Version-Release number of selected component (if applicable):
Version 3.3
Update-03
DR01 
jon-plugin-pack-eap-3.3.0.GA.zip

How reproducible:
always

Steps to Reproduce:
1. Change some of property values, for instance "Max Pool Size". Save them.
2. Reload the properties. Values will be the old ones.


Actual results:
New values are not saved.

Expected results:
Should be saved as happens for EAP6 plugin.

Comment 1 Hayk Hovsepyan 2016-03-04 08:30:09 UTC

Created attachment 1133108 [details]
server.log

Attaching server log which happens after clicking save.

Comment 2 Hayk Hovsepyan 2016-03-04 08:32:10 UTC

Alert message which shows after saving and returning to "Current" subtab of Configurations:

"Failed to retrieve member Resource configurations for [ResourceGroup[id=10032, name=ejb3 ( Strict Max Bean Instance Pool ), category=COMPATIBLE, type=Strict Max Bean Instance Pool, isDynaGroup=false, isClusterGroup=false]]"

"Current" subtab is empty here.

Comment 3 Michael Burman 2016-03-08 14:53:37 UTC

The reason is that max-pool-size and derived-size can't be both used in EAP7.

Comment 4 Michael Burman 2016-03-10 13:23:48 UTC

In the master:

commit f7a8a1e389cca25e8aa6b2aec6e1bb26de46e582
Author: Michael Burman <miburman>
Date:   Thu Mar 10 15:23:07 2016 +0200

    [BZ 1314388] Update properties of pool-configuration in EJB3 and send only max-pool-size or derive-size to the server

Comment 5 Mike McCune 2016-03-28 23:06:24 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 8 Hayk Hovsepyan 2016-04-01 12:00:19 UTC

Tested on revision: jon-plugin-pack-eap-3.3.0.GA-update-04-DR02.

Still not able to save neither "Derive Size" nor "Max Pool Size".

Steps:
Unset one of them, set the another one.
Save.
It still shows the old values.

Tried with JBoss CLI manally, it works.

Comment 9 Michael Burman 2016-04-04 12:48:26 UTC

Fixed in the master:

commit e882ea67aa642eb9821424f41dfd15abcb0d1729
Author: Michael Burman <miburman>
Date:   Mon Apr 4 15:47:52 2016 +0300

    [BZ 1314388] Using composite operation to do undefine for derive-size

Comment 12 Hayk Hovsepyan 2016-04-12 14:43:45 UTC

Verified on revision jon33-eap-update04 ER01

Comment 17 Hayk Hovsepyan 2016-04-29 14:27:02 UTC

Verified on revision jon33-eap-update04 CR01.