linkedin / linkedin/ambry

SSLEngine closed already exception

Open
#1,107 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Java
Stars
1.8k
Forks
298
Avg merge
21h 43m
Merged PRs (30d)
9

Description

Saw an exception in `FrontendIntegrationTest` during a travis build. Seems to be intermittent but filing this issue to keep track since
1) This is in the `stitchBlob` test (recently introduced)
2) We made some SSL changes recently
```
om.github.ambry.frontend.FrontendIntegrationTest > stitchedUploadTest[5] FAILED
java.util.concurrent.ExecutionException: javax.net.ssl.SSLException: SSLEngine closed already
at com.github.ambry.router.FutureResult.resultOrThrow(FutureResult.java:113)
at com.github.ambry.router.FutureResult.get(FutureResult.java:99)
at com.github.ambry.frontend.FrontendIntegrationTest.getBlobInfoAndVerify(FrontendIntegrationTest.java:836)
at com.github.ambry.frontend.FrontendIntegrationTest.uploadDataChunksAndVerify(FrontendIntegrationTest.java:1244)
at com.github.ambry.frontend.FrontendIntegrationTest.stitchedUploadTest(FrontendIntegrationTest.java:414)
Caused by:
javax.net.ssl.SSLException: SSLEngine closed already
```

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with FrontendIntegrationTest.stitchedUploadTest and the failing getBlobInfoAndVerify and uploadDataChunksAndVerify calls named in the stack trace. Run the stitched upload test and inspect FutureResult.java around resultOrThrow and get, along with the recent SSL changes. Done means the intermittent SSLEngine closed already failure is understood and the test passes reliably.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.