Run Mq Diagnostic
Run MQ connection diagnostic with verbose step-by-step output.
Tests STOMP connectivity to an MQ broker (e.g., AWS AmazonMQ) with detailed timeline of DNS, TCP, TLS, and STOMP handshake phases.
This is a one-shot diagnostic connection that does NOT use the production ArtemisQueueProvider. It’s designed for debugging connection issues with custom credentials.
Args: request: Connection parameters including host, port, credentials
Returns: MQDiagnosticResponse with step-by-step timeline and connection details
Request Body required
Section titled “Request Body required ”Connection parameters for MQ diagnostic test.
object
MQ broker host (e.g., b-xxxxx.mq.eu-north-1.amazonaws.com)
STOMP+SSL port (61614 for AWS MQ)
MQ username
MQ password
Enable SSL/TLS (required for AWS MQ)
Verify SSL certificates
Heartbeat send interval (ms)
Heartbeat receive interval (ms)
Connection timeout (seconds)
Test message publish/subscribe flow
Pub/sub test timeout (seconds)
Number of test messages to publish
Report progress every N messages (0=auto: every 10% for <=1000, every 1000 for >1000)
Delay between messages in ms
Random jitter range to add to delay in ms
Test publish retry behavior on SSLEOFError
Number of retry attempts for publish
Base backoff between retries in ms
Test fresh-connection-per-publish pattern (replicates ArtemisQueueProvider)
Number of fresh-connection publishes to attempt
Max jitter in ms before each connection (0=disabled)
Max concurrent fresh connections (semaphore limit)
Test fresh-connection with retry logic (proves SSLEOFError fix)
Max retry attempts per publish on SSLEOFError
Base backoff in ms (exponential: 100, 200, 400…)
Responses
Section titled “ Responses ”Successful Response
Full MQ diagnostic result with connection timeline.
object
Whether connection test succeeded
Total diagnostic duration (ms)
Formatted STOMP connection URL (stomp+ssl://host:port or stomp://host:port)
Step-by-step connection timeline
Single step in the connection diagnostic process.
object
Milliseconds since diagnostic start
Diagnostic phase: dns, tcp, tls, stomp, pubsub_publish, pubsub_subscribe, complete, error
Human-readable event description
Whether this step succeeded
Whether STOMP connection was established
Result of pub/sub message flow test.
object
Whether pub/sub test succeeded
Number of messages published
Number of messages received
Number of messages expected
Delay between messages in ms
Jitter range applied in ms
Result of publish retry behavior test.
object
Whether retry test succeeded
Total publish attempts made
Number of successful publishes
Number of failed attempts before success
SSLEOFError count caught and retried
ConnectionLostError count caught
Other errors caught
Backoff used between retries
Result of fresh-connection-per-publish test (replicates ArtemisQueueProvider pattern).
object
Whether all publishes succeeded
Total connection+publish attempts
Successful publishes
Failed publishes
SSLEOFError count
ConnectionLostError count
FailedAllConnectAttemptsError count
Other error count
Jitter setting used
Concurrency limit used
Sum of all retries across all publishes
Publishes that worked without retry
Publishes that needed at least one retry
Worst case retries for one publish
Max retry attempts setting used
Base backoff setting used
Validation Error