Vaadin Flow with JRebel enabled causes UI to not render properly

Flow
1

In previous Vaadin versions (7 & 8), JRebel works fine. But when enabling JRebel for flow project, UI won’t render properly (See attached image). Right now, I’ll have to wait for Tomcat to detect code changes, then it will reload.

The message I get when deploying the project:

2018-04-24 17:47:34 JRebel: Contacting myJRebel server ..
2018-04-24 17:47:38 JRebel:  Starting logging to file: C:\Users\IEA\.jrebel\jrebel.log
2018-04-24 17:47:38 JRebel:  
2018-04-24 17:47:38 JRebel:  #############################################################
2018-04-24 17:47:38 JRebel:  
2018-04-24 17:47:38 JRebel: ** JRebel Agent 2018.1.0 (201803221138)**
2018-04-24 17:47:38 JRebel:  (c) Copyright ZeroTurnaround AS, Estonia, Tartu.
2018-04-24 17:47:38 JRebel:  
2018-04-24 17:47:38 JRebel:  Over the last 1 days JRebel prevented
2018-04-24 17:47:38 JRebel:  at least 0 redeploys/restarts saving you about 0 hours.
2018-04-24 17:47:38 JRebel:  
2018-04-24 17:47:38 JRebel:  Licensed to **** (using myJRebel).
2018-04-24 17:47:38 JRebel:  
2018-04-24 17:47:38 JRebel:  
2018-04-24 17:47:38 JRebel:  #############################################################
2018-04-24 17:47:51 JRebel: **Directory 'C:\Users\IEA\eclipse-workspace\virtualsafeconsole\target\classes' will be monitored for changes.**
2018-04-24 17:47:51 JRebel: **Directory 'C:\Users\IEA\eclipse-workspace\virtualsafeconsole\target\m2e-wtp\web-resources' will be monitored for changes.**
2018-04-24 17:47:51 JRebel: **Directory 'C:\Users\IEA\eclipse-workspace\virtualsafeconsole\src\main\webapp' will be monitored for changes.**

17056992.png

2

Since JRebel takes over any resource (re-)loading you should probably ask in their forums.

3

I’m Meelis from the JRebel team.

The issue is caused by a faulty behavior in tomcat that JRebel relies on. I have submitted an issue to their bugzilla.
In the meantime we’ll be working on a workaround on JRebel side as well.

4

Meelis Müür:
I’m Meelis from the JRebel team.

The issue is caused by a faulty behavior in tomcat that JRebel relies on. I have submitted an issue to their bugzilla.
In the meantime we’ll be working on a workaround on JRebel side as well.

Could you post the issue link here?

5

Sure,
https://bz.apache.org/bugzilla/show_bug.cgi?id=62329

6

Waiting for the new tomcat versions to come out, you can still work with JRebel for server/java side.
Opening jrebel.xml, comment all the “web” section.

7

The following tomcat versions that contain the fix have been released: 8.0.52, 8.5.31, 9.0.8

8

The new spring-boot version 2.0.2.RELEASE was released and uses tomcat 8.5.31.
I’ve already test and works fine.