milleruntime opened a new issue, #2660:
URL: https://github.com/apache/accumulo/issues/2660

   I saw this Exception in the tserver when it started up. It is being logged 
as a WARN.
   <pre>
   2022-04-28T09:56:33,406 [rpc.CustomNonBlockingServer$CustomFrameBuffer] WARN 
: Exception while invoking!
   org.apache.thrift.protocol.TProtocolException: Service name not found in 
message name: startScan.  Did you forget to use a TMultiplexProtocol in your 
client?
           at 
org.apache.thrift.TMultiplexedProcessor.process(TMultiplexedProcessor.java:116) 
~[libthrift-0.15.0.jar:0.15.0]
           at 
org.apache.accumulo.server.rpc.TimedProcessor.process(TimedProcessor.java:54) 
~[accumulo-server-base-2.1.0-SNAPSHOT.jar:2.1.0-SNAPSHOT]
           at 
org.apache.thrift.server.AbstractNonblockingServer$FrameBuffer.invoke(AbstractNonblockingServer.java:524)
 ~[libthrift-0.15.0.jar:0.15.0]
           at 
org.apache.accumulo.server.rpc.CustomNonBlockingServer$CustomFrameBuffer.invoke(CustomNonBlockingServer.java:129)
 ~[accumulo-server-base-2.1.0-SNAPSHOT.jar:2.1.0-SNAPSHOT]
           at org.apache.thrift.server.Invocation.run(Invocation.java:18) 
~[libthrift-0.15.0.jar:0.15.0]
           at 
org.apache.accumulo.core.trace.TraceWrappedRunnable.run(TraceWrappedRunnable.java:52)
 ~[accumulo-core-2.1.0-SNAPSHOT.jar:2.1.0-SNAPSHOT]
           at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) 
~[?:?]
           at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) 
~[?:?]
           at 
org.apache.accumulo.core.trace.TraceWrappedRunnable.run(TraceWrappedRunnable.java:52)
 ~[accumulo-core-2.1.0-SNAPSHOT.jar:2.1.0-SNAPSHOT]
           at java.lang.Thread.run(Thread.java:829) ~[?:?]
   
   </pre>


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

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to