You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Shishkov (Jira)" <ji...@apache.org> on 2026/03/03 16:17:00 UTC
[jira] [Resolved] (IGNITE-27881) Rare "Invalid message type" error while reading TcpDiscoveryMetricsUpdateMessage in client mode in PerformanceStatisticsSelfTest
[ https://issues.apache.org/jira/browse/IGNITE-27881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ilya Shishkov resolved IGNITE-27881.
------------------------------------
Resolution: Fixed
> Rare "Invalid message type" error while reading TcpDiscoveryMetricsUpdateMessage in client mode in PerformanceStatisticsSelfTest
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-27881
> URL: https://issues.apache.org/jira/browse/IGNITE-27881
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksandr Chesnokov
> Assignee: Ilya Shishkov
> Priority: Major
> Labels: IEP-132, ise
> Attachments: IGNITE-27881_Invalid_message_type.patch
>
>
> When running PerformanceStatisticsSelfTest#testCacheOperation[clientType=client] many times, a rare error appears (about 1 time per ~200 runs).
> The test still passes, but Ignite prints an ERROR from the client discovery socket reader thread:
> * IgniteCheckedException: Invalid message type: -30720
> * sometimes the type is different, for example: Invalid message type: -22272
> Log is given below:
> {noformat}
> [ERROR][tcp-client-disco-sock-reader-[02113c43 127.0.0.1:47500]-#9%performancestatistics.PerformanceStatisticsSelfTest2%-#112%performancestatistics.PerformanceStatisticsSelfTest2%][TestTcpDiscoverySpi] Failed to read message [sock=Socket[addr=/127.0.0.1,port=47500,localport=50288], locNodeId=d3f1d2a4-84e0-4ca9-8216-3366dcc00002, rmtNodeId=02113c43-a5b0-4deb-93e0-d340b1200001]
> org.apache.ignite.IgniteCheckedException: Invalid message type: -22272
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoveryIoSession.readMessage(TcpDiscoveryIoSession.java:222)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.readMessage(TcpDiscoverySpi.java:1813)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketReader.body(ClientImpl.java:1210)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:58)
> Caused by: org.apache.ignite.IgniteException: Invalid message type: -22272
> at
> org.apache.ignite.internal.managers.communication.IgniteMessageFactoryImpl.create(IgniteMessageFactoryImpl.java:142)
> at
> org.apache.ignite.internal.direct.stream.DirectByteBufferStream.readMessage(DirectByteBufferStream.java:1532)
> at
> org.apache.ignite.internal.direct.stream.DirectByteBufferStream.read(DirectByteBufferStream.java:2207)
> at
> org.apache.ignite.internal.direct.stream.DirectByteBufferStream.readMap(DirectByteBufferStream.java:1705)
> at
> org.apache.ignite.internal.direct.DirectMessageReader.readMap(DirectMessageReader.java:399)
> at
> org.apache.ignite.internal.codegen.TcpDiscoveryMetricsUpdateMessageSerializer.readFrom(TcpDiscoveryMetricsUpdateMessageSerializer.java:151)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoveryIoSession.readMessage(TcpDiscoveryIoSession.java:199)
> ... 3 more{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)