Details

    • Type: Task
    • Status: Open
    • Priority: L3 - Default
    • Resolution: Unresolved
    • Affects Version/s: 7.11.0
    • Fix Version/s: None
    • Component/s: engine
    • Labels:
      None

      Description

      7.11.0 uses MyBatis v3.4.4
      in JDK 9+ this generates Illigal Reflective access warnings in the Logs.

      WARNING: An illegal reflective access operation has occurred
      WARNING: Illegal reflective access by org.apache.ibatis.reflection.Reflector (file:/Users/pearces/.m2/repository/org/mybatis/mybatis/3.4.4/mybatis-3.4.4.jar) to method java.lang.Object.finalize()
      WARNING: Please consider reporting this to the maintainers of org.apache.ibatis.reflection.Reflector
      WARNING: All illegal access operations will be denied in a future release
      

      This was fixed in the 3.5.0 release - https://github.com/mybatis/mybatis-3/issues/1156
      However when manually excluding 3.4.4 and using the latest 3.5.2

      I not longer get the error at startup, but during use I get a slightly different error

      WARNING: An illegal reflective access operation has occurred
      WARNING: Illegal reflective access by org.apache.ibatis.ognl.OgnlRuntime (file:/Users/pearces/.m2/repository/org/mybatis/mybatis/3.5.2/mybatis-3.5.2.jar) to method java.util.Arrays$ArrayList.size()
      WARNING: Please consider reporting this to the maintainers of org.apache.ibatis.ognl.OgnlRuntime
      WARNING: All illegal access operations will be denied in a future release
      

      this one is mentioned in the github issue https://github.com/mybatis/mybatis-3/issues/1586
      and suggest you remove the parenthesis for the size() and other commands

      I could reproduce the same error by writing someMapParam.keys.size(), someMapParam.keySet.size() or someMapParam.keySet().size() in an OGNL expression [1].
      To avoid the warning, you just need to remove the parentheses after size (e.g. someMapParam.keys.size).

        Issue Links

          Activity

          Hide
          thorben.lindhauer Thorben Lindhauer added a comment -

          Hi Steven,

          Thanks for the ticket and the excellent description. We are already aware of this issue, however we haven't been able to update to MyBatis 3.5 as we currently still support Java 7 and Mybatis 3.5 requires 8+. We are currently in the process of dropping Java 7 support and if all goes well we will update Mybatis with 7.12.0.

          Cheers,
          Thorben

          Show
          thorben.lindhauer Thorben Lindhauer added a comment - Hi Steven , Thanks for the ticket and the excellent description. We are already aware of this issue, however we haven't been able to update to MyBatis 3.5 as we currently still support Java 7 and Mybatis 3.5 requires 8+. We are currently in the process of dropping Java 7 support and if all goes well we will update Mybatis with 7.12.0. Cheers, Thorben
          Hide
          tonny1983 tonny added a comment -

          I faced the same issue with Camunda ver. 7.11 and JDK 11. If it is hard to upgrade the MyBatis currently, would you confirm that the warning would not affect the function of Camunda please? As according to the Supported Environments of the current documents, the Camunda Engine supports JAVA from 7 to 12, but I don't know if the warning would make something wrong.

          Show
          tonny1983 tonny added a comment - I faced the same issue with Camunda ver. 7.11 and JDK 11. If it is hard to upgrade the MyBatis currently, would you confirm that the warning would not affect the function of Camunda please? As according to the Supported Environments of the current documents, the Camunda Engine supports JAVA from 7 to 12, but I don't know if the warning would make something wrong.
          Hide
          thorben.lindhauer Thorben Lindhauer added a comment -

          Hi,

          That should be fine, our CI runs successfully with both Java 11 and 12. As the warning says, it could happen that a future Java version no longer works with this Mybatis version at all.

          Cheers,
          Thorben

          Show
          thorben.lindhauer Thorben Lindhauer added a comment - Hi, That should be fine, our CI runs successfully with both Java 11 and 12. As the warning says, it could happen that a future Java version no longer works with this Mybatis version at all. Cheers, Thorben

            People

            • Assignee:
              Unassigned
              Reporter:
              Stexxen Steven
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:

                Development