Fedora Account System
Red Hat Associate
Red Hat Customer
The updateConfiguration API calls return PluginResourceUpdate or ResourceConfigurationUpdate depending on the config type. When called remotely via jbossws we get an error: [com.sun.istack.SAXException2: A cycle is detected in the object graph. This will cause infinitely deep XML: ResourceConfigurationUpdate[status=In Progress, configuration=Configuration[id=503052, notes=null], subjectName=ws-test, createdTime=1226344038239, modifiedTime=1226344038240, errorMessage=null, id=501051, resource=Resource[id=500055, *************** LOOKS LIKE THIS RESOURCE RECURSES ************** type=JBossAS Server, key=C:\Eclipse-ws\rhq\dev-container\jbossas\server\default, name=jshaughnessy-PC RHQ Server, JBossAS 4.2.1.GA default (0.0.0.0:2099), version=4.2.1.GA]] -> Resource[id=500055, *************** HERE IT IS AGAIN *************** type=JBossAS Server, key=C:\Eclipse-ws\rhq\dev-container\jbossas\server\default, name=jshaughnessy-PC RHQ Server, JBossAS 4.2.1.GA default (0.0.0.0:2099), version=4.2.1.GA] -> ResourceConfigurationUpdate[status=In Progress,configuration=Configuration[id=503052, notes=null], subjectName=ws-test,createdTime=1226344038239, modifiedTime=1226344038240, errorMessage=null, id=501051, resource=Resource[id=500055, *************** AGAIN *************** type=JBossAS Server, key=C:\Eclipse-ws\rhq\dev-container\jbossas\server\default, name=jshaughnessy-PC RHQ Server, JBossAS 4.2.1.GA default (0.0.0.0:2099), version=4.2.1.GA]]] The update succeeds, this is in the return processing
This most likely needs judicious placement of an @XmlTransient
We're first working to get java clients working via jboss remoting. After that we'll revisit WS clients and jaxb serialization issues.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1099
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
jshaugh, is this still an issue?