You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And tries to send a cluster message to it resulting in an Assert in ContextTransport. It seems that the bug is caused by low-level IO code.
ScalienDB.shard-dev-2.2.6-rc30.exe!ContextTransport::OnMessage(unsigned __int64 nodeID, ReadBuffer msg) Line 111 + 0x37 bytes C++
ScalienDB.shard-dev-2.2.6-rc30.exe!ClusterConnection::OnMessage(ReadBuffer & msg) Line 298 C++
ScalienDB.shard-dev-2.2.6-rc30.exe!MessageConnection::OnRead() Line 173 + 0x1e bytes C++
ScalienDB.shard-dev-2.2.6-rc30.exe!MFunc<TCPConnection,&TCPConnection::`vcall'{24}'>::Thunk(void * arg) Line 81 C++
ScalienDB.shard-dev-2.2.6-rc30.exe!Callable::Execute() Line 22 + 0x3b bytes C++
ScalienDB.shard-dev-2.2.6-rc30.exe!Call(Callable & callable) Line 39 C++
ScalienDB.shard-dev-2.2.6-rc30.exe!CallWarnTimeout(Callable & callable) Line 115 C++
ScalienDB.shard-dev-2.2.6-rc30.exe!ProcessTCPRead(TCPRead * tcpread) Line 872 C++
ScalienDB.shard-dev-2.2.6-rc30.exe!IOProcessor::Poll(int msec) Line 758 + 0xd bytes C++
ScalienDB.shard-dev-2.2.6-rc30.exe!EventLoop::RunOnce() Line 68 C++
ScalienDB.shard-dev-2.2.6-rc30.exe!EventLoop::Run() Line 74 + 0x5 bytes C++
ScalienDB.shard-dev-2.2.6-rc30.exe!RunApplication() Line 94 C++
ScalienDB.shard-dev-2.2.6-rc30.exe!Service::Main(int argc, char * * argv, void (void)* serviceFunc, ServiceIdentity & identity) Line 334 C++
ScalienDB.shard-dev-2.2.6-rc30.exe!RunMain(int argc, char * * argv) Line 65 C++
ScalienDB.shard-dev-2.2.6-rc30.exe!main(int argc, char * * argv) Line 33 + 0x14 bytes C++
ScalienDB.shard-dev-2.2.6-rc30.exe!__tmainCRTStartup() Line 278 + 0x19 bytes C
ScalienDB.shard-dev-2.2.6-rc30.exe!mainCRTStartup() Line 189 C
The text was updated successfully, but these errors were encountered:
And tries to send a cluster message to it resulting in an Assert in ContextTransport. It seems that the bug is caused by low-level IO code.
The text was updated successfully, but these errors were encountered: