You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by GitBox <gi...@apache.org> on 2020/12/18 08:01:49 UTC
[GitHub] [rocketmq] preinlov opened a new issue #2509: Client sends heartbeat with new channel each time
preinlov opened a new issue #2509:
URL: https://github.com/apache/rocketmq/issues/2509
there are many error logs in broker log as follows, It looks like my client send heartbeat with new channel each time
2020-12-16 18:39:41 INFO ClientManageThread_2 - new consumer connected, group: myapplication-consumer-group CONSUME_PASSIVELY CLUSTERING channel: ClientChannelInfo [channel=[id: 0xdb9dc65f, L:/30.16.4.204:32228 - R:/clientip:54875], clientId=clientip@quartzPushConsumer@1, language=JAVA, version=293, lastUpdateTimestamp=1608115181093]
2020-12-16 18:41:49 ERROR NettyServerNIOSelector_3_3 - ProcessRequestWrapper response to /clientip:54875 failed
java.nio.channels.ClosedChannelException: null
2020-12-16 18:42:01 INFO ClientManageThread_9 - new consumer connected, group: myapplication-consumer-group CONSUME_PASSIVELY CLUSTERING channel: ClientChannelInfo [channel=[id: 0x32c769af, L:/30.16.4.204:32228 - R:/clientip:5505], clientId=clientip@quartzPushConsumer@1, language=JAVA, version=293, lastUpdateTimestamp=1608115321118]
2020-12-16 18:42:02 WARN ConsumerManageThread_24 - [NOTIFYME]update consumer offset less than store. clientHost=clientip:5505, key=mytopic@myapplication-consumer-group, queueId=1, requestOffset=1920741, storeOffset=1920742
2020-12-16 18:44:19 ERROR NettyServerNIOSelector_3_3 - ProcessRequestWrapper response to /clientip:5505 failed
java.nio.channels.ClosedChannelException: null
2020-12-16 18:44:21 INFO ClientManageThread_12 - new consumer connected, group: myapplication-consumer-group CONSUME_PASSIVELY CLUSTERING channel: ClientChannelInfo [channel=[id: 0x31d1e67c, L:/30.16.4.204:32228 - R:/clientip:16055], clientId=clientip@quartzPushConsumer@1, language=JAVA, version=293, lastUpdateTimestamp=1608115461183]
2020-12-16 18:46:34 ERROR NettyServerNIOSelector_3_1 - ProcessRequestWrapper response to /clientip:16055 failed
java.nio.channels.ClosedChannelException: null
I dont know why the channel connected last time is not ok, the code is as follows
NettyRemotingClient#invokeSync
final Channel channel = this.getAndCreateChannel(addr);
private Channel getAndCreateChannel(final String addr) throws InterruptedException {
if (null == addr) {
return getAndCreateNameserverChannel();
}
ChannelWrapper cw = this.channelTables.get(addr);
if (cw != null && cw.isOK()) {
return cw.getChannel();
}
// why every time create new channel
return this.createChannel(addr);
}
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] RongtongJin closed issue #2509: Client sends heartbeat with new channel each time
Posted by GitBox <gi...@apache.org>.
RongtongJin closed issue #2509:
URL: https://github.com/apache/rocketmq/issues/2509
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] RongtongJin commented on issue #2509: Client sends heartbeat with new channel each time
Posted by GitBox <gi...@apache.org>.
RongtongJin commented on issue #2509:
URL: https://github.com/apache/rocketmq/issues/2509#issuecomment-751157314
> I'd like to say, before the strange event, there was a OOM ERROR in my client application, and then I restarted it with larger JVM heap size first time. Maybe this action caused Netty frequent disconnections ? I dont know much about netty...
It is likely that this is the case because of frequent gc on the client.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] RongtongJin commented on issue #2509: Client sends heartbeat with new channel each time
Posted by GitBox <gi...@apache.org>.
RongtongJin commented on issue #2509:
URL: https://github.com/apache/rocketmq/issues/2509#issuecomment-748418512
Is there a problem with the network between the client and the broker, causing frequent disconnections?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] preinlov commented on issue #2509: Client sends heartbeat with new channel each time
Posted by GitBox <gi...@apache.org>.
preinlov commented on issue #2509:
URL: https://github.com/apache/rocketmq/issues/2509#issuecomment-748558687
I'd like to say, before the strange event, there was a OOM ERROR in my client application, and then I restarted it with larger JVM heap size first time. Maybe this action caused Netty frequent disconnections ? I dont know much about netty...
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] preinlov commented on issue #2509: Client sends heartbeat with new channel each time
Posted by GitBox <gi...@apache.org>.
preinlov commented on issue #2509:
URL: https://github.com/apache/rocketmq/issues/2509#issuecomment-748557848
> Is there a problem with the network between the client and the broker, causing frequent disconnections?
I think no problem in network, I restarted the client application and the problem got fixed, no error logs in broker now.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org