GPSS to RabbitMQ job fails to start when using SSL and CONSISTENCY=strong

Products

• VMware Tanzu Greenplum
• VMware Tanzu Data Suite
• VMware Tanzu Data Suite

Issue/Introduction

When trying to start a job in Greenplum Streaming Serve(GPSS) which will read a stream from RabbitMQ broker fails to start and reports no error in the GPSS log under the following conditions:

1. Using SSL/TLS connection to connect to RabbitMQ
2. Reading a stream from RabbitMQ
3. Using "CONSISTENCY: strong" in the job's yaml file

The error seen in the RabbitMQ log is:

2025-02-26 13:06:00.416125+03:00 [notice] <0.2154929.0> TLS server: In state hello at tls_record.erl:561 generated SERVER ALERT: Fatal - Unexpected Message
2025-02-26 13:06:00.416125+03:00 [notice] <0.2154929.0>  - {unsupported_record_type,0}

Cause

The cause of the error is due to GPSS trying to connect to the RabbitMQ server using a plaintext connection. It is not trying to connect using the SSL/TLS as required.

Resolution

Workaround

Use non-SSL connections to RabbitMQ

or

Use "CONSISTENCY: at-least" in the job's yaml file

Fix

As of March 2025, fix is being developed expected to be released in GPSS 1.11.4.

Check GPSS Release Notes for fix.