JVM crashes when using aws-crt-client #2150
Comments
croudet
added
bug
|
Thank for your reporting the issue. We will investigate it. |
zoewangg
added
the
investigating
|
@croudet could you enable CRT logging using the system properties showing here https://github.com/awslabs/aws-crt-java/blob/main/src/main/java/software/amazon/awssdk/crt/Log.java#L129 and provide the wirelogs? Make sure you redact the senstive information. Example: |
|
I got a trace file, but it is to big (even compressed) to attach. How can I share it? |
|
You can either send it to us via email |
|
Log file uploaded to google drive: |
|
Should be ok now. Or this link should work for everybody: https://drive.google.com/file/d/1Czf6sohk8G3ypOLjqtpR4-k59NBCyC2X/view?usp=sharing |
|
I was able to download it. Thank you for sharing the logs. We will investigate it. |
|
The version of the CRT used by the Java SDK is fairly old and does not have a number of stability fixes we've made with respect to C-level ref-counting certain objects, which include the host resolver. I think it is reasonable to update the SDK's crt version when safe (possibly post-reinvent) and recheck. |
|
Thanks Bret. I created PR #2167 to bump up crt version. @croudet could you try specifying |
|
Still got a jvm crash, error is a bit different: crt logs: |
|
In addition to the assert itself, it's also a mystery as to why asserts are causing a crash. Published jars shouldn't be built in Debug mode and so asserts should be getting compiled out. So we may have a CD issue on Windows with the wrong config getting built as well. |
|
Just to give an update here, I currently suspect there's a platform inconsistency where getaddrinfo is returning no error but also no addresses. I have a PR to relax the constraints we apply in host resolution and improve the logging at the debug level to help confirm/deny this situation: awslabs/aws-c-io#337 I don't have a reliable estimate as to when this will get into the java crt which in turn then needs to get into (version bump) the Java v2 sdk, but hopefully in a week or two. Also, I still haven't determined why the Windows maven build has fatal asserts enabled. |
debora-ito
removed
the
investigating
|
There was a fix to the host resolver in version 0.9.1; but the latest is 0.9.2 which should work: |
|
@croudet Sorry to ask you to upgrade the aws-crt version again. Please let us know if you still experience any issues after the upgrade. |
debora-ito
added
the
response-requested
|
It looks like this issue hasn’t been active in longer than a week. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please add a comment to prevent automatic closure, or if the issue is already closed please feel free to reopen it. |
github-actions
bot
added
closing-soon
…aedae6587 Pull request: release <- staging/97ffea06-fa75-4345-bc2a-ebfaedae6587
Describe the bug
I am trying to use aws-crt-client as a netty replacement.
Unfortunately, swtiching to crt_client does not work. The jvm crashes with the following trace:
Expected Behavior
Should not crash the jvm. The netty client is working well.
Current Behavior
The jvm crashes.
Some logs before the jvm crash:
{"@timestamp":"2020-11-17T21:29:38.947Z","loglevel":"ERROR","message":"Response Encountered an Error.","logger":"software.amazon.awssdk.http.crt.internal.AwsCrtAsyncHttpStreamAdapter","thread":"Thread-5","exception":"software.amazon.awssdk.crt.http.HttpException: socket not connected.\r\n\tat software.amazon.awssdk.http.crt.internal.AwsCrtAsyncHttpStreamAdapter.onResponseComplete(AwsCrtAsyncHttpStreamAdapter.java:116)\r\n\tat software.amazon.awssdk.crt.http.HttpStreamResponseHandlerNativeAdapter.onResponseComplete(HttpStreamResponseHandlerNativeAdapter.java:31)\r\n","level":40000} {"@timestamp":"2020-11-17T21:29:38.947Z","loglevel":"ERROR","message":"Error processing Response Body","logger":"software.amazon.awssdk.http.crt.internal.AwsCrtResponseBodyPublisher","thread":"Thread-5","exception":"software.amazon.awssdk.crt.http.HttpException: socket not connected.\r\n\tat software.amazon.awssdk.http.crt.internal.AwsCrtAsyncHttpStreamAdapter.onResponseComplete(AwsCrtAsyncHttpStreamAdapter.java:116)\r\n\tat software.amazon.awssdk.crt.http.HttpStreamResponseHandlerNativeAdapter.onResponseComplete(HttpStreamResponseHandlerNativeAdapter.java:31)\r\n","level":40000} {"@timestamp":"2020-11-17T21:29:38.951Z","loglevel":"ERROR","message":"Error before ResponseBodyPublisher could complete: socket not connected.","logger":"software.amazon.awssdk.http.crt.internal.AwsCrtResponseBodyPublisher","thread":"Thread-5","level":40000} {"@timestamp":"2020-11-17T21:29:39.699Z","loglevel":"ERROR","message":"Response Encountered an Error.","logger":"software.amazon.awssdk.http.crt.internal.AwsCrtAsyncHttpStreamAdapter","thread":"Thread-8","exception":"software.amazon.awssdk.crt.http.HttpException: socket not connected.\r\n\tat software.amazon.awssdk.http.crt.internal.AwsCrtAsyncHttpStreamAdapter.onResponseComplete(AwsCrtAsyncHttpStreamAdapter.java:116)\r\n\tat software.amazon.awssdk.crt.http.HttpStreamResponseHandlerNativeAdapter.onResponseComplete(HttpStreamResponseHandlerNativeAdapter.java:31)\r\n","level":40000} {"@timestamp":"2020-11-17T21:29:39.699Z","loglevel":"ERROR","message":"Error processing Response Body","logger":"software.amazon.awssdk.http.crt.internal.AwsCrtResponseBodyPublisher","thread":"Thread-8","exception":"software.amazon.awssdk.crt.http.HttpException: socket not connected.\r\n\tat software.amazon.awssdk.http.crt.internal.AwsCrtAsyncHttpStreamAdapter.onResponseComplete(AwsCrtAsyncHttpStreamAdapter.java:116)\r\n\tat software.amazon.awssdk.crt.http.HttpStreamResponseHandlerNativeAdapter.onResponseComplete(HttpStreamResponseHandlerNativeAdapter.java:31)\r\n","level":40000}Steps to Reproduce
Just replace netty client with crt client:
Your Environment
The text was updated successfully, but these errors were encountered: