Jump to content
  • Bundled Java 8 151 Version leads to InvalidAlgorithmParameterException: DH key size must be multiple of 64, and can only range from 512 to 2048 (inclusive). The specific key size 4096 is not supported


    christoph.luder
    CategoryBug report
    Component: 31141
    PriorityNormal
    ReproducibilityAlways
    ResolutionNot Fixable
    SeverityMajor
    StatusClosed

    When using the bundled java 8 151 Version we get the following Error, when trying to connect to the remote Jasper Server. See screenshot for more infos.

    Caused by: java.security.InvalidAlgorithmParameterException: DH key size must be multiple of 64, and can only range from 512 to 2048 (inclusive). The specific key size 4096 is not supported

     

    When changing the Java Version to Java 8 251 by editing the Jaspersoft Studio Professional.ini the error is not appearing.

    Jaspersoft Studio Professional.ini

    -vm

    C:\Program Files\Java\jdk1.8.0_251\bin

     

    Tested with Jasper Studio 7.5.0 and 7.9.0.

     

    The Server is version 7.5.1.

    Server jdk: java-1.8.0-openjdk-1.8.0.302.b08-0.el8_4.x86_64

    Red Hat Enterprise Linux release 8.3 (Ootpa)

     


    Attachments:

    User Feedback

    Recommended Comments

    Changed Resolution from Open to Not Fixable

    Changed Status from New to Closed


    Hi, I tried to reproduce with a test JRS server 7.5.1 and connecting from a JSS PRO 7.9.0. I was not able to.Not sure from which it could depend on. Do you have some custom server settings?We used that specific JRE8 version for multiple releases (both CE and PRO), and at some point we went also back to update 151 because of some technical issue (https://community.jaspersoft.com/jaspersoft-studio/issues/10956). I can't recall similar issues.Latest CEs are using Adopt OpenJDK 11.0.8 and the next upcoming Professional one will use it as well.Can you please give it a try with a test CE installation to see if you are able to connect to the server correctly?That said, there is not much we can do about this. The best workaround to avoid the error is to do like you did and give it a try with a different JRE/JDK.Regards,Massimo.
    Link to comment
    Share on other sites


×
×
  • Create New...