+++ This bug was initially created as a clone of Bug #833187 +++ Description of problem: Three list properties should be sent as null if empty to the AS7. The current implementation treats all the lists in an equal manner, if the list is empty then an empty list is sent back to AS7 for a configuration update. The three list properties identified so far are: static-connectors (from Cluster Connection of HornetQ), static-connectors (from Bridge of HornetQ), and remoting-inceptors (of HornetQ). How reproducible: Every time Steps to Reproduce: 1. Discovery and import an AS7 standalone server 2. Find the resource with the following path subsystem=messaging,hornetq-server=default,cluster-connection=my-cluster 3. Try to update the resource configuration. Actual results: The following error is received from AS7: {JBAS014653: Composite operation failed and was rolled back. Steps that failed:={Operation step-16=JBAS014706: [0] is an invalid size for parameter static-connectors. A minimum length of [1] is required}}, Expected results: The update should happen without an error. Additional info: For most cases sending an empty list back to the server is correct way of setting the property to empty; in those cases sending an null value will result in errors. So this update needs to be specific for the properties identified. --- Additional comment from snegrea on 2012-06-18 17:56:22 EDT --- Added support for nullable lists. If a nullable list is empty then send back to the AS7 the null value instead of an empty list.
release/jon3.1.x branch commit: http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commit;h=3e354dccd5859417ce58fb4b2f010e12bd1daad4
JON 3.1.1 ER1 build is available. Moving to ON_QA. https://brewweb.devel.redhat.com/buildinfo?buildID=226942
reopened. There are no errors visible neither on logs nor int the UI, but the update is not being done. additional info: This may be the same problem as - https://bugzilla.redhat.com/show_bug.cgi?id=843514 and https://bugzilla.redhat.com/show_bug.cgi?id=844434
A couple more updates were required to the loading and writing code for nullable lists. The code did not handle well the loading from JSON. Please retest. This bug is not related at all to bug 844434. The new commit to release/jon3.1.x branch: http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?h=release/jon3.1.x&id=b40c6d9c81f01382ffd2a8321b7e0a81b5e7e682
Moving to ON_QA. The JON 3.1.1 ER3 build is available at https://brewweb.devel.redhat.com/buildinfo?buildID=230321.
bug#846400 is being reproduced by this steps, so marking back to on_dev.
Bug 846400 is something totally different and triggered by setting connector and discovery groups at once. as7 does not catch that on the api and writes a bogus configuration to disk. It has nothing to do with this case of empty lists. There is an issue here though (again reproducible with : connection-factory=InVmConnectionFactory) If you unset the connector and add a discovery group the config update will fail with: Null key for a Map not allowed in JSON (use a converting NullKeySerializer?), rolled-back=false, rolled-back=false
Created bug 852534 to resolve the error mentioned in comment 8 with regards to the connector property.
Please retest updating the properties for this resource type. This issue has been resolved by other fixes applied to the AS7 plugin.
The CR1 build is available at https://brewweb.devel.redhat.com/buildinfo?buildID=231258. Moving to ON_QA.
verified. discovery group and static connector are non-editable anymore.
Bulk closing of old issues in VERIFIED state.