Mendix SDK unable to download Working Copy with DB snapshot: Broken pipe (Write failed) or 413 Request Entity Too Large error

0
I'm no longer able to download a working copy of 1 project after a certain revision using the Mendix SDK: Creating new online working copy for project 9273b39b-0329-4797-a2ba-46e9ae36850b : XXXXX Error3: com.mendix.modules.microflowengine.MicroflowException: com.mendix.core.CoreRuntimeException: com.mendix.systemwideinterfaces.MendixRuntimeException: communitycommons.UserThrownException: ab2e4583-6181-49ab-9d49-fae1bf297828: Failed to expose Team Server app revision as Online Working Copy: 9273b39b-0329-4797-a2ba-46e9ae36850b Details: com.mendix.modules.microflowengine.MicroflowException: com.mendix.core.CoreRuntimeException: com.mendix.systemwideinterfaces.MendixRuntimeException: java.lang.RuntimeException: Unable to parse HTTP response: Broken pipe (Write failed) at ModelApiClient.CreateModelApiWorkingCopy (JavaAction : 'CreateModelApiWorkingCopy_Java') at MpkUploadService.TransferTeamServerMpkToModelServer_WrappedWithWorkingDir (SubMicroflow : 'CreateModelApiWorkingCopy') at MpkUploadService.TransferTeamServerMpkToModelServer (SubMicroflow : 'TransferTeamServerMpkToModelServer_WrappedWithWorkingDir') Advanced stacktrace: at PCP_ProjectsAPI.ExposeTeamServerRevisionAsOnlineWorkingCopy (JavaAction : 'ThrowException') Advanced stacktrace: I noticed that a 300MB is causing problems with creating a new working copy. Are there limitations on what you can check in or is this an SDK "bug"?
asked
2 answers
0

This is probably due to a 5 minute default timeout in the SDK when checking out a working copy. It seems that this timeout expires with big team server projects.

answered
0

The Mendix SDK FAQ indicates a maximum of 250MB for a project.

answered