topic Re: SAS Studio 3.8 - Problems when trying to upload a file in SAS Studio

SAS Studio 3.8 - Problems when trying to upload a file

mvcastro — Wed, 02 Jun 2021 06:53:30 GMT

We need to upload a file to SAS Studio but the file upload limit is set at 500 mb and the file is close to 3 Gb. We have the following error: "The size of the uploaded files cannot be greater than 500 MB. The size of the selected files is 2,8Gb.

How can I change that limit?
Is there any limitation on the maximum size?

Thanks

Re: SAS Studio 3.8 - Problems when trying to upload a file

Manoj07k — Fri, 04 Jun 2021 00:52:42 GMT

Please ref this doc : https://go.documentation.sas.com/doc/en/calcdc/3.4/calconfig/n08025sasconfiguration0admin.htm#n08001sasconfiguration0admin

Large files can take a long time to load. If you have a large amount of content to upload, divide your content into smaller files if possible

Re: SAS Studio 3.8 - Problems when trying to upload a file

mvcastro — Fri, 04 Jun 2021 06:09:42 GMT

Thanks for the reply.

Following that doc, I changed the webdms.maxUploadSize parameter and I set it to 4,3GB. Once the change was made, I tried to upload the same file and now I have this error:

I did several tests and the max file size that I manage to upload is 2GB. In Catalina´s log, I have this error:

2021-06-02 11:48:01,580 [tomcat-http--2] ERROR [unknown] org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/SASStudio].[coderServlet] - El Servlet.service() para el servlet [coderServlet] en el contexto con ruta [/SASStudio] lanzó la excepción [Request processing failed; nested exception is org.springframework.web.multipart.MultipartException: Could not parse multipart servlet request; nested exception is org.apache.commons.fileupload.FileUploadBase$IOFileUploadException: Processing of multipart/form-data request failed. null] con causa raíz
java.net.SocketTimeoutException
at org.apache.tomcat.util.net.NioBlockingSelector.read(NioBlockingSelector.java:201)
at org.apache.tomcat.util.net.NioSelectorPool.read(NioSelectorPool.java:235)
at org.apache.tomcat.util.net.NioSelectorPool.read(NioSelectorPool.java:216)

I don´t know if there is any limit to the file size regardless of the webdms.maxUploadSize parameter. Or maybe there is some proxy level restriction that prevents the upload of such large files, or a problem with the java configuration... I don´t know.

Thanks a lot!

Re: SAS Studio 3.8 - Problems when trying to upload a file

Manoj07k — Sat, 05 Jun 2021 01:34:35 GMT

Not sure about proxy thing @mvcastro. The best option I would suggest is please open a track with SAS .

Also if your ultimate goal is to convert raw data in file into dataset then you can try PROC IMPORT.

Thanks

Re: SAS Studio 3.8 - Problems when trying to upload a file

mvcastro — Mon, 07 Jun 2021 06:00:53 GMT

It doesn´t go by proxy, so this isn´t the problem.
Could it be a timeout problem? (for the error in catalina.out)
Perhaps the parameter "–Dvsd.lasr.client.timeout = number of minutes" should be specified in JVM_OPTS with a value large enough. I don´t know...

I keep investigating. Thank you

Re: SAS Studio 3.8 - Problems when trying to upload a file

Kurt_Bremser — Mon, 07 Jun 2021 07:42:15 GMT

Since this is not SAS ODA, why don't you do a direct SFTP upload, using a tool like WinSCP or Filezilla? These provide for automatic resumes, and the SSH/SFTP protocol is inherently faster than HTTPS.

Re: SAS Studio 3.8 - Problems when trying to upload a file

mvcastro — Mon, 07 Jun 2021 08:56:36 GMT

Thank you so much. That would be the best solution but end users are not allowed access via ftp or via winscp.
Finally I think I have solved it by adding the "–Dvsd.lasr.client.timeout=30" parameter in JVM_OPTS.

I have tried it and now large files (4GB for example) can be uploaded.

Regards!

Re: SAS Studio 3.8 - Problems when trying to upload a file

Kurt_Bremser — Mon, 07 Jun 2021 09:45:09 GMT

@mvcastro wrote:

Thank you so much. That would be the best solution but end users are not allowed access via ftp or via winscp.

So you have Mordacs disguising as admins.