Код: Выделить всё
try {
containerApi(tenant).updateContainerStorageUri(
tenant,
containerId,
updateContainerRequest).block();
} catch (RuntimeException e) {
log.error("Exception while updating storageURI for container",
v(StructuredLoggingFields.TENANT_ID, tenant),
v(StructuredLoggingFields.CONTAINER_ID, containerId),
v(StructuredLoggingFields.EXCEPTION_MESSAGE, e.getMessage()),
v(StructuredLoggingFields.EXCEPTION, e));
throw e;
}
< /code>
Когда ошибка возникает Encoder logstack rescack encoder сообщает о следующем < /p>
signal-offloader-84b96dbb4c-6cgbd signal-offloader 15:34:54,345 |-WARN in
net.logstash.logback.encoder.LoggingEventCompositeJsonEncoder@59febcf9 -
Error encountered while encoding log event. Event: [ERROR] Exception while
updating storageURI for container com.fasterxml.jackson.databind.exc.InvalidDefinitionException:
Direct self-reference leading to cycle (through reference chain: org.springframework.web.reactive
.function.client.WebClientResponseException$Conflict["mostSpecificCause"])
< /code>
за ребята Logstash для аналогичной проблемы: < /p>
As far as I can tell, the problem is caused by Jackson that complains about a cycle in the object graph to serialise. . . .
This likely comes from an object you added to the log via the
StructuredArguments feature. There is unfortunately not much
logstash-logback-encoder can do about it... You should definitely
look at what solution Jackson has to offer to work around this situation.
Offloader
app
ts
UTC
level
class
method
line
thread
false
,
stack
msg
< /code>
Примечание: я не вижу, чтобы это происходило перед моим обновлением до Spring Boot 3.5.0 < /p>
оцените какие -либо идеи, обходные пути или исправления. Спасибо! < /P>
Обновление: я только теперь только что узнал < /p>
Do NOT use structured arguments or markers for exceptions.
[/code]
https://github.com/logfellow/logstash-l ... ack-traces
Подробнее здесь: https://stackoverflow.com/questions/797 ... tion-due-t