unresponsive after upgrade to 7.2.x

Vaadin 6 / 7 / 8
1

After upgrading from 7.1.13 to 7.2.2 my app has stopped responding to button clicks etc.

There’s nothing unusual in the server logs when starting the app, and I don’t get anything in the server logs when I click my simple button. my button clicklistener is never called.

In the client logs I see this:

[code]
Sun Jun 22 10:54:44 GMT+100 2014 com.vaadin.client.VConsole
INFO: Making UIDL Request with params: {“csrfToken”:“731ea064-734c-42cd-bbdb-60742f454367”, “rpc”:[[“6”,“com.vaadin.shared.ui.button.ButtonServerRpc”,“click”,[{“relativeX”:“28”, “relativeY”:“8”, “clientX”:“494”, “clientY”:“404”, “button”:“LEFT”, “metaKey”:false, “type”:“1”, “shiftKey”:false, “ctrlKey”:false, “altKey”:false}]
]], “syncId”:-1}
Sun Jun 22 10:54:44 GMT+100 2014 com.vaadin.client.VConsole
INFO: Server visit took 9ms
Sun Jun 22 10:54:44 GMT+100 2014 com.vaadin.client.VConsole
INFO: JSON parsing took 0ms
Sun Jun 22 10:54:44 GMT+100 2014 com.vaadin.client.VConsole
INFO: Handling message from server
Sun Jun 22 10:54:44 GMT+100 2014 com.vaadin.client.VConsole
SEVERE: Server response didn’t contain an id.
afb
Zfb
Yfb
igb
hzb
fzb
jAb
HC
cD
(anonymous function)
Um
Zm
(anonymous function)
Sun Jun 22 10:54:44 GMT+100 2014 com.vaadin.client.VConsole INFO: * Handling resources from server

… etc.
[/code]We have a custom widgetset, that’s been recompiled & deployed. I’ve tried other releases of 7.2 with the same result in my app.

I’m at a bit of a loss as to what might be going wrong - any ideas or suggestions to try?

Many thanks,
Dave

2

That looks a little bit strange… I know you said you have recompiled the widgetset, but are you absolutely sure that your new one is being used? Sometimes the browsers cache the old widgetsets a bit too eagerly.

3

Hi Thomas,
Thanks for looking at my issue.

Yes, the browser is definitely using the new widgetset. See the attached image. The “HOME RECOMPILED” and “CONFIGURE RECOMPILED” labels are part of my client-side menu. I added the RECOMPILED label to that client-side widget to test that I’m really running the recompiled widget set.

In 7.2.2 my button is still unresponsive.

Many thanks,
Dave

15303.png

4

The next step would be to either recompile the widgetset with the pretty option (to get useful stacktraces) or to use devmode to get the real stacktrace. Does the ?debug window tell you anything else? what about the browser javascript console?

5

My pervious paste is what I saw in the JS browser console. With PRETTY, i now get:

Mon Jun 23 12:09:19 GMT+100 2014 com.vaadin.client.VConsole
SEVERE: Server response didn't contain an id.     Widgetset-0.js:11192
publish     Widgetset-0.js:11192
$log_0     Widgetset-0.js:11567
$log     Widgetset-0.js:11552
$log_1     Widgetset-0.js:11620
$handleUIDLMessage     Widgetset-0.js:17183
$handleJSONText     Widgetset-0.js:17146
onResponseReceived     Widgetset-0.js:17810
$fireOnResponseReceived     Widgetset-0.js:7737
onReadyStateChange     Widgetset-0.js:7927
(anonymous function)     Widgetset-0.js:16530
apply_0     Widgetset-0.js:3566
entry0     Widgetset-0.js:3614
(anonymous function)

The ?debug window says:

1047msVariable burst to be sent to server:
1048ms   35 (class com.vaadin.client.ui.button.ButtonConnector) :
1048ms      com.vaadin.shared.ui.button.ButtonServerRpc.click([LEFT,274,250,false,false,false,false,1,25,19]
)
1049ms   30 (class com.ejt.vaadin.loginform.shared.LoginFormConnector) :
1050ms      com.ejt.vaadin.loginform.shared.LoginFormRpc.submitted()
1052msMaking UIDL Request with params: {"csrfToken":"ade2795b-67f3-4859-9d42-dd9af1fc67a8", "rpc":[["35","com.vaadin.shared.ui.button.ButtonServerRpc","click",[{"altKey":false, "metaKey":false, "shiftKey":false, "type":"1", "clientX":"274", "clientY":"250", "button":"LEFT", "relativeX":"25", "relativeY":"19", "ctrlKey":false}]
],["30","com.ejt.vaadin.loginform.shared.LoginFormRpc","submitted",[]
]], "syncId":-1}
1061msServer visit took 10ms
1062msJSON parsing took 0ms
1064msHandling message from server
1065msServer response didn't contain an id.
1066ms* Handling resources from server
1067ms* Handling type inheritance map from server
1068msHandling type mappings from server
1068msHandling resource dependencies
1069ms* Handling meta information
1070ms* Creating connectors (if needed)
1070ms* Updating connector states
1071ms* Handling locales
1072ms* Updating connector hierarchy
1072ms* Running @DelegateToWidget
1073ms* Sending state change events
1073ms* Passing UIDL to Vaadin 6 style connectors
1074ms* Performing server to client RPC calls
1075ms* Unregistered 0 connectors
1076mshandleUIDLMessage: 5 ms
1076msStarting layout phase
1078msMeasured 3 non connector elements
1080msPass 1 measured 4 elements, fired 0 listeners and did 0 layouts.
1083msNo more changes in pass 2
1086msTotal layout phase time: 7ms
1086ms* Dumping state changes to the console
1087msUIDL: undefined
1088msProcessing time was 25ms for 119 characters of JSON
1088msReferenced paintables: 12
1151msVariable burst to be sent to server:
1153ms   30 (class com.ejt.vaadin.loginform.shared.LoginFormConnector) :
1154ms      com.ejt.vaadin.loginform.shared.LoginFormRpc.submitCompleted()
1156msMaking UIDL Request with params: {"csrfToken":"ade2795b-67f3-4859-9d42-dd9af1fc67a8", "rpc":[["30","com.ejt.vaadin.loginform.shared.LoginFormRpc","submitCompleted",[]
]], "syncId":-1}
1163msServer visit took 7ms
1164msJSON parsing took 0ms
1165msHandling message from server
1166msServer response didn't contain an id.
1167ms* Handling resources from server
1167ms* Handling type inheritance map from server
1170msHandling type mappings from server
1170msHandling resource dependencies
1171ms* Handling meta information
1171ms* Creating connectors (if needed)
1174ms* Updating connector states
1175ms* Handling locales
1176ms* Updating connector hierarchy
1178ms* Running @DelegateToWidget
1178ms* Sending state change events
1180ms* Passing UIDL to Vaadin 6 style connectors
1181ms* Performing server to client RPC calls
1182ms* Unregistered 0 connectors
1182mshandleUIDLMessage: 11 ms
1183msStarting layout phase
1185msMeasured 3 non connector elements
1187msPass 1 measured 4 elements, fired 0 listeners and did 0 layouts.
1188msNo more changes in pass 2
1189msTotal layout phase time: 5ms
1189ms* Dumping state changes to the console
1190msUIDL: undefined
1192msProcessing time was 27ms for 119 characters of JSON
1192msReferenced paintables: 12

I don’t have dev mode setup on this project at the moment, but can try that if helpful…

Many thanks,
Dave

6

Dave-

I am just guessing here, but I suspect that you may be using Ivy to handle your dependency? If so, try and clear all cache and resolve. Then I would recompile everything. I had the some weird issues happen when I made the jump to 7.2 from 7.1.

Best Regards,
Eric

7

Apparently there was a change in communication between 7.1 and 7.2; your widgetset seems to be using 7.2 and your server uses 7.1. Please check your classpath for old or duplicate JARs; clearing the Ivy cache might well clear the issue.

8

Thanks both - that pointed me in the right direction.

I’m using Maven (not Ivy), but the problem was that I’m also using
https://github.com/peholmst/vaadin4spring
 which isn’t upgraded to 7.2 yet. So the result was that I did have both 7.1 and 7.2 on my classpath.

I’ve rebuilt vaadin4spring against 7.2 and everything works as expected.

Thanks again,
Dave