Additional event queue appearing after RMI callback

Question

Hi,
I am working on a client-server applicaion in which the client passes the server a callback object so it can be notified if shared data is changed so it can refresh.
After receiving the notification from server the processing is moved to a Runnable executed on the dispatch tread with SwingUtilities.invokeLater(Runnable).
But a case arose in which there there seems to appear an additional event queue.
The original event queue (Thread name is AWT-EventQueue-2) is busy. Then in a thread named "RMI TCP Connection(3)-192.168.1.4" a notification comes but it is dispatched on a thread named "AWT-EventQueue-0". But I want the notification processing happen after AWT-EventQueue-2 has finished its current task.
How can I avoid the additonal queue creation and what wrong am I doing so it is created(Swing is single-threaded as I have read everywhere)?
Thanks
Mike

Answer 1

I found a way to solve this but I am not sure it is good.
I save reference to the event queue the application uses on startup and instead of
SwingUtilities.invokeLater(changeRunnable)
use
systemQueue.postEvent(new java.awt.event.InvocationEvent(Toolkit.getDefaultToolkit(), changeRunnable));
Currently that works fine and change events are dispatched synchronously to the other things happening. But I wonder if there is a chance that the system queue is substituted in runtime by another queue and my reference will become invalid.
Mike