So the software sending and consuming the messages is not something you (or your company) has written but instead is something from a vendor? If so, do you have the source-code for this product?
Unfortunately a list of libraries starting with "activemq" doesn't clarify what the software is actually using. Regarding upgrades...This seems like a false dichotomy. You can't really get new features without upgrading. There's been over 30 releases of ActiveMQ Artemis since 2.6.3 which have included 4,700+ commits to the code-base. Those commits include bug fixes and features. Couple more questions: - How are you sending the messages? Can you paste the code from the producer? Also, what library are you using to send the messages? - Have you gathered any statistics from the queue where you're sending messages (e.g. Consumer Count, Message Count, Delivering Count, etc.)? If so, what did they show? If not, could you gather these before and after you see the problem? Justin On Mon, Sep 18, 2023 at 2:34 PM Miller, Michael < michael.mill...@flooranddecor.com> wrote: > Thanks for the quick response. I started working on this project just a > couple months ago, so not completely sure I will be able to answer your > questions correctly, but here goes: > We have 1 Central Server and X number of Store servers - all running > WildFly as the app server. I believe Artemis is the version embedded in > WildFly 16.0.0.Final. The message listener is not an MDB, but a 'task' > that implements MessageListener interface. Not sure how the activemq-core > fits in - I just threw that in just in case it mattered - again these are > libraries I found in our Libraries folder. I just searched our \Libraries > folder where we store all 3rd party software and supplied any that started > with activemq. 🙂 > > We (including me) are the retailer and the software comes from our > vendor, and I have heard that retailers are never in a hurry to upgrade > their software, but prefer new features instead. Not much chance right > now that we would be able to update any packages. > > > > ________________________________ > From: Justin Bertram <jbert...@apache.org> > Sent: Monday, September 18, 2023 1:55 PM > To: users@activemq.apache.org <users@activemq.apache.org> > Subject: [EXTERNAL] Re: Sporadic messageListener > > Can you elaborate on your application components? What are you using as a > broker? Is it ActiveMQ Artemis 2. 6. 3 embedded in WildFly 16. 0. 0. Final? > Are your MessageListener implementations running in WildFly (e. g. as MDBs) > or elsewhere? How does > ZjQcmQRYFpfptBannerStart > This Message is From an Unknown or Untrusted Sender > You have not recently corresponded with this external sender. Do not click > links, download attachments or share sensitive information unless you > recognize the sender and know the content is safe. If this email looks > suspicious, please report via “Report Suspicious” button. > < > https://us-phishalarm-ewt.proofpoint.com/EWT/v1/D60pOmjYakNXXA!oq8qymrG5Kcjsx0gp5MxPXHKrr6gJs4f2iGQDt7dMh9X7nXrS00QtnLjXq2Yy58U-Uf0zyDwjUHiC4or-Y1ua0EAyhgXgDQghJWlnvqNuoXnUjX9mCSizI4o16qryEQGGh40zg$ > > > Report Suspicious > > ZjQcmQRYFpfptBannerEnd > > Can you elaborate on your application components? What are you using as a > broker? Is it ActiveMQ Artemis 2.6.3 embedded in WildFly 16.0.0.Final? Are > your MessageListener implementations running in WildFly (e.g. as MDBs) or > elsewhere? How does "ActiveMQ core 5.7.0" fit in and what exactly do you > mean by "core" in this context? > > Also, these components are pretty old. Both WildFly 16.0.0.Final and > ActiveMQ Artemis 2.6.3 were released in early 2019 and ActiveMQ 5.7.0 was > released in late 2012. Has there been any thought given to upgrading these > components? > > > Justin > > On Mon, Sep 18, 2023 at 1:40 PM Miller, Michael < > michael.mill...@flooranddecor.com> wrote: > > > We are encountering a problem where a small number of messages are not > > triggering the messageListener. We have a shared folder where our host > > drops files to be delivered to all our retail stores. We have a process > > that has to collect a full set of files as a set and when the set is > found, > > we put each file on a local queue on a centralized server. The > > messageListener gets called and we attempt to put the new message on a > > remote queue for retail store. > > > > Generally this works fairly well, but we have started encountering > > problems where, according to our logging, we can see a log message that > the > > (file)message was put in the local queue, but in some small percentage of > > the cases, we never get the onMessage() for the message listener to put > the > > message on the remote store, which breaks our process. > > > > Looking for help/suggestions on how to debug this process to make sure > > that our message listener gets called. Is there a way to request activemq > > debug logging without debugging logging that entire application? > Happening > > in production but not in QA or local dev... > > > > We are running WildFly 16.0.0.Final, with ActiveMQ core 5.7.0 and > ActiveMQ > > Artemis 2.6.3. > > > > We have added extra logging around the our executor service and the > > message listener but some files/messages seem to either 1) NOT make it > into > > the local queue or 2) the message listener doesn't fire. Based on the > > logging, it seems like the message gets to the local queue, as we found > no > > exceptions around that timeframe, so seems to be the listener. > > > > > > > > Mike Miller > > > > Senior Developer II > > > > Floor & Decor > > > > 214-477-9953 > > > > mailto: michael.mill...@flooranddecor.com > > > > This email and any files transmitted with it are the property of Floor & > > Decor, are confidential, and are intended solely for the use of the > > individual or entity to which this email is addressed. If you are not one > > of the named recipient(s) or otherwise have reason to believe that you > have > > received this message in error, please notify the sender at 214.477.9953 > > and delete this message immediately from your computer. Any other use, > > retention, dissemination, forwarding, printing, or copying of this email > is > > strictly prohibited. > > > > Please consider the environment before printing this email. > > > >
