-
Which browser are you using?
Can you see the stack trace of the error?
The extra info Dario mentioned is not yet printed by the official builds, I'll have to send you a preview of the next library, or you might wait January for the official release, for these new info to be in the error message.
Let me know your thoughts.
-
Using Google Chrome - and no there is absolutely nothing in the call stack for the exception, which is the annoying thing. All it points to is a line number (48) which of course is difficult to assess in a minified script.
-
1 Attachment(s)
I have more information now. Please find attached screenshot from a Google Chrome console.
Attachment 176
-
Code:
'Attr.ownerElement' is deprecated and has been removed from DOM4 (http://w3.org/tr/dom).
:9081/js/jquery/jquery.min.js?v=y097eeydkk6xyldi1420029582638:3 'Attr.textContent' is deprecated. Please use 'value' instead.
:9081/js/jquery/jquery.min.js?v=y097eeydkk6xyldi1420029582638:3 'Attr.nodeValue' is deprecated. Please use 'value' instead.
:9081/js/lightstreamer/lightstreamer.js?v=6.02a.7946:178 WebSocket connection to 'ws://ctsdmz:8686/lightstreamer' failed: WebSocket is closed before the connection is established.
http://ctsdmz:8686/lightstreamer/create_session.js Failed to load resource: net::ERR_NAME_NOT_RESOLVED
http://ctsdmz:8686/lightstreamer/control.js Failed to load resource: net::ERR_NAME_NOT_RESOLVED
3http://ctsdmz:8686/lightstreamer/create_session.js Failed to load resource: net::ERR_NAME_NOT_RESOLVED
http://ctsdmz:8686/lightstreamer/create_session.js?LS_phase=8529&LS_cause=t…NS&LS_user=KTURNER&LS_password=nullpassword&LS_force_head=true&LS_eng=866& Failed to load resource: net::ERR_NETWORK_CHANGED
http://ctsdmz:8686/lightstreamer/create_session.js Failed to load resource: net::ERR_NETWORK_CHANGED
http://ctsdmz:8686/lightstreamer/create_session.js?LS_phase=8533&LS_cause=t…NS&LS_user=KTURNER&LS_password=nullpassword&LS_force_head=true&LS_eng=866& Failed to load resource: net::ERR_NETWORK_CHANGED
http://ctsdmz:8686/lightstreamer/create_session.js Failed to load resource: net::ERR_NAME_NOT_RESOLVED
3http://ctsdmz:8686/lightstreamer/create_session.js Failed to load resource: net::ERR_CONNECTION_TIMED_OUT
http://ctsdmz:8686/lightstreamer/create_session.js?LS_phase=8565&LS_cause=t…NS&LS_user=KTURNER&LS_password=nullpassword&LS_force_head=true&LS_eng=866& Failed to load resource: net::ERR_CONNECTION_TIMED_OUT
http://ctsdmz:8686/lightstreamer/create_session.js Failed to load resource: net::ERR_CONNECTION_TIMED_OUT
http://ctsdmz:8686/lightstreamer/create_session.js?LS_phase=8571&LS_cause=t…NS&LS_user=KTURNER&LS_password=nullpassword&LS_force_head=true&LS_eng=866& Failed to load resource: net::ERR_CONNECTION_TIMED_OUT
http://ctsdmz:8686/lightstreamer/create_session.js Failed to load resource: net::ERR_CONNECTION_TIMED_OUT
http://ctsdmz:8686/lightstreamer/create_session.js?LS_phase=8575&LS_cause=t…NS&LS_user=KTURNER&LS_password=nullpassword&LS_force_head=true&LS_eng=866& Failed to load resource: net::ERR_CONNECTION_TIMED_OUT
http://ctsdmz:8686/lightstreamer/create_session.js Failed to load resource: net::ERR_NETWORK_CHANGED
http://ctsdmz:8686/lightstreamer/create_session.js?LS_phase=8581&LS_cause=t…NS&LS_user=KTURNER&LS_password=nullpassword&LS_force_head=true&LS_eng=866& Failed to load resource: net::ERR_NETWORK_CHANGED
:9081/js/lightstreamer/lightstreamer.js?v=6.02a.7946:48 console.trace():9081/js/lightstreamer/lightstreamer.js?v=6.02a.7946:48 x.addPackedTimedTask
:9081/js/lightstreamer/lightstreamer.js?v=6.02a.7946:49 Uncaught Executor error for times: 1420191599170 + null
-
The line number is not relevant because it simply points to the place where the exception is thrown, but that's not where the problem lies as the null->NaN value is coming in as a parameter to that method.
The stack trace would actually show the bad call, I'm trying to imagine why is missing.
In the library there are many calls to (a method that calls) that method, that's why pinpointing the case with static analysis of the code is not easy. Unfortunately it looks like at this point is the only path left.
Just to try and reduce the code to be analyzed, does your application use our visual widgets?
-
Yes , I am using the statusWidget and the moment as a safety blanket on our login screen to check that the connection is all OK. It gets removed from the DOM after a certain period of time.
-
I checked the various calls to the method, but I'm still at a loss, I don't seem to be able to justify the error.
Can you please open the console on your application and run:
do you get the stack trace in this case?
Did you see the error on firefox? Maybe the stacktrace does appear there.
-
1 Attachment(s)
I ran that in Chrome and get this
Attachment 180
-
good news,
by chance I reproduced the error you're facing. I can't be sure the cause is the same but I hope so, even if in my case I got a stack trace.
I'm going to fix the bug tomorrow.
Just so you know, the bug I found is harmless (the only effect is the error on console).
Thanks for you patience!
-
OK - that sounds great :)