no such connector could be found

Hi

this warning bothers me:

WARNING: RPC call to v.v received for connector 95 but no such connector could be found. Resynchronizing client. I tried to find out, from where it comes, but couldn’t (even with -ea flag). Is it a bug in Vaadin? I don’t think so, because I’m using 7.3.1:

Code:

  private class SearchButtonListener implements ClickListener {

    @Override
    public void buttonClick(ClickEvent event) {
      getUI().setPollInterval(200);
      getUI().addWindow(blockerWindow);
      workThread = new WorkThread();
      workThread.start();
    }
  }

  private class WorkThread extends Thread {

    @Override
    public void run() {
      getUI().access(new Runnable() {

        @Override
        public void run() {
          // load and update tables
          boolean noResult = loadResult(searchField.getValue());
          errorLabel.setVisible(noResult);
          getUI().setPollInterval(-1);
          getUI().removeWindow(blockerWindow);
        }
      });
    }
  }

  private class BlockerWindow extends Window {

    public BlockerWindow() {
      this.setResizable(false);
      this.setDraggable(false);
      this.setCaption("Query is running");
      this.setModal(true);
      this.center();
      this.setClosable(false);

      VerticalLayout mainLayout = new VerticalLayout();
      mainLayout.setSizeFull();
      mainLayout.setMargin(true);
      mainLayout.setSpacing(true);
      mainLayout.setWidth("200px");
      mainLayout.setHeight("140px");
      mainLayout.addComponent(new Label("Please wait while the Query is running."));
      this.setContent(mainLayout);
    }
  }

Can anyoune see, why I got this warning?

Cheers
Stefan

Hi, I think this is
issue #12909
. You remove the window on the server side, but the client doesn’t know it yet and tries to send some update to the removed window. This is basically harmless, although will result in a slightly more traffic as the server re-sends the whole client state to ensure the client is in sync.

Thanks a lot
I saw this issue, but didn’t notice, that it is still open. :wink: