本文介紹了頻道管理頻道Impl未正確關(guān)閉的處理方法，對(duì)大家解決問題具有一定的參考價(jià)值，需要的朋友們下面隨著小編來一起學(xué)習(xí)吧！
問題描述
如果我按照這兩個(gè)測(cè)試運(yùn)行，則會(huì)出現(xiàn)錯(cuò)誤。
第一次測(cè)試
@Rule
public GrpcCleanupRule grpcCleanup = new GrpcCleanupRule();
@Test
public void findAll() throws Exception {
// Generate a unique in-process server name.
String serverName = InProcessServerBuilder.generateName();
// Create a server, add service, start, and register for automatic graceful shutdown.
grpcCleanup.register(InProcessServerBuilder
.forName(serverName)
.directExecutor()
.addService(new Data(mockMongoDatabase))
.build()
.start());
// Create a client channel and register for automatic graceful shutdown.
RoleServiceGrpc.RoleServiceBlockingStub stub = RoleServiceGrpc.newBlockingStub(
grpcCleanup.register(InProcessChannelBuilder
.forName(serverName)
.directExecutor()
.build()));
RoleOuter.Response response = stub.findAll(Empty.getDefaultInstance());
assertNotNull(response);
}
第二次測(cè)試
@Test
public void testFindAll() {
ManagedChannel channel = ManagedChannelBuilder.forAddress("localhost", 8081)
.usePlaintext()
.build();
RoleServiceGrpc.RoleServiceBlockingStub stub = RoleServiceGrpc.newBlockingStub(channel);
RoleOuter.Response response = stub.findAll(Empty.newBuilder().build());
assertNotNull(response);
}
io.grpc.internal.ManagedChannelOrphanWrapper$ManagedChannelReference
清理隊(duì)列嚴(yán)重：~~~Channel ManagedChannelImpl{logID=1，
目標(biāo)=本地主機(jī)：8081}未正確關(guān)閉！~~~
請(qǐng)確保調(diào)用Shutdown()/Shudown Now()并等待，直到waitTermination()返回True。java.lang.RUNTIME異常：托管頻道分配站點(diǎn)
在io.grpc.internal.ManagedChannelOrphanWrapper$ManagedChannelReference.(ManagedChannelOrphanWrapper.java:94)
如果我注釋掉其中一個(gè)，則沒有錯(cuò)誤，單元測(cè)試將通過，但如果兩者同時(shí)運(yùn)行，則會(huì)引發(fā)異常。
編輯
基于建議。
@Test
public void testFindAll() {
ManagedChannel channel = ManagedChannelBuilder.forAddress("localhost", 8081)
.usePlaintext()
.build();
RoleServiceGrpc.RoleServiceBlockingStub stub = RoleServiceGrpc.newBlockingStub(channel);
RoleOuter.Response response = stub.findAll(Empty.newBuilder().build());
assertNotNull(response);
channel.shutdown();
}
推薦答案
嘿，我剛剛在使用Dialogflow V2 Java SDK時(shí)遇到了類似的問題，收到錯(cuò)誤
Oct 19, 2019 4:12:23 PM io.grpc.internal.ManagedChannelOrphanWrapper$ManagedChannelReference cleanQueue
SEVERE: *~*~*~ Channel ManagedChannelImpl{logId=41, target=dialogflow.googleapis.com:443} was not shutdown properly!!! ~*~*~*
Make sure to call shutdown()/shutdownNow() and wait until awaitTermination() returns true.
此外，由于擁有龐大的客戶群，我們開始遇到out of memory unable to create native thread錯(cuò)誤。
在執(zhí)行了大量調(diào)試操作并使用了Visual VM線程監(jiān)控后，我終于發(fā)現(xiàn)問題是由于SessionsClient沒有關(guān)閉。所以我使用了附帶的代碼塊來解決這個(gè)問題。在測(cè)試后，我終于能夠釋放所有已使用的線程，也解決了前面提到的錯(cuò)誤。
SessionsClient sessionsClient = null;
QueryResult queryResult = null;
try {
SessionsSettings.Builder settingsBuilder = SessionsSettings.newBuilder();
SessionsSettings sessionsSettings = settingsBuilder
.setCredentialsProvider(FixedCredentialsProvider.create(credentials)).build();
sessionsClient = SessionsClient.create(sessionsSettings);
SessionName session = SessionName.of(projectId, senderId);
com.google.cloud.dialogflow.v2.TextInput.Builder textInput = TextInput.newBuilder().setText(message)
.setLanguageCode(languageCode);
QueryInput queryInput = QueryInput.newBuilder().setText(textInput).build();
DetectIntentResponse response = sessionsClient.detectIntent(session, queryInput);
queryResult = response.getQueryResult();
} catch (Exception e) {
e.printStackTrace();
}
finally {
sessionsClient.close();
}
The shorter values on the graph highlights the use of client.close(). Without that the threads were stuck in Parking State.
這篇關(guān)于頻道管理頻道Impl未正確關(guān)閉的文章就介紹到這了，希望我們推薦的答案對(duì)大家有所幫助，
