When Publishing larger items(>100MB) stuck at transporting phase for long time and getting failed.

We have 4 publishers running with 2 Rendering, 2 Deploying threads on each server

We have 1 deployer.

Currently, we have applied CD_8.5.0.6435 hot fix and increased the SendTimeout to "960000 ms" in cd_transport.config suggested by SDL support still the same issue persist.

Before that SDL support team suggested to apply hot fix CD_8.5.0.3725 to resolve issue but this also didn't help us out.

These failures happen in the "Transporting" phase.

Transport log errors:

 2018-11-02 06:45:40,075 DEBUG StepPrepare - Zipping has been completed successfully for transaction: tcm:0-2383794-66560
2018-11-02 06:45:40,121 INFO  ParallelTransportWorker - Scheduling sending TransportPackage to destinations for transaction: tcm:0-2383794-66560
2018-11-02 06:45:40,121 DEBUG DestinationControllerFactory - Returning existing destination controller.
2018-11-02 06:45:40,121 DEBUG ParallelTransportWorker - TransportPackage transport has been scheduled, blocking and waiting for result for transaction: tcm:0-2383794-66560
2018-11-02 06:45:40,121 DEBUG ParallelDestinationWorker - Waiting for transport result for: tcm:0-2383794-66560
2018-11-02 06:45:40,121 DEBUG TransportSender - Starting TransportSender for transportPackage D:\Program Files (x86)\SDL Web\bin\transactions\tcm_0-2383794-66560.Content.zip and destination OnvfQIG9nRtElNqYzK9fzg==. 
    2018-11-02 06:45:40,137 DEBUG TransportPoolManager - Returning a freely available and alive TransportConnector
2018-11-02 06:45:40,137 DEBUG TransportSender - Starting sending of transportPackage D:\Program Files (x86)\SDL Web\bin\transactions\tcm_0-2383794-66560.Content.zip to destination OnvfQIG9nRtElNqYzK9fzg==. 
2018-11-02 06:49:40,219 DEBUG DestinationControllerMonitor - Cleaning up destination controllers.
2018-11-02 06:49:40,219 DEBUG DestinationController - Idle(ms): 240098, Notifications: true
2018-11-02 06:54:40,223 DEBUG DestinationControllerMonitor - Cleaning up destination controllers.
2018-11-02 06:54:40,223 DEBUG DestinationController - Idle(ms): 540102, Notifications: true
2018-11-02 06:59:40,216 DEBUG DestinationControllerMonitor - Cleaning up destination controllers.
2018-11-02 06:59:40,216 DEBUG DestinationController - Idle(ms): 840095, Notifications: true
2018-11-02 07:01:40,137 ERROR ParallelDestinationWorker - Timeout of 960000 ms exceeded for transaction tcm:0-2383794-66560
java.util.concurrent.TimeoutException: null
at java.util.concurrent.FutureTask.get(Unknown Source) at com.tridion.transport.workers.ParallelDestinationWorker.blockAndGetResult(ParallelDestinationWorker.java:109)
at 
 com.tridion.transport.workers.ParallelTransportWorker.doWork(ParallelTransportWorker.java:49)
at com.tridion.transport.model.transaction.context.StepTransport.execute(StepTransport.java:54)
at com.tridion.transport.model.transaction.context.StepPrepare.lambda$execute$0(StepPrepare.java:57)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2018-11-02 07:01:40,137 DEBUG BaseHTTPSTransportConnector - Aborting current post to http://*****:9084/httpupload
2018-11-02 07:01:40,137 DEBUG BaseHTTPSTransportConnector - Aborted current post to http://*****:9084/httpupload
2018-11-02 07:01:40,137 DEBUG BaseHTTPSTransportConnector - Unable to execute: send on destination: http://*****:9084/httpupload due to: java.net.SocketException. Attempt=1; MaxRetries=5; Exception: Socket closed
2018-11-02 07:04:40,215 DEBUG DestinationControllerMonitor - Cleaning up destination controllers.
2018-11-02 07:04:40,215 DEBUG DestinationController - Idle(ms): 1140094, Notifications: true
2018-11-02 07:09:40,227 DEBUG DestinationControllerMonitor - Cleaning up destination controllers.
2018-11-02 07:09:40,227 DEBUG DestinationController - Idle(ms): 1440106, Notifications: true
2018-11-02 07:14:40,229 DEBUG DestinationControllerMonitor - Cleaning up destination controllers.
2018-11-02 07:14:40,229 DEBUG DestinationController - Idle(ms): 1740108, Notifications: true
2018-11-02 07:19:40,229 DEBUG DestinationControllerMonitor - Cleaning up destination controllers.
2018-11-02 07:19:40,229 DEBUG DestinationController - Idle(ms): 2040108, Notifications: true
2018-11-02 07:24:40,229 DEBUG DestinationControllerMonitor - Cleaning up destination controllers.
2018-11-02 07:24:40,229 DEBUG DestinationController - Idle(ms): 2340108, Notifications: true
2018-11-02 07:29:40,231 DEBUG DestinationControllerMonitor - Cleaning up destination controllers.
2018-11-02 07:29:40,231 DEBUG DestinationController - Idle(ms): 2640110, Notifications: true

Please let me know your thoughts.

  • 1
    Just a thought, it's possible that the issue lies on the Deployer side, e.g. the HTTP max request size setting might be too small. Take a dig through some of the older posts circa 2010-2013 where this was a configuration issue with older Tridion versions. Could be the same thing wrapped in a different exception message. – Nickoli Roussakov Nov 2 at 14:02
  • Also look for some clues in the Deployer log. – Nickoli Roussakov Nov 2 at 14:18
  • @nickoli In deployer application.properties HTTP max request size is 100Mb – k951 Nov 3 at 4:10
  • 1
    Looks like that is your problem then. – Nickoli Roussakov Nov 3 at 12:12
  • Sorry that is typo mistake in deployer application properties HTTP max request size is 1000MB and max-file-size=1000Mb – k951 Nov 5 at 13:21

Seems to look like still your package size still larger than 100MB

Try following steps to troubleshoot to fix:

Content Manager

  1. Capture that Large published transport package item by Modify your cd_transport_conf.xml, add a "Cleanup" attribute with the value of false to the Workfolder element:

<WorkFolder Location="./transactions" NotificationBatchSize="10" Cleanup="false"/>

The packages will appear in [Tridion-Home]\bin\transactions.

  1. Find out the size of the transport package file which getting failed, adjust the upload size in the deployed service.

  2. Worth review this cd_transport_conf.xml config timeout values.

<Polling MaxAttempts="900" Timeout="15" Interval="5000"/>

<Senders SendTimeout="960000"/>

Restart the transport service for this change to take effect.

Content Delivery:

In your deployer service application.properties file to increase the maximum size permitted for uploaded/allowed for files requests according to your maximum package size requirements

spring.http.multipart.max-file-size=300Mb

spring.http.multipart.max-request-size=300Mb

Clean up the package incoming folders and Restart your deployer for these changes to take effect.

DONT FORGET TO REVERT cd_transport_conf.xml, "Cleanup" attribute property once your issue got resolved.

I hope it helps.

  • Sorry that is typo mistake in deployer application properties HTTP max request size is 1000MB and max-file-size=1000Mb and tried all the steps whichever you have mentioned before raising question . The packages size are 876MB, 312MB – k951 Nov 5 at 5:21

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.