Vaadin-push getting blocked

Support
#1

Hi,

Jmix 1.5
What we have observed that multiple combobox are there even if we randomly switch from one box to other at some point we can see loader keep on loading till 60000ms and when check in browser we are getting below logs in chrome in some scenario it throws server connection lost.
Should i update to 1.7.2 version if any modification done in that version or any configs need to focus on.

tried below configs

vaadin.push.mode=websocket-xhr
vaadin.push.enabled=false
vaadin.push.mode=disabled
jmix.ui.production-mode=tr
jmix.ui.productionMode=true

web-test
downloadable font: Glyph bbox was incorrect (glyph ids 458) (font-family: "Open Sans" style:normal weight:400 stretch:100 src index:1) source: https://re.m.com/web-test/VAADIN/themes/valo/fonts/open-sans/OpenSans-Regular-webfont.woff 
downloadable font: Glyph bbox was incorrect (glyph ids 458) (font-family: "Open Sans" style:normal weight:600 stretch:100 src index:1) source: https://re.m.com/web-test/VAADIN/themes/valo/fonts/open-sans/OpenSans-Semibold-webfont.woff 
downloadable font: Glyph bbox was incorrect (glyph ids 33 55 62 81 82 83 84 87 88 89 90 112 119 120 123 139 159 162 164 166 178 184 185 217 218 272 273 274 275 279 281 284 290 291 292 309 310 319 321 323 326 329 330 331 332 333 334 339 341 347 349 351 352 353 354 357 358 361 366 367 370 371 414 431 436 444 445 458 460 464 465 483 505 508 511 514 516 517 518 520 521 538 539 546 568 574 579 580 585 586 594 596 599 602 603 616 618 622 627 629 630 633 634 638 643 645 651 654 665 675 685 686 688 691) (font-family: "FontAwesome" style:normal weight:400 stretch:100 src index:1) source: https://re.m.com/web-test/VAADIN/themes/valo/fonts/fontawesome-webfont/fontawesome-webfont.woff 
Firefox can’t establish a connection to the server at wss://re.m.com/web-test/vaadinServlet/PUSH?v-uiId=0&v-pushId=7a922345-a166-4c31-ae04-473f7709867e&X-Atmosphere-tracking-id=0&X-Atmosphere-Framework=2.3.2.vaadin2-javascript&X-Atmosphere-Transport=websocket&X-Atmosphere-TrackMessageSize=true&Content-Type=application/json;%20charset=UTF-8&X-atmo-protocol=true. vaadinPush.js:1:12672
Websocket closed, reason: Connection was closed abnormally (that is, with no close frame being sent). - wasClean: false vaadinPush.js:1:40443
Websocket failed on first connection attempt. Downgrading to long-polling and resending

Screenshot from 2026-01-23 17-20-28

#2

@krivopustov

Can you help on this since combo box values are static and if we try frequent navigate loader comes and it keeps on loading till 60000ms

Screenshot from 2026-01-24 12-51-48

#3

Screenshot from 2026-01-24 12-56-06

#5

Hi,

It seems that Vaadin-push getting blocked because you disabled it as shows attached config.

Could you describe in more details why you need to disable vaadin push? Could you attache a sample project that reproduces the problem?

Regards,
Gleb

#7

hi @gorelov,

Below are the current properties set in the application. Previously share vaadin disable config was added when the request was going into the long pooling even though values set in the combo box are static can you suggest any debug config how to debug long pooling scenario in some scenario it throws server connection lost.


jmix.ui.composite-menu = true
jmix.ui.app-window-mode = SINGLE
jmix.ui.httpSessionExpirationTimeoutSec=600
vaadin.servlet.heartbeatInterval=-1
vaadin.servlet.close-idle-sessions=true
main.datasource.hikari.maximum-pool-size=2
main.datasource.hikari.connection-timeout=900000
spring.jmx.enabled=false
#8

@gorelov

Also on click on condition contains to = in add search condition loader keeps on loading, attached is the response when process is completed.
com-1769492341206.log (250.9 KB)

Screenshot from 2026-01-27 11-06-28

#9

Provided log doesn’t contain any error or warning. Also, provided config has nothing to do with comboboxes. Does this problem occurs on the prod environment or any? Could you attache a sample project that reproduces the problem?

#10

This problem occurs on Prod environment only.