[CLOSED] [1.1.3] Dispatcher and Hosted Mode

[amundb]

I have noticed an issue when running in hosted mode and using the Dispatcher. For some reason, hosted mode is able to produce a congruent modification exception as seen in this stack trace:

java.util.ConcurrentModificationException: null
at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
at java.util.AbstractList$Itr.next(Unknown Source)
at com.extjs.gxt.ui.client.mvc.Dispatcher.dispatch(Dispatcher.java:232)
at com.extjs.gxt.ui.client.mvc.Dispatcher.dispatch(Dispatcher.java:166)
...

I know that once this gets compiled to javascript it is single threaded and would be impossible to produce this exception. But hosted mode is able to produce this exception.

This looks to be a problem with hosted mode in the GWT compiler, something with their internal timers being incorrect I would imagine.

[Kutu]

I notice this code in the Dispatcher:

      
      history.put(token, event);
      ignoreNext = true;
      History.newItem(token);

Why not use :

History.newItem(token, false);

Now you don't have to deal with boolean flag?

[darrellmeyer]

amundb
I am not sure why you are seeing this issue. Are you removing a controller within code executing via a event passed to the dispatcher?

Kutu
Thanks for the tip, I was not aware of the newItem(String historyToken, boolean issueEvent) method. It looks like it was added in 1.5.1. I have updated the Dispatcher code.

[DaBlick]

Are you removing a controller within code executing via a event passed to the dispatcher?

Short answer: Yes. Thanks for the pointer.