xiaozi0lei commented on issue #1927:
URL: https://github.com/apache/rocketmq/issues/1927#issuecomment-658613762


   Meet the same issue.
   
   Java Version:
   java version "1.8.0_231"
   Java(TM) SE Runtime Environment (build 1.8.0_231-b11)
   Java HotSpot(TM) 64-Bit Server VM (build 25.231-b11, mixed mode)
   
   RocketMQ version:
   rocketmq-4.7.1
   
   
   Interesting things below:
   ```java
           at 
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:140)
 ~[netty-all-4.0.42.Final.jar:4.0.42.Final]
           ... 1 common frames omitted
   Caused by: java.lang.NoSuchMethodError: 
java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer;
           at 
org.apache.rocketmq.remoting.protocol.RemotingCommand.encodeHeader(RemotingCommand.java:427)
 ~[rocketmq-remoting-4.7.1.jar:4.7.1]
           at 
org.apache.rocketmq.remoting.protocol.RemotingCommand.encodeHeader(RemotingCommand.java:400)
 ~[rocketmq-remoting-4.7.1.jar:4.7.1]
           at 
org.apache.rocketmq.remoting.netty.NettyEncoder.encode(NettyEncoder.java:38) 
~[rocketmq-remoting-4.7.1.jar:4.7.1]
           at 
org.apache.rocketmq.remoting.netty.NettyEncoder.encode(NettyEncoder.java:30) 
~[rocketmq-remoting-4.7.1.jar:4.7.1]
           at 
io.netty.handler.codec.MessageToByteEncoder.write(MessageToByteEncoder.java:107)
 ~[netty-all-4.0.42.Final.jar:4.0.42.Final]
           ... 19 common frames omitted
   2020-07-15 15:40:06 INFO ShutdownHook - Try to shutdown service 
thread:FileWatchService started:false lastThread:Thread[FileWatchService,5,]
   2020-07-15 15:40:06 INFO ShutdownHook - Try to shutdown service 
thread:TransactionalMessageCheckService started:true 
lastThread:Thread[TransactionalMessageCheckService,5,main]
   2020-07-15 15:40:06 INFO ShutdownHook - shutdown thread 
TransactionalMessageCheckService interrupt false
   2020-07-15 15:40:06 INFO ShutdownHook - join thread 
TransactionalMessageCheckService elapsed time(ms) 1 90000
   2020-07-15 15:40:06 INFO ShutdownHook - Shutdown hook over, consuming total 
time(ms): 4585
   2020-07-15 15:42:55 INFO main - 
rocketmqHome=/Users/xiaoneng/webserver/rocketmq-all-4.7.1-source-release/distribution/target/rocketmq-4.7.1/rocketmq-4.7.1
   2020-07-15 15:42:55 INFO main - namesrvAddr=10.30.127.220:9876
   2020-07-15 15:42:55 INFO main - brokerIP1=10.30.127.220
   2020-07-15 15:42:55 INFO main - brokerIP2=10.30.127.220
   2020-07-15 15:42:55 INFO main - brokerName=xiaonengdeMac-Pro.local
   2020-07-15 15:42:55 INFO main - brokerClusterName=DefaultCluster
   2020-07-15 15:42:55 INFO main - brokerId=0
   ```
   
   After many Exceptions, the broker restart itself. **The important Thing** is 
that the broker register successfully and no Exception throws.
   ```java
   2020-07-15 15:56:06 INFO brokerOutApi_thread_4 - register broker[0]to name 
server 10.30.127.220:9876 OK
   2020-07-15 15:56:36 INFO brokerOutApi_thread_1 - register broker[0]to name 
server 10.30.127.220:9876 OK
   2020-07-15 15:57:06 INFO BrokerControllerScheduledThread1 - dispatch behind 
commit log 0 bytes
   2020-07-15 15:57:06 INFO BrokerControllerScheduledThread1 - Slave fall 
behind master: 0 bytes
   2020-07-15 15:57:06 INFO brokerOutApi_thread_2 - register broker[0]to name 
server 10.30.127.220:9876 OK
   2020-07-15 15:57:36 INFO brokerOutApi_thread_3 - register broker[0]to name 
server 10.30.127.220:9876 OK
   2020-07-15 15:58:06 INFO BrokerControllerScheduledThread1 - dispatch behind 
commit log 0 bytes
   2020-07-15 15:58:06 INFO BrokerControllerScheduledThread1 - Slave fall 
behind master: 0 bytes
   2020-07-15 15:58:06 INFO brokerOutApi_thread_4 - register broker[0]to name 
server 10.30.127.220:9876 OK
   2020-07-15 15:58:36 INFO brokerOutApi_thread_1 - register broker[0]to name 
server 10.30.127.220:9876 OK
   ```


----------------------------------------------------------------
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:
[email protected]


Reply via email to