Skip to main content
1-Visitor
December 11, 2012
Question

Publishing Engine 6.0 m010: APE Request Failure. Failed to save body file to ....rq_4746\rqbody.dat

  • December 11, 2012
  • 1 reply
  • 607 views
Changing PE's maxBusyInterval did not resolve the problem. Support is now
recommending I change Tomcat's connector configuration. They want me to add
disableUploadTimeout="false" a setting that if absent defaults to "true".
It seems counter-intuitive to me that disabling the disabling of a timeout
(isn't that enabling a timeout?) would "help" on a spotty network, but
maybe I'm reading the explanations for the setting wrong.

Chris: This is in line, I think, with what you were suggesting earlier.

This isn't the actual version of Tomcat I'm using but I assume the
explanation is still the same:

    1 reply

    naglists1-VisitorAuthor
    1-Visitor
    January 11, 2013
    Setting disableUploadTimeout="false" has resolved the problem. Whoo hoo!
    Thanks, PTC Support.

    I still maintain even after careful and repeated reading of the Tomcat
    documentation that changing the setting from the default "true" to "false"
    seems counter-intuitive as far as creating a connection tolerant of latency
    / dropped packets / jitter ... whatever the specific problem was that we
    were having with our WAN to India. But, it's a good day when you can close
    a ticket.