Ok but what do you think about Tapas finding that this worked again in a higher version? So 5.16.7 and 6.1.2 did not have this issue, but 5.18.4 did.
Thanks, From: Matt Pavlovich <mattr...@gmail.com> Sent: Monday, July 15, 2024 2:50 PM To: users@activemq.apache.org Cc: Bhattacharjee, Tapas <tapas.bhattachar...@fisglobal.com>; Mau, I-Min <i-min....@fisglobal.com> Subject: Re: Test message api looks to be broken in ActiveMQ 5.18.4 Hi I-Min- The default for the messages API is to set the destination as a topic. If you want to read from a queue, add the &type=queue parameter to your query string. curl --user admin:admin "http://localhost:8161/api/message/TEST?readTimeout=10000&type=queue"; ref: https://activemq.apache.org/components/classic/documentation/rest Thanks, Matt Pavlovich On Jul 15, 2024, at 1:12 PM, Mau, I-Min <i-min....@fisglobal.com.INVALID<mailto:i-min....@fisglobal.com.INVALID>> wrote: Hi, we recently tried out ActiveMQ 5.18.4 (we were at 5.16.7) and one thing we encountered is that the test message api seems to be broken in this newer version. That is, when we tried curl --user admin:admin http://localhost:8161/api/message/TEST?readTimeout=10000 We got below. Just wondering if others have encountered same. Thanks, <title>Error 500 AsyncContext timeout</title> </head> <body><h2>HTTP ERROR 500 AsyncContext timeout</h2> <table> <tr><th>URI:</th><td>/api/message/TEST</td></tr> <tr><th>STATUS:</th><td>500</td></tr> <tr><th>MESSAGE:</th><td>AsyncContext timeout</td></tr> <tr><th>SERVLET:</th><td>MessageServlet</td></tr> </table> </body> </html> The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. Message Encrypted via TLS connection The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. Message Encrypted via TLS connection
