larksuite / larksuite/oapi-sdk-java
SDK Client request 经常报 socketTimeOut 配置了 requestTimeout 不起作用
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 310
- Forks
- 115
- PR merge metrics
- No merged PRs in 30d
Description
BatchCreateAppTableRecordReq req = BatchCreateAppTableRecordReq.newBuilder()
.appToken(feishuBitableConfigDO.getAppToken())
.tableId(feishuBitableConfigDO.getTableId())
.batchCreateAppTableRecordReqBody(
BatchCreateAppTableRecordReqBody.newBuilder()
.records(appTableRecordList.toArray(new AppTableRecord[] {}))
.build()
).build();
feishuBitableRecordLogDO.setRequest(JSON.toJSONString(req));
BatchCreateAppTableRecordResp resp = null;
try{
resp = feishuPushClient.bitable().appTableRecord().batchCreate(req);
}catch(Exception e){
log.error("Exception",e);
feishuBitableRecordLogDO.setErrorInfo(e.toString());
}
经常报 SocketTimeoutException；设置了 Client feishuPushClient=Client.newBuilder(appId,appSecret)
.requestTimeout(60, TimeUnit.SECONDS)
.build(); 不起作用
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 Client.newBuilder requestTimeout configuration and the feishuPushClient.bitable().appTableRecord().batchCreate(req) call shown in the report. Reproduce the SocketTimeoutException and trace which timeout is applied during the request; done means the configured 60-second requestTimeout governs the batchCreate call or the limitation is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100