The log snippet given below isnt really much to go on. Guessing: is the broker on the second machine perhaps flow controlling producers, due to its queue / memory / disk usage being above threshhold ?
On Thu, 9 May 2019 at 16:03, paolobar <[email protected]> wrote: > > Hi, > we have a java application producing and consuming messages using > qpid-jms-client-0.11.1.jar and Qpid Broker-J 7.0.0. > > On one machine our application is able to produce and send messages to its > local QPID broker. > On another machine the application is unable to send messages to its local > QPID broker and the only difference we see is that here linkCredit=0. > > Full log: > [appserver0] [389039584:1] <- Flow{nextIncomingId=1, incomingWindow=8192, > nextOutgoingId=0, outgoingWindow=2048, handle=0, deliveryCount=0, > linkCredit=0, available=null, drain=true, echo=false, properties=null} > > As far as we can see the 2 machines are identical and configured in the same > way. > > Any suggestion to explain the different behavior? Is there a way to force > linkCredit > 0 so the second machine can send and produce messages to the > broker? > > The java application runs on java 1.7 (can't be upgraded) > QPID runs on java 1.8 > > Thanks! > > > > -- > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
