Cannot communicate with websocket. Autobahn: received HELLO message, and session is not yet established

like below fixes the issue I am working on websocket communication with Autobahn. On the main.class of my app, I set to call 'connect()' when users click a button.

public class WebSocket_Connector {

private static final String TAG = "ECHOCLIENT";
public final WebSocketConnection mConnection = new WebSocketConnection();
private String tmpString = "";
public void connect(final String wsuri) {

      Log.d(TAG, "Connecting to: " + wsuri); 

      try {
         mConnection.connect(wsuri, new WebSocketHandler() {

            @Override
            public void onOpen() {
               Log.d(TAG, "Status: Connected to " + wsuri ); 
               Log.d(TAG, "Connection successful!\n");
               mConnection.sendTextMessage(tmpString); 
               tmpString = "";
            }

            @Override
            public void onTextMessage(String payload) {
               Log.d(TAG, "Got echo: " + payload);
            }

            @Override
            public void onClose(int code, String reason) {
               Log.d(TAG, "Connection closed.");
            }
         });
      } catch (WebSocketException e) {

         Log.d(TAG, e.toString());
      }

 public void sendMessage(String message) {

    if (mConnection.isConnected()) 
            mConnection.sendTextMessage(message); 
    else {
       tmpString = message;
       connect("ws://192.168.x.xxx:xxxx");
    }

 }

 }

To fix the issue you can do Sorry it was a silly mistake apt-get installed an old version of autobahn . I have installed the binary provided by autobahn site and problem solved :)

will help you The WebSocket spec (RFC6455) requires a compliant client to generate a random key on each and every connection.
A server that mandates a specific key isn't spec compliant. There are no hooks in AutobahnAndroid to set a specific key (and we won't add such things). Please fix your server or use a compliant one.

around this issue I think you need some kind of context object that represents your user session (or search session). In that context you can put a latestSearchId which you increment every search. Then you could add the searchId parameter to main_search. And supposing you have a loop or some kind of different stages in which you can abort, you could test whether the searchId in your current search is still the latest by comparing it to the search sessions' latestSearchId.
A different approach (for example if you can't abort your searches) could be to wait a few milliseconds before you compute the search and check whether any new searches have come in, in the mean time.

def resume_search(position):
    #stuff

reactor.callLater(0, resume_search, current_position)