Re: Negative Bytes Credit

Thanks Alex. Could you point to the broker code that logs this message? I'd like understand the context in which it's being logged, to see if I can reproduce the issue for you. -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html --

Re: Negative Bytes Credit

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/

Negative Bytes Credit

Hi, We recently upgraded to version 7.0.7 of the Java broker. We are using a customized version of version 0.16 of the client. Yes, it's ancient, and we are considering upgrading, but that is difficult for us for multiple reasons. We noticed the following error in our logs after upgrading from 7.0

Qpid Broker-J Authentication Failure Lockout

Is there server-side logic that locks out the client if the client fails to authenticate X times in a row? Is there any logic that forces the client to wait for Y time units if the client fails to authenticate X times in a row, or something like that? If so, is that logic configurable? Thanks!

Re: Availability of holdOnPublishEnabled attribute in Qpid Broker-J 0.32

Could you explain how the logic behind the holdOnPublishEnabled attribute works? For example, is there a thread that periodically iterates over all messages in queues for which this attribute is enabled and releases, or pushes those messages which are eligible for being processed? -- Sent from:

Re: Rollback Failure

Thanks Rob! That makes sense. Similarly, we're seeing a lot of exceptions of the form "Session sync was interrupted by failover. [error code 541: internal error]." Unfortunately, I'm not seeing in anything in the broker logs and we're logging at the "INFO" level. -- Sent from: http://qpid.215893

[Broker-J v7.0.6] Connection Pool Churning

We're noticing a lot of churn in our connection pool, with connections being opened/closed frequently. Our ExceptionListener frequently gets triggered by a connection being closed with the following stacktrace: javax.jms.JMSException: Connection closed by external action at org.apache.qpid

Rollback Failure

Our server is running broker-j 7.0.6 and our sessions are transacted. We're seeing a lot of exceptions of the form "Failed to rollback: org.apache.qpid.AMQException: timed out waiting for sync: complete = 18, point = 19 [error code 541: internal error]" I read that this can be a symptom of the brok

Re: Using the holdOnPublishedEnabled Attribute

Ignore this post! -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org

Re: Availability of holdOnPublishEnabled attribute in Qpid Broker-J 0.32

Thank you both for responding so quickly! I've got an instance of 7.0.6 up and running and am trying to specify the attribute over the wire, which I believe is supported per https://issues.apache.org/jira/browse/QPID-7694. Unfortunately, I'm unable to do so, i.e, holdOnPublishEnabled is still false

Re: Using the holdOnPublishedEnabled Attribute

Also, how would one specify that attribute as a wire argument? I looked over https://issues.apache.org/jira/browse/QPID-7694, but am not able to set the attribute even with Broker-J 7.0.6. -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html --

Using the holdOnPublishedEnabled Attribute

I read about the holdOnPublishEnabled attribute here https://qpid.apache.org/releases/qpid-broker-j-master/java-broker/book/Java-Broker-Concepts-Queues.html and was wondering if that functionality is available in Qpid Broker-J 0.32? If so, how would we go about specifying that attribute? -- Sent