3 Replies Latest reply on Oct 20, 2014 10:36 AM by dchretien

    FileMaker and Java 8

    Michael Frankel

      I was forwarded an email from the IT director for one of my clients yesterday, mentioning something about Java 7 being marked as EOL (end-of-life) in April of 2015. I know Java 8 is already out but I have not been willing to install it, mostly because I don't want to deal with programs that might break.


      I was wondering if anyone at FileMaker can chime in on this regarding compatibility for Pro, Advanced, and Server.


      I was also wondering if anyone in the community has been in a situation where they used or experimented around with Java 8 and FileMaker and knows if it works or not, and if there are any issues.




      Michael Frankel

      Wizard Consulting Group, Inc.

        • 1. Re: FileMaker and Java 8



          I have not seen anything official with regards to Java 8. This KB article for FM Server 13 mentions the recommended version of Java 1.70_67.  I tend to get confused about this, but don't think the regular FM client app needs Java at all - unless you are running one of the 360Works plugins.





          • 2. Re: FileMaker and Java 8

            Hi Michael


            If you don't have to, don't update Java. FileMaker Server relies heavily on Java (though the admin console doesn't, thank God) so the last place you want to early update Java is the server.


            You can take a test machine, make the update and see what happens after a few weeks. If nothing looks broken then you can plan a massive deployment.


            Just my 2¢ of mexican pesos.



            • 3. Re: FileMaker and Java 8



              I received this, this morning, from 360Works support, in response to a question that I'd asked of them regarding Java and their plugins:


              We are working on making sure that all of our plugins will work with 64-bit Java (obviously given the FileMaker technology being used is 64-bit) on OS X. Unfortunately, they will all still require the presence of a 32-bit Java 6 from Apple because of an Oracle bug. For some reason, Oracle's implementation still looks at Apple's Java Framework when natively starting a Java Virtual Machine (there are hooks present on any Mac even if you don't have Java installed). If the 32-bit version is not present, then the JVM does not load. If the 32-bit version is present, the 64-bit version is actually the one that gets loaded.

              There is already a bug filed on this issue with Oracle, and I have filed a similar bug with Apple in hopes that there is some resolution in the future.



              I'm hoping that this is resolved soon, becuase I don't like having versions of Java that are no longer supported running on my machine. 


              --Dennis Chretien