Github user geomacy commented on the issue:
https://github.com/apache/brooklyn-server/pull/672
I have **finally** got round to doing a test on this, sorry to have taken
so long.
I will attach a couple of zip files here for test purposes, each being a
separate -SNAPSHOT revision of a simple blueprint. The second builds upon the
first, getting a bit more complicated.
My first test zip file causes an error when I try to upload it; what you
see on the command line is
br catalog add file://$(pwd)/test672a.zip
json: cannot unmarshal string into Go value of type
models.CatalogEntitySummary
and in the Karaf log you get
2017-05-26 15:46:42,844 WARN 121
o.a.b.u.c.j.ErrorAndToStringUnknownTypeSerializer [qtp941342355-186] Standard
serialization not possible for class
org.apache.brooklyn.rest.resources.CatalogResource$BundleInstallationRestResult
(org.apache.brooklyn.rest.resources.CatalogResource$BundleInstallationRestResult@3f7a9dbf)
... lots of repetition deleted...
com.fasterxml.jackson.databind.JsonMappingException: Infinite recursion
(StackOverflowError) (through reference chain:
org.apache.brooklyn.core.relations.ByObjectBasicRelationSupport["source"]->org.apache.brooklyn.core.typereg.BasicManagedBundle["relations"]->org.apache.brooklyn.core.relations.ByObjectBasicRelationSupport["source"]->org.apache.brooklyn.core.typereg.BasicManagedBundle["relations"]->org.apache.brookly
at
com.fasterxml.jackson.databind.ser.std.BeanSerializerBase.serializeFields(BeanSerializerBase.java:694)
at
com.fasterxml.jackson.databind.ser.BeanSerializer.serialize(BeanSerializer.java:157)
at
com.fasterxml.jackson.databind.ser.BeanPropertyWriter.serializeAsField(BeanPropertyWriter.java:672)
at
com.fasterxml.jackson.databind.ser.std.BeanSerializerBase.serializeFields(BeanSerializerBase.java:678)
at
com.fasterxml.jackson.databind.ser.BeanSerializer.serialize(BeanSerializer.java:157)
at
com.fasterxml.jackson.databind.ser.BeanPropertyWriter.serializeAsField(BeanPropertyWriter.java:672)
... many lines deleted...
I tested the same file against `master` and it loads ok there, so I think
there is something in the PR to cause this.
I will see if I can make a bit of time next week to look at this again and
investigate what's going on.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
