[ 
https://issues.apache.org/jira/browse/QPID-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264185#comment-17264185
 ] 

Robert Godfrey commented on QPID-8496:
--------------------------------------

Hi [~hlizza88],

I would suggest that you turn on AMQP (protocol) logging both on the client and 
the broker.  Given where the exception occurs in the broker code, I'd be pretty 
sure that the ultimate error is on the client side (i.e. it is sending an 
illegal message transfer instruction with no associated message data).  

The transfer is never reaching a queue so the type of the queue will not be a 
factor.  The hearbeats between client and broker are a different instruction 
type to message transfer, so again that will not be a factor.

Hope this helps,
Rob

> 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]

Reply via email to