landon30 opened a new issue #1927: start boker failed,the log shows 
NoSuchMethodError
URL: https://github.com/apache/rocketmq/issues/1927
 
 
   # environment
      - jdk: 1.8.0_241
      - rocketmq: 4.7.0
   
   # reproduce 
   - nohup sh bin/mqbroker -n localhost:9876 &
   -  [reference](https://rocketmq.apache.org/docs/quick-start/)
   
   # error log: `java.lang.NoSuchMethodError: 
java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer`
     ```
        2020-04-09 18:02:42 WARN brokerOutApi_thread_1 - registerBroker 
Exception, localhost:9876
   org.apache.rocketmq.remoting.exception.RemotingSendRequestException: send 
request to <ocalhost/127.0.0.1:9876> failed
           at 
org.apache.rocketmq.remoting.netty.NettyRemotingAbstract.invokeSyncImpl(NettyRemotingAbstract.java:440)
 ~[rocketmq-remoting-4.7.0.jar:4.7.0]
           at 
org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:373)
 ~[rocketmq-remoting-4.7.0.jar:4.7.0]
           at 
org.apache.rocketmq.broker.out.BrokerOuterAPI.registerBroker(BrokerOuterAPI.java:194)
 ~[rocketmq-broker-4.7.0.jar:4.7.0]
           at 
org.apache.rocketmq.broker.out.BrokerOuterAPI.access$000(BrokerOuterAPI.java:61)
 ~[rocketmq-broker-4.7.0.jar:4.7.0]
           at 
org.apache.rocketmq.broker.out.BrokerOuterAPI$1.run(BrokerOuterAPI.java:150) 
~[rocketmq-broker-4.7.0.jar:4.7.0]
           at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
[na:1.8.0_241]
           at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
[na:1.8.0_241]
           at java.lang.Thread.run(Thread.java:748) [na:1.8.0_241]
   Caused by: io.netty.handler.codec.EncoderException: 
java.lang.NoSuchMethodError: java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer;
   at 
io.netty.handler.codec.MessageToByteEncoder.write(MessageToByteEncoder.java:125)
 ~[netty-all-4.0.42.Final.jar:4.0.42.Final]
      ```

----------------------------------------------------------------
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]


With regards,
Apache Git Services

Reply via email to