Troubleshooting myFileGateway 2.0

If you encounter errors in the myFileGateway 2.0 application, use the troubleshooting tips.

myFileGateway 2.0 does not perform as expected

You can refer to the following error trace or log files when the myFileGateway 2.0 application does not perform as expected.
  • Browser network trace – provides information about network and console logs on browser
  • <Install_dir>/logs/cfx_gateway.log – provides information about API gateway related logs
  • <Install_dir>/logs/cfgapi.logs – provides information about SFG APIs, which are internally used by myFileGateway 2.0 application
  • <Install_dir>/liberty/wlp/usr/server/SIServer/logs/console.log and messages.log – provides information about gateway.war when you access from Liberty Server
  • Jetty.log, noapp.log and filegateway.logs – provides information about smartClient REST calls

Download size limit

File download fails for large files.

Workaround: The maximum size of the file to be downloaded is limited to the heap size and RAM of the Liberty server where the APIs are hosted. If you want to increase the download size, you must increase the RAM of the computer and then increase the heap size of the JVM by updating the jvm.options file in the Liberty server. To increase the heap size, use the -Xmx parameter for the maximum size and the -Xms parameter for the minimum size.

File activity or profile section hangs

If the file upload takes more time than the session time of the user, the file activity or profile section hangs.

Workaround: Set the session time of the user higher than the maximum time that is required for the file upload.

Performance issue during file upload

Chunk size for file upload is optimally set to 4 MB and number of concurrent uploads is also optimally set to 4. However, you find some performance issues during the file upload.

Workaround: Update the CHUNK_SIZE and MAX_CONNECTIONS in the app-prod-env-config.js file under <Install-dir>/noapp/deploy/myfg_exploded/webapp/assets/.

Unable to upload or download files

The following error message is displayed when you try to upload or download files using myFileGateway 2.0.
jetty.log -
org.springframework.web.client.ResourceAccessException: I/O error on POST request for
 "https://<ip_address>:<ip_address>/restwar/restapi/jwt/jwtaccesstoken": Received fatal alert:
 handshake_failure; nested exception is Received fatal
 alert: handshake_failure
{{ at org.springframework.web.client.RestTemplate.doExecute( ~[springweb-4.3.25.RELEASE.jar:4.3.25.RELEASE]}}
{{ at org.springframework.web.client.RestTemplate.execute( ~[springweb-4.3.25.RELEASE.jar:4.3.25.RELEASE]}}
{{ at ~[springweb-4.3.25.RELEASE.jar:4.3.25.RELEASE]}}
{{ at [classes/:?]}}
noapp.log -
Caused by: Unrecognized SSL message, plaintext connection?
at ~[?:8.0 build_20200611--106]
at ~[?:8.0 build_20200611--106]
at ~[?:8.0 build_20200611--106]
Caused by: Received fatal alert: handshake_failure
{{ at ~[?:8.0 build_20200611--106]}}
{{ at ~[?:8.0 build_20200611--106]}}
{{ at ~[?:8.0 build_20200611--106]}}


The NoApp Jetty Server uses TLS1.0, but the Liberty Server that hosts the MyFG2.0 uses TLS1.2.


Follow these steps to modify the NoApp Jetty Server to be the same as in the JVM startup as that of the Liberty Server:
  1. Stop the Sterling B2B Integrator server.
  2. Set SSLHelloProtocol to use TLS1.2 in the file.
  3. Back up install/noapp/bin/ and add the following text option to the JAVA_SERVER_ASI parameter.
    JAVA_SERVER_ASI="$JAVA_SERVER_ASI -Dorg.freemarker.loggerLibrary=none
    -Dorg.mortbay.jetty.servlet.AbstractSessionManager.24SessionDestroyed=true -"
  4. Run or setupfiles.cmd.
  5. Restart the Sterling B2B Integrator server.