Page 1 of 2

Java 151 Issue?

PostPosted: Thu Oct 19, 2017 6:12 pm
by bcusick
Hey Guys,

My IT folks always INSIST that we run the most recent version of Java... so I updated a server to 1.8.0_151 and all of a sudden I couldn't get to /servoy-admin.

The browser kept complaining that the site was unreachable (Chrome) with the error: ERR_CONTENT_DECODING_FAILED.

When I uninstall that - and go back to 1.8.0_131 or 1.8.0_144 - everything works again.

Anyone know what's up with that??

Servoy version 7.4.10
Windows Server 2012

Re: Java 151 Issue?

PostPosted: Thu Oct 19, 2017 9:25 pm
by bcusick
This IS an issue with 151!

My computer "helpfully" updated its Java and the CSS file went missing:
"Failed to load resource: net::ERR_CONTENT_DECODING_FAILED" in the login form.

content_error.jpg
The error as seen in Chrome
content_error.jpg (24.97 KiB) Viewed 10527 times


Here's how the login form loaded:

how_it_looks.jpg
How the login screen looks
how_it_looks.jpg (26.02 KiB) Viewed 10527 times


Here's how it SHOULD look:

how_it_should_look.jpg
How the login screen SHOULD look
how_it_should_look.jpg (25.89 KiB) Viewed 10527 times


Any ideas?

Re: Java 151 Issue?

PostPosted: Fri Oct 20, 2017 3:44 am
by chaitanyas
Hi All,

We are also facing the same issue, after java updated to version java 8 update 151 then we can't run servoy admin page, is there any fix for this issue ?

Re: Java 151 Issue?

PostPosted: Fri Oct 20, 2017 8:44 am
by ROCLASI
Did you guys file a bugreport in the tracker yet ?

Re: Java 151 Issue?

PostPosted: Fri Oct 20, 2017 8:51 am
by ROCLASI
Bob and chaitanyas,

Do you see the same thing on different browsers? Or is this only on Chrome ?

Re: Java 151 Issue?

PostPosted: Fri Oct 20, 2017 9:00 am
by Andrei Costescu
The OS is also important. Did you update only java when this happened or the OS as well?
As a workaround you could turn off compression on server by editing application_server/server/conf/server.xml and setting compression to "off".

And yes, if it's not a chrome update going wrong you should create a case for this.

Re: Java 151 Issue?

PostPosted: Fri Oct 20, 2017 9:08 am
by ROCLASI
I do read online some solutions like clearing your browser cache. Try that first.

Re: Java 151 Issue?

PostPosted: Fri Oct 20, 2017 9:40 am
by ROCLASI
Hi Andrei,
Andrei Costescu wrote:As a workaround you could turn off compression on server by editing application_server/server/conf/server.xml and setting compression to "off"


Servoy server 8.2 has the following settings in server.xml:
Code: Select all
<Connector port="8080" protocol="HTTP/1.1"
               maxThreads="500" connectionTimeout="60000"
               redirectPort="8443" useBodyEncodingForURI="true"
                compression="4096"
               compressableMimeType="text/html,text/xml,text/plain,text/javascript,text/css" />

As far as I can see this setting has not changed since Servoy server 6.0

If I read the Tomcat documentation correctly it should be like this:
Code: Select all
<Connector port="8080" protocol="HTTP/1.1"
               maxThreads="500" connectionTimeout="60000"
               redirectPort="8443" useBodyEncodingForURI="true"
               compression="on"
               compressionMinSize="4096"
               compressableMimeType="text/html,text/xml,text/plain,text/javascript,text/css" />



source:
- http://tomcat.apache.org/tomcat-6.0-doc ... /http.html
- http://tomcat.apache.org/tomcat-7.0-doc ... /http.html
- http://tomcat.apache.org/tomcat-8.0-doc ... /http.html

Re: Java 151 Issue?

PostPosted: Fri Oct 20, 2017 9:43 am
by chaitanyas
Hi Robert,

I did try clearing browser cache but no luck and yes it happened with Mozilla firefox and IE also.

Servoy Version : 7.4.2

OS : Windows

Java Version : java 8 update 151

Re: Java 151 Issue?

PostPosted: Fri Oct 20, 2017 10:47 am
by Andrei Costescu
As far as I can see this setting has not changed since Servoy server 6.0

If I read the Tomcat documentation correctly it should be like this:
(...)


It can have a number in there directly, not just on and off.
https://tomcat.apache.org/tomcat-8.5-do ... /http.html

And yes, it has not changed in Servoy; I was just suggesting turning it off as a workaround if this was caused by an OS or JVM update - until a better solution is found.

Re: Java 151 Issue?

PostPosted: Fri Oct 20, 2017 11:14 am
by ROCLASI
Andrei Costescu wrote:
ROCLASI wrote:If I read the Tomcat documentation correctly it should be like this:
(...)


It can have a number in there directly, not just on and off.

So obviously I didn't read the documentation correctly :oops:
Thanks for clarifying!

Re: Java 151 Issue?

PostPosted: Fri Oct 20, 2017 12:25 pm
by lwjwillemsen
Is Servoy going to follow up on this (fix it)?
I don't want to turn off compression!

We are using Servoy 7.4.10.

Re: Java 151 Issue?

PostPosted: Fri Oct 20, 2017 12:42 pm
by Gabi Boros
I see there is already 1.8.0_152 released. is it the same with this one?

Re: Java 151 Issue?

PostPosted: Fri Oct 20, 2017 12:46 pm
by ROCLASI
Some observations:

I updated my Windows 10 VM with Java 8-151 and have Tomcat 8.5 installed on it. By default it doesn't have compression enabled so I added it in the server.xml and restarted it.
Then I deployed a 7.4 war file and tried to access the servoy-admin page. It uses Java 8-151 and it loaded fine :!: .

Then I installed Servoy server 7.4.10 and tried to access the servoy-admin page and it failed as described in this thread.
Changing the compression property to "off" does indeed the trick to make it load properly again.

Hope this helps.

Re: Java 151 Issue?

PostPosted: Fri Oct 20, 2017 12:48 pm
by lwjwillemsen