[ https://issues.apache.org/jira/browse/QPID-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy resolved QPID-8518. ------------------------------ Resolution: Fixed > [Broker-J] Message transfer freezes when session runs out of transfer frames > ---------------------------------------------------------------------------- > > Key: QPID-8518 > URL: https://issues.apache.org/jira/browse/QPID-8518 > Project: Qpid > Issue Type: Bug > Components: Broker-J > Reporter: Marek Laca > Priority: Minor > Labels: Broker, Java, Messages > Fix For: qpid-java-broker-8.0.5 > > > It is stated in AMQP protocol documentation: > _An AMQP connection consists of a full-duplex, reliably ordered sequence of > frames. A frame is the unit of work carried on the wire. Connections have a > negotiated maximum frame size allowing byte streams to be easily defragmented > into complete frame bodies representing the independently parsable units._ > Each session negotiates properties and state that drives the flow of the > frames: > * next-incoming-id > * incoming-window > * next-outgoing-id > * outgoing-window > * remote-incoming-window > * remote-outgoing-window > The capacity of the incoming flow is limited by the maximum frame size and > incoming window. When message size exceeds the capacity of the incoming flow > to broker the transfer freezes. Neither client nor broker tries to negotiate > a new incoming window (I have tested several clients.) The broker is the > receiver and so it is the authority that makes the final decision about > incoming window. Hence, the broker should offer to client a new incoming > window when the capacity is depleted. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org