Regarding 2.19 and ARTEMIS-3677, I just checked and the latest version available to us on the secure network is 2.19.1.
Is there a known "fix" for ARTEMIS-3677? I suppose we can just work with this version with no ability to examine messages in a queue -- or maybe some guidance on how to roll our own message viewer? ________________________________ From: Justin Bertram <jbert...@apache.org> Sent: Friday, June 10, 2022 2:20 PM To: users@activemq.apache.org <users@activemq.apache.org> Subject: Re: [External] - Re: Unable to Browse Messages in ActiveMQ Artemis Queue CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > ...although I don't see when I can view the message content... When you're browsing the messages click the "Show" button on the far right of the row of the corresponding message. Justin On Fri, Jun 10, 2022 at 12:58 PM Richard Bergmann <rbergm...@colsa.com.invalid> wrote: > Thank you Justin. I upgraded to 11 on my dev box, then installed 2.22 and > it now displays my messages -- although I don't see when I can view the > message content, which is something I could do on the Classic console. I > can live with that. > > I'm not entirely sure we can upgrade to 11 on our prod box (running on a > gov't air-gapped secure network), but I will look into it. The nice thing > is I can install it alongside 8 -- assuming I can install it at all -- and > use the alternatives system to switch it out. > > Anyway, thanks for your help again. I think I can muddle through this. > > Rich > ________________________________ > From: Justin Bertram <jbert...@apache.org> > Sent: Friday, June 10, 2022 1:24 PM > To: users@activemq.apache.org <users@activemq.apache.org> > Subject: Re: [External] - Re: Unable to Browse Messages in ActiveMQ > Artemis Queue > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you recognize the sender and know > the content is safe. > > > > Is there a way to get it to run under Java 8? > > Unfortunately there isn't. Both ActiveMQ "Classic" and Artemis have moved > on from Java 8 for the latest releases. "Classic" made the transition in > 5.17.0 and Artemis in 2.20.0. That said, there are still branches where > Java 8 releases are possible, but those releases would be for bug fixes > only and would not have any new features. The 2.19.1 release was like that. > It's technically possible to do another 2.19.x release, but there's > currently nothing scheduled. > > You always have the option of cherry-picking fixes and building your own > release. Any seasoned Java developer could manage that. > > In any event, I would strongly recommend moving beyond Java 8 at this > point. From what I can tell much of the Java world has already done so. > > > ...we work on a secure network that is not always up to the latest and > greatest... > > For what it's worth, Java 11 is not the "latest and greatest." That > distinction goes to Java 18 at this point. Java 11 was released almost 4 > years ago in September 2018 and Java 17 (the latest LTS release) came in > September 2021. But I digress. > > > Justin > > On Fri, Jun 10, 2022 at 11:29 AM Richard Bergmann > <rbergm...@colsa.com.invalid> wrote: > > > Is there a way to get it to run under Java 8? I tried 2.22 but it cried > > about Java 11 and I'm not sure we can upgrade to it (we work on a secure > > network that is not always up to the latest and greatest). :( > > > > ________________________________ > > From: Justin Bertram <jbert...@apache.org> > > Sent: Friday, June 10, 2022 12:04 PM > > To: users@activemq.apache.org <users@activemq.apache.org> > > Subject: [External] - Re: Unable to Browse Messages in ActiveMQ Artemis > > Queue > > > > CAUTION: This email originated from outside of the organization. Do not > > click links or open attachments unless you recognize the sender and know > > the content is safe. > > > > > > You're almost certainly hitting ARTEMIS-3677 [1]. It appears you migrated > > recently so I would have expected you to use a more recent version than > > 2.19.0 (which was released almost 8 months ago). You'll need to move to > at > > least 2.21.0 although 2.22.0 would be better. Keep in mind that 2.23.0 is > > in the voting process now so it should land soon. > > > > > > Justin > > > > [1] > > > https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FARTEMIS-3677&data=05%7C01%7CRBERGMANN%40colsa.com%7Cbce36c031e90495be38808da4b0df5aa%7C9821086b78824b43a5edb1e979bee31f%7C1%7C0%7C637904820580716210%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=XTpZCifLCuk2WGdbjow3G9Ti4AhsfMWLaYn%2B6PmjM6o%3D&reserved=0 > > > > On Fri, Jun 10, 2022 at 10:52 AM Richard Bergmann > > <rbergm...@colsa.com.invalid> wrote: > > > > > I migrated my application from Classic to Artemis 2.19 (Running Java 8) > > > and messages that I used to be able to view are not shown in the new > > > console. Note that there are over 25K messages in the queue and at the > > > moment there are no consumers or producers and the service has been > > > restarted (i.e., the messages are durable). > > > > > > If it makes any difference, the messages are JSON since I am using > Python > > > STOMP and Python is very JSONic. > > > > > > > > > ------------------------------ > > > The information contained in this e-mail and any attachments from COLSA > > > Corporation may contain company sensitive and/or proprietary > information, > > > and is intended only for the named recipient to whom it was originally > > > addressed. If you are not the intended recipient, any disclosure, > > > distribution, or copying of this e-mail or its attachments is strictly > > > prohibited. If you have received this e-mail in error, please notify > the > > > sender immediately by return e-mail and permanently delete the e-mail > and > > > any attachments. > > > > > > COLSA Proprietary > > > > > ________________________________ > > The information contained in this e-mail and any attachments from COLSA > > Corporation may contain company sensitive and/or proprietary information, > > and is intended only for the named recipient to whom it was originally > > addressed. If you are not the intended recipient, any disclosure, > > distribution, or copying of this e-mail or its attachments is strictly > > prohibited. If you have received this e-mail in error, please notify the > > sender immediately by return e-mail and permanently delete the e-mail and > > any attachments. > > > > > > COLSA Proprietary > > > ________________________________ > The information contained in this e-mail and any attachments from COLSA > Corporation may contain company sensitive and/or proprietary information, > and is intended only for the named recipient to whom it was originally > addressed. If you are not the intended recipient, any disclosure, > distribution, or copying of this e-mail or its attachments is strictly > prohibited. If you have received this e-mail in error, please notify the > sender immediately by return e-mail and permanently delete the e-mail and > any attachments. > > > COLSA Proprietary > ________________________________ The information contained in this e-mail and any attachments from COLSA Corporation may contain company sensitive and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments. COLSA Proprietary
