> I now think this only happens for AMQP connections on a cluster... What exactly do you mean by "on a cluster"? Do you mean you have a broker cluster and the client is using AMQP to connect to one of the brokers in the cluster? If so, is a broker cluster necessary to reproduce this or do you also see it with a standalone broker?
The more details (within reason) you can provide about your environment/configuration the better. Justin On Mon, Feb 15, 2021 at 6:22 PM Dondorp, Erwin <erwin.dond...@cgi.com> wrote: > Justin, > > > Are you able to reproduce this reliably? > Yes, this happens very often, but not strictly reproducible. > > > If so could you share those details so I could do the same? > I'm using command-line client https://github.com/fmtn/a > I even added some extra close() statements in there to be sure, but that > did not help. Hence my doubt. > (you may notice that I contributed a few small items to "a", but I'm not a > maintainer) > I've also used "a" to test against ActiveMQ5 in the past. > > > I'm not aware of any bugs related to spurious WARN messages like > this,[...] > With this encouragement, I intensified the search. > All objects are closed from the client side, so looking at the server. > I now think this only happens for AMQP connections on a cluster (as I > could not repeat it on CORE or standalone server). > > thx, > e. > > -----Oorspronkelijk bericht----- > Van: Justin Bertram <jbert...@apache.org> > Verzonden: maandag 15 februari 2021 22:33 > Aan: users@activemq.apache.org > Onderwerp: Re: WARN [org.apache.activemq.artemis.core.server] AMQ222107: > Cleared up resources for session <uuid> > > > EXTERNAL SENDER: Do not click any links or open any attachments unless > you trust the sender and know the content is safe. > EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce > jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous > ayez l'assurance que le contenu provient d'une source sûre. > > I'm not aware of any bugs related to spurious WARN messages like this, but > that doesn't mean one doesn't exist. If a client didn't properly close its > session before terminating then the connection TTL would have to elapse > before the broker closed the server-side resources. You wouldn't see the > WARN immediately. I wouldn't expect to see this message normally. There may > be something wrong with your client, but I can't say without more details. > Are you able to reproduce this reliably? If so could you share those > details so I could do the same? > > > Justin > > On Mon, Feb 15, 2021 at 3:17 PM Dondorp, Erwin <erwin.dond...@cgi.com> > wrote: > > > Hello everyone, > > > > My Artemis log file has this message: WARN > > [org.apache.activemq.artemis.core.server] AMQ222107: Cleared up > > resources for session [uuid here]. > > The message does not happen immediately after the client has > > disconnected, so it is a bit hard to analyse. > > I'm currently still convinced that my client software behaves > > properly, sessions are committed and closed, etc. > > Is this then an un-avoidable warning message? Or is there still > > something wrong in my client? If so, any clues available? > > > > thx! > > Erwin > > >
