Info and Warning messages displayed during install of YF 9.2 on Linux

Hi Steve,

I hope all is well,

I will forward this to our development team, thank you for raising this with us. I will update you of the news.

Regards,

Mark

Hi Steve,

I hope all is well,

I have some feedback... It appears this is a HSQL warning something of which MAY be an issue in the future releases of Java.

One would assume HSQL will release a fix for this if Java begins breaking this.

Regards,

Mark

Hi Steve,

I hope all is well,

I just want to touch base to see where we stand with this issue raised. Happy to assist where I can.

Regards,

Mark

Hi Mark,

I raised this ticket purely so that your dev team can look into why the Linux installer throws HSQLDB related info and warning messages even though there does not appear to be any problems with the install. This is not a good user experience.

The bug is not causing me any problems other than me seeing unnecessary info and warning messages.

Regards,

Steve

Hi Steve,

I hope all is well and apologies for the delay in responding. I have reached out to the wider team to see what options we have going forward.

I will update you asap.

Regards,

Mark

Hi Steve,

I have questioned this with our development team with regards to how we can tackle this going forward as this is HSQL specific.

Going forward I can totally understand that this does not look good from a user point of view however as stated this is HSQL related and not something most clients will be using. Would one mind telling me the reasons for using a HSQLDB?

I look forward to your reply.

Regards,

Mark

The use of HSQLDB is for installing the default Ski Team tutorial content.

I have done some experimentation and I have found the following:

• Open Java JRE Version 8 + Yellowfin 9.2.1 = Does not display HSQLDB Warning and Info errors during Yellowfin installation
• Open Java JRE Version 11 + Yellowfin 9.2.1 = Does display HSQLDB Warning and Info errors during Yellowfin installationJava JRE Version 11 is the current Default Long-Term Servicing version of Java
  
• Open Java JRE Version 13 + Yellowfin 9.2.1 = Does display HSQLDB Warning and Info errors during Yellowfin installation.
  
• Open Java JRE Version 14 + Yellowfin 9.2.1 = Does display HSQLDB Warning and Info errors during Yellowfin installation

It appears there is an incompatibility of the version of HSQLDB being used in Yellowfin and the Java Version 11 or later.

Regards,

Steve

Hi Steve,

Thank you for this additional information, I've decided that I am going to go ahead and raise an idea with our development team to have this message removed within the logs as you did state "This is not a good user experience"

Having submitted this to our development team discussions will be held on how we tackle this going forward and how this affects the different Java versions.

I hope this is ok Steve. I will be keeping you updated with the on goings of this. Let me know your thoughts.

Regards,

Mark

Hi Mark,

The problem I mentioned earlier still exists when installing Yellowfin 9.3.0 with Java 11 running on Linux. The warning messages generated by the install program are shown below. Again these messages do not appear to impact the running on Yellowfin once the installation is complete. It's just a messy user experience.

--- Installing ---

Extracting distribution ............................................. [OK]
Cleaning up installation ............................................ [OK]
Updating configuration .............................................. [OK]
Setting up database ................................................. [OK]
Creating tables ..................................................... [OK]
Creating sequences .................................................. [OK]
Updating database ................................................... [OK]
Loading data ........................................................ [OK]
Updating configuration .............................................. [OK]
Updating database ................................................... [OK]
Updating database ................................................... [OK]
Updating database ................................................... [OK]
Installing Tutorial Data ................................................................Oct 15, 2020 6:58:07 AM org.hsqldb.persist.Logger logInfoEvent
INFO: open start - state modified
Oct 15, 2020 6:58:07 AM org.hsqldb.persist.Logger logInfoEvent
INFO: dataFileCache open start
Oct 15, 2020 6:58:07 AM org.hsqldb.persist.Logger logInfoEvent
INFO: dataFileCache open end
Oct 15, 2020 6:58:07 AM org.hsqldb.persist.Logger logInfoEvent
INFO: checkpointClose start
Oct 15, 2020 6:58:07 AM org.hsqldb.persist.Logger logInfoEvent
INFO: checkpointClose synched
Oct 15, 2020 6:58:07 AM org.hsqldb.persist.Logger logInfoEvent
INFO: checkpointClose script done
Oct 15, 2020 6:58:07 AM org.hsqldb.persist.Logger logInfoEvent
INFO: dataFileCache commit start
Oct 15, 2020 6:58:07 AM org.hsqldb.persist.Logger logInfoEvent
INFO: dataFileCache commit end
Oct 15, 2020 6:58:07 AM org.hsqldb.persist.Logger logInfoEvent
INFO: checkpointClose end
Oct 15, 2020 6:58:08 AM org.hsqldb.persist.Logger logInfoEvent
INFO: dataFileCache commit start
Oct 15, 2020 6:58:08 AM org.hsqldb.persist.Logger logInfoEvent
INFO: dataFileCache commit end
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.hsqldb.persist.RAFileNIO (file:/tmp/driver3576096849651635966jar) to method java.nio.DirectByteBuffer.cleaner()
WARNING: Please consider reporting this to the maintainers of org.hsqldb.persist.RAFileNIO
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Oct 15, 2020 6:58:08 AM org.hsqldb.persist.Logger logInfoEvent
INFO: Database closed
[OK]
Closing database connections ........................................ [OK]

--- Installation Complete ---

Hi Steve,

Thank you for letting me know this this still occurs within 9.3.0, I have made our development team aware of this.

Regards,

Mark