If there are attachments during synchronization, an error will be reported

Originally asked by Bishihai on 09 November 2022 (original question)


No error will be reported when there is no attachment for synchronization,However, an error is reported when an attachment is synchronized.

Error Info:

Impact: ISSUELocal entity: OVSB16-912Remote entity: nullConnection: NOBO B16OS_to_GDC B16OSError type: Issue Tracker ErrorError Creation Time: 2022-11-08 17:52:53.0Error Detail Message: java.io.IOException: Error writing request body to server Error Stack Trace: com.exalate.api.exception.IssueTrackerException: java.io.IOException: Error writing request body to server
at com.exalate.transport.rest.client.v2_4.PublishBlobClient.executePublishAndReturnResult(PublishBlobClient.java:188)
at com.exalate.transport.rest.client.v2_4.PublishBlobClient.publishBlob(PublishBlobClient.java:84)
at com.exalate.transport.rest.client.v1.RestTransportProtocol$6.call(RestTransportProtocol.java:172)
at com.exalate.transport.rest.client.v1.RestTransportProtocol$6.call(RestTransportProtocol.java:169)
at com.exalate.transport.rest.client.v1.RestTransportProtocol.retry(RestTransportProtocol.java:438)
at com.exalate.transport.rest.client.v1.RestTransportProtocol.publishBlob(RestTransportProtocol.java:169)
at com.exalate.transport.TransportService.publishBlob(TransportService.java:76)
at com.exalate.replication.blob.event.PublishBlobIfNeededBlobEventState.transition(PublishBlobIfNeededBlobEventState.java:63)
at com.exalate.replication.blob.event.PublishBlobIfNeededBlobEventState.transition(PublishBlobIfNeededBlobEventState.java:38)
at com.exalate.replication.blob.out.BlobEventProcessorService.processBlobEvent(BlobEventProcessorService.java:110)
at com.exalate.replication.blob.out.BlobEventProcessorService.processBlobEvents(BlobEventProcessorService.java:92)
at com.exalate.replication.blob.out.BlobEventProcessorService.processBlobEvents(BlobEventProcessorService.java:84)
at com.exalate.replication.out.BlobEventWorker.runProcessing(BlobEventWorker.java:32)
at com.exalate.replication.ReplicationWorker.lambda$run$0(ReplicationWorker.java:85)
at com.exalate.node.util.concurrent.ClusteredSensitiveExecutorService.lambda$executeHandlingLocks$0(ClusteredSensitiveExecutorService.java:31)
at com.exalate.node.util.concurrent.ClusteredSensitiveExecutorService.executeHandlingLocks(ClusteredSensitiveExecutorService.java:52)
at com.exalate.node.util.concurrent.ClusteredSensitiveExecutorService.executeHandlingLocks(ClusteredSensitiveExecutorService.java:29)
at com.exalate.replication.ReplicationWorker.run(ReplicationWorker.java:78)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: Error writing request body to server
at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(HttpURLConnection.java:3587)
at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:3570)
at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2315)
at org.apache.commons.io.IOUtils.copy(IOUtils.java:2270)
at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2291)
at org.apache.commons.io.IOUtils.copy(IOUtils.java:2246)
at com.exalate.transport.rest.client.v2_4.PublishBlobClient.executePublishAndReturnResult(PublishBlobClient.java:158)
… 24 more
Incoming sync data: Summary: nullEntity Key: null(id: null)Encoded payload: null


Answer by Bishihai on 09 November 2022

exalate_support_5.3.8-j8_8.6.1_20221109-140520.zip (old community)

Update log Info


Comments:

Jillani Fazal commented on 10 November 2022

Hi Bishihai Thank you for sharing the support zip here. May I know if it would be possible for you to create a support ticket through our support portal, please?

Jillani Fazal commented on 10 November 2022

Hi Bishihai I have opened a ticket EASE-18041 on your behalf and will continue to provide assistance over there. Thank you!

Answer by Jillani Fazal on 09 November 2022

Hi Bishihai

Would it be possible for you to create a support ticket and also share the support zip files from both ends of the connection so that we can check thoroughly and address the concern there? The reason being is it looks like an issue which needs to be checked rather then a configuration scenario.

Thank you for understanding.

BR,

Jillani