You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in our application ActiveMQ queues will be created based on the endpoints created by the users so every time we cannot update the ScaledObject so is it possible to scale up the deployment based on any one of the queues reached the targetQueueSize pods should scale up
Instead of destinationName: "testQueue" can we do destinationName: "*"
Manually tried the api it is working fine curl -u username:password "http://localhost:8161/api/jolokia/read/org.apache.activemq:type=Broker,brokerName=localhost,destinationType=Queue,destinationName=*/QueueSize"
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
stalebot
added
the
stale
All issues that are marked as stale due to inactivity
label
Mar 23, 2025
Currently in our application ActiveMQ queues will be created based on the endpoints created by the users so every time we cannot update the ScaledObject so is it possible to scale up the deployment based on any one of the queues reached the targetQueueSize pods should scale up
`triggers:
metadata:
managementEndpoint: "activemq.activemq-test:8161"
destinationName: "testQueue"
brokerName: "activemq_broker"
targetQueueSize: "100"
activationTargetQueueSize: "10"`
Instead of destinationName: "testQueue" can we do destinationName: "*"
Manually tried the api it is working fine
curl -u username:password "http://localhost:8161/api/jolokia/read/org.apache.activemq:type=Broker,brokerName=localhost,destinationType=Queue,destinationName=*/QueueSize"
But through the keda getting this error
The text was updated successfully, but these errors were encountered: