[ 
https://issues.apache.org/jira/browse/QPID-6403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Robertus updated QPID-6403:
---------------------------------
    Description: 
I have a Rabbit client tied to a QPID broker.  There appears to be a gap in the 
support of the Qpid broker for a 0.91 compliant frame.  This occurs when the 
"<channel>.confirmSelect()" method is called.  The AMQP spec appears to 
recognize this (here is the example in GO- 
https://github.com/streadway/amqp/blob/master/spec091.go) .
Here is the Rabbit oage documenting the use: 
https://www.rabbitmq.com/confirms.html

2015-02-20 10:19:20,499 [] [] DEBUG 
org.apache.qpid.framing.FieldTable:writeToBuffer - FieldTable::writeToBuffer: 
Writing encoded length of 166...
2015-02-20 10:19:20,499 [] [] DEBUG 
org.apache.qpid.framing.FieldTable:writeToBuffer - {product=[LONG_STRING: 
qpid], version=[LONG_STRING: 0.30], qpid.build=[LONG_STRING: 1624307M], 
qpid.instance_name=[LONG_STRING: Broker], 
qpid.close_when_no_route=[LONG_STRING: true], 
qpid.message_compression_supported=[LONG_STRING: true]}
2015-02-20 10:19:20 ERROR AMQProtocolEngine:342 - Frame decoding
org.apache.qpid.framing.AMQFrameDecodingException: Class 85 unknown in AMQP 
version 0-91 (while trying to decode class 85 method 10. [error code 503: 
command invalid]
        at 
org.apache.qpid.framing.amqp_0_91.MethodRegistry_0_91.convertToBody(MethodRegistry_0_91.java:172)
        at 
org.apache.qpid.framing.AMQMethodBodyFactory.createBody(AMQMethodBodyFactory.java:44)
        at org.apache.qpid.framing.AMQFrame.<init>(AMQFrame.java:45)
        at 
org.apache.qpid.framing.AMQDataBlockDecoder.createAndPopulateFrame(AMQDataBlockDecoder.java:104)
        at org.apache.qpid.codec.AMQDecoder.decodeBuffer(AMQDecoder.java:263)
        at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$2.run(AMQProtocolEngine.java:306)
        at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$2.run(AMQProtocolEngine.java:283)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:356)
        at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:282)
        at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:89)
        at 
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:133)
        at 
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:49)
        at 
org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:161)
        at java.lang.Thread.run(Thread.java:745)

  was:
I have a Rabbit client tied to a QPID broker.  There appears to be a gap in the 
support of the Qpid broker for a 0.91 compliant frame.  This occurs when the 
"<channel>.confirmSelect()" method is called.  The AMQP spec appears to 
recognize this (here is the example in GO- 
https://github.com/streadway/amqp/blob/master/spec091.go) 

2015-02-20 10:19:20,499 [] [] DEBUG 
org.apache.qpid.framing.FieldTable:writeToBuffer - FieldTable::writeToBuffer: 
Writing encoded length of 166...
2015-02-20 10:19:20,499 [] [] DEBUG 
org.apache.qpid.framing.FieldTable:writeToBuffer - {product=[LONG_STRING: 
qpid], version=[LONG_STRING: 0.30], qpid.build=[LONG_STRING: 1624307M], 
qpid.instance_name=[LONG_STRING: Broker], 
qpid.close_when_no_route=[LONG_STRING: true], 
qpid.message_compression_supported=[LONG_STRING: true]}
2015-02-20 10:19:20 ERROR AMQProtocolEngine:342 - Frame decoding
org.apache.qpid.framing.AMQFrameDecodingException: Class 85 unknown in AMQP 
version 0-91 (while trying to decode class 85 method 10. [error code 503: 
command invalid]
        at 
org.apache.qpid.framing.amqp_0_91.MethodRegistry_0_91.convertToBody(MethodRegistry_0_91.java:172)
        at 
org.apache.qpid.framing.AMQMethodBodyFactory.createBody(AMQMethodBodyFactory.java:44)
        at org.apache.qpid.framing.AMQFrame.<init>(AMQFrame.java:45)
        at 
org.apache.qpid.framing.AMQDataBlockDecoder.createAndPopulateFrame(AMQDataBlockDecoder.java:104)
        at org.apache.qpid.codec.AMQDecoder.decodeBuffer(AMQDecoder.java:263)
        at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$2.run(AMQProtocolEngine.java:306)
        at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$2.run(AMQProtocolEngine.java:283)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:356)
        at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:282)
        at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:89)
        at 
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:133)
        at 
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:49)
        at 
org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:161)
        at java.lang.Thread.run(Thread.java:745)


> Frame 85 unknown to Qpid Broker
> -------------------------------
>
>                 Key: QPID-6403
>                 URL: https://issues.apache.org/jira/browse/QPID-6403
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: 0.30
>         Environment: Debian, Java 1.7
>            Reporter: David Robertus
>            Priority: Blocker
>
> I have a Rabbit client tied to a QPID broker.  There appears to be a gap in 
> the support of the Qpid broker for a 0.91 compliant frame.  This occurs when 
> the "<channel>.confirmSelect()" method is called.  The AMQP spec appears to 
> recognize this (here is the example in GO- 
> https://github.com/streadway/amqp/blob/master/spec091.go) .
> Here is the Rabbit oage documenting the use: 
> https://www.rabbitmq.com/confirms.html
> 2015-02-20 10:19:20,499 [] [] DEBUG 
> org.apache.qpid.framing.FieldTable:writeToBuffer - FieldTable::writeToBuffer: 
> Writing encoded length of 166...
> 2015-02-20 10:19:20,499 [] [] DEBUG 
> org.apache.qpid.framing.FieldTable:writeToBuffer - {product=[LONG_STRING: 
> qpid], version=[LONG_STRING: 0.30], qpid.build=[LONG_STRING: 1624307M], 
> qpid.instance_name=[LONG_STRING: Broker], 
> qpid.close_when_no_route=[LONG_STRING: true], 
> qpid.message_compression_supported=[LONG_STRING: true]}
> 2015-02-20 10:19:20 ERROR AMQProtocolEngine:342 - Frame decoding
> org.apache.qpid.framing.AMQFrameDecodingException: Class 85 unknown in AMQP 
> version 0-91 (while trying to decode class 85 method 10. [error code 503: 
> command invalid]
>       at 
> org.apache.qpid.framing.amqp_0_91.MethodRegistry_0_91.convertToBody(MethodRegistry_0_91.java:172)
>       at 
> org.apache.qpid.framing.AMQMethodBodyFactory.createBody(AMQMethodBodyFactory.java:44)
>       at org.apache.qpid.framing.AMQFrame.<init>(AMQFrame.java:45)
>       at 
> org.apache.qpid.framing.AMQDataBlockDecoder.createAndPopulateFrame(AMQDataBlockDecoder.java:104)
>       at org.apache.qpid.codec.AMQDecoder.decodeBuffer(AMQDecoder.java:263)
>       at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$2.run(AMQProtocolEngine.java:306)
>       at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$2.run(AMQProtocolEngine.java:283)
>       at java.security.AccessController.doPrivileged(Native Method)
>       at javax.security.auth.Subject.doAs(Subject.java:356)
>       at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:282)
>       at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:89)
>       at 
> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:133)
>       at 
> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:49)
>       at 
> org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:161)
>       at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to