[ https://issues.apache.org/jira/browse/QPID-7393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cliff Jansen resolved QPID-7393. -------------------------------- Resolution: Fixed > Unavailable buffers in Windows SSL > ---------------------------------- > > Key: QPID-7393 > URL: https://issues.apache.org/jira/browse/QPID-7393 > Project: Qpid > Issue Type: Bug > Components: C++ Broker, C++ Client > Affects Versions: qpid-cpp-1.35.0 > Environment: Windows SChannel > Reporter: Cliff Jansen > Assignee: Cliff Jansen > Fix For: qpid-cpp-1.35.0 > > > From the user list (acartcat cartwright_and...@cat.com): > > I get the following error in the broker, looks like the same error as > > QPID-5033. > [...] > > 2016-05-26 05:22:23 [System] error No IO buffers available: getQueuedBuffer > > with empty queue. Debug data: 0 1 0 3 0 0 1 > [...] > > This can be triggered on demand using: > > qpid-send -b ssl:XXXXXXXX.com:5671 --connection-options {protocol:amqp1.0} > > -a testerq --content-string=hello --messages 200 > In my testing, qpid-send must also be Windows based. I do not see the error > if it is sent from a client running on Linux. > This error is caused by the SChannel driver generating (valid but > useless) empty SSL packets when a zero length write is requested from > the codec on the client side. On the server side, these are > processed and empty read callbacks are generated, even after close. > The WSAENOBUFS happens as a side effect of recursive calls to > sslDataIn while processing adjacent empty packets. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org