httpcore | ⚙️ | HTTP Client library

Solved!..
There was another utility logger library initialized in the application class that prevented crashlytics from collecting log. https://github.com/hypertrack/hyperlog-android

Also the initialization & manifest part is not necessary unless you want to explicitly enable/disable crashlytics working.

By default, MWAA is constrained to using version 3.0.0 for the package apache-airflow-providers-slack. If you specify version 4.2.3 in requirements.txt, it will not be installed (error logs should be available in CloudWatch). You'll have to downgrade to version 3.0.0.

apache-airflow-providers-slack (constraints.txt)

OR

Add constraints file to the top of requirements.txt to use version 4.2.3 of apache-airflow-providers-slack.

Add the constraints file for your Apache Airflow v2 environment to the top of your requirements.txt file.

You can mark them beans with @Lazy so spring will not construct them on application startup. It will construct them when you use them runtime.

please see this documentation

https://memorynotfound.com/lazy-initialize-autowired-dependencies-with-lazy-annotation/

For our code, we do:

ConnectionClosedException seems to hint at the fact that your Spring Boot application cannot establish a connection to your ES cluster.

It looks like you're using ES8, which has SSL/TLS on by default, so you would need to configure your Spring Boot application to use SSL instead.

At 6:00 into the video, elasticsearch.url in application.properties should be https://localhost:9200 instead of just localhost:9200.

However, as of March 15th 2022, it doesn't seem like ES 8 is supported by Spring Data ES yet, you might need to revert to the ES 7.15+ release.

You have to use the information SLF4J provide you and back trace the dependency using dependency:tree and its includes option.

This message:

Set the proxy when you create the client, or set the proxy on the Request.

Since you already refer to a createHttpClient() method :

Fixed with

As per SocketTimeoutException description:

Signals that a timeout has occurred on a socket read or accept.

You're expecting JMeter to get the response in 50 milliseconds or less, if the server fails to respond fully in 50 milliseconds - you will get this error.

If you're absolutely sure that your server responds in less than 50 milliseconds be aware that there are also connect time and latency

As per JMeter Glossary:

Elapsed time. JMeter measures the elapsed time from just before sending the request to just after the last response has been received. JMeter does not include the time needed to render the response, nor does JMeter process any client code, for example Javascript.

So there are following operations involved:

1. JMeter connects to the server
2. JMeter sends the request
3. Server prepares the response
4. Server sends the response to the server
5. JMeter receives first byte of the response
6. JMeter receives last byte of the response

And "Response timeout" means full end-to-end sequence.

If you don't want to see this error either increase the timeout or use Duration Assertion instead, in that case JMeter will wait for the full response to arrive and only then will assert whether the response time exceeds the anticipated value