It is a AMQ Broker bug. When we are trying with the Jolokia url and the method retryMessage(long). We can see that there was a similar bug from the console in the earlier version which has been fixed. https://issues.apache.org/jira/browse/ARTEMIS-2137

So, the same bug is still there when using the command line with Jolokia url but working fine from the console/GUI.

 

E.g. this is the command line, we have used to retry a message with id:2147502943

 

curl http://username:password@ipaddress:8161/console/jolokia/exec/org.apache.activemq.artemis:broker=!%220.0.0.0!%22,component=addresses,address=!%22SYNC_OUTBOUND_QUEUE_DEAD_LETTER_QUEUE!%22,subcomponent=queues,routing-type=!%22anycast!%22,queue=!%22SYNC_OUTBOUND_QUEUE_DEAD_LETTER_QUEUE!%22/retryMessage(2147502943)

 

The error from this :

{"request":

{"mbean":"org.apache.activemq.artemis:address=\"SYNC_OUTBOUND_QUEUE_DEAD_LETTER_QUEUE\",broker=\"0.0.0.0\",component=addresses,queue=\"SYNC_OUTBOUND_QUEUE_DEAD_LETTER_QUEUE\",routing-type=\"anycast\",subcomponent=queues","type":"exec","operation":"retryMessage(2147502943)"}

,"error_type":"java.lang.IllegalArgumentException","error":"java.lang.IllegalArgumentException : No operation retryMessage(2147502943) on MBean org.apache.activemq.artemis:address=\"SYNC_OUTBOUND_QUEUE_DEAD_LETTER_QUEUE\",broker=\"0.0.0.0\",component=addresses,queue=\"SYNC_OUTBOUND_QUEUE_DEAD_LETTER_QUEUE\",routing-type=\"anycast\",subcomponent=queues exists. Known signatures: (long)","status":400}

 

We are using AMQ version:

AMQ7.11.6

Artemis2.28.0.redhat-00019

Hawtio2.0.0.fuse-7_12_0-00019-redhat-00001

Hawtio Core4.16.5

Hawtio Integration4.16.12

Hawtio OAuth4.13.15