As we are working to update our application to the version 4.2 services adn restesting, we discovered that there appears to be a problem with the findTermbyCode service call. If "allSynonymTypes" is set to true, or if it is set to false and specific SynonymTypes are specified, then the service returns the error:
<faultstring>Marshalling Error: A cycle is detected in the object graph. This will cause infinitely deep XML: com.apelon.dtsserver.types.TTerm@11808b75 -> com.apelon.dtsserver.types.TSynonym@5185582e -> com.apelon.dtsserver.types.TTerm@11808b75</faultstring>

We are using SynonymTypes in some other concept-related service calls, and it seems to work ok there.

Here is a sample call for SNOMED CT US Edition:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:dts="http://apelon.com/dtsserver/ws/dtsquery" xmlns:typ="http://apelon.com/dtsserver/types">
<soapenv:Header/>
<soapenv:Body>
<dts:findTermByCode>
<!--Optional:-->
<termCode>65256015</termCode>
<namespaceId>36</namespaceId>
<!--Optional:-->
<asd DEFAULT_LIMIT="0">
<!--Optional:-->
<typ:name>asd3</typ:name>
<!--Optional:-->
<typ:snapshotDate>2015-02-01</typ:snapshotDate>
<typ:attributesLimit>100</typ:attributesLimit>
<typ:allPropertyTypes>false</typ:allPropertyTypes>
<typ:allSynonymTypes>true</typ:allSynonymTypes>
</asd>
</dts:findTermByCode>
</soapenv:Body>
</soapenv:Envelope>

We have tried various combinations of things in the ASD to try to work around, but have not found anything that works yet.

Oh, one more potentially important piece of information. We are using MS SQL 2008 and 2012 as the back end database. It was created from scratch using the schema scripts that came with 4.2.

Hi Bill,

When you say you are using MS SQL 2008 and 2012, do you mean you have 2 databases one on 2008 and another on 2012, or are you saying your MS SQL version is 2008, running on a windows 2012 server box?

Sorry, we have some of each type of server. But we can focus on SQL server 2008R2 as the backend database we are using.