I've solved the problem by revising the design. It seems to be working fine now.
Let me try and explain what the problem was more succinctly and then you'll understand the solution.
You had 2 components at play here. The ExchangeModule and the UIComponent.
I originally wanted the exchange module to run as a standalone service and just have the UI subscribe to a datafeed that would be streaming off the exchange module.
This design was unworkable because the UI isn't particularly interested in the exchange data so much as the signals data being generated by the other modules.
Because of the complex interplay between signals and exchanges, it made more sense to have the UI marshall the exchange and signals modules and for expediency they should all share a static informational nexus point.
The exchange module(s) update the nexus with the most current exchange data and nexus notifies the signals modules and ui modules with the latest data.
The problem was that the UI, because it was using JavaFX was forcing all javascript to run through the Event Dispatch Thread.
There is a lot of javascript at play. A lot of it is just hooks to allow scripts to run and implement some custom functionality at key points, but the fact is there is a lot of it.
JavaFX for some reason is forcing all contexts onto a single context and a single thread. This means that any data no matter what thread it was running on would have to wait for the EDT to fire an action before it could be processed. This of course caused a back-up and even a halting to occur.
The solution was to drop JavaFX as the UI toolkit. It was causing problems and I'm just lucky I caught it early enough.
The new design, which appears to be working, uses the NetBeans Platform and nbm bundles in place of what we were calling modules before.
The current UI is mostly swing, it really didn't take that long to re-implement and I think I like the netbeans gui designer a lot more than the JavaFX gui designer
I'll be posting some screenshots soon. Also I'm waiting on the logo to come back then the site expressvest.com will be up later today or early tomorrow.