OrientDB 3.2.27 有大量 OStorageRemotePushThread.subscribe 线程长时间锁定是否正常?如果不是,原因可能是什么?我们正在使用 Kotlin 协程,我相信线程本地正在协程挂起之间保存和恢复。
| +---Thread-402 Frozen for at least 10s <Ignore a false positive> |
| | | |
| | +---jdk.internal.misc.Unsafe.park(boolean, long) (native) |
| | | |
| | +---java.util.concurrent.locks.LockSupport.parkNanos(Object, long) |
| | | |
| | +---java.util.concurrent.SynchronousQueue$TransferStack.transfer(Object, boolean, long) |
| | | |
| | +---java.util.concurrent.SynchronousQueue.poll(long, TimeUnit) |
| | | |
| | +---com.orientechnologies.orient.client.remote.OStorageRemotePushThread.subscribe(OBinaryRequest, OStorageRemoteSession) OStorageRemotePushThread.java:124 |
| | | |
| | +---com.orientechnologies.orient.client.remote.OStorageRemote.subscribeStorageConfiguration(OStorageRemoteSession) OStorageRemote.java:1839 |
| | | |
| | +---com.orientechnologies.orient.client.remote.OStorageRemote.onPushReconnect(String) OStorageRemote.java:2331 |
| | | |
| | +---com.orientechnologies.orient.client.remote.OStorageRemotePushThread.run() OStorageRemotePushThread.java:99
在一个 OrientDB 上下文中的客户端中打开的每个数据库都有一个 OStorageRemotePushThread 实例是正常的。
因此,该数字应该与您拥有的数据库数量相匹配,并期望您在应用程序中只有一个 OrientDB 上下文。
问候