Fixed issue clearing RMI proxy objects on connection close

src/dorkbox/network/connection/Connection.kt

@@ -301,6 +301,8 @@ open class Connection(connectionParameters: ConnectionParams<*>) {
 
             publication.close()
 
+            rmiConnectionSupport.clearProxyObjects()
+
             // this always has to be on a new dispatch, otherwise we can have weird logic loops if we reconnect within a disconnect callback
             endPoint.actionDispatch.launch {
                 // a connection might have also registered for disconnect events

src/dorkbox/network/rmi/RmiManagerConnections.kt

@@ -122,8 +122,7 @@ internal class RmiManagerConnections<CONNECTION: Connection>(logger: KLogger,
         connection.send(response)
     }
 
-    override fun close() {
+    fun clearProxyObjects() {
         proxyObjects.clear()
-        super.close()
     }
 }

src/dorkbox/network/rmi/RmiManagerGlobal.kt

@@ -205,8 +205,7 @@ internal class RmiManagerGlobal<CONNECTION : Connection>(logger: KLogger,
         return success as T?
     }
 
-    override fun close() {
-        super.close()
+    fun close() {
         rmiResponseManager.close()
         remoteObjectCreationCallbacks.close()
     }

src/dorkbox/network/rmi/RmiObjectCache.kt

@@ -43,8 +43,4 @@ internal open class RmiObjectCache(logger: KLogger) {
     fun <T> removeImplObject(rmiId: Int): T? {
         return implObjects.remove(rmiId) as T?
     }
-
-    open fun close() {
-        implObjects.close()
-    }
 }