Forum Discussion

APERRY's avatar
APERRY
Occasional Contributor
6 years ago

Re: ReadyAPI 3.1 - TestRunner - An illegal reflective access operation has occurred

Hi richie 

 

Thank you for your answer. 

My gitlab runner do not contain any java version, I use the openjdk 12 which is installed on the ReadyAPI 3.1 image

Maybe iy's openjdk the source of the problem ?

 

3 Replies

  • richie's avatar
    richie
    Community Hero

    Hey APERRY 

     

    perhaps?  from my remedial understanding, I think that some java component type shouldnt be accessing some other component and if it does (considering the Oracle JRE v9 upgrade) you get the warning where you wouldn't on earlier versions.....i think! :)

     

    did you upgrade the openjdk when you upgraded ReadyAPI!?

     

    nice one,

     

    rich

    • APERRY's avatar
      APERRY
      Occasional Contributor

      richie 

       

      I do not upgrade the openjdk, I just use the openjdk which preinstalled on the latest image of the testrunner (delivered by smartbear).

      • richie's avatar
        richie
        Community Hero

        Hi APERRY 

         

        sorry - just so I'm clear - you keep mentioning 'image' - are you saying you have something like a ghost image/acronis true image and you reapplied an image to your harddisk and the image included ReadyAPI! v3.1?

         

        also - I always wait a while before upgrading my ReadyAPI! instance so I'm not running v3.1 - are you talking about the version of Java installed WITH ReadyAPI!??

         

        Are you saying the Java installed with ReadyAPI! is openJDK? - reason I ask is that the following link indicates ReadyAPI! doesn't work with openJDK.

         

        have you tried installing Oracle's version of Java? (the JDK not the JRE - there are files you need (for something that I cant remember) that are not available in the JRE)

         

        I'd install Java 8 (JDK), ensure your environment variables point to the installed Java, bounce your machine, restart ReadyAPI! and then try running something via testRunner

         

        cheers,

         

        rich