i'm trying run route example when client starts connecting server (blockingstub.getfeature(request)) hangs. if stops client (ctrl+c in terminal) error occurs (look below).
does knows might wrong?
stack trace:
terminal1-server:
./gradlew routeguideserver :grpc-core:compilejava up-to-date :grpc-core:animalsniffer ... may 06, 2015 4:56:06 pm io.grpc.examples.routeguide.routeguideserver start info: server started, listening on 8980 // server started; running client terminal2-client:
./gradlew routeguideclient :grpc-core:compilejava up-to-date :grpc-core:animalsniffer ... :grpc-examples:classes up-to-date may 06, 2015 4:56:51 pm io.grpc.examples.routeguide.routeguideclient info info: *** getfeature: lat=409,146,138 lon=-746,188,906 // @ point everythings hangs stoping client ctrl+c results int error in server
may 06, 2015 4:57:50 pm io.netty.channel.defaultchannelpipeline$tailcontext exceptioncaught warning: exceptioncaught() event fired, , reached @ tail of pipeline. means last handler in pipeline did not handle exception. java.io.ioexception: existing connection forcibly closed remote host @ sun.nio.ch.socketdispatcher.read0(native method) @ sun.nio.ch.socketdispatcher.read(socketdispatcher.java:43) @ sun.nio.ch.ioutil.readintonativebuffer(ioutil.java:223) @ sun.nio.ch.ioutil.read(ioutil.java:192) @ sun.nio.ch.socketchannelimpl.read(socketchannelimpl.java:379) @ io.netty.buffer.pooledunsafedirectbytebuf.setbytes(pooledunsafedirectbytebuf.java:311) @ io.netty.buffer.abstractbytebuf.writebytes(abstractbytebuf.java:854) @ io.netty.channel.socket.nio.niosocketchannel.doreadbytes(niosocketchannel.java:242) @ io.netty.channel.nio.abstractniobytechannel$niobyteunsafe.read(abstractniobytechannel.java:115) @ io.netty.channel.nio.nioeventloop.processselectedkey(nioeventloop.java:510) @ io.netty.channel.nio.nioeventloop.processselectedkeysoptimized(nioeventloop.java:467) @ io.netty.channel.nio.nioeventloop.processselectedkeys(nioeventloop.java:381) @ io.netty.channel.nio.nioeventloop.run(nioeventloop.java:353) @ io.netty.util.concurrent.singlethreadeventexecutor$4.run(singlethreadeventexecutor.java:703) @ java.util.concurrent.threadpoolexecutor.runworker(threadpoolexecutor.java:1145) @ java.util.concurrent.threadpoolexecutor$worker.run(threadpoolexecutor.java:615) @ java.lang.thread.run(thread.java:745)
it bug; although client sleeps, there no reason should hang. can't reproduce problem though.
the exception on server-side may related, since client graceful shutdown not produce exception. however, if client did ungracefully shut down connection, warning.
i did see assume message yesterday on grpc-io@googlegroups.com, hadn't had chance respond. i've created an issue tracking bug.
Comments
Post a Comment