aliyun / aliyun/aliyun-tablestore-java-sdk
怎么检查otsclient是否处于shutdown状态
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 57
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
java.lang.IllegalStateException: Request cannot be executed; I/O reactor status: STOPPED
at org.apache.http.util.Asserts.check(Asserts.java:46)
at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase.ensureRunning(CloseableHttpAsyncClientBase.java:90)
at org.apache.http.impl.nio.client.InternalHttpAsyncClient.execute(InternalHttpAsyncClient.java:123)
at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:68)
at com.alicloud.openservices.tablestore.core.http.AsyncServiceClient.asyncSendRequest(AsyncServiceClient.java:150)
at com.alicloud.openservices.tablestore.core.OperationLauncher.asyncInvokePost(OperationLauncher.java:152)
at com.alicloud.openservices.tablestore.core.BatchGetRowLauncher.fire(BatchGetRowLauncher.java:63)
at com.alicloud.openservices.tablestore.InternalClient.batchGetRow(InternalClient.java:586)
at com.alicloud.openservices.tablestore.SyncClient.batchGetRow(SyncClient.java:273)
怎么检查otsclient是否处于shutdown状态???
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the stack trace at AsyncServiceClient.asyncSendRequest and CloseableHttpAsyncClientBase.ensureRunning, then trace how InternalClient and SyncClient use the client. Determine how shutdown is represented or exposed by the SDK, and verify the behavior around batchGetRow; done means the shutdown state can be checked reliably or the limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100