Javatest 4.2

https://jtharness.dev.java.net/svn/jtharness/trunk/code/src/com/sun/javatest/exec/ContextManager.java (current revision is 1267)

See method .refreshTests():
public void refreshTests() {
        synchronized (this) {
            if (pendingRefresh)
                return;
            pendingRefresh = true;
        } // sync
        // start the task on a new thread if needed to release
        // the GUI
        if (EventQueue.isDispatchThread()) {
            Runnable cmd = new Runnable() {
                public void run() {
                    refreshTestsImpl();
                } // run()
            };
            Thread t = new Thread(cmd, "ContextMgr Refresh Defer");
            t.start();
            return;
        }

        try {
            Thread.currentThread().sleep(4000);
        }
        catch (InterruptedException e) {
        }
        refreshTestsImpl();
    }

If method is called from Event Dispatch Thread everything looks OK - refreshTestsImpl() is submitted with a separate thread and then method quits.
However if it's already a different thread - then the code looks very suspicious - why there's a need to do a Thread.currentThread().sleep(4000) before calling to actual refreshTestsImpl()? It may cause unpredictable response time for the user.

Is there a hidden problem behind this .sleep()?