Classic (per the subject line) Stomp 1.1 Among other issues, the STOMP specification suggests I will receive a receipt for my DISCONNECT frame, which I do not receive.
Honestly, it has been about 5 months since I started this inquiry, and have not received any useful information yet. I wrote my own STOMP client, in Progress OpenEdge, with a starter project from the OE Hive. So far, I have not hit any roadblock preventing me from using the ActiveMQ Classic STOMP broker, but would like to have the necessary tooling in place in case issues arise in the future. Regards, Paul Bouscaren | Business Analyst | Wyman-Gordon Forgings, Inc. From: Simon Lundström <si...@su.se.INVALID> Sent: Tuesday, May 14, 2024 10:19 AM To: users@activemq.apache.org Subject: [EXTERNAL] Re: Apache ActiveMQ Classic 5.17.3; STOMP receipts Hi Paul! While not an ActiveMQ dev we've used STOMP a lot (with receipts) without any problems from Perl and Python. How are the receipts coming in and what are you expecting? Which version of ActiveMQ are you using? Classic or Artemis? Which ZjQcmQRYFpfptBannerStart This Message Is From an Untrusted Sender You have not previously corresponded with this sender. ZjQcmQRYFpfptBannerEnd External Email ________________________________ Hi Paul! While not an ActiveMQ dev we've used STOMP a lot (with receipts) without any problems from Perl and Python. How are the receipts coming in and what are you expecting? Which version of ActiveMQ are you using? Classic or Artemis? Which STOMP version are you using? Which client library are you using? I suspect answers to these questions will help the devs answer faster. BR, - Simon On Tue, 2024-05-14 at 15:45:02 +0200, Bouscaren, Paul wrote: > The STOMP receipts are not coming in as the STOMP specification dictates they > should. > > The log4j troubleshooting page is of no help since the logger library has > been updated. > > Any help would be appreciated. > > Regards, > > Paul Bouscaren | Business Analyst | Wyman-Gordon Forgings, Inc. > > > ________________________________ > > This email and any attachments may contain confidential and proprietary > information and must be treated as such. In addition, export or re-export of > the information contained in or attached to this email may be prohibited > under export control laws. > To review our Privacy Policy please visit: > https://urldefense.com/v3/__http://www.precast.com__;!!Nhky1-KV!t9edV3LrrtqPK-GFkO2tMdkwzLsw95DoAaxTa40bcCVqC-4m_3ak4ive3raA5VNRxfTtqPD10ZfyFWcpIXaVVg$<https://urldefense.com/v3/__http:/www.precast.com__;!!Nhky1-KV!t9edV3LrrtqPK-GFkO2tMdkwzLsw95DoAaxTa40bcCVqC-4m_3ak4ive3raA5VNRxfTtqPD10ZfyFWcpIXaVVg$> ________________________________ This email and any attachments may contain confidential and proprietary information and must be treated as such. In addition, export or re-export of the information contained in or attached to this email may be prohibited under export control laws. To review our Privacy Policy please visit: www.precast.com
