Rob, Thanks a lot for the hint how to fix. I committed the changes as part of https://issues.apache.org/jira/browse/QPID-8322. I will merge them into 7.0.x and 7.1.x branches for inclusion into 7.0.8 and 7.1.4 releases accordingly.
Kind Regards, Alex On Thu, 13 Jun 2019 at 21:00, Rob Godfrey <[email protected]> wrote: > Alex, > > looks like a broker defect to me. If the bytes (or message) credit is set > to "infinite credit", then the useCreditForMessage method won't update the > used bytes (or message) credit. However the restoreCredit method always > tries to deduct from the bytes (or message) used value, which will lead to > this error. Since the default for the JMS client is (IIRC) an infinite > bytes credit paired with a fixed amount of message credit then we will see > this error. Ironically it is being seen in 7.0.7 because we fixed a real > bug in 7.0.6 (https://issues.apache.org/jira/browse/QPID-8225). The > "error" observed by Sirdath here is (as you say elsewhere) completely > harmless and can be ignored. > > -- Rob > > On Wed, 12 Jun 2019 at 11:52, Oleksandr Rudyy <[email protected]> wrote: > > > Sidarth, > > > > I cannot see any negative effect from the error at the moment. I believe > > that WARN log level should be used to report the issue like this one. > > Though, it is unclear for me yet whether it is a client or broker defect. > > > > Kind Regards, > > Alex > > > > > > On Tue, 11 Jun 2019 at 23:50, sidarthsc <[email protected]> > > wrote: > > > > > I will try to get that information to you asap. Do you know if this > error > > > messages signifies something impactful? Functionally, the broker > appears > > to > > > be doing fine. Our throughput has not not decreased and most vitals, > e.g. > > > heap memory, look okay. > > > > > > > > > > > > -- > > > Sent from: > > > http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > >
