title: Server restart results in never ending Bad_ServiceUnsupported errors, onSubscriptionTransferFailed not called
body: <p>my Milo client (sdk 0.4.1) subscribes on server events by use of UaSubscription and can receive events sucessfully. But once I restart the server, the clients only logs errors in an endless loop in the form of:</p>
  <blockquote>
  <p>[ERROR] 2021-06-11 17:29:11.467 [milo-netty-event-loop-0]
  UascClientMessageHandler -
  errorMessage=ErrorMessage{error=StatusCode{name=Bad_ServiceUnsupported,
  value=0x800B0000, quality=bad}, reason=null}</p>
  </blockquote>
  <p>Unfortunately implementing the onSubscriptionTransferFailed method does not help because it is never called.</p>
  <pre><code>    client.getSubscriptionManager().addSubscriptionListener(new UaSubscriptionManager.SubscriptionListener() {
                      @Override
                      public void onSubscriptionTransferFailed(UaSubscription subscription, StatusCode statusCode) {
                          try {
                              LOGGER.info(&quot;onSubscriptionTransferFailed&quot;);
                              client.getSubscriptionManager().clearSubscriptions();
                              client.disconnect().get();
                              run(client, serverAddress, biConsumer, requestedPublishingInterval);
                          } catch (InterruptedException | ExecutionException e) {
                              LOGGER.error(&quot;Failed re-subscription: {}&quot;, e.getMessage(), e);
                          }
                      }
     }
  </code></pre>
  <p>Any idea how I can get the client to detect its current problem and resubscribe on server events?</p>
  <p>Thank you in advance.</p>
  <p><strong>Update</strong>:
  Found this commit <a href="https://github.com/eclipse/milo/commit/e854374845e6c5f46a7b033c2c62cee2ee10622a" rel="nofollow noreferrer">https://github.com/eclipse/milo/commit/e854374845e6c5f46a7b033c2c62cee2ee10622a</a> and was able to fix the problem by just increasing the Milo client sdk version to 0.6.1. Version 0.5.3 should probably also fix it but I did not test it.</p>