[
https://issues.apache.org/jira/browse/QPID-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17263834#comment-17263834
]
Alex Rudyy commented on QPID-8496:
----------------------------------
Hi [~hlizza88],
Thanks for reporting this issue.
It looks like "unknown QBB implementation" error can occurs on receiving a
transfer without a payload.
Could you please clarify why your application need to send transfers without
payload?
The amqp spec allows no payload only on resuming a transfer. (As per section
2.7.5 "Transfer", resume flag description). The resume functionality currently
unsupported by the Broker.
It seems that Broker need to report a better error for a transfer without
payload (something like amqp:not-implemented) and detach the link with an error.
Another alternative solution could be to actually allow transfers without
payload, but I am strangling to find a business justification for such
behaviour.
Do you send transfers without payload on purpose?
Kind Regards,
Alex
> Randomly hit "unknown QBB implementation" error
> -----------------------------------------------
>
> Key: QPID-8496
> URL: https://issues.apache.org/jira/browse/QPID-8496
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Affects Versions: qpid-java-broker-8.0.2
> Reporter: Lisa Hong
> Priority: Major
> Attachments: UnknownQBB_callstack
>
>
> Hi team,
> I'm running qpid java broker with modelVersion8.0. And the client is
> qpid-proton with python. Unfortunately, my producer will randomly hit this
> "unknown QBB implementation" error thus failing with on_connection_error.
> Could you please help to advice what could be the root cause? The error call
> stack could be found from attachment.
> I'm suspending some null buffer is provided for this
> QpidByteBufferFactory.concatenate method. But I have no idea why it could
> happen. Would you please help to figure out? Thank you so much!
> Regards,
> Lisa
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
