ttlInSeconds in bindings.rabbitmq failing

[isaacnikon93]

Expected Behavior

I am trying to bind a queue in rabbit mq using a component attaching the component below

`apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: wait-for-thirty-days
spec:
type: bindings.rabbitmq
version: v1
metadata:

• name: queueName
  value: "wait-for-thirty-days"
• name: host
  value: amqp://guest:guest@rabbit-mq:5672
• name: durable
  value: "true"
• name: maxPriority
  value: "10"
• name: direction
  value: "output"
• name: ttlInSeconds
  value: "2592000"`
  i have created the queue in rabbit mq with the correct ttl, i was expecting the queue to bound

Actual Behavior

i am getting the following error

time="2024-04-25T11:40:10.503551172Z" level=fatal msg="Fatal error from runtime: process component wait-for-thirty-days error: [INIT_COMPONENT_FAILURE]: initialization error occurred for wfe-thirty-days (bindings.rabbitmq/v1): [INIT_COMPONENT_FAILURE]: initialization error occurred for wait-for-thirty-days (bindings.rabbitmq/v1): Exception (406) Reason: \"PRECONDITION_FAILED - inequivalent arg 'x-message-ttl' for queue 'wait-for-thirty-days' in vhost '/': received '-1703967296' but current is '2592000000'\"" app_id=journey-builder instance=135652a5087c scope=dapr.runtime type=log ver=edge

i think there is some overflow happening

Steps to Reproduce the Problem

• i spun up a rabbit mq container
• created the queue with ttl and dead letter
• defined the dapr compnent
• ran the dapr pplication

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.