Do not install Java 155. WebDirect is not working, it happend in my server.
Where are you seeing "155"?
From the Oracle site, the latest version I see is 152.
Java SE Runtime Environment 8 - Downloads
It's no biggie.
For the life of me, however, I'm baffled why:
1. FMS isn't coded to manage its own dependencies (like modern software I write).
2. Why a point release of Java would "break" FMS when it doesn't break any of the other program I use.
3. Why FMI doesn't quickly (like the same day reported) come out with a point release of their own to fix their bug!
By all appearances, at least in this case, FMS is highly brittle.
Yes it's biggie because your WebDirect solution will stop working.
Sorry I wasn't clear.
YES, it's a super biggie that...
But, it's no biggie that you mistook 155 for 151.
There is notification that "There is update for your FMS" in admin console, so how about notifying "Don't install latest Java update" ?
KB is worse than old days that not show recent articles as new... it would be better if can be sorted by date.
I do search web before applying any update, then be helped many times by someone did it before I do it.
I have many, many Java web services running all over the place. And, I have other programs that rely on Java. I've never had an issue where an update caused any problem. Ever.
So, I disagree. Rather than "document" not to do a Java update or have a KB that describes it, make the (FMS) code robust so no KB or other documentation (or warnings..."do not install.") are necessary in the first place.
I just give an advertise because I am admin of more than 10 FM Servers and 3 of this servers have been update Java to 151 and WebDirect stop working. rendering blank pages!
You should contact FM Support and raise an issue.
Also submit a bug report.
Having software break like FMS does with a simple Java point update is NOT OK.
This "simple Java update kills FMS" problem should never have happened or have been fixed the same day by FMI after all these people reported it.
Testing and Development are aware of this issue. Please see WebDirect fails to render after updating to Java 8u151.
Not to pile on, but how can an product at this cost point fail with a simple point release of Java?
I found super easy workaround, changing server.xml (default location is C:\Program Files\FileMaker\FileMaker Server\Web Publishing\publishing-engine\jwpc-tomcat\conf\server.xml)
to "off" (changing only 1 character to 2) then restart server.
I tested only opening 2 files (FMServer_Sample and a mine) and changing some layout.
As the meaning of setting, larger data may become slower. So I can't prefer this instead of reinstalling older JRE.
See here. [JDK-8189789] tomcat gzip-compressed response bodies appear to be broken in update 151 - Java Bug System
This bug looks caused by using old Tomcat (7.0.72 in FMS16). Tomcat 7 is old but yet supported, so I'm not sure it is better to use Tomcat 8 (of couse the selection is on FMI, not us).
Why isn't FMI using current versions of Tomcat?
What about JDK 152?
This issue is described as "known" in oracle document now,
Java™ SE Development Kit 8, Update 152 Release Notes
And 161 had released but not fixed. We should wait for 171.
I had some issues with 141. As far as I know 131 is the latest certified to work with FMS 16.
It's ridiculous, I know I've said this before, that FMI can't keep their product working with current Java versions. The problem has been reported for many months. Has there ever been a fix?
For me, I had enough with the crazy FMS config issues and having the onus of the "correct Java version" being dumped on me to manage by FMI -- seemingly not able to manage that in-product themselves. Thus, now I've deleted my testing copy of FMS from my MacOS Server since Apple is abandoning that server option anyway as we currently use it. And as wimdecorte does, I've received and am now setting up a Raspberry Pi to do all the stuff, minus FMS, that the MacOS server did.
Raspberry Pi kit: $69.
Retrieving data ...