3573951 - Deployment fails in Restart System for Java-Only phase due to "JCE Jurisdiction Policy Files don't allow the use of AES/GCM/NoPadding with key length 256"

Software Update Manager (SUM) Stuck in RESTART-SYSTEM-JAVAONLY phase and AS Java fails to start during upgrade process. below logs can be detected:

RESTART-SYSTEM-JAVAONLY_xx.LOG:

[...]
[Error ]: Return code condition success evaluated to false for process sapcontrol for action wait for started.

[Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Could not check status of SAP instance with number (YY).
Could not check if the instance number (YY) on host (XX) is started.
Sapcontrol client could not perform action wait for started on instance (YY)
Return code condition success evaluated to false for process sapcontrol for action wait for started.
[...]

dev_jstart:

[...]
F  *** ERROR => Node 'bootstrap' failed with exit code 558.
F  ***
F  *** Please see section 'Failures in the 'synchronizing binaries' phase'
F  *** in SAP Note 1316652 for additional information and trouble shooting advice.
F  ********************************************************************************
[...]

dev_bootstrap:

[...]
F  *** ERROR => Java node 'Instance_bootstrap' terminated with exit code 558.
F  ***
F  *** Please see section 'Java program exit codes'
F  *** in SAP Note 1316652 for additional information and trouble shooting advice.
F  ********************************************************************************
[...]

jvm_bootstrap.out:

[...]
Starting to initialize database connection
Exception occurred for component [internal/unkown] of type [unkown]
com.sap.engine.bootstrap.SynchronizationException: Storage access initialization failed due to OpenSQL error.Check if your db driver file is available on the file system or if the user has correct permissions for that file
[...]
----------==[ Caused by: ]==----------
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
[...]    
Caused by: com.sap.sql.log.OpenSQLException: Error while accessing secure store: Encryption or decryption is not possible. JCE Jurisdiction Policy Files don't allow the use of AES/GCM/NoPadding with key length 256..
[...]
Caused by: com.sap.security.core.server.secstorefs.NoEncryptionException: Encryption or decryption is not possible. JCE Jurisdiction Policy Files don't allow the use of AES/GCM/NoPadding with key length 256.
[...]    
Caused by: java.security.InvalidKeyException: Illegal key size
    at javax.crypto.Cipher.checkCryptoPerm(Cipher.java:1044)
    at javax.crypto.Cipher.implInit(Cipher.java:810)
    at javax.crypto.Cipher.chooseProvider(Cipher.java:869)
    at javax.crypto.Cipher.init(Cipher.java:1401)
    at javax.crypto.Cipher.init(Cipher.java:1332)
    at com.sap.security.core.server.secstorefs.crypt.aes.CryptAES.tryCipherInitialization(CryptAES.java:106)
    at com.sap.security.core.server.secstorefs.crypt.aes.CryptAES.<init>(CryptAES.java:77)
[...]

• SAP NetWeaver Application Server Java 7.5
• SAP Java Virtual Machine 8.1

Illegal key size, JCE Jurisdiction Policy Files don't allow the use of AES/GCM/NoPadding with key length 256, AES256, Deployment, Restart System for Java-Only. , KBA , BC-JVM , SAP Java Virtual Machine , BC-UPG-TLS-TLJ , Upgrade tools for Java , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , BC-JAS-DPL , Deployment , Problem