New Member.
106 views

timeout uploading to cloudscan

I keep getting a timeout error when I try to submit a job for cloud scan.  Is there a way to increase the timeout?

Here's the end of output from running my batch file that I generated using ScanWizard:

Time Elapsed 00:14:19.99
Testing Difference between Translations
Starting cloud scan
Log files will be stored in "C:\Users\<redacted>\AppData\Local\Fortify\cloudscan\log" directory.
Retrieving controller URL...
Verifying controller URL...
Controller at https://<redacted>:8445/cloud-ctrl is UP
No email address detected. No status emails will be sent for this job.
WARNING: deprecated parameter names 'versionname' 'project' were used. Start using new names, see command help.
Retrieving SCA version...
Exporting MBS...
Compressing job files...
Restructuring SCA arguments...
Uploading job...
An exception occurred; org.springframework.web.client.ResourceAccessException: I/O error on POST request for "https://<redacted>:8445/cloud-ctrl/rest/job": Read timed out; nested exception is java.net.SocketTimeoutException: Read timed out
Shutting down with errors. Please see log for details.

 

The cloudscan.log file contains this:

 

2020-03-26 15:25:52,198 [INFO] com.fortify.cloud.cli.Main - Initializing: CloudScan version: 19.1.0.2238
2020-03-26 15:25:52,206 [WARN] com.fortify.cloud.cli.util.ArgHelper - C:\Fortify\Fortify_SCA_and_Apps_19.1.0\Core\config\cloudscan.properties (The system cannot find the file specified)
2020-03-26 15:25:52,207 [INFO] com.fortify.cloud.cli.command.UnrecognizedArgumentCommand - Executing
2020-03-26 15:25:52,210 [INFO] com.fortify.cloud.cli.command.FindUrlCommand - Executing
2020-03-26 15:25:55,437 [INFO] com.fortify.cloud.cli.command.PingCommand - Executing
2020-03-26 15:25:56,113 [INFO] com.fortify.cloud.cli.command.SscLockdownCommand - Executing
2020-03-26 15:25:56,303 [INFO] com.fortify.cloud.cli.command.SscLockdownCommand - SSC lockdown mode is disabled
2020-03-26 15:25:56,303 [INFO] com.fortify.cloud.cli.command.GetDescriptiveDataCommand - Executing
2020-03-26 15:25:56,303 [INFO] com.fortify.cloud.cli.command.GetStartModeCommand - Executing
2020-03-26 15:25:56,304 [WARN] com.fortify.cloud.cli.command.GetStartModeCommand - Deprecated parameter names usage: 'versionname' 'project'
2020-03-26 15:25:56,305 [INFO] com.fortify.cloud.cli.command.ScaVersionCommand - Executing
2020-03-26 15:25:58,853 [INFO] com.fortify.cloud.cli.command.ExportMbsCommand - Executing
2020-03-26 15:27:33,621 [INFO] com.fortify.cloud.cli.command.CompressJobFilesCommand - Executing
2020-03-26 15:27:37,604 [INFO] com.fortify.cloud.cli.command.RestructureScaArgsCommand - Executing
2020-03-26 15:27:37,609 [INFO] com.fortify.cloud.cli.command.UploadCommand - Executing
2020-03-26 15:27:37,611 [INFO] com.fortify.cloud.cli.command.UploadCommand - Uploading 89667929 byte file
2020-03-26 15:27:49,169 [ERROR] com.fortify.cloud.cli.Main -
org.springframework.web.client.ResourceAccessException: I/O error on POST request for "https://<redacted>:8445/cloud-ctrl/rest/job": Read timed out; nested exception is java.net.SocketTimeoutException: Read timed out
at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:674) ~[spring-web-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:621) ~[spring-web-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.web.client.RestTemplate.postForObject(RestTemplate.java:388) ~[spring-web-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at com.fortify.cloud.cli.command.UploadCommand.execute(UploadCommand.java:74) ~[cloud-cli-19.1.0.3007.jar:?]
at com.fortify.cloud.cli.AbstractMain.executeChain(AbstractMain.java:181) [cloud-cli-19.1.0.3007.jar:?]
at com.fortify.cloud.cli.Main.main(Main.java:64) [cloud-cli-19.1.0.3007.jar:?]
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method) ~[?:1.8.0_181]
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) ~[?:1.8.0_181]
at java.net.SocketInputStream.read(SocketInputStream.java:171) ~[?:1.8.0_181]
at java.net.SocketInputStream.read(SocketInputStream.java:141) ~[?:1.8.0_181]
at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) ~[?:1.8.0_181]
at sun.security.ssl.InputRecord.read(InputRecord.java:503) ~[?:1.8.0_181]
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) ~[?:1.8.0_181]
at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) ~[?:1.8.0_181]
at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) ~[?:1.8.0_181]
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) ~[?:1.8.0_181]
at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) ~[?:1.8.0_181]
at java.io.BufferedInputStream.read(BufferedInputStream.java:345) ~[?:1.8.0_181]
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) ~[?:1.8.0_181]
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) ~[?:1.8.0_181]
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1587) ~[?:1.8.0_181]
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492) ~[?:1.8.0_181]
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) ~[?:1.8.0_181]
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:347) ~[?:1.8.0_181]
at org.springframework.http.client.SimpleClientHttpResponse.getRawStatusCode(SimpleClientHttpResponse.java:52) ~[spring-web-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.web.client.DefaultResponseErrorHandler.hasError(DefaultResponseErrorHandler.java:50) ~[spring-web-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.web.client.RestTemplate.handleResponse(RestTemplate.java:696) ~[spring-web-4.3.15.RELEASE.jar:4.3.15.RELEASE]
at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:661) ~[spring-web-4.3.15.RELEASE.jar:4.3.15.RELEASE]
... 5 more
2020-03-26 15:27:49,182 [FATAL] com.fortify.cloud.cli.Main - An exception occurred.
2020-03-26 15:27:49,182 [INFO] com.fortify.cloud.cli.Main - Shutting down with errors.

Labels (1)
0 Likes
1 Reply
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: timeout uploading to cloudscan

Hi

Did you try to increase the timeout in server xml for the controller?

you can find something here

https://stackoverflow.com/questions/17079273/java-net-sockettimeoutexception-read-timed-out-under-tomcat

If a connectionTimeout value is set on the connector, it may need to be increased - e.g. from 20000 milliseconds (= 20 seconds) to 120000 milliseconds (= 2 minutes). If no connectionTimeout property value is set on the connector, the default is 60 seconds - if this is insufficient, the property may need to be added.

 

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.