Hi,

I’m using Software AG Designer Version 10.7.I created a webMethods adapter for Apache Kafka. Connection type is Confluent for Kafka Consumer Connection.

I create adapter notification in service development perspective which takes an avro value schema. Recently I was given a schema which had a nested array in another array and both had the same name. This schema failed to load and in server logs I found below error:

Error Details:
Failed to run notificationLookupValues service. Details provided in error log.
schema contains circular dependency.
Caused by: java.lang.IllegalArgumentException: schema contains circular dependency.

Sample Extract of avro schema:

{
"name": "unitDetails",
"type": {
"items": {
"fields": [
{
"name": "num",
"type": "string"
},
{
"name": "id",
"type": "string"
},
{
"name": "unitDetails",
"type": {
"items": {
"fields": [
{
"name": "name",
"type": "string"
},
{
"name": "role",
"type": "string"
}
],
"name": "unitDetails_record_2",
"type": "record"
},
"type": "array"
}
}
],
"name": "unitDetails_record",
"type": "record"
},
"type": "array"
}
}

Kindly help to use such a schema which may have nested arrays with same name. The actual schema was validated properly and other team was able to send data.

— THANK YOU —

Do you have the latest adapter fix installed? There are some fixes for schema and avro handling, though I don’t see anything mentioned about handling circular dependencies.

Thanks Dave,

I’m using Adapter version 9.6 and update is WAK_9.6_Fix10. Is there a more recent update available?

Hi,

according to the Fix Explorer in Empower, latest Fix is WAK_9.6_Fix11.

Most related entries related to avro schema added in Fix 11 are the following:

WAK-261
In webMethods Adapter for Apache Kafka, listener notification fails to receive
the message when the Avro schema with a field of type array contains a single
item.

This issue is now resolved.

WAK-234
In webMethods Adapter for Apache Kafka, the Produce service fails to execute if
the Avro schema contains a nested array.

This issue is now resolved.

Regards,
Holger