Skip to main content
S
17-Peridot
ScottMorris17-Peridot
17-Peridot
April 26, 2023
Solved

AWS Error Message: "com.amazonaws.SdkClientException: Unable to execute HTTP request"

  • April 26, 2023
  • 4 replies
  • 3768 views

Looking for others with AWS private cloud implementations,

 

We are experiencing the following failure and error message in the BGMS logs when attempting to ZIP a large Package Delivery. We have a top priority case open with PTC, but have not made any headway in two weeks. Curious if anyone else has experienced this issue with Windchill hosted in AWS?

 

ERROR [WPSyncQueue.PollingThread] com.ptc.windchill.wp.action.DefaultActionDelegate Administrator - Delivery ZIP file could not be created. Contact your administrator if the problem persists. wt.util.WTException: com.amazonaws.SdkClientException: Unable to execute HTTP request: The target server failed to respon. Nested exception is: com.amazonaws.SdkClientException: Unable to execute HTTP request: The target server failed to respond

 

We have a similar issue but no error messages, preventing us from uploading a primary content file larger than 1GB for a Windchill Document. Never had problems when the servers were in the data center, but something is now preventing an upload to Windchill when larger than 1gb.

Best answer by ScottMorris

Apologies, never posted the solution here. PTC identified the software defect with the AWS handshake and corrected it in 12.0.2 CPS13

4 replies

B
BryanK16-Pearl
16-Pearl
May 4, 2023

Hi,

I was wondering if you had managed to get this sorted. You didn't add the windchill version.

I think it could be related to Apache time out or upload limit.

Have a look at these two calls. One is related to upload limit and the other is Apache timeout.

https://www.ptc.com/en/support/article/CS378894

https://www.ptc.com/en/support/article/CS75225

 

S
17-Peridot
ScottMorris17-PeridotAuthor
17-Peridot
May 4, 2023

Oh right, this is Windchill 12.0.2.9. We are experiencing the same behavior with CPS11 on our non-production systems. I found a PTC SPR related to this issue reported as fixed in CPS08, but it did not fix our issue. We are digging deep into the vaults now to make sure nothing is mismatched. We are continuing to work with PTC TS on this issue.

S
17-Peridot
ScottMorris17-PeridotAuthor
17-Peridot
May 9, 2023

Exciting news, PTC found the 1GB file upload limitation in the latest version of Apache!

https://www.ptc.com/en/support/article/cs378894

If you have the same issue, just follow the guidance in this CS Article.

Setting LimitRequestBody to 0 makes file upload limitless. We opted for 4GB and we'll see how that goes.

    S
    17-Peridot
    ScottMorris17-PeridotAuthor
    17-Peridot
    May 9, 2023

    We are still working with PTC on the AWS error message during Package ZIP. It does not appear to be an issue with our AWS architecture, but rather a connection/timeout issue connecting to the servers when the ZIP process is running on the BGMS. We are getting the same errors on our DEV monolithic implementation and our TEST & PROD cluster implementation. The problem appears to be data specific because one package will ZIP without errors while another will not ZIP successfully.

    S
    17-Peridot
    ScottMorris17-PeridotAuthorAnswer
    17-Peridot
    December 6, 2023

    Apologies, never posted the solution here. PTC identified the software defect with the AWS handshake and corrected it in 12.0.2 CPS13

      Terms & ConditionsCookie settingsAccessibility statement