SSLException: Unsupported or unrecognized SSL message about s3mock HOT 6 CLOSED

Magic, but the failure does not occur anymore. I think we can close this issue for now.

from s3mock.

@tashoyan
which test did you run in a loop?
How did you determine that S3Mock suddenly respond with HTTP to an HTTPS request? We are relying on Docker, Jetty, Java and Spring for communication, S3Mock does not implement HTTPS communication.

Maybe you just overloaded the S3Mock, it may have run out of memory, it may be a problem with your Docker runtime or TestContainers...

Are the errors evenly distributed or are all errors occurring towards the end of the run?

We are using a self-signed certificate, which does not pass curls SSL certificate inspection.

$ curl http://localhost:9090/
<ListAllMyBucketsResult><Owner><ID>79a59df900b949e55d96a1e698fbacedfd6e09d98eacf8f8d5218e7cd47ef2be</ID><DisplayName>s3-mock-file-store</DisplayName></Owner><Buckets/></ListAllMyBucketsResult>

$ curl https://localhost:9191/
curl: (60) SSL certificate problem: self signed certificate
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

$ curl --insecure https://localhost:9191/
<ListAllMyBucketsResult><Owner><ID>79a59df900b949e55d96a1e698fbacedfd6e09d98eacf8f8d5218e7cd47ef2be</ID><DisplayName>s3-mock-file-store</DisplayName></Owner><Buckets/></ListAllMyBucketsResult>

Also: when using the S3Mock locally, it's unnecessary to use an SSL connection.

from s3mock.

My test does the following:

• create a bucket
• list all buckets
• put a file in the bucket
• list objects in the bucket

An instance of S3Mock is created before each test and shut down after each test.

A loop is implemented as a shell script which repeatedly runs a Maven command to execute the test. For sure it is not a load test.

Nevertheless I get failures in approximately 30% of runs.

I checked the failure with the debugger. Indeed the failure occurs in SSLSocketInputRecord.decode(), where either HADSHAKE or ALERT is expected, but a string "HTTP/" appears in the header instead:

                // header is actually "HTTP/"
                if ((header[0] != ContentType.HANDSHAKE.id) &&
                        (header[0] != ContentType.ALERT.id)) {
                    plaintext = handleUnknownRecord();
                }

I also checked the response from the S3Mock endpoint with curl command, as described above. Indeed, in case of the failure it responses with plain HTTP rather than HTTPS - see the examples above.

from s3mock.

Regarding your remark:

Also: when using the S3Mock locally, it's unnecessary to use an SSL connection.

We use S3Mock for integration tests on some application, that expects HTTPS endpoint. That's why we need S3Mock with HTTPS.

from s3mock.

And this is how S3Mock endpoint responds in case of success:

# Try HTTPS
$> curl --insecure https://localhost:49650
<ListAllMyBucketsResult><Owner><ID>79a59df900b949e55d96a1e698fbacedfd6e09d98eacf8f8d5218e7cd47ef2be</ID><DisplayName>s3-mock-file-store</DisplayName></Owner><Buckets><Bucket><Name>b1</Name><CreationDate>2023-10-04T19:16:28.391Z</CreationDate></Bucket></Buckets></ListAllMyBucketsResult>

# Try HTTP
$> curl http://localhost:49650
curl: (1) Received HTTP/0.9 when not allowed

from s3mock.

# Try HTTP
$> curl http://localhost:49650
curl: (1) Received HTTP/0.9 when not allowed

This is expected - you tried to connect to an HTTPS port using HTTP. This would not work in any application...
Not sure what you want me to do here...
Are there logs from one of the failed runs? Any errors that are actually in the S3Mock code?

I added a test that does the same thing as your test, ran it 1000 times.
Locally, all is fine.
On the PRB on Github, all is fine.

https://github.com/adobe/S3Mock/actions/runs/6418197863/job/17425509251?pr=1398
#1398

Try checking out the branch and run a mvn build (this will take hours).

from s3mock.